Dependencies hide the real finish
A bar chart shows tasks moving, but it never tells you which late trade actually pushed practical completion out.
CONSTRUCTION PROJECT GOVERNANCE
Construction project software for operations teams running site works, refurbishments, and multi-trade fit-outs, where one late trade moves the whole completion date. Phaselo gives you an honest projected finish against baseline and a record you can defend when the budget gets questioned.
Free 14-day trial · No credit card needed · $8/user/month

The problem
On site works and fit-outs, the finish date is set by the chain of trades, not by any one of them. Demolition slips three days, the electrician cannot rough in, the plasterer is now booked elsewhere, and a small slip at the front becomes a four-week slip at the end. By the time it shows up on a bar chart, the trades are already standing on site and the owner is asking why nobody flagged it.
A bar chart shows tasks moving, but it never tells you which late trade actually pushed practical completion out.
Variations and committed costs pile up across cost centres until the overrun is a surprise instead of a warning.
The programme gets quietly redrawn after every delay, so nobody can say how far the job has really slipped from day one.
When the owner or finance asks why a date or a number changed, the answer lives in email threads and a site diary nobody can search.
How Phaselo handles it
Break the job into the whole project, work packages by trade, and tasks, then set the dependencies that actually drive completion. The critical-path engine returns a projected practical completion date and the trades on the critical path, recalculated as progress moves, and alerts you in-app and by email the moment a task is overdue or the job is projected past baseline.
Going live captures the programme baseline, and slip is always measured against it, never a moving target. Re-baselining is allowed but requires a recorded written reason, and the append-only audit trail keeps who changed what, when, and why, so a date or scope change is always defensible.
A triage board sorts every active job into on-fire, at-risk, and on-track, with a portfolio money strip totalling budget, committed, exposure, and headroom by cost centre. When you need owner sign-off, a capex request freezes its figures at generation so the document you circulate cannot disagree with what the job is actually spending.
Built for this work
Break the project into phases, work packages, and tasks, set the dependencies, and Phaselo returns the projected finish and the critical path. Go live to lock the baseline, then track slip against it as the work moves.

Pricing
$8 per user per month, flat. No tiers, no caps. Every plan includes the critical-path engine, baseline governance, the audit trail, slip alerts, and all five views. 14-day free trial, no credit card.
FAQ
Phaselo is built for owner-side and operations teams running site works, refurbishments, capital works, and fit-outs, not for main-contractor estimating or BIM. It focuses on the governance an owner needs: a real critical-path engine that gives an honest projected completion date, a baseline you cannot quietly move, and an append-only audit record. It is the projected finish and the honest slip, not a site-diary app.
Create a work package per trade and set the dependencies between tasks, for example rough-in after demolition, finishes after rough-in. The critical-path engine then shows you the chain of trades that drives the finish date and the total float on every task, so you can see exactly which late trade is pushing practical completion out and which slack you still have.
Yes. Phaselo captures the baseline when the job goes live, and slip is always measured against that original programme. If you genuinely need to re-baseline after a major scope change, it is allowed, but it requires a recorded written reason, so the original commitment and the documented change sit side by side and the slip number stays honest.
Every change is written to an append-only audit trail of who changed what, when, and why, and entries are never edited or deleted. Cost rolls up by cost centre into budget, committed, exposure, and headroom, and a capex request freezes its figures at generation for offline sign-off. When finance or the owner asks why a date or a number moved, the answer is already on the record.
Phaselo is $8 per user per month, flat, with no tiers and no caps, and every plan includes the full governance engine and unlimited projects. A 6-person site team pays $48 a month. There is a 14-day free trial with no credit card required, and it works on mobile so the crew can update progress from site.
An equipment commissioning checklist run as a live project plan: 5 phases, cold vs hot commissioning, acceptance tests, punch lists, and a clean handover.
Read the guide →Jira was built for software sprints, not site works. The honest guide to a Jira alternative for operations teams in manufacturing and facilities.
Read the guide →Start a free 14-day trial, no credit card. Bring your work packages, trades, and cost centres, and see the projected finish, the slip against baseline, and the dollars at risk across every job.
Start Free Trial