Module · Programme
A programme that the rest of your project actually reads.
Phases, milestones, baseline and slippage in one project view - feeding cashflow, cost forecast and the executive summary. No re-keying of the same dates into three tools.
Why programme tools fail consultancies
The programme is in one tool. The cost forecast is in another. Cashflow is in a third.
Most consultancies maintain a Primavera or MSP file that nobody else opens. The PM exports a screenshot for the monthly report. The QS forecasts cashflow off a separate spreadsheet. They drift constantly.
Programme drift never reaches commercials
Construction slipped two weeks. The cost forecast still assumes the original handover. By the time the QS notices, the cashflow miss is already certified.
Two views of the same dates
The programme says one thing, the project record says another. Whoever updated their copy last night is "right" - until tomorrow.
The client sees the prettier of the two
Programme exports go into client decks; the live programme stays in the PM's tool. The version the client sees is always two weeks stale.
What's inside
A programme that connects to the project.
Phases & milestones
Define project phases (Tender, Pre-construction, Construction, Closeout) and milestones within each. Owned, dated, baselined.
Baseline tracking
Lock a baseline at each gateway. Slippage from baseline shows in the programme view AND on the executive intelligence card automatically.
Slippage flags
Auto-flag any milestone that has moved more than X days from baseline or is approaching with no progress. Surfaces in the project Overview, not buried in the programme tool.
Cashflow integration
Programme dates feed the cashflow S-curve. Move construction back two weeks, the cashflow shifts. No second update required.
Cost report linkage
Programme drift drives forecast cost movement in the PCSR. Two-week extension, two weeks of preliminaries, the PCSR shows it.
Client visibility
A controlled programme view ships in the client portal. Clients see the live programme - not last month's screenshot.
Who uses it
Built for the people accountable to the dates.
Project Managers
Maintain ONE programme. The cost report and cashflow read from it. The client portal shows it. Stop exporting screenshots.
Construction Managers
See programme + site reports + risks side by side. Spot the trade clash before it hits the milestone.
Cost Coordinators
Programme moves → forecast moves. No need to ping the PM for the latest dates before refreshing the cashflow.
See programme drift hit your PCSR live.
A 30-minute walkthrough on a real project - bring your programme, we'll show you what changes when it moves.
Frequently asked questions
Will Projavio replace MSP / Primavera?
Projavio is built for consultancy-grade programme management - phases, milestones, baseline, slippage. It is intentionally not a CPM scheduling engine. For complex CPM logic, you can keep MSP/Primavera and import the dates Projavio cares about; for typical consultancy projects, Projavio is the only programme tool you need.
Can I import an existing MSP/Primavera file?
Milestones can be imported via CSV today. A native MSP/Primavera importer is on the roadmap.
How does this connect to cashflow?
Programme dates drive the cashflow S-curve. The phase + milestone schedule sets the spend curve; moving a milestone shifts the curve, which shifts the forecast cost in the PCSR.
Can subcontractors / consultants update milestones?
Designer and consultant accounts can update milestones they own; client roles see milestones read-only via the client portal. Internal CM / PM hold the source of truth.
Connects to
Other Projavio modules that work alongside this one.
Cashflow
S-curve plan vs actual vs forecast cashflow per project, rolled up across the portfolio.
Cost Reports (PCSR)
Live PCSR consolidating committed (POs), anticipated (variations), forecast (cashflow) and out-turn cost.
Site Reports
Daily site reports filed from a phone, surfaced in the project record. Photos, weather, attendance, delays.
One programme. Read by everything else.
Stop maintaining two versions of the same dates.