Quick answer
Quick answer
Workflow overview
Weak onboarding poisons every downstream workflow—dispatch sends wrong tech, PM attaches to the wrong record, renewals become arguments.
Treat onboarding as a short project with a checklist, not a side task.
Visual workflow steps
Ordered phases your team can operationalize as SOPs, dispatch rules, and automation triggers.
Step 1
Create durable identity
Model, serial, location, install context.
Merge policy for duplicates before go-live.
Step 2
Baseline media
Photos, nameplates, access paths.
Store once; reference forever.
Step 3
Warranty + vendor artifacts
Registration, coverage windows, vendor contacts.
Link labor/parts coverage explicitly.
Step 4
Attach PM template
Correct family for asset class and contract.
Avoid default generic PM for specialized assets.
Step 5
First-visit plan
Schedule baseline inspection if required.
Capture measurements that future visits compare against.
Operational objectives
- Duplicate rate stays low
- Renewals cite clean history early
- Dispatch carries correct asset context
Recommended KPIs
Duplicate asset merges / month
Spikes indicate intake or import issues.
Time-to-first PM scheduled
Long delays often predict early-life failures and warranty gaps.
Role responsibilities
Ops admin
Owns naming, merge rules, and import hygiene.
Technician
Owns serial capture discipline and baseline completeness.
Sales
Aligns sold scope to enumerated assets when contracts demand it.
Automation opportunities
- Duplicate warnings on similar serial/model at same site.
- Template suggestion based on model class.
- Missing baseline field blocks scheduling until resolved (policy-gated).
Common failure points
Nickname-only records
They break enterprise reporting and audits.
Skipping baseline photos
Damage and warranty disputes become unsolvable.
Related Equipify features
Related SOPs (Help Center)
Implementation checklist
- Minimum viable asset fieldsPublish and enforce in onboarding UI.
- Photo standardsAngles and naming—10 minutes training saves weeks later.
FAQ
- Who owns merges?
- Ops admin with audit notes—never silent deletes.
