Creating Your First Handover Pack

What is a handover pack?

A handover pack is the structured document you send to a client at the end of a project. It combines everything they need in one place: login credentials, how-to guides, your support terms, and a sign-off form they can sign digitally. Once signed, both parties have a timestamped record that the project closed cleanly.

Before you begin

Before building your pack, make sure you have:

• All credentials ready (hosting, CMS, domain registrar, analytics)
• A list of deliverables you want to confirm with the client
• A clear idea of your post-launch support window (e.g. 30 days of bug fixes)
• Any training videos or written guides you want to include

You do not need all of this perfectly prepared before starting. Finalizo lets you save and return to a draft at any time.

Step 1: Create the project

From your dashboard, click New Project. Add the project name, link or create the client profile, choose the project type, and continue to the handover builder.

You can also start from Templates when you want Finalizo to pre-fill the pack structure:

• Web design handover: ideal for Webflow, WordPress, Framer, or custom builds
• Brand identity handover: for logo, typography, and asset delivery
• No-code / low-code handover: covers Bubble, Glide, Softr, and similar tools
• Agency delivery: multi-deliverable template with team-facing fields
• Blank pack: start with an empty structure and build from scratch

Select the template that best matches your project type. You can always add, remove, or reorder sections after selecting.

Step 2: Add project details

The first section asks for the basics: project name, linked client, delivery date, and a short scope summary. This scope summary is important because it becomes the anchor for your support boundary. Write it in plain language, describing what was built and for what purpose. A one or two sentence summary is enough.

Step 3: Fill in credentials

The credentials section is built as a structured table. For each login you add (CMS, hosting, domain, analytics, etc.) you will enter:

• Platform name
• Login URL
• Username or email
• Password
• Notes (optional)

Credentials are encrypted at rest. Client-facing packs show passwords only when the client clicks Reveal; each reveal is rate-limited, temporary, and logged. Add a pack password if you want the client to unlock the full pack before viewing any handover details.

Step 4: Set your support boundary

This is the section most freelancers skip, and the one that causes the most problems. Fill in:

• Support window: how many days of post-launch support are included (e.g. 30 days)
• What's included: bug fixes, broken links, content not displaying as signed off
• What's excluded: new features, redesigns, content additions, third-party tool errors
• Post-window rate: your hourly rate for work outside the included support period

Finalizo pre-fills sensible defaults based on the template you chose. Review and adjust them to match your standard terms.

Step 5: Add training resources

Upload or link any training materials you want to include. This can be:

• A Loom or YouTube walkthrough video link
• A written guide (paste directly or link externally)
• A link to a shared Google Drive or Dropbox folder
• A PDF of ongoing maintenance tasks

Adding even one training resource significantly reduces post-launch support requests.

Step 6: Preview and send

Use the Preview button to see exactly what your client will receive. When you are satisfied, click Send to client. Finalizo generates a clean, branded page your client can read and sign. They do not need an account.

You will receive an email notification the moment they sign.