Project understanding
You can see where delivery stands
Project Health reads the position from what the documents say, not from how the last update was worded.
Project Intelligence Workspace
Project Intelligence Workspace for delivery leaders.
Where a project actually stands is already written down — spread across status reports, charters and meeting notes nobody has time to reconcile. Docussentials turns those artifacts into a workspace per project, where health, risks, issues, decisions and actions sit together and stay current as new documents arrive.
No credit card required. Free plan available.
Status reportsProject chartersMeeting notesRequirementsRAID logsGovernance packs
Risks
Issues
Decisions
Actions
Intelligence layer
Project Control Center
Meridian Freight — Terminal Operations RolloutProject Health: At Risk
Project HealthExecutive ReadoutProject LaunchpadSaved Work
Your project already contains the signals that matter.
Docussentials reveals:
- Where the project stands
- What changed
- What needs attention next
How it works
Fragmented documents in. Structured project intelligence out.
The first step is work you have already done.
Source documents
Meridian Freight — Terminal Operations Rollout
Weekly status report
Weekly status report
Terminal Operations Rollout
Project charter
Project charter
Steering committee
Meeting notes
Meeting notes
Intelligence
Docussentials reads each document and extracts what matters.
Structured intelligence
Risks3
Issues2
Decisions2
Action items4
Extracted from the sample status report shown below, each with an owner and an impact.
Project Intelligence Workspace
Everything sits against the project
The Project Control Center keeps documents, analyses and outputs in one place, with Saved Work and Snapshot History behind them.
Actionable project outcomes
The analysis ends in a decision
An Executive Readout for leadership, and a Project Launchpad ordering what to do now, next and later.
The transformation
One status report in. Structured project intelligence out.
A real Docussentials output surface, rendered from a sample weekly status report for a fictional program.
What you upload
Meridian-Freight-Status-Report-Week-14.docxWeekly Status Report
Week 14 status. Terminal 2 pilot went live Tuesday with 40 users on the new dispatch flow. Adoption is ahead of plan but the integration to the legacy yard-management system is still running on the interim file transfer rather than the API. Vendor has now missed the API delivery date twice; latest commitment is week 17, which puts the Terminal 3 cutover at risk. Training completion sits at 62% against a 90% gate for the next wave. Two of the four regional supervisors have not scheduled their sessions. Finance has flagged that the contingency draw is now at 48%, mostly from the extended parallel run. We need a decision on whether Terminal 3 proceeds on the interim integration or waits for the API. Steering committee meets Thursday.
What Docussentials returns
Standard AnalysisProject Control Center
Docussentials Analysis
Meridian Freight — Terminal Operations Rollout
Source: Meridian-Freight-Status-Report-Week-14.docx
Generated from project source evidence: Meridian-Freight-Status-Report-Week-14.docx. Review findings, risks, decisions, and actions against the originating documents before executive or delivery use.
Status Update
At Risk
The Terminal 2 pilot is live and adopting ahead of plan, but a twice-missed vendor API delivery has pushed the integration onto an interim file transfer and now threatens the Terminal 3 cutover. Training completion is below the gate for the next wave, and contingency is approaching the halfway mark. A steering decision on whether Terminal 3 proceeds on the interim integration is required this week.
Key Accomplishments
- Terminal 2 pilot went live with 40 users on the new dispatch flow.
- Adoption in the pilot group is tracking ahead of the plan curve.
Key Risks / Issues
- Vendor has missed the yard-management API date twice; week 17 commitment puts Terminal 3 at risk.
- Training completion at 62% against a 90% gate for the next wave.
- Contingency draw at 48%, driven largely by the extended parallel run.
Decisions Needed
- Whether Terminal 3 proceeds on the interim file transfer or waits for the vendor API.
Upcoming Priorities
- Close the training gap for the two unscheduled regional supervisors.
- Confirm or replace the vendor's week 17 API commitment.
- Re-baseline the Terminal 3 cutover date once the integration path is settled.
Recommended Leadership Actions
- Take the Terminal 3 integration decision at Thursday's steering committee rather than deferring a further week.
- Escalate the vendor API slippage to the contract owner with a defined remedy date.
Executive Summary
Delivery is progressing where the team controls the work and slipping where it depends on the vendor. The pilot validates the operating model; the integration path does not yet support scaling it. The decisive item is not the training gap or the contingency draw — both are recoverable inside the current plan — but whether leadership accepts the interim integration for Terminal 3 or holds the cutover for the API.
Key Takeaways
- The pilot has proven the dispatch flow with real users, so delivery risk has shifted from product to integration.
- The vendor API is now the critical path for Terminal 3, not internal readiness.
- Training and contingency are trending unfavorably but remain inside recoverable range this period.
- A single steering decision this week determines the Terminal 3 date.
Risks
R-01
Likelihood: HighVendor yard-management API misses the week 17 commitment for a third time.
Impact: Terminal 3 cutover slips beyond the operational freeze window.
Recommended mitigation: Secure a contractual remedy date and prepare the interim file transfer as the accepted path for Terminal 3.
Owner: Program Director
R-02
Likelihood: MediumTraining completion stays below the 90% gate at the next wave checkpoint.
Impact: Next wave is deferred, compressing the remaining rollout schedule.
Recommended mitigation: Schedule the two outstanding regional supervisors this week and report completion daily against the gate.
Owner: Change Lead
R-03
Likelihood: MediumContingency consumption continues at the current rate through the extended parallel run.
Impact: Insufficient contingency remains for the final two terminals.
Recommended mitigation: Set an exit date for the parallel run and forecast contingency to completion at the next finance review.
Owner: Finance Business Partner
Issues
I-01
Terminal 2 is running on an interim file transfer instead of the intended API integration.
Impact: Manual reconciliation effort continues and the integration remains unproven at scale.
Recommended resolution: Hold the interim transfer as the supported path until the API is delivered and regression tested.
Owner: Integration Lead
I-02
Two of four regional supervisors have not scheduled training sessions.
Impact: Regional readiness cannot be confirmed for the next wave.
Recommended resolution: Regional Operations Manager to confirm both sessions within five working days.
Owner: Change Lead
Action Items
A-01
Priority: HighTable the Terminal 3 integration decision at Thursday's steering committee with both options costed.
Owner: Program Director
Suggested due date: Before Thursday's steering committee
A-02
Priority: HighObtain a written vendor commitment and remedy position on the yard-management API.
Owner: Commercial Lead
Suggested due date: Within 5 working days
A-03
Priority: MediumSchedule the two outstanding regional supervisor training sessions.
Owner: Change Lead
Suggested due date: Within 5 working days
A-04
Priority: MediumProduce a contingency forecast to completion covering the remaining terminals.
Owner: Finance Business Partner
Suggested due date: Next finance review
Decisions
D-01
Terminal 2 proceeds on the interim file transfer rather than holding for the vendor API.
Rationale: Preserved the pilot date and allowed the operating model to be validated with real users.
Owner: Steering Committee
Date or timing: Week 12
D-02
Parallel run extended to cover the full pilot period at Terminal 2.
Rationale: Protected dispatch continuity while adoption stabilised, accepting the contingency cost.
Owner: Program Director
Date or timing: Week 13
The document tells you what happened. Docussentials shows what it means.
The intelligence stays connected to the project.
Project Control CenterProject HealthExecutive ReadoutProject Launchpad
Actionable outputs
The same document, rewritten for the people who decide
An Executive Readout drops the delivery detail and keeps the outlook, the decisions being asked for, and what leadership should watch.
Executive ReadoutProject Control Center / Generate
Executive Leadership Brief
Meridian Freight — Terminal Operations Rollout
Source: Meridian-Freight-Status-Report-Week-14.docx
Leadership Summary
The rollout is working where we control it and slipping where we depend on the vendor. Terminal 2 is live and adopting ahead of plan, which validates the operating model. The open question is whether Terminal 3 goes ahead on the interim integration or waits for an API the vendor has now missed twice.
Delivery Outlook
At Risk. Internal readiness supports the current schedule; the vendor integration does not. The Terminal 3 date is recoverable if the integration path is settled this week and deferred if it is not.
Strategic Risks
- Third vendor miss on the yard-management API would push Terminal 3 past the operational freeze window.
- Sustained contingency consumption leaves insufficient cover for the final two terminals.
Decisions Needed
- Approve Terminal 3 on the interim file transfer, or hold the cutover for the vendor API.
Executive Actions
- Take the Terminal 3 integration decision at Thursday's steering committee.
- Escalate vendor API slippage to the contract owner with a defined remedy date.
Watch Items
- Training completion against the 90% gate for the next wave.
- Contingency draw rate once the parallel run closes.
The workspace
Everything sits against the project, not in your inbox
Project Control Center
One place per project holding its documents, analyses and outputs, so the current position is never spread across a drive and an inbox.
Standard Analysis
The core output: status, executive summary, key takeaways, risks, issues, decisions and action items, each extracted with owner and impact.
Executive Readout
A leadership-facing brief covering delivery outlook, strategic risks, the decisions being asked for, and watch items.
Project Health
A readout of where delivery actually stands, derived from what the documents say rather than from how the last update was worded.
Project Launchpad
Action items organized into what to do now, what comes next, and what is due later — so the analysis ends in a plan.
Saved Work and Snapshot History
Keep analyses against the project and reopen them later, with snapshot history showing how the position changed over time.
Pricing
Start free. Upgrade when it is carrying real work.
Every plan includes the full analysis output. Paid plans add saved work, downloads and a higher monthly volume.
Free
$0forever
Try Docussentials on a real document before committing.
- 4 document analyses per month
- 2 generated documents per month
- Standard Analysis output
- Executive Readout
- Not included: Saved work
- Not included: Downloadable outputs
Essentials
Most popular$19per month
For the practitioner running delivery day to day.
- 30 document analyses per month
- 15 generated documents per month
- Saved work and snapshot history
- Downloadable outputs
- Project Control Center and Project Health
Plus
$29per month
For consultants and leaders carrying several projects.
- 100 document analyses per month
- 50 generated documents per month
- Saved work and snapshot history
- Downloadable outputs
- Project Control Center and Project Health
Prices in USD. Plans are billed monthly and can be canceled at any time from your account.
Try it · Customer Support Portal Modernization
Follow one project through its evidence
Everything below is one sample project: a charter and three status reports written over the weeks that followed. Analyze any one of them, then see what Docussentials understands once it has read them all.
Step 1 — Analyze one document
One piece of this project’s evidence → structured intelligence
Public Demo · No Signup Required
See what Docussentials extracts from project documents
Choose a sample document and run a live analysis. No file upload or account needed.
Executive SummaryRisksIssuesDecisionsAction ItemsAssumptionsDependenciesRecommendations
Preview a sample RAID CSV
Static curated sample for demonstration. Not generated from your account or saved Project Launchpad output.
Step 2 — See what three reports mean together
Accumulated evidence → what is still true about the project
The report on the left is one of three in Customer Support Portal Modernization. Earlier reports already exist, and reading them together is what shows which risks keep returning, which got worse, and which quietly stopped being mentioned — none of which a single document can tell you.
See Customer Support Portal Modernization after the third status report →
See a project through five documents of its evidence →
Starting a project instead?
Project details → Do Now / Do Next / Due Later
Department process improvementSimple
What you tell Docussentials
A manual approval process causing delays, missed handoffs, and inconsistent tracking.
Project Launchpad output
Do Now
- Map the approval path as it actually runsThe real route, not the documented one
- Name the owner at each handoffEvery step needs one accountable name
Do Next
- Agree the target turnaroundOne measure the process is held to
- Standardize the request formatIncomplete requests cause most delays
Due Later
- Publish the tracking viewWhere anyone can see current status
- Review after one full cycleConfirm the delay actually moved
Key risks
- Staff keep using the old informal routeThe new process is bypassed · Process owner
Decisions needed
- Whether approvals are delegated below manager levelSets how much delay can be removed · Department head
New SaaS tool rolloutMedium
What you tell Docussentials
Rolling a new tool out across several departments: access, training, and adoption.
Project Launchpad output
Do Now
- Confirm which departments go firstA sequence beats a single big-bang date
- Get the access list rightWrong access is the most common blocker
Do Next
- Schedule training per departmentEach one works to different hours
- Write the switch-over messageWhat changes, when, and who to ask
Due Later
- Retire the tool it replacesA firm date, so both are not run
- Check adoption per departmentLow use is a training gap, not a tool gap
Key risks
- Departments adopt at very different ratesTwo systems run in parallel for longer · Rollout lead
Decisions needed
- Whether the old tool stays available after go-liveDetermines whether adoption lands · Sponsor
Executive reporting modernizationLarger
What you tell Docussentials
Leadership asks for monthly reporting that surfaces risks, decisions, and milestones.
Project Launchpad output
Do Now
- Agree what leadership decides from itReporting follows decisions, not the reverse
- Inventory what is reported todayMost of it will not survive the cut
Do Next
- Define the standard report structureOne format across every project
- Set who supplies what, and whenNamed contributors and a cutoff
Due Later
- Run one cycle in the new formatThen fix it before mandating it
- Retire the reports it replacesOtherwise both keep being produced
Key risks
- Contributors submit late or in the old formatThe cycle slips and the format erodes · Reporting lead
Decisions needed
- Whether project leads or the PMO own the dataSets where the effort and accountability sit · Sponsor
Curated examples. Project Launchpad builds these from your own project once you sign in.
Account Access
Sign in or create an account to access the authenticated dashboard experience.
Checking account session...
Start free
Your project already contains the signals that matter
Bring one status report. Docussentials reads it, surfaces what it means for delivery, and gives the result somewhere to live — against the project, alongside everything that follows it.
No credit card required. Nothing you analyze leaves your account.
Status reports, charters, meeting notes
Risks, issues, decisions, actions
Project Health, Executive Readout, Project Launchpad