Lantide Data

Back to Learning Center

Report to HTML: Weekly Meetings and Tweaks

Read time: ~7 minutes · Series: Business & Ops practice · Previous: Accept Report · Next: Annotate Plan


What to attach to the weekly meeting: Markdown or HTML?

You confirmed numbers and limitations via Report acceptance. Next question: how to attach to the meeting, email, or external deck.

Format Good for Limits
Report (Markdown) Internal metric alignment, annotation edits Still need re-layout for slides
HTML Report Open in browser, export file to share Numbers must match Report; metric changes go back to Plan

HTML Report turns the same Report into a standalone .html—layout, theme, slide mode for meetings. It does not create a second metric definition; wrong numbers need new Plan + Execute, not HTML-only fixes.


Three principles (whoever clicks Generate)

  1. Content first, presentation second — accept Report numbers and limitations before HTML; don't skip content review for "something to show."
  2. HTML changes how you tell the story, not how you calculate — titles, layout, wording OK; wrong denominator/stage/stats → new Plan → Execute.
  3. External attachments must match Report — before sharing, confirm HTML still shows stage definitions and limitations (same as Markdown Report).

The product does not require "analyst only" for HTML—anyone with project access who can open the Report tab can Generate. Both paths below are common.


Two paths (pick one or mix)

Path A: ask analyst Path B: self-serve
When No Lantide access; team policy analyst delivers You have project access; Report accepted, need meeting polish
You Specify presentation needs (table below) → receive Open / Export file On Report tab GenerateOpen / Export
Analyst Generate, Re-generate / tweak HTML if needed Re-run Plan when content wrong; help with config if unsure
sequenceDiagram
    participant Biz as Business / Ops
    participant Analyst as Analyst

    Note over Biz: Report content accepted
    alt Path A analyst generates
        Biz->>Analyst: Layout / offline requirements
        Analyst->>Analyst: Generate HTML Report
        Analyst-->>Biz: Open or Export file
    else Path B self-serve
        Biz->>Biz: Generate HTML Report
        Biz->>Biz: Open or Export
    end
    Biz->>Biz: Open in meeting or forward

You don't press Execute or know SQL; to Generate yourself, open Report tab and use HTML Report menu.


Self-serve HTML: shortest path

After Report content is OK:

  1. Open project Report tab in sidebar (Report type, not Plan).
  2. Toolbar HTML Report (globe) → Generate Report.
  3. Pick layout/style in dialog → Generate (Agent runs; wait for completion).
  4. Open Report to preview, or Export HTML Report for email attachment.
  5. Globe on sidebar Report row opens HTML later without re-Generate.

Steps and button states: USER_GUIDE §10.2–10.4. Only for Executed Reports you accept.


Before Generate: config in plain language

Whether you or the analyst operates, decide upfront:

What you need Option (plain)
"Scrollable weekly report" Layout: Standard
"Fullscreen slide-by-slide meeting" Layout: Presentation
"KPI dashboard for leadership" Style: Executive
"Meeting room may have no internet" Use CDN off (offline HTML)
"Interactive charts" Standard + Use CDN on always includes Chart.js (needs network)
"Custom interaction (such as D3)" Custom Script; confirm the risk acknowledgement, and do not combine it with Presentation
"Chinese titles + one-line executive summary" Other Requirements free text

Full options: USER_GUIDE §10.3. Config affects presentation only, not metrics in body text.


After generation: view, export, share

  • Open Report — browser preview before meeting
  • Export HTML Report — save locally (desktop) for email / upload
  • Globe shortcut — one-click from project list when HTML exists

Export is an HTML snapshot at that moment. If Report changes or you Re-generate, confirm version before external forward.


Tweaks: what you can do vs ask analyst

Change Approach You can DIY?
Titles, wording, business context Annotate Report → analyst Resolve → Re-generate Annotate yes; Re-generate either party
Colors, overall style Re-generate new Style Preset, or analyst AI style patch Yes (Re-generate); AI tweak often analyst
Typos, fixed copy Quick Edit HTML or ask analyst Quick Edit yes (USER_GUIDE §10.5.2)
Custom JavaScript tweak Ask the analyst to use patch_html_scripts; use Re-generate to change layout Ask the analyst
Full slide restructure Re-generate, not piecemeal patch Yes—align with analyst before external use
Denominator, stage, statistics New Plan → Execute Don't fix numbers only in HTML; annotate Plan

Rule: storytelling OK in HTML; calculation goes back to Plan.
AI HTML edits, Quick Edit, Re-generate boundaries: USER_GUIDE §10.5–10.5.2.


Weekly meeting tips

  1. Before: attachment is HTML from Executed Report, not Quick screenshot
  2. During: cite stage definitions and limitations verbally
  3. After: forward Export file; note analysis date and metric version
  4. Offline venue: Generate with CDN off

Pair with vs BI and meetings: BI for daily monitoring; HTML Report for this adhoc analysis sign-off packaging.


One thing to do now

After Report acceptance, try once:

  • Have access: Generate Presentation + Executive (or your combo), Open check limitations visible, Export for meeting.
  • No access: send config table to analyst; request Export file.

Next steps