Clanker CloudA reusable starting point
Try an operations review with a workbook, brief, and task handoff.
Use this fictional operations packet to evaluate a Workspace Agent across data analysis, Office deliverables, and task handoff. Start with the brief and operating data, check a workbook and management summary, then supply a dated correction. The expected results below are authored reviewer checks; they are not observed Agent outputs or a customer case study.
Start with $20 in included credits. See usage and plans.
Download the first two files and keep the correction separate
Add the brief and operating data to a new Project. Ask for a workbook and a one-page management brief for 19–23 October 2026. Keep the later correction out of the first request so you can test a meaningful revision.
Ask for the requested native file types and inspect them. Add a short slide presentation only after the workbook and brief agree. These are deliberately small authored inputs; passing this trial does not establish performance on your own larger or messier data.
Reviewer reference for the first pass
The packet has five daily records. Blank refund data on Wednesday means the refund total for the full period is incomplete. The brief identifies an approved reporting period and a proposed staffing change; a proposal is not a commitment.
| Check | Expected from the supplied files |
|---|---|
| Tickets received | 500 across five records. |
| Tickets resolved | 470 across five records. |
| Opening and closing backlog | 40 opening; 70 calculated closing: 40 + 500 − 470. |
| Refunds | Known recorded refunds total $300; Wednesday is unknown, so the full-period total is incomplete. |
| Staffing | One extra Friday shift is proposed; approval and owner are unknown. |
Supply the second-pass correction
The 24 October correction confirms Wednesday refunds of $40 and approves the extra Friday shift with Rowan as owner for the next review cycle. The corrected full-period refund total is $340. Ticket counts and closing backlog stay unchanged.
Ask the Agent to revise the workbook, management brief, and any deck. Check that each file uses the corrected refund total and approval state. Attach the reviewed versions and a concise note to a Planner task if you are testing the handoff. Creating the task must not be treated as starting another run.
Record what you actually observed
For each check, record pass, revise, or not observed with the output filename and version. Include manual corrections and whether the actual Office files opened and rendered. A confident explanation without the saved artifact is not a pass for file creation.
If the method is useful, turn its source-checking and revision rules into a custom Agent. Keep these fictional records out of its permanent business knowledge; they are test data. Try a different packet before concluding the method generalizes.
Try it with a small example.
Sample files to try
Fictional inputs for this example. Download a file and add it to your Project to follow along.
- operations-brief.md
Fictional audience, source rules, and initial approval state.
- operating-data.csv
Five fictional daily records, including one unknown refund value.
- dated-correction.md
Second-pass input: confirmed refund and an approved staffing decision.
Copy into a Workspace Session. Opening Workspace does not send it automatically.
An illustrative result.
Fictional sample, written to show the expected structure. Your result depends on your inputs and needs review.
Authored reviewer reference, not an observed Agent output: initial tickets received 500; resolved 470; closing backlog 70. Known refunds $300 with Wednesday unknown. After the correction: complete-period refunds $340; extra Friday shift approved with Rowan as owner. Ticket totals and backlog remain unchanged.
Before you use the result.
- First pass: 500 received, 470 resolved, closing backlog 70.
- First pass: known refunds $300 with Wednesday explicitly unknown.
- First pass: extra shift remains proposed; approval and owner remain unknown.
- Second pass: full-period refunds $340 and approved shift owned by Rowan in every dependent output.
- Saved files open, layout was inspected, and the Planner handoff identifies reviewed versions.
Common questions.
Are these results from a real Agent run?
No. The files are fictional inputs and the expected results are authored reviewer checks. Run the packet yourself and record the files and behavior you actually observe.
Can I use this packet to test a custom Agent?
Yes. Keep the same acceptance criteria across candidates, withhold the second-pass correction initially, and compare saved outputs. Use a different packet before reusing the Agent for consequential work.
Sources: Office workflow · Planner handoff · Agent acceptance testing
Content reviewed against the Workspace Guide & FAQ. Features and access can depend on your account.