Engineer how-to

Use site context before you touch the checklist.

The faster you understand the building, system scope, and known issues, the cleaner and more confident the inspection will feel on site.

Audience

Engineers preparing for the day or reviewing the next stop before arrival.

You need an assigned visit or a site you can access from Dashboard or Sites.

You know where you are going, what system you are working on, and what historical context matters.

Start on Dashboard to review upcoming work and any route-level context the office team has already assigned.
Use this screen to decide whether you can jump straight into the next inspection or whether you need more site context first.
If sync warnings or overdue items are visible, understand those before you start the next critical visit.

Open the site record from Dashboard, Inspections, or the Sites tab.
Use the site detail workspace to confirm building details, contacts, systems, and inspection history.
Review the Documents and History areas if you need to understand what happened previously at this location.

Open the site briefing if available when access notes, previous failures, or special handling requirements could affect the visit.
Check inspection history when you want to know whether a problem is recurring, newly introduced, or already under remediation.
Use this context to decide how much time the visit is likely to need and what evidence will matter most.

Problem	What to check
The site record looks incomplete	Capture what you can safely on the visit, then flag the gap back to the office team so the admin record can be improved.
You cannot tell which system is in scope	Check the assigned inspection record and the site systems list before you begin recording results.
The history does not match what you see on site	Continue the visit using the live condition in front of you and document the mismatch clearly in notes or defects.

Once you are oriented, move into the live inspection workflow.

Last updated: .