---
title: "Inverness"
description: "Hand over a finished online shop: what is live, what the client now owns, the everyday tasks, warranty and support. A handover template for web studios."
canonical: "https://formlio.com/templates/inverness-ecommerce-project-handover"
locale: "en"
type: "template"
lastModified: "2026-11-11"
category: "Digital & web design"
alternates:
  fr: "https://formlio.com/fr/templates/inverness-passation-de-projet-e-commerce.md"
---

# Inverness

Web Project Handover Template for Ecommerce Studios

A web project handover a studio sends at launch: what is live, what the client now owns, the four everyday tasks, warranty and support, and what comes next.

![](https://cdn.formlio.com/content/thumbnail-170.jpg)

- [Use this template](https://formlio.com/workspaces/claim?template=inverness-ecommerce-project-handover)
- [Live preview](https://formlio.com/documents/inverness-ecommerce-project-handover)

- **Categories:** [Digital & web design](https://formlio.com/templates/digital-web-design), [Handover](https://formlio.com/templates/handovers)
- **Document goal:** Hand over a finished Shopify store with clear details on live features, ownership, and next steps.
- **Blocks:** Image reveal, Scroll gradient, Split, Grid 2x2 image left, Left-aligned, Single column
- **Palette:** Soft Porcelain Background (#F6F2EF), Blush Mist Secondary (#E8DDDB), Orchid Rose Accent (#C56F8E), Deep Plum Depth (#2E1A26), Midnight Espresso Text (#140C11)

## Get more from every document

Close out a Shopify build with a handover document your client can actually use on day one. Built-in blocks cover live site results, account ownership, store management steps, and post-launch support.

### Make every page look like yours

Swap colours, fonts, and layout on the hero, showcase, and cards until the page matches your brand, no design app open.

### Stack hero to FAQ in minutes

Drop in a hero, steps, cards, or accordion, then save your tweaked versions and reuse them in your next document.

### Looks sharp on every screen

Your hero images, showcase, and step flow reflow on phone, tablet, and desktop from one design, with no extra layouts.

### See which sections hold attention

Heatmaps show where readers stall in your showcase or accordion, and replays let you watch them scroll before you follow up.

### Know the moment they open it

Get a ping when someone views, comments on, or signs your document, so you can reply while the page is still fresh.

### Build the page together, live

Your teammates edit the hero copy, steps, and cards at the same time, and you watch the changes land as they happen.

## See how every part fits

The document opens with a hand-off banner and closes with a post-launch review meeting, walking the client from what you built to who owns what. Keep, drop, or reorder anything to match your project.

### Project Handover Hero with Client Hand-Off Banner

A welcoming opening that names the client, the agency team and the handover date. It frames the project as officially complete and puts ownership with the client from the first screen.

![](https://cdn.formlio.com/content/section-f18c7c0b-b3e4-43bd-9b80-ad160a7b5133.jpg)

### Project Summary: What We Built and Why It Matters

An animated text statement that restates the brief and the core promise: a shop the client's team can run without the agency. It sets the tone and reminds stakeholders what success looks like.

![](https://cdn.formlio.com/content/section-f5998d56-47d4-440a-8438-592956e05e78.jpg)

### Live Site Showcase with Performance Results

A showcase of what went live on Shopify Plus, with the launch date and measurable gains such as 1.8s mobile page loads versus 4.1s before. It backs up the project's value with concrete proof.

![](https://cdn.formlio.com/content/section-04d9a04e-519c-4184-8d8d-4a911bb2e229.jpg)

### Asset and Account Ownership Checklist

Cards listing every asset, account and credential now held in the client's name. It also explains the agency's move to guest access and eventual exit, giving full clarity on ownership and control.

![](https://cdn.formlio.com/content/section-3bc62d4d-218d-40c2-9a09-5624a2f1219f.jpg)

### Step-by-Step Store Management Guide

The four most common tasks the team will perform, laid out as clear steps. Each links back to the training session and to screen recordings in a shared folder, so staff can run the store with confidence.

![](https://cdn.formlio.com/content/section-fcc6598e-22ec-45e9-b7dd-2dfb01ce1411.jpg)

### Warranty, Support Contacts and Escalation FAQ

An expandable accordion covering warranty scope and end date, support terms and who to call. It keeps the practical detail organized and easy to find when something goes wrong months later.

![](https://cdn.formlio.com/content/section-f03f2eb7-d6af-4e19-9639-dc977719855c.jpg)

### Next Steps and Post-Launch Review Meeting

A closing message confirming the independence plan and booking a complimentary review of the first two months of data. It ends the handover on reassurance and a clear next date.

![](https://cdn.formlio.com/content/section-51b70cc7-7a9c-46e8-9102-7ec11d48efca.jpg)

## Find your answers

Answers to common questions about handing over finished Shopify stores to agency clients, from ownership and access to warranty and support.

### What should be included in a project handover document?

A strong project handover document covers what was built, what is currently live, who owns each asset, how to run and maintain it, and how to get support. This template organizes those into six sections: Handover, What we made, What is live, What you own, Running it, and Support. Following this structure ensures nothing is missed when transferring a project to a client or team.

### How do I customize this handover template for my project?

Replace the placeholder text in each section with your project details, such as deliverables under 'What we made' and URLs, hosting, and credentials locations under 'What is live'. Delete any section that doesn't apply and add project-specific items like domain registrars or third-party tools. Keep entries short and specific so the client can act on them without follow-up questions.

### What should the 'What you own' section of a handover include?

List every asset the client owns after handover: source code, design files, domains, hosting accounts, content, brand assets, and third-party licenses. Note who holds the login for each and whether ownership has been formally transferred. Be clear about anything you retain, such as pre-existing tools or reusable code, to avoid disputes later.

### How do I document how to run and maintain a live project?

In the 'Running it' section, outline routine tasks like updating content, deploying changes, renewing domains and certificates, taking backups, and monitoring uptime. Include step-by-step instructions or links to guides, plus the frequency of each task. Add a short troubleshooting list for common issues so the client can resolve problems independently.

### What support details should I include after project handover?

State what support is included, for how long, and how to request it, including contact methods, response times, and business hours. Clarify what is covered, such as bug fixes, versus what is billable, like new features or content changes. Add escalation steps for urgent issues so the client knows exactly who to contact and when.

## Related

- [Ottawa](https://formlio.com/templates/ottawa-website-replatform-estimate): Professional template for your business needs
- [Kingston](https://formlio.com/templates/kingston-web-design-review-sign-off): Design review round for client sign-off
- [Victoria](https://formlio.com/templates/victoria-website-rebuild-statement-of-work): Website rebuild statement of work for clients
- [Aberdeen](https://formlio.com/templates/aberdeen-web-design-discovery-findings): Professional template for your business needs
- [Lyon](https://formlio.com/templates/lyon-hotel-website-proposal): Website proposal for multi-property hotel groups
- [Cardiff](https://formlio.com/templates/cardiff-website-care-plan-proposal): Monthly care plan proposal for festival organisers
