One project. One reality.
The operating platform for heavy civil construction.
Survey, field operations, quantities, utilities, quality control and project oversight — connected in one shared system, and usable in the field with no signal.
- iPhone + iPad
- Field-ready on the hardware crews already carry
- Offline-first
- The project opens and works with no signal
- Immutable records
- A published revision cannot be edited under a crew
The problem
Your project should not operate through disconnected information.
On most heavy civil projects the information that decides the work is real, but it is scattered. The survey lives in one file, the field record in another, and the decision gets made from whichever one is open.
- Survey files on a laptop in the office trailer
- Field notes in a notebook or a phone photo
- Quantities in a spreadsheet nobody else has
- Screenshots pasted into messages
- PDFs emailed and then superseded
- Utility records held by whoever did the locate
- Verbal updates that leave no record
The cost is not the files. It is the disagreement.
When the register says one thing and the map says another, nobody can tell which is wrong. Work gets rebuilt, quantities get argued after the fact, and the record that would have settled it was never written down.
ARKAK connects these into one project reality.
One set of project data, one filter model, one revision chain. What the field captured, what the design says, and what management sees are the same information — not three copies of it.
Built for the whole field team
Every role sees its own work. Everyone works from the same project.
ARKAK does not give each role a different copy of the truth. It gives each role the view its responsibilities require, over one shared set of project data — with permissions that decide what a person may change, not just what they may see.
Superintendent
Full project authority, and the record of who did what.
- Progress and production records
- Approvals and publication override
- Deficiencies and issue status
- Members, roles and project settings
- Audit visibility across the project
Role behaviour shown here reflects ARKAK's permission model, in which operational roles do not edit survey geometry. Crew, shift and work-area scoping is planned.
From design to field reality
From design data to field decisions.
ARKAK's value is the connection between three layers that are usually kept in separate systems — and the record that connection leaves behind.
- 01
Design and spatial data
Points, alignments, surfaces and CAD linework are imported from the office toolchain — CSV, LandXML and DXF — and carry their source with them, so any value can be traced back to the file it came from.
- CSV and TXT points
- LandXML alignments and surfaces
- DXF linework and layers
- Project coordinate reference and units
- 02
Field activity and verification
Crews work against that data on site, offline. Positions are captured, surfaces compared, volumes measured, utilities recorded, and areas checked against tolerance — with photos and notes attached where they belong.
- Station and offset against the active alignment
- Cut and fill against the design surface
- Stockpile volume measurement
- Utility locate records
- Coverage: verified, missed, corrected
- 03
Management decisions and records
The result is not a folder of exports. It is a reviewable, versioned register: what was surveyed, by whom, to which construction layer, at what revision — and what is still missing.
- Submitted, approved, published, superseded
- Immutable published revisions
- Gap and overlap analysis
- PDF sheets and registers
- Append-only audit history
Platform capabilities
One platform, connected modules.
ARKAK is not a set of separate tools that happen to share an icon. The modules below read and write the same project data, and are filtered by the same rules.
Field Operations
AvailableThe day-to-day work: what is happening on site, who is doing it, and what needs attention.
- Daily field workflows
- Issues and approvals
- Photos, notes and attachments
- Role-based operational views
- Full offline field use
Survey & Spatial Data
AvailableDesign data in, field geometry out — points, alignments, surfaces and the coordinate framework they sit in.
- Points and coordinate data
- CSV and TXT point import with column mapping
- LandXML alignment and surface import
- DXF import (linework, points, layers)
- Alignments, stationing and station/offset
Earthworks & Quantities
AvailableMeasuring ground against design, and turning that measurement into a defensible number.
- Cut and fill against a design surface
- Surface comparison
- Stockpile volume measurement
- LiDAR capture on supported hardware
- Camera capture
Utility Intelligence
AvailableWhat is buried, where it was found, and the record that proves it was looked for.
- Utility locate records
- Known utility visualization
- Utility Locate Sheets
- Locate comparison
- Utility warnings
Quality & Verification
AvailableWhich ground has been checked, to what tolerance, at what revision — and what has been missed.
- Tolerance checks
- Coverage tracking by construction layer
- Passed, failed, corrected and approved areas
- Missed-area and gap identification
- Categorised overlaps, not raw overlap counts
Reports & Deliverables
AvailablePrint-ready documents produced from project data, not retyped from it.
- Cut Sheets
- Utility Locate Sheets
- Stockpile Volume Sheets
- Coverage Register
- QC and as-built records
Showing capabilities that are available in the current product. The full register — including what is in development and what is planned — is on the Features page.
See the full capability registerDecision support
Know tomorrow before tomorrow starts.
ARKAK answers questions from the project's own information. It supports the decision; it does not make it, and it is not an engineering authority.
How far are we from the design surface?
AvailableCut and fill against the design surface, with tolerance bands.
Which areas have not been verified?
AvailableCoverage gaps against a configured expected extent.
What changed since yesterday?
AvailableRevision history and an append-only activity record.
Which deficiencies require correction?
AvailableInspection outcomes and issue status.
What is still awaiting approval?
AvailableThe review queue for submitted work.
How much material is in that pile?
AvailableStockpile volume measurement with a defensible base.
Are field activities near a known utility?
AvailableKnown utility visualization and utility warnings.
How much material will tomorrow's work require?
PlannedMaterial requirements and forecasting.
How many trucks should we schedule?
PlannedTruck and haul scenarios.
Two of these are on the roadmap and are labelled as such. ARKAK will not present planning capability it does not have.
Defensible field records
Field records that remain useful after the work is complete.
A sheet that can change after a crew has built to it is not a record. ARKAK's deliverables carry their identity, their inputs and their history — and once published, they cannot be quietly edited.
Revision identity
Every deliverable belongs to a revision chain. Publishing a new revision supersedes the previous one in the same transaction, so two live published revisions never exist.
Immutable published records
Immutability is enforced independently on the device, at the API, and by a database trigger — so it holds even against a mistake in our own code.
Calculation traceability
The geometry used for a calculation is stored with the result, not re-derived later from data that may have moved on.
Dates and responsible people
Who surveyed it, who checked it and when are recorded. Personnel are stored always and printed only when the project chooses.
Photos and attachments
Evidence attaches to the record it belongs to, and travels with it.
Audit history
Deliverable events are append-only. History is added to, never rewritten.
Professional output
ARKAK produces print-ready PDF deliverables from project data. The previews below are generated from the sample project fixture.
Cut Sheet
Utility Locate Sheet
Stockpile Volume Sheet
Coverage Register
ARKAK produces engineering and field documentation. It does not issue certified survey plans or legal utility clearances, and does not replace verification required by the project owner or by law.
ReportsField-ready architecture
Built for the field. Designed for accountability.
The constraints of a construction site are not edge cases in ARKAK — they are the design centre.
- Available
Offline-capable field workflows
The device keeps its own database and never blocks on the network. Work done in a trench with no signal is queued, not lost.
- Available
Local Mode
A standalone iPad with no server and no account is a permanently supported state, not a setup step.
- Available
Role-based access
One permission vocabulary across iPad, Local Mode and server — 60 permissions and 16 project roles, with deny always beating grant.
- Available
Server-enforced authorization
The interface hides what a user cannot do; the server re-checks it. Another company's project returns 404, never 403.
- Available
Revision history and audit trail
An append-only audit log written in the same transaction as the change it describes.
- Available
Hardware-aware functionality
Where LiDAR, camera, location or sensors are unavailable, ARKAK says so and offers the alternative — it does not fail or pretend.
- In Development
Multi-user project collaboration
Accounts, invitations, roles and tenant isolation are in place; synchronisation currently covers survey points, with the remaining record types in progress.
- Planned
Crews, shifts and work areas
Crew and shift scoping of permissions and work areas.
Talk to ARKAK
Ask about ARKAK, and get a straight answer.
Prefer to ask before booking a demo? The ARKAK assistant can answer questions about what the platform does today, what is still in development, and whether it fits your project.
- Identifies itself as an AI assistant, always
- Explains approved capabilities only, and separates available from roadmap
- Hands technical, pricing, contractual, safety and legal questions to a person
- Books a demonstration and passes a written summary to the team
Assistant not yet connected
The ARKAK assistant is not live on this site yet. Until it is, the fastest route to an answer is a demo request or a direct email — both reach the same team.
Bring your field operations into one connected system.
See how ARKAK can connect field information, quantities, verification and project decisions.