The worked example: a vendor-renewal decision
The downloadable kit follows a fictional review of Vendor North. The procurement committee must renew, renegotiate, or exit. Three sources govern the package: a service agreement, a recurring-invoice export, and an incident register. The workbook calculates annual cost and service performance; the memo explains the recommendation and unresolved issues; the deck supports the decision meeting.
The example is deliberately modest. It includes three completed source rows and three facts mapped to illustrative cells, pages, and slides. It is not a set of generated Office files. Its value is showing what traceability looks like before you adapt the blank templates.
Freeze the sources before drafting
The source register records an ID, date, owner, location, relevant fields, limitation, and review status. In the example, the invoice export is accepted for the recurring charge but excludes tax and one-time adjustments. The incident register remains provisional because two classifications are unresolved. Those limitations travel with the facts derived from each source.
Record a cutoff time and, when practical, a hash or version for the packet. When sources disagree, keep both values visible and assign the decision to an accountable owner. Silent reconciliation creates a clean-looking package that nobody can audit.
Give each artifact a different job
| Artifact | Job in the Vendor North example | Primary gate |
|---|---|---|
| Workbook | Preserve invoice and incident inputs; calculate annual cost and failure rate; expose assumptions and exceptions. | Recalculate in the target spreadsheet engine, scan formula errors, and test zero or missing inputs. |
| Memo | Put the renewal decision first, explain evidence and tradeoffs, and name the unresolved contract question. | Render the pages; inspect citations, tables, page breaks, headings, and accessibility. |
| Presentation | Guide the committee through the decision, essential numbers, caveats, and requested action. | Render at presentation size; inspect clipping, contrast, hierarchy, units, and narrative order. |
Writing one block of prose and pasting it into three formats defeats the purpose. Shared facts should match; explanation density and interaction with the audience should not.
Follow one fact through the chain
Vendor North's provisional failure rate is F-002. Its source row is S-003. The transformation is “21 failed events ÷ 500 total events = 4.2%.” The workbook location is Quality!E9, the memo uses it on page 2, and the deck uses it on slide 4. The matrix keeps the row PROVISIONAL until the two incident classifications are resolved.
A cross-artifact check compares value, unit, period, denominator, and status—not only the characters “4.2.” A slide that calls it “4.2 points,” drops the reporting window, or removes the provisional label has changed the meaning even though the number looks familiar.
Build and review in a useful order
- Inventory and freeze the source packet. Stop affected claims when a governing source is missing.
- Define the few facts that must agree across all outputs. Give each an ID, source, transformation, unit, and status.
- Build the workbook first when calculations drive the decision. Keep raw inputs, calculations, and review flags separate.
- Draft the memo from accepted workbook outputs and source records. Label recommendations as judgments rather than source facts.
- Design the deck for the meeting. Keep caveats beside the claim and move supporting detail to an appendix.
- Run format-specific checks, then reconcile the fact matrix. Release only when every row passes or has an accepted exception.
Where an AI model fits
A model can inventory a large packet, propose the fact table, draft purpose-specific content, and help inspect rendered artifacts when the host provides the necessary tools. GPT-6 Astra is one candidate for a long, tool-heavy version of this work, but the workflow does not depend on Astra. The model cannot compensate for an absent spreadsheet engine, unavailable rendering, unclear source ownership, or missing approval.
Give the model the source order, artifact contract, blank templates, and completion gates. Require it to report which files were created, which were rendered or recalculated, which facts were reconciled, and what remains open. A DOCX, XLSX, or PPTX filename establishes structure only; the final gate comes from the target applications and human review.
Use the kit on your next package
Read the completed Vendor North files first, then copy the three files prefixed with blank-. The release checklist covers source integrity, formulas, document rendering, slide rendering, cross-artifact status, and delivery authorization. Keeping that small evidence system beside the final files makes later corrections much cheaper: change the governing fact, locate every downstream appearance, rerun the relevant gates, and record a new version.
