1. Log in and navigate
Get started as an administrator
Learn what an owner or administrator sets up in LambdaAssetCheck and in what order, so your team can inspect, report, and close work without guessing where to go.
Last updated: September 2026
What you'll need
| Tier | Any plan |
| Platform | Web app |
| Permission | Owner or Administrator. Individual stages need specific platform-management capabilities, noted on each article. |
| Where | Administration, in the sidebar |
The five stages
Work through these in order. Each one depends on the one before it — you cannot assign a person to a site that does not exist yet, and you cannot run an inspection without a published template.
| Stage | What you do | Where |
|---|---|---|
| 1. Log in and navigate | Sign in, set up two-step verification, and learn the layout. | Log in · Navigate |
| 2. Prepare your organisation | Organisation settings, billing, SSO, roles, sites, groups, then users — in that order. | Prepare your organisation |
| 3. Run your first inspection loop | Build a template, inspect against it, and watch a failed answer become tracked work. | Run your first inspection loop |
| 4. Start field work | Get inspectors onto the mobile app and working, including offline. | Get started as a field user |
| 5. Go live and keep it running | Widen beyond the pilot, then schedule and monitor. | Go live |
Users come last in stage 2 on purpose. Roles decide what a person can do, sites decide what they can see, and groups decide what work reaches them. Create those first and each new user is a single step rather than three follow-ups.
Decisions you cannot undo later
Two choices are effectively permanent. Make them deliberately before you invite anyone.
Location hierarchy is a third to think about early. It is switched on for the whole organisation, and once any site has locations recorded against it the organisation-wide setting locks. See Organisation settings.
Keep the first run small
Set up one site, one template, and a handful of users before you widen. A small first run surfaces the questions your team will actually ask — which response types you need, who should be notified, what a failed answer should trigger — while changing your mind is still cheap.
Stage 5 is where you widen, once the loop has run end to end at least once.
Related articles
Was this page helpful?
