Client Delivery Auditor

Client Delivery Auditor

Turn completed project work into a checked delivery package with clear status, instructions, and communication.

1. Reconstruct the agreed delivery scope

• Confirm the project root, delivery milestone, recipient, and intended delivery channel.
• Read the latest brief, proposal, feedback, approval notes, and existing handoff material.
• Use the latest explicit decision when it changes earlier scope.
• Do not infer pricing, rights, approval, deadlines, or included deliverables.
• Preserve exact project names, links, dates, formats, and file requirements supplied by the user.

2. Audit every promised item

Classify each deliverable as:

• present and verified: exists, opens correctly, and matches the agreed format
• present but unverified: exists but still needs an appropriate check
• partial: identifiable work remains
• missing: promised but not found
• excluded: explicitly removed from scope
• awaiting client: depends on approval, content, access, or another client action

Check filenames, formats, dimensions, variants, links, versions, accessibility needs, and usage instructions relevant to the project. Do not report the delivery as ready while required items are missing or unverified.

3. Prepare the handoff

• Use assets/client-delivery-handoff-template.md.
• Follow an existing delivery structure when one is already established.
• Include only final or intentionally shared files in the client package.
• Exclude scratch work, backups, raw prompts, logs, databases, account exports, and internal notes.
• Do not delete, rename, archive, upload, or change access permissions unless requested.
• Keep client-facing instructions separate from internal continuation notes.

4. Draft the delivery message

• Include To: only when the recipient is known and always include Subject:.
• Lead with what is complete and where the client can access it.
• Keep the message concise, warm, and easy to act on.
• State missing or follow-up items plainly.
• Offer future support as an option, not a sales push.
• Request portfolio permission only when useful and include a clear opt-out.
• Never send the message or record it as sent.

5. Separate delivery from public proof

• Name a client, show work, quote feedback, or publish outcomes only when public use is confirmed.
• Keep a public-proof brief separate from the delivery handoff.
• Generalize or omit private correspondence, unpublished metrics, implementation details, account data, and internal paths.

6. Verify and report

• Open or inspect representative deliverables rather than checking only filenames.
• Verify links, downloads, routes, dimensions, document pages, archive contents, or builds as appropriate.
• Report complete, partial, blocked, and awaiting-client items separately.
• Return the handoff location, package status, checks performed, unsent message draft, and remaining action.