Every project, from estimate to final account.

The estimate, the budget, the commitments and the schedule are one record. Change one and the rest follows — nothing re-keyed, nothing reconciled at month-end.

Get a demo instance See it working

One number, followed all the way down.

From estimate to project closure, it stays one number — through budget, commitments and variance, never re-keyed.

Cost planHarbour Quarter · Block CRev 14 · locked 12 May

Code	Description	Estimate	Budget	Committed	Variance
01-200	Preliminaries	€492,000	€486,000	€471,300	€+14,700
02-100	Substructure	€1,215,000	€1,240,000	€1,268,400	€−28,400
03-400	Superstructure frame	€2,940,000	€2,905,000	€2,861,900	€+43,100
05-100	MEP first fix	€1,588,000	€1,610,000	€1,602,750	€+7,250
07-300	Envelope & cladding	€2,205,000	€2,180,000	€2,180,000	—
	Total	€8,440,000	€8,421,000	€8,384,350	€+36,650

Substructure is running €28,400 over commitment — the only line that needs a decision this week.Sample project shown.

The line that is over budget is the line that is late. On most projects those are two different conversations.
Why the cost plan and the schedule share one record

A slip and its cost are the same fact.

Sync the schedule from Microsoft Project and track it against baseline and the critical path. Every late task shows up in the budget it belongs to — the moment it slips.

ScheduleSynced from MS Project · HQ-BlockC-r14.mppAgainst baseline 3

Mar

Apr

May

Jun

Jul

Aug

Sep

Oct

Piling & substructure

Frame erection

Envelope & cladding

MEP first fix

Fit-out

Substructure is two weeks past baseline — and it is on the critical path, so the slip reaches every bar after it.Critical pathFloat availableBaseline 3Sample project shown.

To do12

Pile cap rebar inspection

Due Fri · A. Petrauskas

DOC

Issue revised setting-out

Due Mon · Site eng.

In progress7

MEP

Riser coordination — levels 3–6

J. Kazlauskas

FIN

Reallocate €28,400 to 02-100

Awaiting QS sign-off

Blocked2

SUB

Substructure pour — sequence 4

Commitment over budget

It reads the project, not the documentation.

CitraWorks exposes its own budget, estimate and schedule records to AI assistance and MCP servers. Answers are computed from the live cost plan and cite the lines they came from — so you can check them the same way you would check a colleague.

It runs inside the same permission model as everyone else. It cannot see a project you cannot see.

Which cost codes moved against baseline this week, and what is driving it?

One line moved. 02-100 Substructure is committed at €1,268,400 against a budget of €1,240,000 — €28,400 over. The commitment was raised on 8 May against variation VO-017 (additional piling depth, grid lines D–F). Sequence 4 of the pour is blocked pending QS sign-off, which is also holding the schedule two weeks past baseline 3.

Cost plan · rev 14VO-017Schedule · baseline 3Task #4821

Sample project shown. Every figure in the answer traces back to the cost plan higher up this page.

What's in the platform.

Budget control: Hierarchical cost types, live commitment tracking, and owner change-order workflows.
Estimate linkage: Estimates stay bound to the budget they feed, so a revision reaches the cost plan without re-keying.
Schedule management: MS Project sync, Gantt, critical path, and variance alerts against baseline.
Issues & tasks: Kanban with typed labels, subtasks, dependencies, and a finance tab on every task.
Teams & HR: People and roles per project, with team costs and cost forecasts.
AI & MCP controls: Assistance and MCP servers operating on live budget, estimate and schedule records.
API & integrations: Custom integrations against the same records the interface uses.