How they connect
From drawing to proof: how Sampraxis CAD and Project Management connect
On most projects the drawing, the estimate, the site diary and the bills live in different tools, and every change is typed again. Sampraxis is being built so that one record carries through: the quantities designed in Sampraxis CAD are the quantities planned, built, measured, claimed and proven in Sampraxis Project Management.
Launching soon. Each product works on its own today; the exchange between them is in development.
The connection · one record from drawing to proof
Typed once. Carried through.
On most projects the drawing, the estimate, the site diary and the bills live in different tools, and every change is typed again. Sampraxis is built so one record carries through, and a drawing revision arrives as a difference to approve, not a surprise on site.
-
Drawing
Drawn or imported, with levels and grids
works -
Quantities
Measured from the model, element by element
finishes today -
BOQ
Priced with reviewed rates
In development -
Estimate baseline
Design QTO, rate books, approved baseline
Pilot rollout -
Tasks
Plan, dependencies, make-ready
Beta -
DPR
Work done, labour, material, photos
Beta -
Measurement
Measurement Book, L × B × D
Pilot rollout -
Acceptance
Quality, curing, consultant, PM review
Pilot rollout -
Claim
RA bills, certification, deductions, GST, TDS
Beta claim control in pilot -
Proof
Accounts posted; client confidence report
Pilot rollout
Teal steps happen in Sampraxis CAD, amber steps in Sampraxis Project Management. The hand-off between them is in development. How the two products connect
When the drawing changes in development
A revision becomes a change to approve, not a surprise on site
A drawing revision should carry its consequences with it. The Design QTO, rate and estimation authorities in Project Management already compare a new version with the approved one and wait for approval; the hand-off from Sampraxis CAD that starts that comparison is what is being built.
- 1 Revision. A room grows or a wall moves in the drawing.
- 2 Difference. The affected quantities and estimate lines are recalculated and shown as a difference from the approved baseline: changed quantities, deductions and sources, line by line.
- 3 Approval. Someone with authority accepts or rejects the change. Nothing changes on site until then; an unaccepted change blocks the tasks it affects.
- 4 Project update. Only the approved difference reaches tasks, budgets and material plans; the original baseline stays on record.
Why the record can be trusted
Every step owns one thing and never the next
The chain holds because no step is allowed to do the next step’s job. These are the rules the application is built and tested against.
| Authority | Owns | Must never own |
|---|---|---|
| Task plan | identity, hierarchy, schedule, dependencies | award rates or payment |
| Design QTO | drawing-derived planned quantities and deductions | site work-done quantity |
| Rate authority | resources, rates, recipe calculation | the approved estimate |
| Approved baseline | approved quantity, rate, amount, source, revision | automatic refresh from a source |
| Cost allocation | approved value assigned to tasks and subtasks | a fabricated equal split |
| DPR | what happened on a date | completion certification |
| Site measurement | executed, measured quantity | the drawing QTO |
| Quality authority | inspection, curing, NCR, closure, waiver | payment authorisation |
| Completion authority | submitted, accepted, PM-reviewed work | bill payment |
| Commercial authority | claim, certification, deduction, tax, payable basis | inventing technical progress |
| Accounting authority | journal, transaction, settlement | quality acceptance |
| Confidence engine | deterministic status and reasons | approval, waiver, posting, payment |
| AI Copilot | explain, compare, forecast, cite, warn | decide, certify, deduct, approve, pay |
How it is built
Engineering you can check
-
Every release replays every migration
Each release candidate is replayed into a fresh database from the first migration to the last, with the SQL tests, before it can ship.
-
8,000+ automated tests
Application, database and edge-function tests run on every change; the figure is from the last recorded release qualification.
-
Row-level security on every table
Each organisation sees only its own rows, enforced in the database, not only in the screens.
-
Nothing is deleted or edited in place
Records are soft-deleted; money is corrected by reversal; the audit trail keeps who did what and when.
Status words on this site mean exactly one thing each. Beta: live in the private beta. Pilot rollout: built, tested and installed in production, dormant, and switched on project by project after qualification. In development: being built. Planned: decided, not started.
Sampraxis CAD · Limited Test Demo Preview
Register for Preview
Register for the Sampraxis CAD limited test demo preview. We review registrations and email selected participants a download link and access instructions. Registration does not guarantee access.
Talk to us
Questions about your projects, a pilot, or how Sampraxis would fit your firm? Write to sam@sampraxis.com.