T43 Implementation kickoff plan
Implementation kickoff plan
The shared plan for Beacon's Clinicflow implementation: every milestone, who owns it and what needs a decision before go-live. Prepared by the Clinicflow Implementation team for Beacon's project lead, Tomas Lind, and updated weekly through go-live. Customer names, dates and figures in this template are synthetic sample data.
Sample template: the firm, people, clients and figures are fictional, and the embedded view holds synthetic sample records.
Live example from the Dashboards app, shown with Harborline Logistics's demo data.
What we are trying to achieve
Beacon is moving 240 support and delivery staff off a legacy ticketing tool. The kickoff goal is a working staging environment by Oct 9, with user import, permission audit and template rebuild complete, so production training can start the week of Oct 12.
The live implementation plan
The table below is the shared source of truth for every customer we are currently onboarding, sorted by target date. Beacon's rows are the ones to track for this plan; other customers' rows will keep moving independently.
Before you share this page with a client
This view lists implementation milestones for every customer we are onboarding, not only Beacon. Before sending this page to Tomas Lind or anyone at Beacon, switch the embed to a saved view filtered to Customer equals Beacon, or copy this page and embed that filtered view instead.
Beacon milestones at a glance
| Milestone | Workstream | Status | Owner | Target date | Note |
|---|---|---|---|---|---|
| Beacon admin enablement | Training | Leo Hart | Sep 11, 2026 | Admins can manage users and templates | |
| Beacon user import | Data | Priya Nair | Sep 21, 2026 | HR group list not delivered | |
| Historical import | Data | Priya Nair | Sep 26, 2026 | Waiting on a clean export from the legacy tool | |
| Permission audit | Configuration | Leo Hart | Oct 6, 2026 | Needs the HR group list first | |
| Beacon template rebuild | Configuration | Priya Nair | Oct 9, 2026 | Template inventory already reviewed with Tomas |
Phases
Who owns what
| Milestone | Responsible | Accountable | Consulted | Informed |
|---|---|---|---|---|
| Beacon user import | Priya Nair, Clinicflow | Priya Nair | Tomas Lind and Beacon HR | Leo Hart |
| Historical import | Priya Nair, Clinicflow | Priya Nair | Beacon legacy tool admin | Tomas Lind |
| Permission audit | Leo Hart, Clinicflow | Leo Hart | Tomas Lind | Beacon support managers |
| Template rebuild | Priya Nair, Clinicflow | Priya Nair | Beacon workflow leads | Tomas Lind |
| Training rollout | Leo Hart, Clinicflow | Leo Hart | Beacon support managers | All Beacon end users |
What is blocking us
Beacon user import is blocked
The 240-account user import needs the HR group list so accounts land in the correct groups on creation. Beacon's operations director role changed in August, and the new director has not yet signed off the group names submitted in July. We need: Tomas Lind to get written sign-off, or a revised list, by Sep 26. Impact if it slips past Sep 26: the permission audit and template rebuild both wait on this import, which pushes the Oct 9 staging milestone and puts the Nov 3 go-live at risk.
Historical import is customer-dependent
The two-year project history import needs a clean export from Beacon's legacy tool. This is scheduled but not started; it does not block staging, only the decision on whether history is visible from day one of go-live.
Kickoff checklist
We are ready to move as soon as our new operations director signs off the group list. That is the one thing on our side holding this up.
Confidence in the Nov 3 go-live
Three out of five while the user import is blocked. This moves to four once the HR group list is signed off, because every other milestone is on or ahead of schedule.
How to use this template
Duplicate this page once per customer at kickoff. Replace the values below; if a required value is missing, show Needs review rather than guessing a date or owner.
| Variable | Meaning | Required |
|---|---|---|
{{customer.name}} | Customer the implementation covers | Required |
{{customer.project_lead}} | Named contact on the customer side | Required |
{{implementation.manager}} | Vendor-side implementation owner | Required |
{{implementation.target_golive}} | Agreed go-live date | Required |
{{milestone.blocked_dependency}} | What is blocking any milestone in Blocked status, and who owns clearing it | Required when a milestone is blocked |
{{milestone.target_date}} | Target date per milestone, pulled from the tracker | Optional |
Before sharing: filter the embedded view to this customer only, and confirm every blocked or customer-action milestone names an owner and a date.