RACK SAFETY

Damage reported at 9:04.
The bays it compromised stop accepting pallets at 9:05.

Racking fails progressively and quietly. A forklift clips an upright, nobody records it, and the bay keeps accepting pallets until the frame buckles. The dangerous gap is not detection — it is the hours or weeks between finding damage and stopping product from going back into the compromised bay.

Spatialis OS closes that gap because it already knows where every pallet sits. A damaged structural component resolves to a set of affected storage locations, and those locations change state the moment the finding is recorded.

Two categories of tool exist today. Neither closes that gap.

The spatial model is what makes this defensible. An inspection tool cannot change inventory state without a warehouse system underneath it, and a maintenance platform will not build a millimetre-accurate spatial model in order to compete.

BLAST RADIUS

One bent beam. Three levels out of service.

Damage attaches to structural components — frames, uprights, braces, beams — not to storage locations. The two do not map one to one, and that mismatch is exactly where the value sits.

Select a damaged component on the rack elevation. The locations it compromises are highlighted, with the containment the resolver recommends.

CONTAINMENT

Amber drains. Red blocks.

A finding that strands forty pallets creates an operational emergency, and the predictable response is that somebody acquires permission to disable automatic blocking. Once disabled, it stays disabled. So the common case is designed to cost operations nothing: the bay empties itself over days through picking that was going to happen anyway, and only then goes out of service for repair.

Nothing returns to service on its own.

The transition out of Pending always requires a human signature, recorded with name, role and timestamp. Severity follows measured deflection over a gauge length rather than judgement: the inspector enters millimetres, the system proposes a severity, and a named person confirms or overrides it. Both values are stored, and a persistent gap between them is the signal that the rubric needs tuning. Every override requires a reason from a controlled list and is written to the audit trail.

FIELD CAPTURE

Under 30 seconds, gloved, one-handed.

If reporting damage is slower than not reporting it, operators stop reporting and the data goes dark. The operator has the lowest friction tolerance of anyone who touches this module, and their tolerance governs the whole design of capture.

1. 01Scan any location barcode in the bay. Location barcodes already exist — nothing needs relabelling to start.
2. 02The app resolves the bay from the code and renders that bay’s actual frame diagram, not a generic picture.
3. 03Tap the damaged component on the diagram. No aisle lookup, no typing — this is the step where competing tools lose their users.
4. 04Capture a photo. The camera opens directly; for red findings, gallery upload is not permitted, because those images may become evidence.
5. 05Optionally enter a measurement. Skippable for operators, required for inspectors.
6. 06Submit. The resolver runs and the location effects apply.

No severity judgement is asked of an operator. They report what they see; the system and a qualified person decide what it means. Capture completes fully offline and queues for sync — and when it is queued, the screen says so plainly rather than implying containment has already happened.

Inspection frequency follows the damage, not the calendar.

Damage concentrates in a small fraction of bays, and the warehouse system already holds the data that predicts which ones. High-risk bays are inspected monthly; dead bulk storage quarterly. The same total labour, materially better coverage where damage actually occurs. Coverage is tracked per bay — the percentage of bays inspected within their assigned interval — because that is the number that survives contact with an inspector.

• Pick and putaway frequency for the locations
• Floor-level position — level 1 takes almost all impacts
• Aisle-end and cross-aisle position
• Proximity to dock doors, charging areas and pinch points
• Damage history on that bay and its neighbours
• Missing or damaged protective accessories

QUEBEC

No prescribed frequency — a general duty, and a standard you are measured against.

Quebec prescribes no racking inspection interval. The obligation is a general employer duty plus a building-code design obligation, with CSA standards supplying the benchmark that inspectors and engineers measure against. That absence is precisely why operators need something to point at: nothing tells them what "enough" looks like.

This is guidance, not a determination of your obligations, and not legal advice. Spatialis OS records what a qualified person determined and packages the evidence. It does not certify racking, and it does not render engineering or legal opinions.

EVIDENCE

One button. The whole file. In French.

Since 1 October 2025 a documented prevention programme is effectively mandatory, rack risk belongs inside it, and that programme is now regulated and auditable. So the output of this module has to be the evidence for it — a complete file for an inspection visit, produced in under a minute, legible when printed, because printed is how it gets handed over.

What the export contains

• Every inspection round with date, scope, inspector and coverage achieved
• Every finding with photos, measurements, classification and who confirmed it
• Every corrective action with dates, owner and verification signature
• Every engineering opinion and sealed letter
• Current capacity plaque values per bay, with their derivation
• Sealed drawings and layout version history
• Operator and inspector training records, where held
• Overrides, with reason and authorising user

The external engineer needs no licence and no email attachments.

A scoped, expiring, revocable read-only link opens on the component in question, with the dossier already assembled:

• The finding: photos, measurements, classification, who recorded it and when
• The component’s full history, including prior findings and repairs
• Original sealed drawings and load calculations, where held
• Posted capacity plaque values and computed values, side by side
• The actual load history for that bay — what has really been stored there, by weight, over time

That last item is the one nothing else in this market can supply. An engineer asked whether an upright is still serviceable normally has to assume the demand side. Spatialis can give them the measured demand.

BOUNDARIES

What this is not.

Stated plainly, because a product whose credibility rests on not overclaiming should say where it stops.

• It does not certify racking as safe. It records what a qualified person determined.
• It does not replace an annual expert inspection. It schedules it, packages it and stores it.
• It does not price repairs or hold vendor contracts.
• It does not detect damage automatically. A human reports; the system reasons about the consequences.
• It does not determine your regulatory obligations. It gives you the record to show whoever does.

FAQ

Questions about rack safety and compliance.