Two drafts. One missing decision.
A writer finds “the first order is cheaper at 199 rupees” in an old draft. The editor has a newer script saying the second order is cheaper at 219. Both files sit in the same folder. A search result that finds both has located the disagreement without resolving it.
In this fictional teaching example, the first draft left out delivery and handling. The approved comparison uses final totals: 244 and 219 rupees, a difference of 25. The team needs that reason as well as the latest sentence.
Make the decision retrievable with its evidence.
Decision: Compare full order totals.
Evidence: First order: 199 + 35 + 10 = 244. Second order: 219 all-in. All prices are invented for the exercise.
Reason: Comparing the first item price with the second final total omits charges from only one side.
Status: Approved teaching version 2. Version 1 is superseded.
Owner: Producer. Recheck whenever the receipts or comparison premise change.
The complete editable record includes source location, approved wording, the rejected alternative and affected deliverables. In a live project, replace role placeholders with named owners and link the actual approval record.
Give different kinds of material different jobs.
Keep raw sources available for checking. Put approved decisions in a clear home and link them from the working brief. Keep reusable methods separate from facts that apply to only one project. A good interview question can travel further than a confidential guest detail.
A record should identify the source version or retrieval date, the person responsible and the next review trigger. A folder called “final” cannot explain whether advice is still current. Neither can a recent file timestamp establish that somebody approved a change.
Carry a correction to the files that use it.
If the receipt totals change, updating the decision record is only the first step. The script, graphic, captions, descriptive transcript and short adaptation may all use those numbers. The record names those dependencies so the producer can assign the affected revisions.
Retain the earlier decision as history, mark it superseded and point it to the current version. If the team uses AI search, test that a question about current guidance returns the approved record with its source and status. Include conflicting and superseded records in that test.
If sources disagree and the owner has not resolved them, mark the decision unresolved. Do not let the newest filename silently become the approved answer.
Test the handoff with someone new to the job.
Give a new editor the record and ask which order is cheaper, why the old line fails and which files need review after a correction. If they still need the original writer to explain the choice, add the missing context to the record.
Set access and reuse rules before inviting people or connecting retrieval tools. A shared search interface should preserve the underlying permission boundaries. The downloadable example is public teaching material; a real client brief may require a much narrower audience.
Questions about the method.
Do we need a new knowledge-management app?
Not necessarily. A shared document or existing workspace can hold the record if the team can find its canonical location, identify the approved version and manage access. Choose software after identifying what the handoff is missing.
What should be kept from a finished episode?
Keep the source evidence, consequential editorial decisions, approved reusable methods and relevant outcome notes. Preserve the permission and date context. Storing every draft without a current-version rule can make the next handoff harder.
Can AI search replace maintaining the records?
Search can help locate material, but someone still owns approval, corrections and access. Test retrieval with conflicting versions and verify that the answer identifies the current record and any unresolved gap.
Tell us what you want to make.
Tell us about the channel or idea, the team you have and where you need help. We’ll discuss the scope on a 30-minute call.
Book a 30-minute call rishwajeet@machinehouse.media