Rounds

Operator rounds

Rounds send a team along a fixed **route** of asset stops on a repeating schedule, so the same set of assets is inspected in order, on time, every shift or every day. Rounds are built for field operations that walk the same path repeatedly — such as operator rounds in oil and gas or utilities.

Last updated: July 2026

The short version

What it is
RouteAn ordered list of asset stops at a site. Each stop is an asset paired with a template.
RoundThe recurring rule that runs a route for a group within a daily window.
Round instanceOne occurrence of a round that a team member claims and completes stop by stop.

The rounds tools live in the sidebar under Round configuration: Define routes, Define round, and Conduct rounds.

Before you start

  • Rounds is an optional module. It must be included in your plan and switched on by an administrator. If you don't see Round configuration in the sidebar, ask your administrator to enable it.
  • To create routes and rounds you need the define rounds permission.
  • To conduct rounds you need round execution access and membership of the group a round is assigned to.
  • Each site used for rounds needs its timezone set, so windows and deadlines calculate correctly.
  • You need at least one site with assets, and a published template for each asset on the route.

How rounds fit together

Route (ordered asset stops)  →  Round (frequency + window + group)  →  Round instance (a claimed, completed pass)
Touring the Round configuration area: the Inspection routes list, the Define round schedule list, and the Conduct rounds day view

Setup is two steps, then a repeating field task:

  1. Define a route once (Round configuration → Define routes).
  2. Define a round on that route (Round configuration → Define round).
  3. Operators conduct each round instance as it comes due (Round configuration → Conduct rounds).

Step 1: Define a route

A route is the ordered set of asset stops a team walks.

  1. Go to Round configuration → Define routes. The page is titled Inspection routes.
  2. Select Create route.
  3. Enter a Name and, optionally, a Code.
  4. Choose the Site (and location, if used).
  5. Add stops in order — each stop is an asset.
  6. Save the route.

The routes list shows Name, Code, Site, Location, Stops, Schedules, and Status (Active or Inactive). Use the row actions to Open, Edit, Pause, or Resume a route.

Step 2: Define a round

A round turns a route into recurring, assigned rounds.

  1. Go to Round configuration → Define round and select a route from the list.
  2. Enter a Round name.
  3. Under Inspection templates for this round, choose the published template for each asset on the route. (Each asset needs a template; when several exist for an asset type, pick the one that applies.)
  4. Choose the Assigned group — any member of that group can claim the round.
  5. Set the Frequency (for example, DAILY) and Interval.
  6. Set the Start date and, optionally, an End date.
  7. Set the Window start and Window end — the daily window each round must be completed within. Times use the site's timezone.
  8. Optionally set a Claim lead time (minutes) — how early operators may claim before the window opens (0 = at window start only).
  9. Optionally set a Completion grace value and Grace unit (Hours or Days) — extra time after the window ends before a round is marked missed (0 = none).
  10. Add a Description (optional) and select Publish round.

The round generates an instance for each occurrence, with a claim time and a completion deadline calculated from the window, lead time, and grace.

Step 3: Conduct a round

Operators complete rounds from Round configuration → Conduct rounds — "Claim and complete round instances assigned to your groups." Switch between My groups and All rounds, and use the day navigator (Previous day / Today / Next day) to find a round.

  1. Open a round that is due for the day.
  2. Claim the round so your team knows you're taking it.
  3. Work through the stops in order, completing the inspection at each one.
  4. If a stop can't be done, skip it and record a reason.
  5. Finish once every stop is completed or skipped.

A round instance records who claimed it, when it started and finished, and whether it was completed on time.

Round statuses

A round instance moves through these statuses:

StatusMeaning
PendingGenerated and waiting to be claimed.
ClaimedA team member has taken the round.
In progressStops are being completed.
CompletedAll stops finished within the deadline.
PartialFinished with some stops skipped or incomplete.
MissedThe deadline passed without completion.

Track round compliance

From Conduct rounds, open Compliance to see Round compliance for a period (Last 7 / 30 / 90 days):

  • Scheduled, Completed, On time, Completed late, and Missed (open) totals.
  • A By day breakdown of done vs missed.
  • An Action items table (Round, Route / site, Window, Status, Compliance) for following up on missed rounds.

A late finish still counts as completed but remains missed for compliance.

Frequently asked questions

What's the difference between a round and a schedule?

A schedule recurs one inspection against a single asset, asset type, or site. A round walks an ordered route of several asset stops in one pass, assigned to a group. Use rounds when the same path of assets must be checked in sequence.

Who can complete a round?

Any member of the group the round is assigned to, provided they have round execution access.

Why does a round show "Site timezone not set"?

The site the route belongs to has no timezone. Set the site's timezone so execution windows and completion deadlines calculate correctly.

Why don't I see Round configuration in my sidebar?

Rounds is an optional module. It must be included in your plan and enabled by an administrator.

Was this page helpful?

Need more help?

Top