Website handover at Quillary Web Studio, a fictional web agency
Handover checklist slide for closing a website build
A handover checklist slide lists what a supplier gives the client when a project closes, so both sides agree the work is finished and nothing is left with the wrong party. This one shows the five items Quillary Web Studio, a fictional web agency, hands over at the end of every website build.
What is on the slide
- Title and framing line
- Project Handover. Quillary Web Studio, five items handed to the client before a website build is closed.
- Credentials and training
- Domain, hosting and admin logins moved to the client password manager, studio access removed. One recorded 90 minute session for two client editors.
- Documentation and warranty
- A 12 page guide covering editing, forms, backups and who to call. Bugs fixed free for 60 days from launch, changes quoted separately.
- Final invoice
- Last 30% of the fee invoiced on sign off, with the warranty end date printed on it.
When this is the right slide
Pick this slide when a client project closes and both sides need to agree the five things handed over, each with a measurable promise, before the final invoice goes out.
What to swap it for
Checklist: Two Column Dense Eight. Use the two column dense layout when the closeout has eight items, such as separate lines for domain, hosting, analytics and backups, each in one short line.
What this slide shows
The title reads Project Handover, with the framing line Quillary Web Studio, five items handed to the client before a website build is closed. Five full width coloured rows stack down the slide, each with a white icon disc, a heading and one sentence. Credentials: domain, hosting and admin logins moved to the client password manager, and studio access removed. Training: one 90 minute session for two client editors, recorded so new staff can watch it later. Documentation: a 12 page guide covering page editing, forms, backups and who to call for each kind of problem. Warranty: bugs fixed free for 60 days from launch, with changes and new pages quoted separately. Final Invoice: last 30% of the fee invoiced on sign off, with the warranty end date printed on it. The icons are a key, a graduation cap, a document, a shield and a receipt. The rows run in the order the items are usually completed, ending with the invoice, which is the last thing to go out once the client is satisfied.
When this is the right slide
Use a handover checklist slide at the close of a client project, in a final meeting where both sides confirm what has been delivered, and earlier in a proposal so the client knows what to expect at the end. It suits agencies, consultants, builders and any supplier whose work becomes the client's to run. It is the wrong slide for the launch itself, which the launch checklist example covers with owners and statuses in the weeks before go live, and the wrong slide for an internal handover between staff, which needs tasks and contacts rather than invoices and warranties. For eight closeout items, the two column dense layout holds them with shorter lines. The slide also protects the relationship after the project. Clients who know exactly what the warranty covers are less likely to feel let down when a change request is quoted, and the studio is less likely to drift into months of unpaid support. Agreeing the five items in a meeting, with the slide on screen, makes the end of the project a shared decision.
How to adapt it
First, add the date each item was completed in brackets when the slide is used in the final meeting, so the client can see the handover happened in full. Second, adjust the items for other kinds of project: a fit out handover might list keys, manuals, defects list, warranty and final claim. Third, add a sixth item on a following slide for retained services, such as monthly hosting and backups, so ongoing work is clearly separate from the closed project. Keep the warranty wording exactly the same in the proposal, the slide and the signed handover document, because that is the line clients and suppliers most often read differently. Keep the slide in the proposal template so every project starts with the same promise and ends with the same checklist.
What makes this slide work
Every item has a measurable promise
One 90 minute session for two editors, a 12 page guide, bugs fixed free for 60 days, the last 30% of the fee. Each line can be checked off by the client, which is what makes a handover feel finished rather than drifting into support.
Access is moved and removed
Domain, hosting and admin logins go to the client's password manager, and the studio's access is removed. Saying both halves on the slide shows the client is in control of their own site from handover day.
The warranty draws a line
Bugs fixed free for 60 days from launch; changes and new pages quoted separately. One sentence settles the most common argument at the end of a project, and the invoice line repeats the warranty end date so both sides keep the same record.
Questions people ask
Why include the final invoice on a handover checklist?
Because payment is part of closing the project, and putting it on the same list as credentials and training makes the link clear: the last invoice goes out when the client signs off the handover. It avoids an awkward separate conversation about money and ties payment to a visible finish line.
What should a handover say about credentials?
Where the logins go and what happens to the supplier's access. Here they move to the client's password manager and the studio's access is removed. Removing access protects both sides: the client controls its own site, and the studio is not responsible for changes it did not make.
How long should a project warranty be?
Long enough for real use to show up problems, commonly 30 to 90 days for a website. This slide says 60 days from launch. More important than the length is the boundary: bugs are fixed free, while changes and new pages are quoted separately. Writing that line prevents most end of project disputes.
When should the handover checklist first be shown?
At the start of the project, in the proposal or kickoff, not only at the end. A client who knows from day one what the handover includes can plan for it, such as choosing the two staff for training. Showing it again at the end then confirms what was promised.
Should a handover checklist be signed?
Yes, the written version should be. The slide is for agreeing the list in a meeting; a short handover document with the same five items and a signature line is the record. Many agencies attach it to the final invoice, which is why the invoice line mentions the warranty end date.
How do I present a handover checklist to a client?
Go through each item and show the evidence: the password manager entry, the training recording link, the guide. Ask the client to confirm each one before moving on. End on the warranty dates and who to contact, so the client leaves knowing what happens if something breaks next month.
Build your own in about a minute
The button below opens the generator with this use case already described. Change the wording to match your own, generate, then edit anything you like.
Make one like thisOther slide examples
Launch checklist slide with an owner and status on every item
A launch checklist slide lists everything that must be true before a product goes on sale, with who owns each item and where it stands today. This one shows the Cradwell Pro standing desk, a fictional product, two weeks before its launch on Tuesday 4 May 2027, with four items done and four still open.
Mind map slide that turns a planning day into five themes
A mind map slide gathers the ideas from a brainstorm or planning session into a few themes, so a group can see everything it discussed and who will take each idea forward. This one captures the planning day of Marrowbank Landcare, a fictional volunteer group, as five themed cards, each tagged with its lead.
Safety checklist slide split into before, during and after
A safety checklist slide lists the checks a crew must make to do a risky job safely, organised so nobody can start work with a check missed. This one is the roof work toolbox talk for Ravelstone Solar, a fictional solar installer, with three checks before, three during and three after every residential install.
Want the steps in the builder? Read Style text and add callouts, stats and lists, then Present your slides with speaker notes and a pen. For everything this generator can do, see the slide maker.
Written and checked by the OneCraft team. Last checked .