Does Wavesteam provide a structured project handover?
Yes, and the handover requirements can be contractual. Completion means the client team can use its own accounts to build, release, roll back, restore data, and resolve a common incident. Sending files is not sufficient evidence.
Wavesteam identifies the future operator at initiation rather than writing documents just before launch. A client engineering team needs architecture, pipelines, and diagnostic training. An operations-only team needs account administration, content controls, exports, and a support process. A client retaining Wavesteam for operations should still hold source, data, and critical accounts so it can change providers later.
When agreeing deliverables, handover, and ownership boundaries, also compare Can our technical team maintain the system after source-code handover?; the linked guidance adds context that should be considered in the same decision.
| Arrangement | Suitable situation | Client must receive | Acceptance action | Main risk |
|---|---|---|---|---|
| One-time documentation | Simple system and client knows the stack | Repository, documents, accounts, backups | Independent clean-environment deployment | Tacit knowledge may be missed |
| Documentation plus guided training | Multiple clients, integrations, or complex rules | Full assets and diagnostic methods | Client performs release, rollback, and incident exercise | Requires time from both teams |
| Transitional operations | Client team is not yet ready | Client owns assets while Wavesteam operates temporarily | Permissions transfer monthly and provider exits by a fixed date | No exit date creates dependency |
The inventory includes client-controlled repositories, tags, build and deployment automation, lockfiles, database migrations, backup and restore, API definitions, data dictionary, editable designs, test records, monitoring, alerts, third-party services, and renewals. Production secrets move into the client's secret environment and rotate; temporary Wavesteam identities are revoked after transition. Third-party licences and authorization status accompany included components.
An OpenAPI description can preserve requests, responses, and errors. The repository belongs to the client's organization. GitHub's repository roles illustrate differentiated access; whether the project uses GitHub, GitLab, or self-hosting, at least two client administrators should be able to manage access.
Handover proceeds through an asset and issue review, Wavesteam-led demonstrations of deployment, logs, alerts, recovery, and rollback, then role reversal with the client operating and Wavesteam observing. Finally, supplier privileges are removed and both parties record outstanding work and warranty boundaries. Video supports training but does not replace searchable, version-aligned documents.
Acceptance uses reproducible measures: time from clean environment to service, recovery point and time objectives, delivery of key alerts, independent release result, and dated resolution of open issues. At least one failed-release rollback and backup restore should be exercised. The client must also be able to inspect billing, rotate keys, and open support requests for payment, messaging, map, and other external services.
If the client lacks developers, Wavesteam can provide continuing maintenance, but management and handover are not mutually exclusive. The agreement still defines export formats, support response, documentation and version synchronization, migration assistance, termination deletion, and privilege revocation. New features remain distinct from warranty defect repair.
Our Transparent Delivery Standard describes the broader asset boundary; project-specific source, handover period, and support duties follow the contract annex.