The report announces itself, pre-fills itself - and stands by what it says
From work package to committee: contributions arise in the system, the status report waits as a prepared draft, and approved states stay verifiable - a reporting chain instead of a collection round.
The reporting chain
Sub-projects report with traffic lights and decision-needed flags - finalised, locked, visible in the project report.
Why reporting fails today
Rarely at the writing - mostly at collecting, transferring and formatting.
The collection round before the meeting
Three reminder mails per sub-project, then an outdated spreadsheet arrives anyway. Half the reporting week goes into collecting.
Every level builds its own picture
Sub-project in Excel, project in PowerPoint, PMO in a third format. Numbers can tip over with every transfer - and they do.
A snapshot instead of a direction
Whether the cost light just worsened for the third time in a row, no single report reveals. The history is buried in old file versions.
A new document for every committee
The same numbers, prepared three times: slides for the board, a PDF for the steering committee, a spreadsheet for controlling.
The reporting chain step by step - from work package to committee
This is how a report state everyone trusts comes together: feed-in from below, a scheduled report, actuals from time tracking, a trend across periods - and the right hand-out at the end.
Sub-projects report in the system - not by mail
Owners report right on the work package: traffic lights for overall status, schedule, cost and performance, plus the decision-needed flag with next steps. Finalised reports are locked and join a browsable history - and the project report shows the approved container reports as a summary. The contribution is there before anyone has to ask.
Project report
Summary of the approved container reports
Decisions needed: 1At the due date, the draft is already waiting
The reporting cadence is configured per project. When a report falls due, the system creates the draft automatically and reminds the project lead; the dashboard shows upcoming and overdue reports in a window of 14 days ahead to 30 days back. Snapshot fields come pre-filled from the last report or the current project value - and after the four-eyes approval, the reporting-date values are locked.
wk 33
approvedwk 35
approvedwk 37 · due today
Draft is waitingDashboard window: 14 days ahead, 30 days back - due and overdue reports at a glance.
The actuals come from the approved week
What your team submits as timesheets and managers approve - up to 500 sheets in one go if needed - appears as actual effort in the time reports: per project with budget context, as a per-employee monthly breakdown, up to the aggregated portfolio effort. The billable flag separates external from internal hours.
Approved hours become the actuals - down to the per-employee monthly breakdown.
The direction is in the report - not just the point
Across reports, the assessment trend emerges per dimension: overall, schedule, cost and performance, each as improved, worsened or unchanged against the last report. Meanwhile, KPIs arise from the project work itself and roll up to the portfolio - a cost light tipping for the third time gets noticed before the committee asks.
Assessment trend per dimension across the last reports - improved, worsened or unchanged.
One report state, four ways to the audience
The approved state remains the single source - handed out per audience: the project one-pager as a PDF for the steering committee, a Word document from your .docx template with live data including the latest status report, the portfolio dashboard with selectable widgets for management, the REST API for your corporate reporting. Nobody formats by hand anymore.
One source, four hand-outs - nobody formats by hand anymore.
And where a report flags a decision needed, the path is short: the steering committee decides in the minutes, and the decision becomes a trackable task.
One reporting chain, eight modules - one data foundation
In WORKSPACE.PM, reporting is not document craftsmanship but the platform working in concert: numbers emerge below, decisions emerge on top.
Project management
Resources & time
AI & automation
One data foundation - from feed-in to briefing document
Container reports, hours and KPIs feed the same base that reports, dashboards and documents are made of. Nothing gets retyped, nothing maintained twice.
And who writes all of this?
A reporting system only helps if it relieves the people reporting - not just the PMO.
The draft is already waiting
When a report falls due, the system creates the draft automatically and reminds the project lead. Snapshot fields are pre-filled from the last report or the live value - all that's left to write is the assessment.
Approved means locked in
The approval path runs through defined stages, and from approval on, the reporting-date values are locked. Status changes fire events that workflows can react to - every follow-up question meets evidence.
No handiwork for the committee either
The one-pager becomes a PDF in one click, Word documents are generated from .docx templates with live data, and every executive assembles the portfolio dashboard from widgets. Formatting is no longer a Friday job.
Related use cases
The report stands - this is what comes next.
Frequently asked questions about reporting
What PMOs and project managers want to know before switching.
Owners create container status reports with traffic lights for overall status, schedule, cost and performance, plus the decision-needed flag. Finalised reports are locked and historised - and the project report shows the approved container reports as a summary.
The reporting cadence is configured per project. A daily run creates due reports as drafts and reminds the project lead; the dashboard shows upcoming and overdue reports, and the “report due soon” event can additionally trigger your own workflows.
No - deliberately so: reports live in the system, where they stay current and verifiable. Hand-outs are deliberate: the one-pager as a PDF, Word documents from templates, dashboards for executives and the REST API for your BI. Reminders and events run automatically - sending a document remains a conscious act.
The assessment trend shows per dimension - overall, schedule, cost, performance - whether the situation improved, worsened or held against the last report. Container reports have a browsable history, and per project you can record earned-value figures at reporting dates and analyse them over time.
From time tracking: approved timesheets yield the actuals, analysed personally, per team, per project with budget context and aggregated up to the portfolio. The per-employee monthly breakdown serves controlling as evidence, and the billable flag separates external from internal hours.
Abolish the collection round
Start for free: set the reporting cadence, approve the first report, watch the trend - and in 30 days you'll know whether it fits.