To hand over client files, give the new team a short index that shows the current files, unfinished work and the person handling each next step. Have them open the files and try one real task before you close the handover. Agree separately who will keep the collection available and when the outgoing team's access should end.
The new agency starts on Monday. You've sent a folder link, but their first reply asks which design was approved, where the editable file lives and whether the client ever answered the last question. The files arrived. The working context is still in someone's inbox.
The handover has to carry both. A small table and a short call will cover most of it.
Start with the work the new team needs to do
Ask the incoming lead what they need to pick up first. Updating a brochure needs different files from taking over a whole website. Use that first task to decide what belongs in the handover.
Agree the scope with the client and the outgoing team. Include the files they are allowed to pass on, the formats the next team needs and anything still awaiting approval. Check the agreed rights for editable artwork, stock assets and other licensed material before including it.
Keep another client's files, internal commercial discussions and unrelated working notes outside the shared collection. If an internal note contains something the new team needs, write a clean summary of that point.
Make an index that answers the first questions
For each important item, record its purpose, current location, status and next action. Link to the maintained file where possible. A folder called "Final" cannot explain whether the client approved its contents.
For example, a client moving a brochure project to a new agency could start here:
| Item | Current file or record | What the new team needs to know | Next step |
|---|---|---|---|
| Brochure copy | Copy v4, approved 18 October | Approved wording; contact details still need checking | Client lead confirms the phone number |
| Page layouts | Layout v7, working draft | Pages 1 to 6 reviewed; page 7 is awaiting a decision | Incoming designer finishes page 7 after the reply |
| Editable artwork | Source package linked in the index | Open it with the agreed software; check linked assets | Incoming designer reports missing links |
| Brand rules | Current brand guide | Use the listed colors and type styles | New team follows it for remaining pages |
| Open questions | Handover questions sheet | Two client replies are outstanding | Client lead replies by the agreed date |
These are example records. Replace them with your project's actual files and decisions. Keep a dated copy of the handover index so everyone can see what was passed across at that point. Keep later working files in their maintained location and record subsequent changes separately.
Give unfinished work a person and a next step
"Waiting for feedback" leaves too much for the new team to reconstruct. Write down the question, who can answer it, what depends on the reply and when it is needed.
For the brochure, that could read:
Page 7 uses the provisional service list. The client lead will confirm the list by Thursday. The incoming designer can then finish the layout and send the review PDF.
The outgoing team can explain past choices, while the incoming team takes responsibility for future work. Agree that change explicitly. Atlassian's roles and responsibilities exercise gives both teams a structured way to talk through gaps and overlapping duties. A job title alone rarely answers every handover question.
Keep contact details for whoever can resolve each open item. Leave passwords and recovery codes out of the index. Use the service's access controls or your agreed process for sharing credentials.
Check who will keep the files available
Decide where the maintained project files will live after the outgoing agency stops work. Name the person who manages that location, who pays for it and who can change access. If those are different people, record all three.
Opening a shared link and taking over ownership are separate steps. Google Drive, for example, limits work or school ownership transfers to people in the same organization. Transferring a folder also does not transfer ownership of every file inside it. Check the specific service before promising a simple transfer to another company. Google's ownership-transfer guidance.
If files need to move, agree the destination and verify the copies there. Check file formats, supporting assets and links again after the move. Record anything that will remain with the outgoing team and how it can be requested later.
In Aurora, a library can hold the maintained project documents, with a room for the client and another for the incoming agency. Choose the files each room includes. Shared files stay connected to the same library document, so replacing that document updates what both rooms show when participants reopen or refresh it. Groups can refine access within a room when colleagues need different selections.
The rooms share the handover pack. It does not transfer ownership of the client's website, design-tool account or other external services. Keep those access changes on the same checklist and complete them in the services concerned.
Let the new team try the first task
Before the handover call ends, ask the incoming colleague to use their own account and:
- Open the index and find the approved copy and current layout.
- Open or download the editable package, if their work requires it and sharing is permitted.
- Check that the package opens in the agreed software with its required assets.
- Explain the next action for page 7 and who supplies the missing answer.
If they cannot finish a check, leave that item open with a named person to fix it. You can still hand over the parts that work. Record the remaining gaps and the agreed follow-up date instead of calling the whole pack complete.
This is a practical check of whether the new team can continue. It does not replace the client's approval of the work or settle any commercial sign-off.
Close access at the agreed time
Once the incoming team has the required files and working access, review the outgoing team's permissions. Remove access they no longer need, including any separate groups, shared links and external service accounts covered by the handover. Keep any agreed support access limited to its purpose and end date.
Changing online access does not erase copies already downloaded. Agree how retained copies will be handled as part of the project's existing arrangements. The guide on download permissions for outside reviewers explains that choice in more detail.
Save a short completion note: who checked the handover, when, what worked and what remains open. The free worksheet below gives you space for the file index, unfinished work, access changes and that final note.
To try the sharing setup in Aurora, use three harmless sample PDFs: a project summary, a client review copy and an agency handover note. Start with one library and two rooms, then check that the client and agency each receive the selection you chose. The 30-day free trial includes one organization, unlimited libraries, two rooms, three internal users, 25 external users and 10 GB, with no card required.
Client project handover worksheet
Free to use and adapt. Keep your completed worksheet in your own project files.
Download Worksheet (.md)Use this sheet with the person handing over the work and the person taking it on. Link to files and access-management locations. Keep passwords and recovery codes elsewhere.
Agree the handover
| Detail | Your answer |
|---|---|
| Client and project | |
| First task the incoming team must complete | |
| Outgoing contact | |
| Incoming contact | |
| Client contact who can approve decisions | |
| Handover date and timezone | |
| Maintained file location | |
| Person who manages that location | |
| Person who pays for it | |
| Person who can change access |
List the files needed for the first task
Use one row per item. Check permission to pass it on, including editable or licensed material.
| Item and purpose | Current file/link and version | Status or approval record | Allowed to share? | Incoming team opened it? | Problem and person fixing it |
|---|---|---|---|---|---|
Keep a dated copy of this handover index. Record later working revisions separately so the original handover remains understandable.
Carry unfinished work forward
| Question or unfinished task | What depends on it | Person who answers or acts | Next step | Agreed date | Result |
|---|---|---|---|---|---|
Example: confirm service list; page 7 layout waits; client lead answers; incoming designer finishes layout; Thursday; reply still pending.
Check file and account access separately
Record the account or service name and its administrator contact, never its secret credentials. Giving access to a document does not transfer an external account.
| Location or service | Incoming person's access needed | Who makes the change | How access was checked | Outgoing access ends or is reviewed |
|---|---|---|---|---|
| Shared project files | ||||
| Design or project tool | ||||
| Other agreed service |
If files move between services, check the destination copies, formats, supporting assets and links. Record retained copies under the project's agreed arrangements.
Try one task together
| Check | Result and any open action |
|---|---|
| Incoming person finds the approved file using their own account | |
| Incoming person opens the editable material and supporting assets where needed | |
| Incoming person can explain and start the next task | |
| Missing answer has a named contact and follow-up date | |
| Outgoing access has been reviewed at the agreed time |
Record the handover
Checked by:
Date, time and timezone:
Files and access that worked:
Items still open, person handling each and follow-up date:
Location of this dated handover copy:
This completion note records the practical handover. Keep project approval and commercial sign-off in their agreed records.
Read the client file handover guide and the download-permissions guide.
