Most manufacturing teams rely on spreadsheets and one-off exports when they need a shared view of performance or operations. That approach breaks down when definitions drift, files multiply, and nobody knows which copy is current.
Manufacturing Reports brings curated, versioned dashboards into Threaded so your team opens the same report in the same place—scoped to your organization and updated when Threaded publishes new data or layout revisions.
#Key Concepts
Manufacturing Report A named report your organization can open from the Reports area. Each report has a title, optional description, identifying slug, and a generation timestamp so you can see when the content was produced.
Shell The interactive layout (“dashboard”) for a report. Reports can have one or more shell revisions over time; you pick which revision to view.
Data revision When a report uses separate data from the shell, Threaded keeps dated data revisions alongside shell revisions. Some reports embed data in the shell instead—those show a note that there is no separate data source.
Planning document On a draft report (no shell revisions yet), editors can keep one Markdown Planning artifact that describes charts, metrics, and SQL the dashboard should use. Planning is replaced on each upload; it is not a shell or data revision.
Report artifacts Shell HTML, SQLite databases, JSON, planning Markdown, and supporting files are stored as report library artifacts scoped to each report—not in the general Admin > Media library.
#Who can use it
Members can browse and open reports. Creating drafts, uploading artifacts, planning documents, and shell revisions require an edit role (Owner or Edit All), not view-only.
If your organization does not have Manufacturing Reports enabled yet, the Reports page explains how to get access.
#How It Works
#Opening the Reports list
Click Reports in the top navigation to open the report library—a list of available reports sorted by when they were last generated.
You will see each report’s title, description when present, slug, and Generated time. Click any row to open that report. Editors can click Add Report → Create draft to start a new report.
#Reading a report
The report viewer fills the workspace so you can focus on the dashboard. At the top you will see the report title and description.
Expand Report details when you need to:
- Choose a different Shell revision from the dropdown.
- Choose a Data revision when data is maintained separately from the shell.
- Use Open dashboard in new tab if you prefer a full browser window (for example, on a shop-floor display).
- Review attribution: who created the report and when, plus creation metadata for the shell and data revisions you have selected.
- Upload artifacts with Upload as (Data, Shell, Auxiliary, or Planning on drafts).
- Delete report appears only when your membership allows editing the organization (for example Owner or Edit All—not view-only). It removes this report from the organization.
#Working with revisions
Changing the Shell or Data selection updates the viewer and keeps your place in the URL, so you can bookmark or share a specific shell and data combination when your report supports both.
If data is embedded only in the HTML shell, you will not see a separate Data dropdown—Threaded tells you that data lives inside the shell.
On Report details, SQLite artifacts also support View to browse tables in the app. That preview is separate from AI SQL (below).
#Building and querying reports with the AI Assistant
Editors can author report content from the AI sidebar while staying on Report details. Connect Threaded MCP in the sidebar for SQL against the report database and for uploading a planning document. Shell upload from chat works in-app as part of the same authoring loop.
#Query the report database (SQL)
When a report has a SQLite Data artifact, ask the assistant to inspect schema or run read-only SELECT queries. The assistant uses Threaded’s report query tools — there is no separate SQL console in the report UI. Query results help you design charts and tables; the live dashboard re-runs SQL in the browser against the attached database when you open the shell.
Example:
“On this report, show the SQLite schema and sample rows from the main fact table.”
#Author a report with the AI sidebar
- Create a draft with Add Report → Create draft (or ask the AI to create one), or open an existing report to update.
- Optionally upload a SQLite file as Upload as → Data.
- Stay on Report details (or the report viewer) and use the prompt chip Workflow: Author a Report (or ask the assistant to create or update the report).
- Answer the assistant’s questions about goals, design, and report elements.
- Review the planning document; the assistant uploads it as the Planning artifact, then scaffolds or revises the HTML shell and updates the plan with as-built notes.
- Open Artifacts → Planning → View to read the plan anytime.
Planning documents can be uploaded or replaced on drafts and after shell revisions exist (one planning artifact per report). You can still upload a shell manually with Upload as → Shell, then Finalize report when you are ready.
Example:
“Create a production KPI report from this SQLite data and upload the shell.”
“Update this report shell to add a filter by site and refresh the planning doc.”
For more example prompts, see AI Assistant Use Cases. For connecting MCP, see Connecting Threaded MCP.
#Report artifacts and the CLI
Day-to-day browsing and AI-assisted authoring happen in the app. The Threaded CLI (threaded task report:*) remains available for automation and local workflows — for example uploading large files or scripting revisions outside the sidebar.
#Why This Matters
Manufacturing Reports reduces friction between “someone exported a chart” and “everyone trusts the numbers.” Versioned shells and data give you a clear audit trail of what was shown and when, while keeping navigation inside Threaded aligned with how you already work—by organization, role, and shared artifacts rather than email attachments.