A useful implement handoff names the actual assembly, its current source and the context question that remains open. Separate field descriptions, counterpart references, sample correspondence and timing notes when they come from different parties. A bundle can be small and still useful if each reference has a readable subject and clear relationship to the proposal.
Keep earlier issues as history with their scope visible. If only one shortlisted object changes, reopen that object’s correspondence rather than marking every source as newly reviewed. The atlas demonstrates independent local source states and discussion order. A noted reference here records preparation only, not a document received or a review completed.
Exporting the local record produces a NOT SENT file on the device. No message, order or provider request is transmitted. Before using a real communication route, replace fictional labels with actual identities, attach only the sources you possess and identify the next responsible reader. Missing information stays an explicit question in the handoff.
Keep these fields together
- Ordered identities
- Current references
- Context sources
- Historical issues
- Next responsible reader
Use the blank source worksheet to record actual information from the responsible provider. Fields are intentionally empty; the fictional collection does not supply a decision, current document or real project record.
Download a blank source register (CSV)