On this page
Read the report’s basis before its score. A finding may be calculated correctly while addressing the wrong project, the wrong data date or a requirement that does not apply. The opening pages should make those conditions easy to inspect.
Establish what was reviewed
Look for the project identifier, source filename or file identifier, data date, report preparation date, software version and calculation settings. These dates serve different purposes: a report generated today may analyze an update from months earlier.
A hash identifies a particular file’s bytes. It does not independently establish when the file existed, who authored it or whether the activity status is true. Keep receipt records and source communications with the analysis.
Read in a useful order
- Which source was analyzed?
- What question was the analysis intended to answer?
- Which method and settings were used?
- Which requirements were applied?
- What was assumed, missing or unsupported?
- What evidence supports each finding?
- Who must decide or act next?
Distinguish finding types
| Statement | What it establishes | What remains to review |
|---|---|---|
| “Activity A has no successor in this file” | A reported network condition | Whether a link was omitted, external or intentionally absent |
| “The duration exceeds the stated rule” | A comparison, if scope and units are correct | Applicability, exceptions and any approval |
| “The completion forecast moves” | A result under the stated model | Causes, credible inputs and implications |
| “The schedule is acceptable” | A decision | The authority and basis for making it |
An automated report can supply evidence for a decision without being authorized to make the decision. Keep that distinction visible in review correspondence.
Sample the evidence trail
Choose a material finding and trace it back to the source activity, relationship, date or clause. Check the reported population and calculation units. If the report says a percentage of incomplete activities fails a rule, confirm which activity types were excluded.
For a fictional report listing twelve open ends, inspect several rows and ask whether the same project boundary was used for every relationship. Missing external-project data may explain some results. That explanation should be documented, not silently removed from the count.
Turn the report into actions
Assign each unresolved finding an owner, requested evidence and due date. Preserve responses and revised source versions. Separate corrected data from accepted exceptions and questions still awaiting a decision.
The GAO Schedule Assessment Guide is a reference for broader assessment practice. For practical next steps, use the audit checklist, AI output review and the Schedule Forensics library.
Share this article