An audit conducted years after closure most commonly requires archived documentation because auditors typically need the full evidence trail of what was approved, executed, delivered, and controlled (plans, baselines, change logs, issue logs, risk registers, approvals, communications, testing evidence, acceptance/sign-off, financials, etc.). CompTIA Project+ explicitly lists “Archiving documentation” as a key project closing activity, and the CompTIA certification page also highlights project closing as including archiving documentation.

While signed contracts (A) can be part of that evidence set, they are only one subset of what an audit may request. A project closeout report (C) is useful as a summary, but auditors often need the underlying artifacts that support the report’s claims. Lessons learned (D) may be reviewed for process maturity, but it’s not usually the primary evidence package for compliance, financial, or governance verification.

Because the scenario emphasizes the long time gap (“years after”), archiving is the key: it ensures records are retained, retrievable, and complete for governance, compliance, and validation needs well beyond the project’s end date.