A comprehensive guide to client handoff covering documentation, credential transfer, CMS training, support transitions, scope boundaries, and ongoing maintenance agreements.
Why Handoff Matters
Handoff quality determines ongoing support burden and client satisfaction. Research indicates that approximately 58% of freelancers experience non-payment issues, and many of these disputes arise from unclear handoff expectations. What was included? What wasn’t? Who’s responsible for what after launch?
Clean handoff protects both parties. Clients receive what they need to operate independently. Designers avoid indefinite unpaid support obligations that drain time and goodwill.
Handoff is not a moment but a process spanning final project weeks. Planning begins before development, with handoff requirements informing technical decisions. Execution requires documentation, training, and transition support. Completion requires clear boundaries that protect your time while honoring client needs.
The handoff that feels like an afterthought becomes the source of ongoing problems. The handoff planned and executed systematically becomes the foundation for satisfied clients and referrals.
Documentation Requirements
Comprehensive documentation enables client independence and reduces post-launch support requests. Every question the documentation answers is a question you don’t have to answer personally.
Content Management Procedures
Document procedures for each editable content type. How to add blog posts. How to update team member profiles. How to change homepage images. How to modify service descriptions.
Step-by-step instructions with screenshots show exact click sequences for common tasks. Write for someone who has never used the CMS before. What seems obvious after months of development isn’t obvious to someone encountering the system for the first time.
Organize procedures by task frequency. Daily tasks like blog post creation appear first. Monthly tasks like updating testimonials appear later. Annual tasks like updating copyright year appear at the end.
Technical Specifications
Technical documentation records key decisions that may need reference later.
Hosting provider information includes account details, login URL, and support contact. Document which plan the site uses and what resources are available.
Domain registrar information includes where the domain is registered, how to access DNS settings, and when renewal occurs. Missing renewal notifications cause site outages.
Third-party service integrations document each service connected to the site. Analytics account. Email marketing integration. Payment processing. Form handling. Contact information for each service.
Custom code functionality documents any custom development. What does it do? Where is it located? What would a future developer need to know to modify or maintain it?
Style Guide
Visual standards documentation prevents gradual brand drift as clients make changes over time.
Color codes with exact hex values ensure consistency. Not “blue” but “#2563EB.” Include color usage guidelines: which colors for what purposes.
Typography specifications cover fonts used, sizes for each context, and weight variations. If web fonts require licensing, document licensing requirements.
Image dimensions for various contexts help clients prepare appropriate imagery. Hero image dimensions. Thumbnail sizes. Team photo specifications.
Component usage guidelines explain when and how to use different design elements. When to use a callout box versus a standard paragraph. How to properly format a quote block.
Maintenance Procedures
Routine maintenance documentation covers tasks clients may perform or need to understand.
Plugin and theme update procedures explain how to update safely, what to test after updates, and what to do if updates break something.
Backup information documents how backups work, how frequently they occur, and how to restore if needed. Client should know their data is protected and how to access backups.
Security practices cover what the client should know about site security. Password requirements. User access management. What to do if they suspect a breach.
Performance considerations document anything affecting site speed. Image optimization requirements. Caching behavior. What might slow things down.
Documentation Format
Video walkthroughs complement written documentation for visual learners and complex procedures. Screen recordings showing exact click sequences prove more useful than written descriptions for many CMS tasks.
Record videos at reasonable resolution. Speak clearly. Pause at important moments. Keep videos focused on single tasks rather than marathon sessions covering everything.
Written guides with screenshots serve as reference during independent work. Searchable and skimmable when clients need specific answers quickly.
Store documentation in accessible format. Shared drive folder. Project management system. Dedicated client portal. Wherever it lives, the client must be able to find it without your help.
Credential Management
Secure credential transfer protects client assets and limits your liability. Sloppy credential handling creates security risks and transfer complications.
Credentials to Transfer
Complete the transfer of all access necessary for client independence.
Hosting account login provides access to server management, file access, and hosting administration.
Domain registrar access enables DNS management, domain renewal, and eventual transfer if needed.
CMS administrator credentials provide full backend access. Client needs administrator level, not limited editor role.
Third-party service accounts include analytics, email marketing, payment processing, form handling, and any other connected services.
SSL certificate management access ensures client can renew certificates when needed. Expiring SSL certificates break site security.
Social media accounts if you managed them during the project need clear transfer of access and ownership.
Transfer Method
Do not email passwords in plaintext. Email is not secure. Passwords in email can be intercepted, remain in sent folders indefinitely, and create security liability.
Use password manager sharing features. LastPass, 1Password, and similar tools enable secure credential sharing. Shared vaults can be transferred to client ownership.
Encrypted documents provide alternative when password managers aren’t available. Password-protected files with password communicated separately.
Secure transfer tools designed for credential sharing provide another option. Whatever method, prioritize security over convenience.
Document transfer completion for your records. Note when credentials were transferred and to whom. This protects you if questions arise later.
Ownership Clarity
Ensure accounts are registered to client, not your agency or personal accounts. Domains registered in your name create dependency and complicate future transitions.
Clean ownership from project start prevents transfer complications. When setting up hosting or registering domains, use client information. If client needs help, set up accounts with them on a call rather than doing it yourself with your information.
Domains and hosting in your name may seem advantageous for maintaining relationship, but ultimately creates resentment and legal complexity. The client owns their property.
Access Level Decisions
Clients need administrator access to their own systems. This seems obvious but deserves emphasis.
Retaining sole admin access creates dependency that may seem advantageous for ensuring ongoing relationship but ultimately breeds resentment and complicates transitions. If client wants to switch providers or bring work in-house, they need access to do so.
Create administrator account for client. You may retain your own administrator access during support period, but client must have independent access that persists after your involvement ends.
CMS Training
Training enables client self-sufficiency for routine content management. Well-trained clients require less support and are happier with their purchase.
Training Scope Determination
Determine what client will actually do themselves. This varies significantly by client.
Most clients need basic capabilities: blog post creation, basic page edits, image updates. They’ll update their team page when someone joins. They’ll post occasional news. They’ll swap out a hero image.
Few clients need advanced capabilities: template modifications, plugin configuration, technical optimization. Most clients shouldn’t be doing these things anyway.
Match training to realistic client involvement. Don’t train for capabilities they’ll never use. Don’t skip capabilities they’ll need.
Training Delivery
Live training sessions walk through common tasks with client observation and practice. Screen share while you demonstrate. Then watch while they do it themselves.
Multiple shorter sessions work better than single marathon. Ninety minutes maximum per session. Brain capacity for learning has limits.
Record sessions for future reference. Client can rewatch when encountering tasks after training knowledge fades. Screen recording with audio captures exactly what you showed.
Documentation Support
Video documentation covers each common task independently. Short focused videos answering specific questions: “How do I add a blog post?” not “Everything about the CMS.”
Written guides with screenshots serve as reference during independent work. When client can’t remember exactly how to do something, they can look it up without rewatching video or calling you.
Both formats serve different needs. Video shows the action. Written documentation is searchable and skimmable.
Realistic Expectations
Here’s the honest truth: clients forget training within weeks of receiving it. What seemed clear during the session becomes fuzzy when they need it two months later.
Documentation exists because training alone doesn’t stick. No matter how good your training, clients will need reference materials.
Expect questions on topics you trained thoroughly. This isn’t training failure. It’s human memory. Respond patiently and point to documentation.
Training Timing
Training should occur near launch, not weeks before. Training conducted too early fades before clients need to apply it.
Optimal timing is immediately before or after launch. Learning connects to imminent need. Client will use skills soon while memory is fresh.
If timeline requires earlier training, plan for brief refresher near launch. Even fifteen minutes reviewing key tasks helps retention.
Support Transition Phasing
Structured transition moves from intensive support to independence or maintenance relationship. The transition shouldn’t be abrupt or confusing.
Launch Period (Weeks 1-2)
Launch period requires intensive availability. Things will go wrong. Questions will arise. Client anxiety will peak.
Rapid response to issues during this period demonstrates professionalism and builds trust. If something breaks, fix it quickly.
Expect questions as client encounters real operation. Scenarios they didn’t anticipate. Situations the documentation doesn’t cover. Content types they didn’t realize they’d need.
This period often reveals documentation gaps. Take note. Update documentation for future clients.
Stabilization Period (Weeks 3-4)
Support remains available but intensity decreases. Urgent issues should be rare by now.
Questions shift from urgent issues to optimization and training reinforcement. “How do I do X?” rather than “The site is down.”
Document recurring questions for future clients. If multiple clients ask the same question, your documentation needs improvement.
Transition Point (Weeks 4-6)
Clear communication about support ending or transitioning to maintenance agreement. This conversation shouldn’t surprise the client.
Establish response time expectations. During included support, you respond within X hours. After support period, response depends on maintenance agreement or lack thereof.
Scope limitations become explicit. What’s included in remaining support. What constitutes new work requiring separate engagement.
Post-Transition
Either maintenance agreement governs ongoing relationship, or client operates independently.
Clear understanding that additional support beyond agreement constitutes new billable work. “Can you help me with X?” might be covered under maintenance or might require new proposal.
Don’t leave relationship status ambiguous. Unclear expectations create conflict.
Scope Boundaries
Clear boundaries protect both parties from scope creep and resentment. What’s included and what isn’t needs documentation before project start.
Define “Included Support”
Include support scope explicitly in contract. Not “some support” but specific terms.
Thirty days of bug fixes. Sixty days of training questions. Specific number of support hours. Whatever structure makes sense, document it in writing before project start.
Without explicit scope, client expectations may expand indefinitely. “You said you’d support us after launch” becomes unlimited obligation.
Bugs vs. Enhancements
Distinguish bugs from enhancements clearly. The distinction matters for scope.
Bug: Site doesn’t work as specified. Feature was supposed to do X but does Y. Functionality is broken.
Enhancement: Client wants something different from specification. New feature not in original scope. Change to approved design.
Bug fixes are included in post-launch support. Enhancements are new work requiring new agreement.
This distinction can create conflict. Document scope clearly to minimize disputes.
Document Exclusions
Make explicit what you won’t do. What’s excluded matters as much as what’s included.
Content creation after initial launch. You built the site; you’re not writing their blog posts forever.
Additional pages beyond original scope. The contract specified ten pages. Page eleven is new work.
New functionality not specified in contract. They want e-commerce now? That’s a new project.
Training for new staff. You trained the people employed at launch. Training their new hire is new work.
Explicit exclusions prevent expectation gaps. Client can’t claim they assumed something was included if you explicitly excluded it.
Change Request Process
Post-launch requests for work beyond handoff support get formal change request response.
Document scope of requested work. Provide cost estimate. Specify timeline impact.
Require written approval before beginning work. Verbal agreements become disputes. Written approval protects both parties.
Maintenance Agreements
Structured ongoing relationships serve clients needing continued support. Not every client wants independence. Some prefer ongoing partnership.
Technical Maintenance
Technical maintenance covers routine site operation: security updates, plugin updates, backup verification, uptime monitoring, and performance maintenance.
Typical range: $100 to $300 monthly depending on site complexity. Simple sites with few plugins cost less to maintain than complex sites with many integrations.
This level covers keeping the site running and secure, not making changes or adding content.
Support Hours
Support hours provide allocated monthly time for content updates, minor modifications, and consultation.
Typical range: $200 to $500 monthly for 2 to 5 hours of support time. Clients use this for changes they can’t or don’t want to make themselves.
Hour allocation should be explicit. What happens to unused hours? What happens if they need more? Specify in agreement.
Comprehensive Retainer
Comprehensive retainer combines technical maintenance with support hours and periodic strategic consultation.
Typical range: $500 to $1,500 monthly. Appropriate for clients who want ongoing partnership rather than just maintenance.
This level might include quarterly strategy calls, ongoing optimization, and more substantial support availability.
Agreement Structure
Maintenance agreements should specify services clearly listed with deliverables, response time commitments specifying how quickly you respond to requests, hours allocation if applicable with rollover or expiration terms, overage rates for work beyond allocation, term length and renewal process, and cancellation provisions protecting both parties.
Recurring Revenue Value
Maintenance agreements provide predictable income smoothing project-based variability. Projects end. Maintenance continues.
Building maintenance portfolio creates business stability. Ten clients at $200 monthly provides $2,000 recurring revenue. Twenty clients provides $4,000. Portfolio compounds over time.
Maintenance work is often lower stress than project work. Relationships are established. Scope is bounded. Expectations are clear.
Common Handoff Pitfalls
Recognize and avoid patterns that create handoff problems. These mistakes recur across projects and are avoidable with awareness.
Verbal Agreements Without Documentation
“I’ll help you after launch” becomes unlimited obligation without written scope. What seemed like friendly assurance becomes open-ended expectation.
Document support terms in writing. What’s included. What’s not. When support ends. Verbal agreements create disputes.
Account Ownership Confusion
Domains or hosting registered in designer’s name create dependency and complicate future transitions.
If client wants to switch providers later, they need control of their domain. If relationship ends badly, you don’t want to hold client’s domain hostage (or be accused of doing so).
Transfer ownership or establish client accounts from project start. Clean ownership prevents problems.
Training Without Documentation
Live training alone fades. You can deliver excellent training, and the client will forget most of it within weeks.
Documentation persists. Clients can reference it when memory fails. Don’t rely on training alone.
No Clear Support End Date
Open-ended support obligation invites indefinite requests. Without defined end date, support never ends.
Define when included support ends. After thirty days. After sixty days. After ten hours of support. Whatever makes sense, but define it.
Incomplete Credential Transfer
Missing any critical access creates future frustration. Client needs to make changes and can’t access necessary accounts.
Use checklist for credential transfer. Verify each item transferred. Don’t discover gaps when client needs access urgently.
Final Payment After Handoff
Here’s the leverage reality: releasing completed work before collecting final payment removes leverage for collection.
Final payment leverage disappears the moment site goes live. Client has what they wanted. Your motivation for them to pay diminishes their urgency.
Collect final payment before transferring live site. This is standard practice. Professional clients expect it.
Unrealistic Independence Expectations
Some clients cannot or will not manage their own sites regardless of training quality. They lack technical comfort, time, or interest.
Recognize when maintenance agreement is more appropriate than independence push. Forcing independence on clients who don’t want it creates dissatisfaction.
The Handoff Checklist
Systematic checklist ensures complete handoff without gaps.
Pre-Launch Preparation
Confirm documentation drafted and reviewed. Don’t wait until launch to start documentation.
Confirm training materials prepared. Videos recorded. Written guides complete.
Confirm credentials documented and ready for transfer. All accounts listed. Transfer method planned.
Confirm support scope confirmed in writing. Contract terms clear. Client expectations aligned.
Launch Period
Confirm site deployed to production. Domain pointing correctly. SSL working.
Confirm final testing completed. All functionality verified. Known issues documented.
Confirm training sessions delivered. Client completed practice exercises. Questions addressed.
Confirm documentation provided to client. Client knows how to access materials.
Transition Completion
Confirm credentials transferred via secure method. All accounts accessible. Client tested access.
Confirm training follow-up questions addressed. Client operating independently.
Confirm support period timeline confirmed. Client knows when included support ends.
Confirm maintenance agreement executed if applicable. Terms signed. Billing established.
Confirm final payment collected. Balance cleared before live site transfer.
Frequently Asked Questions
When should final payment be collected?
Before transferring the live site. Once the site is live, your leverage for collection disappears. Standard practice is final payment, then live site access.
How much documentation is enough?
Enough that clients can perform routine tasks without calling you. Common tasks should have step-by-step instructions. If you’re receiving the same questions repeatedly, your documentation is insufficient.
Should I retain access to client sites?
During support period, yes. After support ends, it depends on maintenance agreement. If no ongoing relationship, transfer all access and remove your administrator account.
What if the client breaks something?
During support period, fixing client-caused issues is gray area. Define in contract. Generally, fixing things broken by incorrect client action is reasonable during launch period but may be billable later.
How do I handle clients who can’t learn the CMS?
Some clients won’t achieve independence regardless of training quality. Recommend maintenance agreement rather than forcing independence. Better for client satisfaction and your recurring revenue.
Should I require maintenance agreements?
Not require, but offer. Many clients appreciate ongoing support option. Those who don’t want it can operate independently.
What if the client wants changes during support period?
Distinguish bug fixes from enhancements. Bugs are included. Enhancements require change order. Document the distinction in original contract to minimize disputes.
How long should included support last?
Common ranges are 30 to 60 days. Longer periods for complex sites or higher project values. Define based on what’s reasonable for the project scope.
Executing Clean Handoffs
Clean handoff is final project deliverable, not afterthought. The quality of handoff affects client satisfaction, referral likelihood, and ongoing support burden.
Start planning handoff before project begins. Include documentation and training in project scope and timeline. Don’t squeeze it into final week.
Document systematically. Written guides with screenshots. Video walkthroughs for complex tasks. Organized storage clients can access independently.
Transfer credentials securely. Use password managers or encrypted transfer. Ensure client has administrator access to their own systems.
Train appropriately to client needs. Focus on tasks they’ll actually perform. Supplement live training with reference documentation.
Transition support clearly. Define included support period. Communicate when it ends. Offer maintenance agreement for ongoing needs.
The handoff that creates satisfied clients who refer others is the handoff planned and executed with the same care as the design and development work itself.
Sources
- Non-payment statistics: DemandSage freelance statistics research (58% experiencing payment issues)
- Documentation best practices: Project management literature, web development handoff guides
- Maintenance pricing ranges: Industry surveys, agency pricing research, freelance community data
- Credential security practices: OWASP guidelines, password security best practices
- Support transition patterns: Client service literature, web agency operations research