Go live with LambdaAssetCheck
Use this checklist when the first setup path is complete and you are ready to move from pilot use into real field work — then set up the rhythm that keeps it going.
A strong launch is focused. Start with one team, site, or asset type; confirm the loop works; then expand.
Before you launch
Do one final pass through the setup, field workflow, and support path. If any item is still open, return to that stage before asking the wider team to switch from paper or spreadsheets.
Launch checklist
Organisation is ready
- Organisation settings are reviewed
- Sites and groups reflect real locations and teams
- Roles match how your people work
- Pilot users can sign in and see the right sidebar areas
Templates and assets are ready
- At least one useful template is published
- Assets or sites needed for the pilot exist
- QR labels are available where they matter
- A completed inspection can be reviewed and downloaded as a standardised PDF with the organisation logo
Field users are ready
- Install and sign-in instructions are shared
- Field users know where to find assigned inspections, work, and tasks
- Offline preparation is understood for low-signal sites
- Incident reporting paths are clear
First week
- Check whether users can sign in and find the work they expect.
- Review one submitted inspection for answer quality and evidence.
- Confirm follow-up work is assigned and moving forward.
- Confirm offline users can sync when they return to coverage.
- Collect feedback before adding the next template, site, or team.
Keep it running
Launching is the easy part. What makes the rollout stick is a schedule nobody has to chase, a number you check every week, and a clear answer when something breaks.
Put inspections on a schedule
A launch that depends on someone remembering will not survive a busy week. Set the recurrence, the window, and who it falls to.
Schedule recurring inspectionsWatch whether it is working
Build one chart you will actually look at — completion, overdue work, or the checks that fail most — and review it weekly.
Analytics quick startKnow where problems go
Field users need one answer to "it is not working". Point them at the common fixes before they fall back to paper.
Troubleshooting