Record usable access, not just file names
| Asset | Location or owner | Receiving test | Example status |
|---|---|---|---|
| Source and release tag | Company repository | Receiver can inspect the delivered version | Access verified |
| Deployment procedure | Operations runbook | Receiver rehearses in isolated environment | Rehearsal pending |
| Service accounts | Named account owner; secret store reference | Owner can rotate access without pasted passwords | Ownership clarification needed |
| Backup and recovery | Backup policy and drill record | A restore has been verified | Evidence received |
| Third-party licences | Licence register | Receiver knows restrictions and renewals | Review pending |
Close gaps with a practical rehearsal
Ask a receiving colleague who did not write the procedure to run a harmless test deployment and recover a synthetic record. Note every undocumented dependency. Do not copy secret values into this CSV; record the controlled store and the authorised owner.
Technical access and contractual rights are separate questions. The register helps identify missing evidence; it does not establish ownership of code, licence transfer rights or warranty terms. Resolve those against the agreed documents before accepting the handover.