Save file outputs in the appropriate Storage folder, link them to the task, identify the canonical deliverable and verify reader access. Use Company Brain for reusable rules and a View for the current summary; neither replaces the original file or its task evidence.
Define the deliverable before execution
For a client analysis, specify the expected file type, reporting period, required source links and where the final result should live. “Analyze the data” leaves the worker to guess whether you want a chat summary, spreadsheet or downloadable report.
Put acceptance criteria on the task. If someone else will use the file, ask what they need to reproduce a figure or understand a caveat. A clear brief reduces the revisions caused by a correct analysis delivered in the wrong form.
Choose a stable folder and name
Use a client/project folder that readers can recognize and the worker is permitted to use. Name the output with its purpose and period, rather than relying on a timestamp that only the author understands.
EmperorClaw Storage provides real folders and artifact records. Search helps retrieval, but a consistent filing rule helps both people and agents. Put that reusable rule in Company Brain and link an approved example.
Link the file to the task story
The task should point to the produced file, the input sources and the result summary. Note any unverified sections or missing data. Do not leave the only link in an agent’s temporary terminal output.
For a multi-step workflow, keep the research evidence and final deliverable distinguishable. A reviewer should be able to open the final report and follow a source link back to the relevant work, rather than guessing which intermediate file was accepted.
Make the final version unambiguous
Use the product’s canonical/version information and a clear handoff note to identify the accepted deliverable. Avoid several unrelated uploads all called “final.” If a revision changes the result, connect it to the same work record and explain what changed.
Native Office editing and file previews can help review supported formats, but always verify the saved output rather than assuming a preview proves every formula, layout or external link is correct. Use the editor and file tools appropriate to the format.
Test the reader, not just the author
- Open the file as the intended reviewer.
- Confirm their client and project access is correct.
- Check a restricted identity cannot find another client’s file.
- Verify links in the task resolve to the intended version.
- Review the external delivery request separately if the file will be sent out.
An accessible file in Emperor does not automatically grant access to a separate Google Drive account or other external copy. Keep those permissions visible in the delivery process.
Understand optional mirroring
Google Drive mirroring is an optional configuration, not the default storage engine. Decide which copy is authoritative and how your configured workflow handles updates and conflicts. Test with a harmless file before using client deliverables.
Do not solve a retrieval problem by asking the agent for backing storage credentials. Use the documented Storage surface and keep provider secrets in the supported configuration. A shared View can summarize file status, while the actual deliverable remains in Storage.
Accept one file from another person’s perspective
Complete a small task, then ask a colleague to locate and inspect the final result without your chat history. If they can identify the accepted file, sources and limitations, the handoff is working. Use the Storage and Drive guide and shared knowledge workflow to make the practice repeatable.