Operations and IT leads planning a rollout
Implementation guide
A typical rollout runs in four phases over six to ten weeks. Each phase has an owner, an exit condition, and a list of what your team needs to prepare.
Four phases
- 01
1. Discovery (week 1-2)
We map current workflows, data sources and integrations with your team. Exit condition: a signed configuration plan naming every workflow in scope.
- 02
2. Configuration (week 2-5)
Roles, templates, coding rules and integrations are set up in a staging environment. Exit condition: staging matches the signed plan and passes a joint review.
- 03
3. Pilot (week 5-8)
A limited group of users runs real cases in production with support on call. Exit condition: agreed volume and error thresholds are met for two consecutive weeks.
- 04
4. Go-live (week 8-10)
All users move over on a fixed date. Exit condition: the old workflow is retired and a 30-day review is scheduled.
What your team prepares
| Phase | From your side |
|---|---|
| Discovery | A named project owner and access to current workflow documentation |
| Configuration | Confirmed integration credentials and a list of role types to configure |
| Pilot | Pilot users' availability and a feedback channel checked daily |
| Go-live | Internal communication to end users and a fallback plan for the cutover date |
Support during rollout
A named implementation lead runs the four phases with you and stays reachable through the pilot. Configuration decisions are documented as they are made, not reconstructed afterward.
This page is part of a platform of 2,156 clinical and operational capabilities across 8 business domains.
Explore the catalogueContinue
A typical rollout runs in four phases over six to ten weeks. Each phase has an owner, an exit condition, and a list of what your team needs to prepare.