06 · Deployment & Handover¶
The approved build is published to production, validated across devices, and transferred to the client. Deployment is only initiated after final approval is confirmed.
What Happens at This Stage¶
Production Deployment
The site is published to GitHub Pages or the agreed static host.
Domain & HTTPS Setup
Custom domain configuration and HTTPS validation, if included in the project scope.
Final Validation
Navigation, responsiveness, and performance checked across mobile and desktop before handover.
Ownership Transfer
Repository access or source files transferred upon payment confirmation.
What You Receive¶
Live URL
Your production-ready website at the agreed domain or GitHub Pages address.
Repository Access or Source Files
Full access to your site files as agreed during intake.
Update Guidance
Documentation covering how to edit and maintain your content going forward.
Finalization Conditions¶
Handover requires both conditions to be met:
- Final approval, all included revision rounds completed and client sign-off confirmed
- Payment confirmation, full payment received before repository access or source files are transferred
After Handover¶
The client assumes full responsibility for ongoing content updates unless a maintenance add-on was agreed in writing. Hosting platform limitations and third-party service policies fall outside Blueprint's control after handover.
Timeline¶
| Tier | Typical Duration |
|---|---|
| Tier 1 – Personal Presence | 1 working day |
| Tier 2 – Project Documentation | 1 working day |
| Tier 3 – Research Documentation | 1–2 working days |
The approved build is published to production, validated across devices, and transferred to the client. Deployment is only initiated after final approval is confirmed.