Rollout timeline
A clear path from first login to full adoption.
Each stage builds on the last, so your team is never guessing what to set up or learn next.
Start by making the workspace safe and legible before day-to-day staff begin operating inside it.
✓Confirm workspace identity, regional defaults, and the operating subscription plan before broader team rollout.
✓Review users, permissions, and notification expectations so each staff member starts with the right scope and alert posture.
✓Connect billing, integrations, and calendar surfaces that need to be available before live operations begin.
Anchor training around the actual module sequence teams will use, not isolated screens.
✓Use the dashboard first so new staff understand current activity, priorities, and exception signals.
✓Walk properties, units, leasing, maintenance, and reports in that order so portfolio context stays intact.
✓Use Help Centre, Resources, and the User Guide together so staff know where to self-serve before escalating questions.
After rollout, make guidance reusable so supervisors are not re-explaining the same flows repeatedly.
✓Share the onboarding guide download with internal operators as the default quick-start document.
✓Use FAQs for repeat questions and the User Guide for deeper orientation during shadowing and early reviews.
✓Point teams to Resources for templates, support paths, and mobile guidance once core navigation is understood.
Go-live checklist
Tick these off before your team starts operating.
A simple, repeatable list so every rollout and every new hire starts the same confident way.
✓
Access and permissions reviewedVerify each operator starts with the correct workspace role and knows which actions remain admin-only.
✓
Core workflow walkthrough completedTrain from dashboard into properties, leasing, operations, reports, and settings rather than teaching modules in isolation.
✓
Guidance surfaces sharedMake sure staff know where to find FAQs, User Guide, Onboarding & Training, and the Resources library.
✓
Support escalation path understoodConfirm when teams should self-serve, when they should ask an internal admin, and when to use support routes.