The Register module replaces physical site registers with a digital, configurable, and auditable system. Every register log is tracked with who filled it, their team, and a timestamp. Typical registers: Concrete Pour Register, Material Received Register, Concrete Cube Register, Safety Register, Training Register, Drawing Register, and more.
Role | Who they are | What they do |
|---|---|---|
System Admin | Organisation-level admin | Creates, edits, publishes and archives register templates (org and project level) |
Project Admin | Project-level admin | Cannot create or edit a register template. Can fill live registers, and manages project users, roles and settings |
Inspector / Filler | Inspector (or Project Admin) | Fills live registers — creates Logs and adds Table entries |
Approver (L1 / L2 / L3) | Senior authority | Reviews submitted logs — Approve or Redo (up to 3 levels) |
Auditor | Read-only authority | View & export logs, comment on web — cannot fill or approve |
Concept | What it means |
|---|---|
Template | The structure of a register — the fields in its Details and Table sections. Created by the System Admin. |
Log | One complete submission — the Details section filled once + one or more Table rows. |
Entry | One row in the Table section — e.g. one concrete batch, one delivery. |
Details section | Header fields filled once per log — e.g. Grade, Location, Pour Date. |
Table section | Multi-row data — filled many times per log; each row is one Entry. |
A template is built from these field types:
Field type | Details section | Table section |
|---|---|---|
Text / Multi-line / Numeric | Yes | Yes |
Option (single) / Checkbox (multi) | Yes | Yes |
Date / Time | Yes | Yes |
Calculation (auto-computed from numeric fields) | Yes | Yes (numeric only) |
Nomenclature (project location hierarchy + free-text Variable) | Yes | No (Details only) |
EQC Link (links the log to inspection EQCs) | Yes | No (Details only) |
A register template moves Draft → Live → Archive:
Status | What it means |
|---|---|
Draft | Template being designed — no one can fill it yet. |
Live | Available for filling. The template can still be edited and updated (add/remove fields). |
Archive | Closed for new entries; all historical logs kept for view/export. Cannot return to Live. |
Individual logs have their own status — Draft, Approval Pending, Redo, Approved — covered in "Register approvals — seek approval, redo & levels".
A digital replacement for a physical site register — configurable and auditable, where every log is stamped with user, team, and time.
A Log is one complete submission (Details filled once + Table rows). An Entry is a single row in the Table section of that log.
Only the System Admin. A Project Admin cannot create or edit a register template — but they can fill it.
Only the System Admin creates, edits, publishes, and archives a register.
A register must be Live before anyone can fill it — and a Live template can still be edited/updated.
Once a log is Approved, it is permanently non-editable — by anyone.
Team Access users see only their own team's logs; Project Access users see all teams' logs.
Nomenclature and EQC Link are Details-only field types.
2.4.2 Create & publish a register template
2.4.3 Fill a register — logs & entries
2.4.4 Register approvals — seek approval, redo & levels
2.4.5 View & export register data
2.4.6 Grouping in a register