The modules share one data spine

Bridge 1 · UnitCheck

A finding becomes a repair — and the status can't lie

Every unit lives in a five-state lifecycle, and the system — not a person — computes the state from the repair items themselves. A passing inspection creates no work; every failed item becomes its own tracked repair. Owners submit proof per item; the one move an owner can make is submitting that proof for review. When management has approved every single item, the unit advances to Compliant automatically — and a single rejection, or any newly found issue, drops it back with the reason preserved.

Bridge 2 · WorkCheck

Equipment age becomes a work order — before the failure

Every common-area asset in the building equipment registry carries its maintenance interval and service dates. A daily scheduler raises a work order when an asset comes due — exactly one per asset, no duplicates on a re-run — and completing that work order writes the service dates back to the asset and rolls the next reminder forward. Nobody re-enters a date, so the schedule can't quietly drift from reality.

Bridge 3 · WorkCheck → UnitCheck

The building pays — and the owner's checklist clears itself

When the association takes responsibility for a repair found in a unit — a building-side valve, say — completing the work order resolves the owner's repair item as building-funded and recomputes the unit's status on the spot. The owner is never chased for proof of work they didn't commission. The discipline matters as much as the convenience: work marked as the owner's responsibility never auto-resolves, so the bridge can't be used to wave a unit through.

Bridge 4 · UnitCheck → ReserveCheck

Inspection findings annotate the reserve study

A structural integrity reserve study says what a component is assumed to have left. Inspectors keep finding what's actually there. HelmHOA joins the two: findings from the field appear beside the matching reserve component, each value labeled with where it came from — the study or the inspection — so the board reads assumption and observation together instead of five years apart.

Extracted study values reach this view only after a person confirms them, and the reserve schedule mirrors your study — HelmHOA is not a reserve study provider and computes no funding recommendations.

Bridge 5 · LeakCheck

A leak event becomes a save, a claim record, and a work order

When a unit's water sensor reports wet, the event arrives over a signature-verified connection and lands in a manager's triage queue — flap-guarded, so a misbehaving sensor can't flood it. A manager who confirms a real catch marks it a save: the running count of incidents the sensors actually prevented from becoming floods. From the same screen, the response chain starts — a plumbing work order and an insurance claim record attached to the event, so the evidence is organized while the floor is still wet.

LeakCheck is monitoring and triage, not a life-safety alarm system — real-time alerting stays with the sensor platform. Sensors are owner-held devices; hardware is not included.

Bridge 6 · VendorCheck

An expired credential blocks the assignment

Vendor licenses and certificates of insurance carry expiration dates, and the platform watches them — reminders as expiry approaches, automatic suspension when a document lapses. One gate guards vendor assignment everywhere it happens, on unit repairs and on work orders alike, so a lapsed vendor can't be assigned through a side door. Un-suspending is a deliberate, logged decision, not a default.

The gate reflects document status — current documents on file, as of their dates — it does not verify insurance coverage with the carrier or the state.

Bridge 7 · Everything → DateCheck

Every module feeds the deadline spine — read-only

DateCheck computes the statutory deadlines from facts your association confirms, each rendered with its formula and citation. On top of that spine, the other modules overlay their own dated obligations — certification clocks, milestone phases, election ladders, credential expirations, filing windows — in one shared shape. The calendar shows them; it never edits them. Signing off an obligation happens in the module that owns it, and an overlay only appears when the association actually runs both modules involved.

Bridge 8 · UnitCheck → Building Twin 3D

Compliance status colors the building

The building model is traced in-app from your own PDF floor plans — no CAD files, no BIM project. Once it exists, the same five compliance states that drive the dashboards color every unit volume live, with pins marking open repairs, inspections coming due, and equipment past its date. Slice a floor, isolate a unit, and jump from the model straight to that unit's repair record.

The model is a schematic visualization — not to survey or engineering accuracy — and the viewer requires a WebGL2-capable browser.