First report — Status Report — week ending August 23
Everything in it is new — there is nothing to compare against yet.
Sample project · Customer Support Portal Modernization
Analyzing one document tells you what that document says. The useful question is what is still true by the third status report — what keeps coming back, what got worse, and what quietly stopped being mentioned. This is a worked example of that.
This continues the document you just analyzed
The public demo analyses one status report from Customer Support Portal Modernization. That report — Status Report — week ending September 20 — is the most recent of the three below. Everything on this page is what Docussentials understands once it has read all three, not just that one.
This is illustrative sample data
“Customer Support Portal Modernization” is a sample project used throughout the Docussentials demo. It is not a real customer project and contains no customer data. The understanding below is presented exactly as the product presents it for a real project.
First report — Status Report — week ending August 23
Everything in it is new — there is nothing to compare against yet.
Second report — Status Report — week ending September 6
Recurrence becomes visible; vendor staffing appears for the first time.
Third report — Status Report — week ending September 20
One risk has now been raised three times; one earlier risk has gone quiet. This is the report analyzed in the demo above.
Up to date with this project's evidence
Reflects every analysis saved to this project.
The most recent report states an overall status of Amber while one risk has been raised in all three reports and one issue was reported as worsening.
Based on 3 analyses saved to this project.
Risk
CRM integration scope remains unconfirmed, and the schedule depends on it.
Mentioned in all three analyzed reports. Docussentials has not been given evidence that it was addressed between them.
Issue
Vendor staffing confirmation has slipped from 2 roles outstanding to 5.
The reports themselves stated a higher number of outstanding roles in the later period. This is what the documents said, not an assessment of severity.
Action
Obtain Customer Operations sign-off on the self-service scope.
Appears in the first and most recent reports but not the one between them. Docussentials cannot tell whether it lapsed or was simply not written down.
Decision
Portal launch moved from the October release window to the November window.
Appears only in the most recent report. There is no earlier evidence to compare it against.
Risk
Support agent training capacity may be insufficient to cover all agents before launch.
Present in earlier reports and absent from the most recent one. Docussentials has no evidence that it was resolved — only that it stopped being written about.
What this is not
Docussentials reads what the reports say. It does not know whether a risk was actually addressed, and it never treats a condition disappearing from a report as evidence that it was resolved — only that it stopped being written about. Every statement above is traceable to a specific report.
Try it on your own documents
Create a project, add a document, then add a second related one. The accumulated view above is what you get.
Get started free →