Customer Rollout Quickstart
Bring a new Deucalion workspace live with the right people, site data, first scheduled job, field workflow, and report review path.
Before you start
- You have an owner or admin login for the workspace.
- You know who needs office access and who needs field access.
- You have at least one real customer site ready to use as the first live test.
Expected outcome
Your team has a clean first workspace, the right users can sign in, the first site is scheduled, and everyone knows how to check field sync and review the output before sending it to a customer.
Roll out in this order
- Confirm the workspace name and the owner account.
- Invite office users and engineers before entering live work.
- Give each user the right role and field-work setting.
- Create one real customer, site, system, and asset set.
- Schedule one real job and deploy it to the engineer.
- Ask the engineer to open the app, confirm the day run, and complete the visit.
- Review sync status, inspection data, evidence, signatures, and reports before sending anything externally.
- Only then repeat the process for the rest of the estate.
Do not start with every site
Use one representative site first. A small live run is safer than importing or creating the full estate before your team has checked:
- who can sign in
- who appears in assignment lists
- whether the site structure makes sense in the field
- whether evidence and visit notes come back cleanly
- whether the final output reads correctly for your customer
First-day checklist
| Area | What good looks like |
|---|---|
| Workspace | The team can identify the correct workspace after sign-in. |
| Users | Office users and engineers have separate accounts. No shared logins are used. |
| Roles | Owners and admins can manage the workspace. Engineers can see field work but do not get office-only controls. |
| Field eligibility | Engineers who need assignments have field work enabled. Office-only users do not appear as field assignees. |
| Site data | The first site has enough customer, address, system, and asset context for an engineer to work from. |
| Scheduling | The first job is deployed, not left in draft. |
| Mobile | The engineer has signed in at least once before relying on weak-signal or offline work. |
| Output review | Reports and certificates are previewed before customer delivery. |
First-week operating rhythm
- Check sync and incomplete work at the start and end of each working day.
- Review new inspections before generating customer-facing reports.
- Keep customer, site, system, and asset names tidy so exports and reports stay readable.
- Use staged import workflows only after the team understands the first manual record.
- Capture support questions with the workspace, site, inspection, and user involved.
When to pause rollout
Pause and fix the setup before adding more work if:
- engineers cannot see deployed jobs
- office users are missing expected controls
- the site structure is confusing in the mobile app
- sync status is unclear after a visit
- reports need manual explanation before being sent
Use the smaller setup guides in this handbook to fix those issues before scaling.