W.A.T. Implementations Workflow
Use this page as the map for W.A.T. Implementations in Mission Control. It tells you which screen to open for each job, in what order, and which detailed guide to follow next.
Audience: Implementation consultants, project leads, and customer SMEs running a Vista implementation in Mission Control.
Where: Mission Control → W.A.T. Implementations
What each area owns
W.A.T. splits implementation work across related pages that share company, milestone, and action data (except Checklists).
| Area | What you do | Primary page |
|---|---|---|
| Guided stages | Walk the company through Onboarding → Stabilization with decisions, checklists, and progress | Implementation Playbook |
| Plan of record | Create companies; manage milestones and actions; export the plan PDF | Company Tracker |
| Scheduling views | Same actions on a calendar, timeline, or status board | Calendar, Gantt, Kanban |
| Code structures | Design and approve Vista datatype code formats for the team | Code Format Generator (also inside Playbook Code Format Design) |
| Ad hoc lists | Team or personal checklists (not company milestone/action data) | Checklist |
Company Tracker is the source of truth for milestones and actions. Calendar, Gantt, and Kanban are alternate views of that same work. The Playbook drives stage progress and can sync visibility and assignees into the tracker.
Recommended order
Use this order the first time you stand up an implementation for a company:
- Create or select the company — in Implementation Playbook or Company Tracker (Create New Company Implementation / duplicate / copy details as needed).
- Work Playbook stages in order — Onboarding → Kickoff → Code Format Design → Core Configuration → Integrations → Testing & Training → Beginning Balance Decisions → Readiness Assessment → Go-Live → Stabilization.
- Approve code formats — during Code Format Design, or anytime on Code Format Generator.
- Maintain the plan — add or edit milestones and actions in Company Tracker (or via Add Milestone / Add Action on Calendar, Gantt, or Kanban).
- Schedule and status work — use Calendar, Gantt, or Kanban for due dates and status; use Adjust Dates / Manage Milestones when the plan shifts.
- Use Checklists when needed — for team/personal task lists that are not the company W.A.T. plan.
- Export when stakeholders need a packet — single-stage Export stage PDF, or the merged package (see below).
You can open scheduling views before every Playbook stage is done. You should not treat Checklist as a substitute for company milestones and actions.
Mission Control page map
| Nav item | Route | Use it to… |
|---|---|---|
| Implementation Playbook | /missioncontrol/implementations/playbook | Select a company, work Implementation stages, export stage or package PDFs |
| Company Tracker | /missioncontrol/implementations/company-tracker | Dashboard for one company or All Companies; milestones, actions, Export Plan |
| Calendar | /missioncontrol/implementations/calendar | Month / Week / Day view of actions across selected companies |
| Gantt | /missioncontrol/implementations/gantt | Cross-company timeline (scale and Company / Milestone / Action granularity) |
| Kanban | /missioncontrol/implementations/kanban | Drag actions across status columns |
| Checklist | /missioncontrol/implementations/checklist | Create, archive, and complete team or personal checklists |
| Code Format Generator | /missioncontrol/implementations/code-format | Approve formats, examples, import/export Excel, CSV/PDF |
Playbook stages
Stages appear in the Playbook sidebar under Implementation stages (company required for most work).
| Stage | Use it to… | Guide |
|---|---|---|
| Onboarding | Company context, team roster, role coverage | Complete the Onboarding stage |
| Kickoff | Scope, owners, cadence, timeline expectations | Complete the Kickoff stage |
| Code Format Design | Durable code structure decisions before live data | Complete the Code Format Design stage |
| Core Configuration | Foundational ERP setup after design is agreed | Complete the Core Configuration stage |
| Integrations | Integration readiness, ownership, workarounds | Complete the Integrations stage |
| Testing & Training | Train users and validate future-state scenarios | Complete the Testing & Training stage |
| Beginning Balance Decisions | Conversion approach and data depth before cutover | Complete the Beginning Balance Decisions stage |
| Readiness Assessment | Explicit go / no-go with visible risk acceptance | Complete the Readiness Assessment stage |
| Go-Live | Cutover runbook, load validation, live status | Complete the Go-Live stage |
| Stabilization | Live issues, adoption, handoff to steady state | Complete the Stabilization stage |
How to select a company, move between stages, and use shared stage controls is in Run the Implementation Playbook.
PDF exports (Playbook)
Two export paths live on Implementation Playbook:
| Export | How you open it | What you get |
|---|---|---|
| Single stage | Export stage PDF (active exportable stage) | One PDF for the current company’s active stage |
| Merged package | Open Implementation Playbook package → dialog Implementation Playbook | One PDF across selected companies and stages |
In the package dialog:
- Choose Companies (Select all, Current only, or clear).
- Choose exportable Stages.
- Toggle Include Images on or off (images in or out of the merged PDF).
- Run Export merged package PDF (shows Exporting... while running).
Use the single-stage export for a quick handout. Use the merged package when stakeholders need a multi-stage (or multi-company) packet and you care whether images are included.
Company Tracker has a separate Export Plan PDF for the milestone/action plan—not the same as the Playbook package.
Guides in this set
Start with Run the Implementation Playbook if you need company selection and stage mechanics. Start with a stage guide when you are already in that stage and need the embedded work. Start with Company Tracker when the plan of record (milestones/actions) is wrong or missing.