Creative and technical services · Practical guide

How to hand over a completed project

Hand over a project by matching the actual delivered files and access to the agreed scope, explaining how the client can inspect and use them, and naming any remaining work. Ask for acknowledgment only after the client has a real opportunity to inspect. Sending a link is a delivery step; it does not by itself confirm that everything is accessible or accepted.

The point where work gets scattered

A final message can sound complete while a file is missing, access belongs to the wrong person or the client cannot tell which export is current. A good handover makes the delivered work inspectable.

Reconcile delivery against the accepted work

Open the agreed scope and accepted changes. Build a short list of required outputs, then inspect the actual delivery against it. For a video project this may be a full-length edit, three short cuts and caption files. For a software project it may include the agreed source, setup notes and operating documentation. Do not substitute a list of intended deliverables for a check of the files that exist.

Name partial or missing items directly. If final images are delivered but editable source files were excluded, make that distinction visible. If a promised operating guide is unfinished, give its status and next decision rather than describing the whole project as complete. Keep payment status separate from the delivery checklist.

Prepare files and access for the actual recipient

Use recognizable names and a short index explaining each file’s purpose, format and version. Open representative exports to check they are usable. Verify that the recipient can access the correct folder or system through your agreed sharing method. If access has an expiry date, tell the client and discuss any longer-term need before the link expires.

Transfer administrative access through the system’s approved invitation or ownership-transfer process. Do not put passwords, private keys or recovery material in a public handover note. Explain where the client will manage their own access and who should accept the invitation. A documentation page can describe a process without containing the credentials themselves.

  • Required outputs are present and correctly named.
  • The intended recipient can open them.
  • Access instructions and any expiry are explicit.
  • Sensitive credentials use the approved secure process.

Send a handover that invites inspection

Sample wording: ‘Project V-18 delivery is ready at the agreed folder. It includes Final Film v4 in 1080p, three vertical cuts and the caption files listed in the index. These match the scope dated 2 May plus change C-01. Please open the files, check captions and confirm access by Friday if that timing works. The separate source archive was not included in this package. Reply with a filename and issue if anything needs inspection.’

Include concise use instructions where they matter, such as which export is intended for a website and which for social platforms. Do not describe ownership or usage rights more broadly than the actual terms. Where licensed materials have restrictions, point to the relevant agreed terms and supporting information.

Record the acknowledgment and support boundary

If the client reports an issue, determine whether it is a missing agreed item, an access problem, a defect or a new request. Resolve a delivery problem without recasting it as extra scope. Review genuinely new work separately. Confirm any agreed support period and the route for questions; avoid inventing ongoing maintenance obligations at handover.

Record what the client actually acknowledged, with the delivered version and any open items. For example: ‘Files opened; captions accepted; account invitation still awaiting Alex.’ Keep the final index, relevant conversation and confirmed payment records findable under the same project reference. That lets you resume a later question without treating delivery, acceptance and payment as interchangeable.

Keep the context with the conversation

Messages can help prepare a handover summary from selected project context and keep the follow-up conversation with the client. Inspect actual files in your existing delivery location. Use the confirmed payment record for payment questions, and Calendar for any reviewed training or follow-up appointment. A summary does not replace the deliverables.

Understand your Twin · See Business access and metered AI usage

The next conversation starts with context.

Keep the messages and records you choose close to the next question. Prepare useful wording with your Twin, review it, and decide what happens next.

Try a client relationship in Messages ↗

Open your own Bankeiz Messages ↗

Messages remain available without Business. Twin assistance uses confirmed access and metered AI usage. Sending, booking and payment retain their own review.