Project work, costed against the same ledger
Projects, portfolios, templates, timesheets and budget-versus-actual - reading the same cost postings and the same people records as accounting and HR, so a project's numbers do not have to be reconciled against the business's numbers.
Built for these teams
What you can do today
Every capability below is labelled with its real availability status - we don't describe planned work as shipped.
-
Project records
A project record carrying scope, dates, owner and the business unit it belongs to.
Available -
Budget vs actual
Planned budget against costs actually posted, so an overrun is visible while there is still time to act on it.
Available -
Timesheets
Time booked against a project by the people doing the work, feeding the actual-cost side of the comparison.
Available -
Portfolios and programmes
Grouping related projects so a programme reports as one thing. Delivered by the Work Management module alongside Projects.
Available -
Project templates
Starting a project from a template rather than an empty record. Delivered by Work Management.
Available -
Stage gates and approvals
Stage-gate policies and approval routing applied to project work. Delivered by Work Management.
Available
See an overrun while it is still worth knowing about
Budget sits on the project; actual cost comes from postings and booked time that already exist elsewhere in the platform. Because neither side is re-keyed, the comparison is current rather than reconstructed at month end.
- Budget held on the project record
- Actuals from real postings and timesheets
- Portfolio rollup via Work Management
How access and records are governed
Role-based permissions and an append-only audit trail apply across every module - see the Security & Compliance page for the full model.
-
Role-based permission scoping
Creating a project, booking time against it and approving a milestone are separately permissioned actions.
Available -
Append-only audit trail
Project changes, time entries and approvals write to the platform audit log with actor and before/after state.
Available -
Business-unit scoping
Projects are scoped to a business unit, so a multi-entity deployment keeps portfolios separate.
Available
What it takes to turn this on
- Decide your portfolio and programme structure in Work Management before creating projects - regrouping later is possible but rewrites how history reports.
- Set up project templates in Work Management for the work you repeat, so scope and stage gates do not get re-typed each time.
- Assign who may book time against a project versus who may approve it.
- Confirm the business-unit scoping matches how you want project reporting split across entities.
Keep learning
Frequently asked
Where does actual cost come from?
From postings already made elsewhere in the platform and from time booked against the project - it is not a separate figure that has to be maintained by hand.
Can a project span more than one business unit?
A project belongs to one business unit. Related work across entities is grouped as a programme rather than as a single cross-entity project.
Where do portfolios, templates and stage gates live?
In the Work Management module, which ships alongside Projects and shares the same project records. Projects covers the project itself, its timesheets and its budget-versus-actual view; Work Management adds portfolio and programme grouping, templates, stage-gate policies and approval routing.
Do designers work in Projects or in the Design Engine?
Both - the Design Engine is where drawings and configurations are produced, and the project record is what carries the commercial and scheduling side of the same job.
See project costing on your own numbers
Book a demo and we'll set up a real project with a budget and book time against it.