Code audit preparation checklist
Prepare review scope, product evidence and access owners, then record findings, limitations, actions and closure tests.
Use this worksheet to prepare a scoped technical review and record its evidence. It is an input and findings register, not proof that a product has passed an audit or a complete transaction due diligence checklist.
Decision, reviewers and scope owner
Product version and system boundary
Critical journeys and review questions
Repository and access owners
Architecture, data and integrations
Build, tests and release evidence
Selected security checks and test permissions
Dependencies and component inventory
Operating and recovery evidence
Known findings and unresolved claims
Expected report and acceptance evidence
Review work, remediation and retesting
Open inputs and needed-by dates
Findings and verification register
Keep observed, suspected, not tested and closed findings distinct. Store sensitive evidence in an approved location and link to it safely.
| Baseline / finding | Evidence and limitations | Impact / next action / owner | Closure test / status |
|---|---|---|---|
Assessment review decision
For a receiving team, use the handover checklist. For a broader decision, read the technical due diligence guide. For delivery recovery, read the project rescue guide.