Project Handover Document
Project | [Customer Self-Service Portal, phase 1] |
Handed over by | [Name, Project Manager] |
Received by | [Name, IT Service Owner, Digital Channels] |
Sponsor | [Name, Director of Customer Experience] |
Go-live date | [8 March 2027] |
Hypercare ends | [9 April 2027] |
Handover date | [12 April 2027] |
1. Project summary
[The portal lets customers view bills, make payments, update details and raise service requests online. Phase 1 went live to all 180,000 customers on 8 March 2027. In the first four weeks 41,000 customers registered and 22% of service requests moved from the contact centre to the portal.]
2. Scope delivered
Feature | Status | Notes |
|---|---|---|
[Registration and login with multi-factor authentication] | [Delivered] | |
[View and download bills (24 months)] | [Delivered] | |
[Card and direct debit payments] | [Delivered] | [Via payment provider; PCI scope held by provider] |
[Update contact details] | [Delivered] | |
[Raise and track service requests] | [Delivered] | [Integrated with CRM] |
[Meter reading submission] | [Delivered with known issue] | [See KI-03] |
3. Outstanding items
Item | Reason | Owner after handover | Target date |
|---|---|---|---|
[Welsh-language version] | [Translation late from supplier] | [Digital Product Owner] | [31 May 2027] |
[Accessibility retest of payment pages] | [Provider fix due] | [IT Service Owner] | [30 Apr 2027] |
[Moving-home journey] | [Deferred to phase 2 by steering group] | [Phase 2 project] | [Q3 2027] |
4. Deliverables and where to find them
Deliverable | Location |
|---|---|
[Solution architecture and design documents] | [Confluence > Digital > Portal > Design] |
[Source code] | [Git repository: portal-web, portal-api (main branch)] |
[Infrastructure as code] | [Git repository: portal-infra] |
[Test plans and results] | [Test management tool, project PORTAL] |
[Runbooks and operational procedures] | [Confluence > IT Operations > Runbooks > Portal] |
[Security assessment and penetration test report] | [Security SharePoint > Assessments > 2027] |
[Data protection impact assessment] | [Privacy team register, ref DPIA-2026-14] |
5. Systems, environments and access
Item | Details | Access transferred to |
|---|---|---|
[Production environment] | [Cloud subscription PROD-PORTAL, two regions] | [Platform Operations team] |
[Test and staging environments] | [Cloud subscription NONPROD-PORTAL] | [Platform Operations team] |
[Admin accounts] | [Held in the password vault, folder "Portal Prod"] | [IT Service Owner, 2 named engineers] |
[Domain and SSL certificates] | [Certificate renews automatically; expiry alert to ops mailbox] | [Network team] |
[Third-party accounts (payment provider, SMS)] | [Contracts in the vendor register] | [Vendor Manager] |
6. Support model
Level | Team | Responsibilities | Hours |
|---|---|---|---|
Level 1 | [Contact centre and IT service desk] | [Password resets, how-to questions, logging incidents] | [8:00–20:00 Mon–Sat] |
Level 2 | [Digital applications support] | [Investigation, configuration, known-error fixes] | [8:00–18:00 Mon–Fri; on-call out of hours] |
Level 3 | [Development partner under support contract] | [Code fixes and releases] | [Per contract, P1 24/7] |
Vendor | [Payment provider, SMS provider] | [Their platform incidents] | [Per contract] |
Service levels
Priority | Example | Response | Resolution |
|---|---|---|---|
P1 | [Portal down or payments failing for all customers] | [15 minutes] | [4 hours] |
P2 | [A key journey failing for some customers] | [1 hour] | [1 business day] |
P3 | [Minor defect with workaround] | [1 business day] | [Next scheduled release] |
7. Known issues and workarounds
ID | Issue | Impact | Workaround | Fix planned |
|---|---|---|---|---|
[KI-01] | [Bill PDF download slow (8–10 s) at month-end peak] | [Low] | [None needed; customers can retry] | [Caching change, release 1.3] |
[KI-02] | [Service request confirmation email sometimes delayed by up to 30 min] | [Low] | [Request shows in portal immediately] | [Email queue tuning, release 1.3] |
[KI-03] | [Meter readings with leading zeros rejected for 2 legacy meter types] | [Medium: about 600 customers] | [Contact centre enters reading manually] | [Release 1.2, 26 Apr 2027] |
8. Warranty and contracts
[Development partner warranty: defects in delivered scope fixed at no cost until [8 June 2027].]
[Support contract: [12] months from go-live, [x] days of change effort per quarter included.]
[Licences and subscriptions: listed in the software register with renewal dates and owners.]
9. Training and knowledge transfer
Session | Audience | Date | Attendees |
|---|---|---|---|
[Architecture walkthrough] | [Digital applications support] | [15 Feb 2027] | [6] |
[Runbook walkthrough and failover test] | [Platform Operations] | [22 Feb 2027] | [5] |
[Portal admin console] | [Contact centre team leaders] | [1 Mar 2027] | [18] |
[Shadowing during hypercare] | [Level 2 engineers] | [8 Mar – 9 Apr 2027] | [4] |
10. Operational information
Monitoring: [Uptime, error rate and payment success dashboards; alerts to the ops on-call rota.]
Backups: [Database backed up every 4 hours, kept 35 days; restore tested 24 Feb 2027.]
Release process: [Fortnightly releases via the change advisory board; emergency changes by the duty manager.]
Recurring tasks: [Monthly access review of admin accounts; quarterly dependency patching.]
11. Key contacts
Role | Name | Contact |
|---|---|---|
[Service owner] | [Name] | [Email, phone] |
[Product owner] | [Name] | [Email] |
[Development partner account manager] | [Name] | [Email, phone] |
[Payment provider support] | [Support desk] | [Phone, portal] |
[Project manager (until project closure)] | [Name] | [Email] |
12. Acceptance criteria
Criterion | Met? | Evidence |
|---|---|---|
[All P1 and P2 defects closed] | [Yes] | [Defect report, 9 Apr 2027] |
[Runbooks reviewed and accepted by operations] | [Yes] | [Sign-off email, 2 Apr 2027] |
[Monitoring and alerting live and tested] | [Yes] | [Alert test, 24 Feb 2027] |
[Access transferred and project accounts removed] | [Yes] | [Access review, 10 Apr 2027] |
[Support contract in place] | [Yes] | [Contract ref SC-2027-08] |
[Outstanding items have owners and dates] | [Yes] | [Section 3] |
13. Sign-off
By signing, the receiving team accepts operational responsibility for the service from the handover date.
Role | Name | Signature | Date |
|---|---|---|---|
Project Manager | [Name] | [Date] | |
IT Service Owner | [Name] | [Date] | |
Project Sponsor | [Name] | [Date] |