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 — unit repairs, work orders and the award of a project bid alike — so a lapsed vendor can't be hired through a side door. A certificate of insurance names one association, so the check is made for the association doing the hiring. 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, the dated steps of open projects — 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.

Bridge 9 · WorkCheck + Projects + Legal → Budget

What was spent lands on the budget line it belongs to

The adopted budget lives in HelmHOA as line items keyed by your own account codes. When a work order's cost is recorded, it can be tagged to its budget line; project expenses and legal invoices carry their line too. Each line then shows its actual beside the adopted figure, with the basis of every number stated — and a cost recorded both on a work order and inside a project is counted once, not twice.

HelmHOA is not an accounting system and never owns your chart of accounts — these are the costs recorded in HelmHOA, not your books. Spending on legal matters restricted to an access list is counted only for the people on that list, and the budget page says so.

Bridge 10 · VendorCheck + Budget + ReserveCheck → Projects

A capital project draws on the bids, the budget and the reserves

A roof replacement or balcony program is one project on one board. A manager can start one straight from a building-equipment asset or a reserve-study comparison card. It opens filled in, and nothing is saved until they save it. Bids come in from vendors in your directory and are compared side by side; the award runs the same credential gate as every other assignment. The project's money plan then says where the money comes from and where it goes — a budget line, a reserve component, a special assessment, a loan or insurance proceeds — and the expenses land as they are paid. Its dated steps appear on the compliance calendar.

Closing a project never changes records in other modules on its own. It hands you a checklist of follow-ups — update the building equipment, record the new reserve figures — for a person to do in the module that owns them.

Bridge 11 · RecordCheck ↔ Legal

A records request is answered from the vault — and privileged files can't leak into it

When an owner asks for records, the request carries its own working-day clock and is researched by searching the association's own document vault, past versions included. What is produced — and what is withheld, with its reason — is frozen into a package, and the response letter is drafted from it for the manager to send. The package refuses privileged legal records and any other association's records outright. Where a request concerns a legal matter, the two are linked, and managers can see one requester's history of requests, stated as facts.

HelmHOA never sends the response for you, and the request clock never pauses. Whether a record must be produced is your association's and its counsel's call; the letter states facts, not whether a deadline was met.

Bridge 12 · CleanCheck → WorkCheck

The cleaning crew finds it — maintenance gets the ticket

The people who walk every hallway every day see the dripping ceiling first. A cleaner reports it from the round they are running; management is notified, a work-order request lands in the triage queue marked as a staff report, and the reporter sees what was decided. The round itself records where and when it was found.

The crew can raise a request but can't read the work-order queue — cleaning staff see their own reports and nothing else of maintenance.