Selected work

See the thinking
behind the systems.

Explore our own product builds: the workflows they support, the architecture behind them, and the decisions that keep a system ready for change.

Explore the build story

01 / Digital Cubic product build

ArkanCS.
An approval is more
than a status.

Construction work moves between people, documents and decisions. The system needs to retain who acted, in which role, and against which record.

Explore ArkanCS

ArkanCS project interface showing project information, document navigation and project status — ArkanCS · Project workspaceInspect the full-size interface ↗

Illustration of connected architecture layers, records and decision pathways — AI-generated architecture illustration. The explanation draws on our published Arkan architecture article; the image is not a product interface or client artifact.

The requirement

Keep the decision in context.

Drawings, submittals and inspections need clear ownership as work moves from site to office.

The design decision

Model the event, not just the result.

Arkan’s published architecture describes an approval as an event against a document, performed by an actor holding a role.

What this supports

Rules that can evolve.

Delegation and approval history sit within the model, keeping each decision connected to the person and record behind it.

Read the decision and its tradeoff

A single status field is simple, but it only remembers the latest state. An event model retains the actor, role and history; those relationships also need deliberate modelling and maintenance.

Our published article explains this choice across Arkan’s construction and ERP platforms. Its contractor scenario is an explanation of the architecture, not a separate customer case study.

Read the architecture article