Agency operations workshop / 5 MIN READ
Leave the client with the work they are entitled to use
Coordinate the end of an engagement around obligations, usable delivery and controlled access changes.
AI-assisted research and analysis for the SNS Creative Fieldbook
Sources checked 2026-11-06
A client exit needs a practical transition plan even when the relationship ends amicably. The agency should distinguish what must be transferred, what remains restricted and which responsibilities continue after active work stops.
What you will leave with: An exit handover register with entitled deliverables, acceptance and closure owners.
Use this when
- A client is moving work to another agency or internal team.
- A completed engagement leaves files, accounts and ongoing obligations unresolved.
This is not legal advice, permission to terminate a contract or a basis for withholding or deleting material outside the governing agreement.
Confirm the authorized end state
Australian government contract guidance notes that some obligations can continue after a contract ends. Have the appropriate commercial and legal owners confirm the actual termination or completion position before building the operational plan.
Record the agreed end date, notice, remaining work and any transition assistance. Distinguish a planned handover from an unresolved dispute. Do not assume a final invoice, an unhappy email or a lack of new requests automatically settles every obligation. Keep the transition team focused on the approved next steps rather than asking it to interpret legal rights.
Inventory deliverables and permitted recipients
List the work the client is entitled to receive and the form required for continued use. Separate final outputs, editable files, licensed third-party material, internal working notes and client-provided assets. Ownership and usage rights may differ across these categories.
Confirm the authorized recipient and whether a new agency may receive each item. A client’s request to move a folder does not necessarily cover unrelated confidential material inside it. Review the contents before transfer and use an approved method. Do not include passwords, other clients’ information or unrestricted copies of third-party assets merely to make the package look complete.
Make the handover usable and verifiable
Provide an index with current versions, relevant dependencies and any limitations the receiving team needs to understand. Explain unresolved tasks and the status of live services. Check that required files open and that the recipient can access the agreed material through their own authorized account.
Use a receipt and acceptance process suited to the agreement. Transfer of a file is different from confirmation that a continuing service has a new owner. If a required item is missing, record the gap and its resolution route. Avoid presenting a large unexplained archive as a completed transition when the client cannot identify what is current.
Close access without disrupting continuity
Agree the timing for removing agency access, changing operational ownership and ending scheduled activity. Coordinate with the client’s authorized administrators so a necessary service does not lose its owner before a replacement is ready. Do not share account credentials as a shortcut.
Apply the approved retention and disposal rules to remaining copies, keeping records that must lawfully or contractually remain. Confirm responsibility for any continuing warranty, confidentiality or support obligation. Close the register when each task has an accountable outcome, and identify unresolved matters explicitly rather than claiming the entire relationship is administratively finished.
Make the reasoning concrete.
A fictional agency ends a client engagement and prepares to send a shared project folder to the replacement supplier. The folder includes licensed templates, outdated exports and another client’s sample material.
Transfer the folder unchanged
Opening: Treat the archive as the quickest complete handover.
Hypothesis: The recipient receives a large amount of material at once.
Risk: The transfer may expose restricted files and leave the current deliverables unclear.
Build an entitled-deliverables package
Opening: Review rights, remove unrelated material and identify the current usable outputs.
Hypothesis: The client receives a clearer transition within the approved scope.
Risk: Some files may require clarification or separate permission before transfer.
The agency confirms the recipient, shares the approved package and tracks remaining access changes. It does not equate a successful upload with completion of every continuing obligation.
Take the questions into your next brief.
Use these prompts in your own notes. Nothing is submitted from this page.
End state
What completion or termination steps are actually authorized?
Entitlement
Which outputs and rights transfer to the client?
Recipient
Who may receive each category of material?
Usability
Can the receiving team identify and open the current work?
Continuity
Which access changes and obligations remain after handover?
Watch for the wrong conclusion.
- Treating every working file as freely transferable.
- Removing access before a live service has a new owner.
- Calling an unexplained archive a complete handover.
Your next action
Create an exit register for one engagement and verify the recipient, rights and usability of its most important deliverable.
Sources & scope
The workflow, worksheets and hypothetical examples are original editorial analysis. Sources support only the identified principles. No measured business results or named human reviewer are claimed.
- Australian Government business.gov.au: End a contract →Primary government business guidance · Supports: The guidance notes that some obligations continue after a contract ends; the agency exit checklist is original analysis, not legal advice.