Reports

Reports turns the data askTheodor already keeps — tasks, goals, activity, costs, compliance posture, fleet status — into clean, scoped digests you can run on demand. Pick one, run it, and read the tables and metrics. Because it’s pure local aggregation, no tokens are spent and no data leaves your machine, so you can run them as often as you like.

How to get here

Click 📈 Reports in the sidebar.

Picking and running one

The page opens to a grid of cards, each with an accent colour and a row of “draws from” chips telling you which data it aggregates before you click. The built-in set includes:

• 🌐 Workforce — last 7 days — cross-company throughput: tasks done, blocked work, top contributors.
• 🏢 Company — this week — per-Company snapshot: tasks open/done, goals advanced, routines fired.
• 📁 Project status — a burn-up: tasks done vs. open, blockers, assignees, last activity.
• 👤 Worker contribution — per-worker tasks completed, work products, and last activity.
• 🛡 Compliance posture — an auditor-friendly snapshot per Company: active framework, PII-redaction status, custom rules, and recent compliance-tagged events.
• 🛰 Fleet — machines — every paired instance: online/offline, scopes, role, and last contact.

Click a card, choose a scope if it asks for one (a specific Company, Project, or Worker), and press ▶ Run report. The output appears instantly as grouped sections of labelled rows — green, amber, or red stripes flag good, watch-this, and bad values at a glance.

No tokens, no network

Every digest is built from your local database — the same records the app already collects while you work. There’s no LLM call and nothing is sent anywhere, which is exactly why you can re-run them endlessly for free.

Sharing the output

Once a digest is on screen you can:

• 📋 Copy it to the clipboard as Markdown, or
• 💾 Save to library — files it as a branded note in the Library (scoped to the relevant Company for the team to read).

Run before a stand-up

A 30-second Company — this week or Project status run gives you a tidy, shareable digest to paste into a meeting note — no spreadsheet wrangling, no agent time, no cost.

In practice

Ask here before asking a worker. “How did we do this week?” put to a worker costs tokens, takes time, and gives you a written answer you then have to trust. The same question as a report is instant, free, and computed from the records themselves. Reach for a worker when you need judgement about the numbers — not for the numbers.

Two uses that hold up:

• A stand-up digest. Run Company — this week or Project status, hit 📋 Copy, paste into the meeting note. Thirty seconds, no spreadsheet, no agent time.
• An audit answer. Compliance posture produces a per-Company snapshot — framework, redaction status, custom rules, recent compliance-tagged events — which is a far better response to “show me your controls” than a description written from memory.

The colour stripes are the read-at-a-glance layer. Green, amber and red flag good, watch-this and bad values, so scanning a digest for what needs attention is faster than reading every row. Use them to decide where to look, then read the rows around the amber ones.

Save to library when the answer should outlive the moment. It files the digest as a note scoped to the relevant Company, which gives your team the same numbers and gives you a dated record to compare next week’s run against.

Empty output usually means the data isn’t there yet, not that the report is broken — a Project digest needs tasks, a Fleet digest needs paired machines. Because re-running is free, check again after the underlying work exists.

Terms in this page

• Report — a curated, on-demand digest over your existing data.
• Local aggregation — computing the numbers directly from your on-machine database, rather than asking an AI model.
• Token — the unit AI models bill per; these digests use none because they don’t call a model.
• Scope — the dimension a digest covers: the whole workforce, or a chosen Company, Project, or Worker.
• Section — a titled block of related rows within the output (e.g. “This week”, “Goals”).
• Burn-up — a progress view comparing completed work against the total, used in the project digest.
• Throughput — how much work got done in a period (e.g. tasks completed in the last 7 days).
• Blocker / blocked — a task that can’t proceed until something is resolved.
• Work product / artefact — a file or deliverable a worker produced.
• Goal — a tracked objective for a Company, with a status and progress percentage.
• Routine — a scheduled, recurring automation that fires on its own.
• Compliance posture — a Company’s current regulatory setup: its framework, redaction status, and rules.
• Framework — a compliance standard a Company follows (e.g. GDPR, HIPAA, SOC 2).
• PII redaction — automatically scrubbing personal data (names, emails, keys) from stored records.
• Audit event — a logged record of something that happened in the app, used for compliance and traceability.
• Fleet — your connected askTheodor machines; the fleet digest summarises their status.
• Markdown — lightweight text formatting used for the copied/saved output.