Multi-stepOperations
Turn the queue into a clear update.
Collect requests, track their status, and produce a dated report of progress and outstanding work.
A complete worked example
Give the client a clear update from the team's working queue.
The studio tracks requests in a private table. The client needs progress and decisions, without internal ownership notes or time estimates.
Fictional project and sample data. This preview does not submit, publish, or change access.
Client report · illustrative result
The launch is taking shape.
September 23 snapshot: three deliverables are ready, two are in review, and one is waiting for source material.
- Ready
- 3 deliverables
- In review
- 2 deliverables
- Waiting
- 1 photography handoff
| Milestone | Progress | Client action |
|---|---|---|
| Creative direction | Ready | Review the selected route |
| Campaign copy | In review | Confirm product names |
| Photography | Waiting | Supply originals by Oct 12 |
What this report represents
The agent compiled a dated snapshot from the authorized table. Internal notes are omitted, and private source records are not presented as client-accessible links.
What the recipient can access
The scoped progress report under the agreed client access.
Kept out of this handoff
The full request table, internal notes, and team estimates.
How it runs
- Collect the requestsCapture the relevant details and files through a form.
- Maintain the work queueUse saved views and internal tracking fields as the team works.
- Publish a snapshotAsk an agent for a dated summary with source links and clear unresolved items.
- You getA readable project report grounded in the selected records.
A prompt to start with
Copy this into your AI tool after connecting it to Fermium. Replace the bracketed details and let it ask for the context it needs.
Use [request table] to prepare a dated project report for [audience]. Summarize status, upcoming dates, and missing information. Link to source records only where readers have access, and publish the report in [folder].
What this workflow needs
The report is a snapshot, not a live dashboard. Native charts use supported scalar fields. Nested feedback needs explicit flattening before charting.
Will it refresh itself when the table changes?
No. Update it on request or configure a separate scheduled runner.