Let a blocked asset go out with a readiness override

Read why an asset is blocked, then add a time-limited override so dispatch can use it anyway, release the override early, or recalculate readiness.

In the sidebar, open Equipment & Fleet, then Assets, press the asset's name, then press the Readiness tab. The page address is /assets/ followed by the asset and /readiness.

Nova blocks an asset from dispatch when something is wrong with it: a blocking issue, overdue service, a failed checklist, missing supplies or documents, a blocked part inside it, or because it is out of service. An override is a written, time-limited exception that lets dispatch use the asset anyway until the problem is fixed.

Before you start

• Your role needs permission to override asset readiness. Without it Request override and Rebuild readiness are not shown.
• A retired asset cannot be overridden. Return it to service first: see Take an asset out of service or retire it.

Steps

1. Read the tiles: Readiness state, Blocking issues, Overdue service, Failed checklists, Missing supplies and Blocked children.
2. Read Readiness reasons. Blocking reasons are red, warnings are amber, and the line under the summary says when readiness was last refreshed and whether dispatch is ready or blocked.
3. If a reason is out of date because the problem was just fixed, press Rebuild readiness first. Nova recalculates and says "Readiness rebuilt."
4. To let the asset go out anyway, press Request override.
5. If your organization asks for a reason, choose a Reason category, type a Business explanation, and press Create override.
6. In Set the override expiry, type when the override ends in the format shown, for example 2026-12-31T18:00:00Z (the date, the letter T, the time, and Z for UTC). Press Create override.
7. To end an override before it expires, press Release on it under Overrides, give a reason if asked, and press Release override. The asset returns to its calculated readiness at once and Nova says "Override released."

What you see

• Nova says "Override recorded." The override starts straight away and appears under Overrides with its reason and "Expires" and the date.
• Dispatch treats the asset as usable until the expiry, and it leaves the Blocked dispatch queue on the asset list. The blocking reasons stay on the page so nobody forgets the real problem.
• A new override replaces any earlier override still running on the same asset.
• When the expiry passes, Nova ends the override on its own and the asset is blocked again if the problem is still there.

If something looks different

• "Readiness overrides cannot be applied to retired assets." appears: the asset is retired.
• Nova refuses the override with an error: the expiry you typed is in the past or not in the format shown. Press Request override again and type a later date exactly like the example.
• Contained-asset rollup lists a part inside this asset: that part is what blocks the whole kit. Press its name to open it and fix it there.
• No readiness snapshot shows: press Rebuild readiness to calculate it.

Open Readiness