Reports
A block document for the monthly and executive report, where the progress table, the S-curve and the risk matrix are bound live to the modules that hold them and re-read at the report’s own status date.
Who it is for. Planners and PMs who currently hand-assemble the monthly pack from five spreadsheets and a folder of screenshots, and need the result to still be defensible after the project has moved on.
What it is for
A status report is normally a snapshot pasted together once, quietly wrong the day after it goes out, and impossible to prove correct months later when a client questions a number in it. Rebuilding it every period from the schedule, the cost sheet and the risk register by hand is most of the work.
The block is bound, not pasted. Because every figure calls the same engine its source module uses and carries the timestamp it was last read, a report can be checked against the model it came from — and because issuing locks a numbered, PDF-archived revision that cannot be edited back into, last month’s report still reads last month’s numbers after the schedule has moved on.
What it does
Every line below is in the product today.
Sixteen block types, each bound to a live module
An S-curve, a cost/EVM table, a risk matrix, a DCMA scorecard and eleven others each call the same engine their own viewport does, so a report figure cannot disagree with the module it came from.
One status date overrides the project’s own
Every bound block resolves against the report’s own status date, not whatever data date the live project happens to be sitting at.
Issuing freezes a numbered revision
Issue takes the next revision number, guaranteed unique even if two people press Issue at the same moment, then archives the resolved document and a PDF under it.
A frozen revision cannot be quietly edited back into
Once issued, saving a document change is refused outright — the only way back to a draft is the explicit new-revision action, and every already-issued revision stays untouched.
Stale blocks are caught, not silently shipped
Each block carries the timestamp it was read at; export stops to ask whether to refresh first whenever a block has never been read or was read before the project last changed.
One resolver, however the number got there
A single block’s Refresh, a whole-document Refresh all, and the read Issue performs right before freezing all resolve the same way, so a manually refreshed table and the numbers baked into a revision cannot diverge.
A PDF that flows real text
The exported PDF is built as real text, not a picture of the page, so it is selectable and searchable — with DOCX, HTML and a print view from the same document.
Any report saves back as a reusable template
Saving a report as a template keeps every block’s binding but strips its resolved numbers and images, so it reproduces the query next period rather than replaying this month’s figures.
It reads and writes with
Cost
One cost dashboard that adds up cost assignments, resource assignments and activity fixed costs without double-counting them.
Risks
A portfolio register carrying threats and opportunities, each with its own matrix and strategies, linked both ways to the schedule.
S-Curves
Baseline, planned and actual progress curves built from activity dates alone — no cost, no budgeted units, no resource data required.
DCMA Checks
Run the DCMA 14-point assessment against your live schedule, a stored project, or a client’s XER — before they run it on you.
See it on your own schedule.
Send an XER before the call and we will import it and show you Reports running against your data.