1. Agree what is required
Use one project packet for a small brochure site. Record which pages and content items are required now, and who may approve them. Keep optional and deferred items visible with an agreed decision reference.
2. Separate receipt from approval
Record the received filename or copy snapshot. An approval should identify that exact version. A file in the folder is not automatically approved, and possession of an image does not establish permitted use.
3. Reopen the record after a replacement
In the fictional example, the client sends hero-v2.jpg after approving hero-v1.jpg. The old approval stays with v1; the replacement remains REAPPROVE until the responsible person checks approval, use evidence, credit and alternative text.
4. Send a bounded handoff
The example hands over HOME-COPY v3 while the replacement hero image stays on HOLD with an owner and next date. A partial content handoff is separate from final site QA and client approval to launch.
5. Save and reopen
Use an existing AcroForm-capable PDF reader, or print and write. Copy the item sheet for each required asset and the change sheet for each replacement. Save, close and reopen to verify your reader kept the values. Fields do not expand; use short references and attached notes for long details.
Choose the right level of tooling
This offline record is for people already using their own project folders. If you need shared client uploads, reminders or live status, compare Gather and Content Snare. Those products overlap this workflow; we do not claim the packet replaces them.