Project Tracker
Plans, capacity, timesheets and margin per project, for teams that bill their time.
Next.js · TypeScript · PostgreSQL · Recharts
Explore
From $529
PortfolioProject manager1 / 8
Project ManagementConstructionLive
Site Operations
Everything on a site is recorded twice: once badly on paper, once from memory a week later. This records it once, at the moment it happened, and then shows the same record to six different people at six different levels of detail.
- From
- $699
- Function
- 24
- Roles
- 6
- Users
- Unlimited
Next.js · TypeScript · PostgreSQL · Tailwind
Inside the app
What it does out of the box
24 connected functions on one schema, spanning six stakeholder views. Everything below is in the template before a line of customisation.
Portfolio dashboard
Active sites, how many are behind the baseline, open issues, change exposure and log compliance, with a health card per project.
Projects
Every site with completion against expected completion. The gap between those two columns is the whole report.
Project overview
The site header, the open blockers highest severity first, and progress by discipline weighted by contract value.
Tasks
Work breakdown by phase, area and discipline, as a board or a table. A blocked task names the issue blocking it.
Daily logs
Manpower, weather, progress, blockers and photographs, one per working day. A blocker in the log becomes an issue automatically.
Issues and blockers
Severity, area, discipline, owner and due date, with a flag for the ones that carry a commercial impact.
Documents and drawings
Revision controlled, with a client-visible flag. A superseded revision is kept and marked rather than deleted.
Approvals
What is waiting on the client, and for how long, timed from when it was sent rather than from when they opened it.
Change requests
Cost impact, schedule impact and status, linked back to the site issue that caused them, with approved-but-unbilled called out.
Punch list
Evidence required before an item can be submitted, and verified closure by a second person. That is the whole point of a punch list.
Reports
Health, log compliance, issues, change and closeout across the portfolio, each one exporting to CSV with the filters applied.
Six roles, one record
A subcontractor sees their project. A client never sees an internal document. Finance sees exposure. All from one schema, enforced server-side.
Permissions
Six roles, one build
A construction project has six kinds of people looking at it, and giving five of them the sixth one’s view is how commercially sensitive numbers end up in front of a client. Every level is included, and scope is enforced on the server rather than by hiding menus.
Project manager17 functions
The whole site, and the commercial exposure
- Portfolio health across every active site
- Every project tab, including approvals and change
- Issues by severity, with the ones carrying cost flagged
- What is waiting on the client, and for how long
- Portfolio reports that export with the filters applied
Site supervisor9 functions
Today's field work, and nothing else
- The daily log, which is the only route to raise a blocker
- Tasks by area and discipline, with blocked ones named
- Issues they own, with a due date
- Drawings, including which revision is current
- Punch items, with evidence required before submission
Admin24 functions
Everything, plus who can see it
- Everything a project manager can do
- Organisation profile, time zone and currency
- The rules: required logs, evidence, approval targets
- People across the client and subcontractor companies
- Role scope enforced server-side, not by hiding menus
Client6 functions
A curated view, with no internal detail
- Project overview and progress against programme
- Approvals waiting on them, with the reason attached
- Change requests with cost and schedule impact
- Only the drawings marked client visible
- Issues, so a delay is never a surprise at handover
Finance6 functions
Commercial risk, and nothing operational
- Portfolio change exposure across every site
- Approved value that has not been billed yet
- Cost and schedule impact per change request
- Project value and completion, for revenue recognition
- Reports that export straight into a month end
Subcontractor7 functions
Their project, and only their tasks
- The project overview for the site they are on
- Tasks assigned to them, with progress they update
- The daily log, so their day is on the record
- Punch items in their name, with the evidence rule
- No commercial figures, no other subcontractors
The build
Every function in the box
24 functions, all of them live in the preview. Nothing on this list is a mockup or a roadmap item.
Access
- Sign in
Portfolio
- Dashboard
- Projects
- Reports
Project workspace
- Overview
- Tasks
- Daily logs
- Issues
- Documents
- Approvals
- Change requests
- Punch list
Organisation
- Settings, rules and people
What you get
Delivered as a repository, not a login.
Contractors and fit-out firms running 3 to 60 concurrent sites.
- 13 production functions spanning six stakeholder views
- Full source code and PostgreSQL schema in your repository
- Role-based access control, enforced server-side
- Immutable audit log written on every change
- Responsive layouts, usable on a phone, not just resized
- CSV import and export on every core record
- Deployment configuration for your cloud account
- Twelve months of updates, and no per-seat charge ever
Access and evidence
Built for the day something goes wrong
On a construction site the record matters most when somebody is arguing about it months later. Logs, issues and approvals are captured at the moment they happen, on a phone, and cannot be quietly backdated afterwards.
- A failed hold point blocks every downstream task automatically
- Tasks tied to a superseded drawing are blocked until re-issued
- An expired ticket blocks site access at the gate, not at the next audit
- Daily logs timestamped on capture, edits kept as revisions
- Photographs attached to the log or punch item, not a shared drive
- Superseded drawing revisions kept and marked, never deleted
- Retained for the life of the project plus twelve years
Related
Apps that pair with this one
Field Service Scheduler
Dispatch board, engineer routing, job sheets and parts usage for teams that work on site.
Next.js · TypeScript · PostgreSQL · Tailwind
Explore
From $629
Asset Register
Every laptop, vehicle, licence and machine, who holds it, what it cost and when it is due.
Next.js · TypeScript · PostgreSQL · Tailwind
Explore
From $569
Questions
Site Operations, in practical terms
Do I get the source code for Site Operations?
Yes. The repository, application code, database schema, migrations, seed data and deployment configuration, is transferred to your organisation on delivery. There is no licence key and nothing that calls home.
Does it work with no signal on site?
The screens used on site, the daily log, tasks and the punch list, are built offline-first, so entries, photographs and sign-offs are captured locally and sync when signal returns. That is the difference between a site app that gets used and one that gets abandoned in week two.
How do hold points work?
A hold point is a task that cannot proceed without a recorded sign-off. Failing one blocks every downstream task automatically rather than relying on someone remembering. The same applies to superseded drawings: a task tied to an old revision is blocked until it is re-issued against the current one.
How many sites can it run at once?
As many as you like, pricing is per application, not per site or per user, so every operative, subcontractor and site manager can have an account. Each site carries its own permit rules, hold points and induction requirements.
Can Site Operations be changed to match our process?
That is the usual route. A fitted build adjusts the daily log fields, issue severities, approval targets, change request workflow, role scope, branding and up to two integrations, and typically takes one to three weeks from a signed scope.
What does it cost to run?
Hosting only, paid to your own cloud provider, roughly $50 to $200 a month depending on site count and photo storage, which is usually the largest component on a busy project.
Want Site Operations shaped around your process?
A fitted build adjusts fields, stages, roles and integrations to how your team already works. One scoping call, a fixed price, one to three weeks.
