Review asset readiness

Asset readiness is the review page that tells you, for every machine on your shop floor, whether it is cleared to start production right now. It reads the current state of each asset's pre-use checks and turns them into a single, plain-language status you can scan in seconds.

A pre-use check is a short safety inspection an operator completes before using a machine — for example, confirming guards are in place and emergency stops work. In Bulk, an asset is any piece of equipment you track, such as a press brake, a laser cutter, or an overhead crane. When a required pre-use check for an asset is unfinished or out of date, Bulk can block production on that asset until the check passes or a supervisor authorises an exception. The Asset Readiness page is where you review that picture across the whole plant, without opening each machine one by one.

Use it at the start of a shift, before assigning work, or whenever you need to know why a machine cannot be started.

Where to find itCopy Anchor Link

Open the Safety area in the left navigation and choose Asset Readiness. The page lives at /safety/asset-readiness.

You need the audit view permission (audits.view) to load the page. That permission is granted to the Super user, Entity admin, Operator, Manager, and Tablet user roles by default, so most production-facing roles can review readiness. If you cannot see the Safety area or the page fails to load its data, ask an administrator to confirm your role includes it.

This page is a review surface: it shows readiness but does not run checks or grant overrides itself. Those actions happen elsewhere and are covered under Related guidance below.

Read the readiness overviewCopy Anchor Link

The panel at the top of the page gives you the plant-wide picture before you look at any single machine.

On the left, Readiness shows the total number of assets and a bar split into one segment per group, sized by how many assets are in it. Under each segment is its count and name:

• Blocked — assets that cannot start production.
• Override — assets running under a manager override.
• Ready — assets cleared to start production.
• No checks — assets with no pre-use checks assigned.

A group with no assets is left out of the bar. Every asset belongs to exactly one group, so the counts always add up to the total.

On the right, four figures summarise the checks themselves across every asset:

• Overdue checks — required checks that are due and not done. This figure turns red when it is above zero.
• Failed checks — checks whose most recent run failed.
• In progress — checks an operator has started but not finished.
• Last check — how long ago the most recent pre-use check was completed on any asset, for example 3 weeks ago. It reads No checks yet if no check has ever been completed.

Filter and search the listCopy Anchor Link

Below the overview, tabs let you narrow the list to one group: All, Blocked, Override, Ready, or No checks. Each tab shows how many assets are in it, and the Blocked count is highlighted when it is above zero. The tabs filter only the list; the overview always shows the whole plant.

Use Search assets in the page header to find a machine by its name, asset code, or asset type. Search works together with the tabs, so you can, for example, search for "press" while the Blocked tab is selected. If nothing matches, the page says so instead of showing an empty list.

Read the asset listCopy Anchor Link

Assets are listed in groups, in this order: Blocked, Override, Ready, then No checks. Each group has a heading that explains what it means and shows how many assets are in it. Groups with no assets are hidden.

Within each group, assets with an overdue or failed check come first, and the rest follow in alphabetical order by name. Each row shows:

• Asset — an icon that shows the most pressing reason for the asset's state (for example a failed or overdue check), the asset name, and its asset type underneath.
• Checks — a small bar with one segment for each pre-use check assigned to the asset, with a count such as 1 of 3 done underneath. Green segments are passed checks, red segments are failed checks, blue segments are in progress, red outlined segments are overdue, and grey segments are not yet due. If the asset has no checks assigned, this column reads No checks.
• Status — one or more badges that say what needs attention: 1 failed, 2 overdue, or 1 in progress. When nothing needs attention you see All passed, or 2 not yet due if some checks have not come round yet. Assets with no checks show Not tracked.
• Last check — how long ago a pre-use check was last completed on the asset, for example 3 weeks ago, with the exact date and time underneath in your own date and time format. If the asset has checks but none has ever been completed, it reads Never checked.

What each status meansCopy Anchor Link

Understanding the four groups is the whole point of the page:

• Blocked — at least one required pre-use check is due or overdue, and there is no active override. Bulk stops operators from starting production on this asset until the check is completed and passes, or a manager grants an override. Recommended and optional checks being due do not, on their own, block an asset.
• Override — the asset is blocked on paper, but a manager has granted a temporary override that lets it run anyway while checks are outstanding. An override always has an expiry (for example one, two, four, eight, or twenty-four hours), after which the asset returns to Blocked unless the check has been completed in the meantime.
• Ready — the asset can be started. Either none of its required pre-use checks are currently due, or its asset type is not set to block production while checks are incomplete.
• No checks — the asset can be started, but no pre-use checks are assigned to it, so there is nothing to track. If the machine should be gated by a safety check, assign a pre-use check template to it or its asset type.

Open an asset's checksCopy Anchor Link

Select any row to open the asset's checks panel on the right. At the top it shows the asset name, its asset type, and a status badge: Blocked, Override, Ready, or No checks. Under that, a summary bar shows one segment per check, how many are done (for example 0 of 3 done), and when the asset was last checked, as a date and how long ago.

Below the summary, every pre-use check assigned to the asset is listed. Each check shows:

• Its name, with its frequency and requirement underneath — for example Daily · Required. Frequencies are One-time, Daily, Weekly, or Monthly; requirements are Required, Recommended, or Optional.
• A single status badge: Overdue, Failed, Passed with issues, Passed, In progress, Due, Expired, or Not started. Overdue means a required check is due and not done, and it is the reason an asset is blocked.
• When the check was last done, as a date and how long ago, or Never done if it has never been completed. A check that is in progress also shows how many of its questions have been answered.

Checks that have been run at least once have an arrow on the right. Select one to open its most recent run, or the run in progress, where you can see the question-by-question results. This is how you move from "this machine is blocked" to "this specific check is the reason".

If no pre-use checks are assigned to the asset, the panel says No pre-use checks assigned and explains that nothing blocks the asset from running.

Example: practice cells at GothamCopy Anchor Link

Bruce opens Safety > Asset Readiness at Gotham Applied Sciences. The overview shows eight assets: 4 Blocked, 1 Override, 1 Ready and 2 No checks, with eight overdue checks.

• Gotham Skills Practice Cell 1 is Blocked at 1 of 2 done. Bruce has passed its guard and emergency-stop check, but the coolant and walkway check is still Overdue.
• Gotham Skills Practice Cell 3 is in Override, with 0 of 2 done. Bruce has granted a signed one-hour exception; both outstanding checks still need attention.
• Gotham Skills Practice Cell 2 is Ready at 2 of 2 done, with All passed and a recent last check.

Bruce selects practice cell 1. Its checks panel shows the coolant check as Daily / Required, Overdue and Never done, while the guard check is Passed. This identifies the exact check that needs completing at the workstation before the cell can be cleared.

What you can and cannot do hereCopy Anchor Link

• Read-only. You review readiness on this page. You complete a pre-use check in the Audits module, and you grant an override at the workstation when starting production — not from this page.
• All active assets are shown. The page lists every active asset in the current plant, including assets with no pre-use checks assigned. Use the tabs and search to narrow the list. Deleted and inactive assets do not appear.
• Empty state. If the plant has no active assets at all, the page shows "No assets with pre-use checks" and a note that assets with assigned pre-use check templates will appear here.

This page is generally available; no part of it is in preview.

TroubleshootingCopy Anchor Link

• An asset is missing. Only active, non-deleted assets appear. If a machine is not listed, confirm it exists and is marked active in your asset settings. Also check that a tab other than All, or a search term, is not hiding it.
• An asset is Blocked and you need to run it. Complete and pass its required pre-use check, or ask a manager with the override permission to grant a temporary override at the workstation. See the related guidance below.
• An asset is in No checks. No pre-use checks are assigned to it, so nothing gates it. Assign a pre-use check template to the asset or its asset type if it should be checked before use.
• An asset is always Ready even though checks are due. Its due checks are recommended or optional rather than required, or its asset type is not set to block production while checks are incomplete.

Related guidanceCopy Anchor Link

• Review pre-use check results — the history of completed checks across your assets.
• Run a pre-use audit — how an operator completes a pre-use check.
• Blocking pre-use checks in production — how blocking and overrides work when starting production at a workstation.
• Override a response — how supervisors authorise a temporary exception.
• Safety overview — the rest of the safety area.