AI File Outputs: What Counts as a Finished Deliverable

An AI-generated file is finished when the intended recipient can open the right version and use it for the agreed purpose. Saving a document establishes only that a file exists. It does not establish that the export contains every page, that formulas still calculate or that the recipient has access.

Use the sixteen checks below to define acceptance before requesting a deck, report or workbook. Acceptance means the evidence you require before calling the work complete. Pick the applicable rows; a plain text note should not inherit every requirement of an interactive financial workbook.

The four layers move from getting the file to using it. Several checks may apply to one defect. Record pass, fail, not applicable or unverified for each selected row; do not convert unverified into pass because the preview looks plausible.

RFC 6266 treats a download filename as advisory. That is a narrow protocol point, not a file-quality standard. Our practical inference is to open and inspect the actual artifact rather than accepting an extension as evidence of its contents.

W3C’s table guidance explains the role of header and data-cell associations. This supports a separate structural review: a table’s visible grid does not establish that its relationships survive in an accessible form.

Microsoft’s SpreadsheetML formula guide (read September 9, 2026) distinguishes formula text from the cached result of its last calculation. A preview can therefore show a value without demonstrating that the intended calculation still works. For an editable workbook, inspect the formula and change an input in a safe copy using the recipient’s spreadsheet application; check the recalculated result.

If the calculation fails, repair the formula or its dependencies and repeat the check on the replacement export. Identify that accepted revision so an older attachment is not mistaken for the tested copy.

Do the same for citations. A report’s claims cannot rely on links that remain only in the agent’s chat. The citation-check reference helps decide which source relationships must travel with the file.

A useful brief names the file type, recipient, target viewer, required editability and the decision the file supports. Add the checks that can fail silently: an appendix that must remain attached, a footnote beside a price or a chart whose labels need to remain readable when exported.

Keep acceptance proportional. A draft for discussion may need only complete content, clear caveats and a working link. A reusable template needs a check that the next person can actually edit it. A publication-ready document needs review of the final export, not just the source.

Choose the observation tool that can establish the property in question. File inspection can show contents; an application viewer can reveal clipping. The browser-versus-API reference distinguishes these observation and execution roles.

Attach a short result record: the accepted artifact and revision, checks performed, and unresolved properties. If the target viewer was unavailable, name the remaining check and its next owner.

If generation is interrupted, preserve the last complete copy separately from partial exports. Do not silently replace a usable file with a newer but incomplete one. The guide to half-finished agent outputs covers another boundary where a plausible result can conceal missing content.

Each illustrative case below is a file that looked finished in the agent’s preview and failed at the recipient. They are not observed incidents; they cover three of the table’s four layers (meaning, structure and access), and each names the row that would have caught it.

None of the four is caught by a better preview. Each is caught by inspecting the delivered copy, in the recipient’s context, for the property the task actually depends on.

Sixteen checks applied to every file would make acceptance slower than generation. The workflow section says to keep acceptance proportional, and the way to do that is to write the acceptance note as a short record before the file exists. Five lines are enough: the file type, the recipient, the viewer or application they will open it in, whether they need to edit it, and the decision the file supports. The last line does the selecting. A file that supports a budget decision needs the meaning rows, including formula recalculation; a discussion draft needs complete content and a working link.

An illustrative note for a workbook reads: spreadsheet for the finance lead, opened in the team’s spreadsheet application, must stay editable with live formulas, supports next quarter’s hiring decision. From that note the applicable rows are access, completeness of sheets, formula recalculation and a check that the chart labels survive export. Rows that do not apply to this file, such as navigation controls, are marked not applicable, with the note saying why.

The note also decides who runs which check. The agent can run everything inside its own access: open the export, change an input in a safe copy, confirm the appendix is inside the file. Properties it cannot observe, such as whether the recipient’s account can open the link or whether the file renders in a viewer the agent does not have, are reported as unverified with the person who can check them named as the next owner. That is a complete handoff; a status of done that rests on a preview is not.

Pick one deliverable your team requests often and write its five-line acceptance note today. Select the applicable rows from the table, run them on the next delivered copy rather than on the source document, and keep the result record beside the file. The first run shows which checks matter for that file type; later runs become routine.