Performing a Check

Performing a check means carrying out an inspection on an asset by answering the questions defined in a check template.

Starting a check

There are three ways to start a check:

Scanning the asset QR code (preferred)

1. Scan the QR code on the asset
2. The scan page shows any scheduled checks for that asset, including the template name and due date — tap one to perform it
3. Or tap Perform an Unscheduled Check to choose a template and start an ad-hoc check

When you start a check via QR scan, AssetBuddy records that the QR code was scanned and the time it was scanned. This is displayed on the completed check as QR Verified with a green tick — providing proof that the operator was physically present at the asset.

TIP

Scanning the QR code is the recommended way to perform checks. It provides verification that the operator was physically at the asset, and is the only way to perform an unscheduled check.

From the Checks page

1. Go to Checks — you'll see a list of upcoming and overdue scheduled checks
2. Click Perform on the check you want to complete

From the asset's Checks tab

1. Go to an asset's detail page and open the Checks tab
2. Click Perform on a scheduled check

Pre-use checks

A check template can be configured as a pre-use check — meaning it must be completed before using the asset each day. When you scan an asset that has a pre-use check assigned, the scan page shows the current status of today's pre-use check.

If the check hasn't been completed today

A green Start Pre-Use Check button is shown — tap it to begin the check.

If the check was completed today and passed

A green badge shows: "Pre-use check completed today" — no further action is needed.

If the check was completed today but failed

• A red message is shown indicating the check failed
• If a defect was raised, you can tap through to view the defect details
• If the defect has since been fixed and closed, a yellow message shows: "Pre-use check failed, but fixed"

Filling in responses

The check form presents each question from the template in order. For each question:

• Pass/Fail — tap Pass or Fail
• Yes/No — tap Yes or No
• Number — enter a numeric value (e.g. a measurement or reading)
• Select — choose from the available options
• Text — type a free-text response
• Photo — take or upload a photo

Adding notes

Each question has an optional notes field where you can add extra detail. Use this to explain observations, record readings, or note anything unusual.

Attaching photos

You can attach photos to individual responses as evidence. If the template has mandatory attachments enabled, you must attach at least one photo before submitting.

Signing and submitting the check

Once you've answered all questions, you must provide your signature before submitting:

1. Tap Sign & Submit after answering the last question
2. Sign on the signature pad using your finger or mouse
3. If you make a mistake, tap Clear signature and sign again
4. Tap Submit Check

Your signature is stored and displayed on the completed check as proof that you personally performed and confirmed the inspection. A signature is required — you cannot submit a check without signing.

AssetBuddy evaluates your responses against the template's pass/fail criteria and scoring model to calculate the overall result.

What happens after submission

• The check status changes to Completed
• An overall result is recorded based on the template's scoring model:
  • Pass — all requirements were met
  • Fail — one or more requirements were not met
  • Partial — some questions passed and some failed (only applies to templates using the Rated scoring model)
• If the check fails and the template has auto-defect creation enabled, a defect is raised automatically
• If the check fails, notifications are sent to H&S admins, site managers, and the asset owner
• If the template has a frequency rule, the next scheduled check is adjusted based on when this check was completed

TIP

Complete checks as close to the actual inspection as possible. The completion timestamp is used for scheduling future checks and for compliance reporting.

Required permissions

Performing checks requires the Operator role or above (the checks:perform permission).