SiteLedger - Contractor Progress & Billing
← All projectsA project management and billing system for a contracting company with several sites. It replaces the three separate lists that QC, billing staff and contractors each kept, and the arguments over the differences between them.
How it works
- The contractor logs work against the signed bill of quantities
- QC verifies it, adjusts it with a reason, or rejects it
- Every cycle (14 days by default) the contractor requests a billing built only from QC-verified quantities
- Staff price it, the main engineer approves it as an invoice, and payment is recorded as a receipt
What is in it
- Five roles, each seeing only what they need: owner, main engineer, QC, billing staff, contractor
- Multi-branch: every site has its own colours, banner and engineer in charge
- Contracts and BOQ with claimed, verified, billed and remaining quantities per line
- Full traceability: every log shows who handled it at each step
- Attendance with a gate-terminal simulator (face, QR or phone geofence)
- Queries settled on the record instead of in a spreadsheet
- Every list sorts and searches every field; every record is a link
This is a working demo: the data lives in the browser and can be reset at any time.
Overview
SiteLedger is a project management and billing system for a contracting company with several sites. It replaces the three separate lists that QC, billing staff and contractors each kept, and the arguments over the differences between them.
The problem
Contractors claimed one quantity, QC verified another, and billing priced a third, each in their own spreadsheet. Bills were disputed every cycle and nobody could show who changed what.
What I built
- Work logged against the signed bill of quantities
- QC verifies, adjusts with a reason, or rejects each log
- Billing every cycle (14 days by default) built only from QC-verified quantities
- Staff price it, the main engineer approves it as an invoice, payment is recorded as a receipt
- Five roles: owner, main engineer, QC, billing staff, contractor
- Multi-branch sites with their own colours, banner and engineer in charge
- Attendance with a gate-terminal simulator (face, QR or phone geofence)
- Full traceability: every log shows who handled it at each step
Architecture
A React single-page app with role-based screens. Every quantity moves through one pipeline: claimed, verified, billed, paid, and each step records who did it. In the public demo the data lives in the browser and can be reset at any time.
A high-level view. Endpoints, hosts and security details are left out on purpose.
Key decisions
- 01
Bills come only from verified quantities
Why: A billing can only include what QC has verified, so the invoice and the site record always agree.
Trade-off: Contractors wait for QC before they can bill new work.
- 02
Adjustments need a reason
Why: QC can change a claimed quantity, but must say why, which settles disputes on the record instead of in a spreadsheet.
Trade-off: One more field to fill for every change.
- 03
Each role sees only what it needs
Why: Five roles keep contractors out of pricing and billing staff out of verification.
Trade-off: More screens and permissions to design and test.
- 04
Demo data stays in the browser
Why: Anyone can try the full flow without an account, and reset it in one click.
Trade-off: The demo is not shared between devices; a real install uses a server database.
Links
The live link is a working demo with sample data. The source code is private; I'm happy to walk you through it in a call.