The export is dead on arrival
Every spreadsheet in a project office begins as a download. The moment it lands it stops agreeing with the record it came from, and from then on the argument is about which copy is right.
Computatur
Spreadsheet · it is reckoned together · com-poo-TAH-tur
A grid that reads the record, not a copy of it.
Computare — com- plus putare, to settle an account together. The Latin ancestor of both compute and count, and the only honest name for a sheet whose job is to reconcile numbers that already exist somewhere else. Formulas, structured tables and pivots run directly over live estimates, schedules, resources and actuals. Nothing is exported, so nothing goes stale.
Why it exists
Every project office runs on a spreadsheet nobody trusts.
The formula outlives the author
A workbook that decides margin is a piece of software with no owner, no tests and no history. It is inherited, not maintained.
The grid is where governance goes to die
Rate cards, escalation, contingency and burden all get retyped into cells nobody audits, then flow into a number a client signs.
What it does
Six things a workbook cannot do.
Live references
A cell can point at ESTIMATE('MX-104').hours or TASK('IQ-12').finish. When the estimate is revised or the schedule is recalculated, the sheet is already correct — there is no refresh button because there is no copy.
Structured tables
Columns are typed: hours, currency, rate, duration, date. A rate column cannot silently hold text, and a duration column knows the project calendar. Errors are caught where they are entered rather than three tabs downstream.
Pivots on the record
Roll up by project, client, discipline, role, phase or deliverable — whatever your work actually breaks down into — without building a lookup column first. The dimensions already exist because the data was never flattened.
Governed inputs
Rate cards, burden and escalation are read from the governed source, not typed. A sheet can override them, but the override is visible, attributed and carried into the audit trail.
Publishable cells
Any range can be bound into a Plicatur proposal or a Numeratur report. The pricing table in the document is the range in the sheet, so the two cannot drift apart.
Versioned, attributed, replayable
Every formula change is a revision with an author. You can ask a workbook what it looked like on the day the number went out the door, and get an answer.
The reference
The formula names the record.
| Cell | Formula | Reads from |
|---|---|---|
| B4 | =ESTIMATE("MX-104").hours | Censetur line item |
| C4 | =RATE("Senior Engineer") | Governed rate card |
| D4 | =B4 * C4 | Computed |
| E4 | =TASK("IQ-12").float | Catenatur network |
| F4 | =CAPACITY("Q3", "Field") | Ponderatur resources |
| G4 | =EARNED("P-2291") - D4 | Numeratur actuals |
No cell addresses pointing into another tab, no VLOOKUP against a pasted range. A reference names the thing it means, so renaming a task or revising an estimate does not break the sheet — it updates it.
What it is not
- A general-purpose office suite. It computes over your record, not over arbitrary data you paste in.
- A replacement for Censetur. Estimating is line-item and structured on purpose; the sheet models around it, not instead of it.
- A macro host. Logic is formulas and named computations, versioned — never embedded code nobody can review.
Computatur is one verb in the Orditur suite. The estimate is assessed in Censetur, folded into a proposal in Plicatur, chained into a schedule in Catenatur and weighed against crew in Ponderatur. Computatur is where all four are reckoned together.