Engineering Workspace / Registers & Claims
In depth

Registers & Claims

RFIs, submittals, shop drawings, risks: one consistent grid, importable from what you already have — and quietly feeding your entitlement record.

Every register, one behaviour

The same grid, filters, column manager and export everywhere. Import an existing export and the columns map themselves; the approval clock shows who is holding what, oldest first.

Excel in, Excel/PDF out — the view is the export
Custom columns and rules per register
Chase pack: one press, every overdue item
Every register, one behaviour
The claims ledger — the feature the others don't have

The claims ledger — the feature the others don't have

Set the contractual review allowances once. From then on every item is measured against them, live: held-vs-allowed clocks, excess days aggregated, notice windows tracked, and a Word evidence pack on demand.

Computed from the registers you already keep
Notice deadlines — never miss a 28-day clause
Monthly exhibit with dates and references

Held vs allowed, item by item

Each row carries its own clock: the teal share is the contractual allowance, the red is the overrun. This is contemporaneous evidence kept by software instead of memory.

Held vs allowed, item by item
Cropped from the live ledger.
Every capability, declared

The complete list.

Every register capability, and the claims engine underneath.

The grids

Seven register typesRFIs, submittals, shop drawings, long-lead items, risks, deadlines, design issues — one consistent behaviour.
Custom columns & rulesAdd the columns your project speaks; rules keep entries consistent.
Column managerShow, hide, resize — remembered per register, per user.
Facet filters + search-every-columnSlice by any value; the count and the export follow the filter.

In and out

Excel import with mappingAconex-style exports map themselves; re-import updates matched rows.
Excel / PDF exportTicked rows if any, else the filtered view, else everything.
Portal downloads intakeFiles fetched from consultant portals land in an intake queue for filing.
Supervised portal fetchSign in to the portal yourself — the workspace never holds your portal password.

The clock & the chase

Approval clockWho is holding what, oldest first — the meeting agenda writes itself.
Chase packOne press: a dated chase list of every overdue item, ready to send.
Analytics + custom analyticsBuilt-in charts plus a builder for the analysis your PM actually asks for.
Attention feed integrationOverdue register items rank into the dashboard's one list.

Claims & entitlement

Review allowancesContractual review periods per type, set once from the contract.
Held-vs-allowed ledgerEvery open item measured live; excess days aggregate for the claim narrative.
Notice trackingMark the contractual notice per item; closing windows (e.g. 28 days) tracked.
Evidence packOne press: the monthly Word exhibit — items, dates, references, totals.
Review-record tie-inDeliverable response codes and issue→response times join the entitlement story.
Against the field — registers & claims
Registers feeding an entitlement ledger automatically
Logs that record events but never compute entitlement
Notice windows with deadlines tracked per item
A diary note, if the engineer remembered
The filtered view IS the export
Export screens with their own separate logic

"The markup suite" is the well-known per-seat PDF application; "the construction cloud" is the big per-user-per-month platform. Both excellent at what they chose — the difference here is one integrated record, on your own server.

See it on a live workspace.

A real account inside a realistic demo project — request it in one minute.
Try the live app →
← Design WorkflowSearch & Ask →