Closing a project: delivery record and open items

Closing a project means leaving the work with someone who can use it and making the remaining work clear. Sending the final file completes delivery; it does not prove that the client has checked it, can edit it or knows who will handle the next issue. This guide provides an operational closure record, ready to copy below, that distinguishes those situations without adding an unnecessary ceremony.

Start after delivery. Preparing the proposal should already have established the deliverables and their references. Retrieve that version and the agreed changes. Do not use closure to introduce new terms or request decisions that are already documented.

A sent file is not a verified result

For each deliverable, describe what the recipient needs to be able to do. “Presentation sent” describes your action. “The recipient opens the final version and exports a copy without missing fonts” describes a test. You do not need to test every feature of an application: check the agreed use and the dependencies that might prevent it.

Asana’s project closure guide includes final checks, handover and archiving. Here we propose a smaller record for service work: deliverable, evidence, decision and next owner. This is our operational recommendation, not a certification standard.

Keep three states separate: delivered, verified and pending. If a response is missing, keep the check pending. “Received” acknowledges receipt, not necessarily acceptance of every part of the work. Identify who confirms on the client’s behalf and link the response to the specific version they reviewed.

One delivery, three different situations

Fictional example: a consultant delivers an editable presentation, a PDF and a spreadsheet feeding two charts. These are not results from a real client.

In P-01, identify the IDs and versions affected by the data in D-03, including D-01 and D-02 if they contain those charts. When the data arrives, regenerate the affected charts and files and update the index. The new versions await recipient verification: record the owner, evidence and date; the earlier check does not validate them.

Do not label the table “everything complete”. D-02 prevents the agreed use of a deliverable. D-03 may require keeping the project open or transferring the item, depending on the data’s effect and the decision made together. The apparent size of the task does not decide the distinction.

Transferring an open item requires its next owner to accept it and understand the action. Putting a name in a cell is not evidence of acceptance. If nobody takes responsibility for P-01, it remains part of the closure process and must stay visible.

Test access before removing yours

Ask the recipient to open the package through their own account and perform the agreed task. A link that works for its creator may fail for the client. Record the resource, owning account or role, result and temporary permissions to remove afterwards. Do not copy passwords into the record.

If you use Drive, one distinction matters: transferring a folder does not automatically transfer ownership of its contents. Google also restricts ownership transfers for work or school accounts to the same organisation. Check the account type and available operation before promising a transfer. Official Google Drive documentation.

If that operation is unavailable, agree on another permitted delivery method and verify the result. Do not remove access indiscriminately: an account may support other projects or an ongoing service. Assign who will review each permission and under what condition.

Make the archive useful to the next person

Prepare a short index: final version, agreed editable files, instructions, decisions and open items. Separate final material from discarded versions. Keep necessary references under the rules applicable to the work; this guide sets no universal retention period and does not propose deleting records.

A useful test is to ask the next owner to locate the deliverable and explain how to update it without consulting your private conversation. If they must ask which of four files is final, the index lacks a decision. In an agency, the recipient may be another team member as well as the client.

Copy the record and give each open item its own entry

Replace the brackets. Use D-01 for a deliverable and P-01 for an open item; these identifiers simply connect references. Add entries as needed rather than combining several issues under “final details”.

Project and agreed reference: [document and version]
Final package: [location, version and date]
D-01: [deliverable / test / evidence / state]
P-01: [missing item / consequence / next action]
Deliverables affected by P-01: [IDs / versions / new verification: owner, evidence and date]
P-01 owner: [who accepts it / confirmation]
P-01 review: [agreed date or condition]
Access: [owner / test / removal pending]
Archive: [index / editable files / instructions]
Administration: [reference / actual state / owner]
Continuity: [channel / owner / agreed coverage]
Decision: [open / closed with transferred items / closed]
Confirmation: [person / version / date; or pending]

Explain what ends and what continues

Adapt this message: “Here are package [version] and closure record [reference]. [Role] still needs to perform [check]. [Open item] continues with [owner who has accepted it]. Please confirm [specific decision]. Until then, [actual state].”

Record administration separately: invoice prepared, issued, outstanding or paid, according to evidence. Operational closure does not itself settle an obligation or prove payment. Include the time spent on this stage in your expense records; happening after delivery does not make that work disappear.

If an issue appears, link it to the deliverable and distinguish correcting agreed work from proposing new work. Do not invent support coverage while writing the record. Finish with one actionable lesson: for example, test permissions with the recipient before the next delivery, assigning an owner. Closure is resolved when decisions and responsibilities are understandable without reconstructing the whole conversation.