WHAT’S YOUR NUMBER?™
Project Record Completeness Score for Construction Projects
Your project has a percent complete. Your project record should too. MSPai evaluates expected project information and produces a clear view of what is present, what requires investigation, and what should be resolved.
What is a Project Record Completeness Score?
The Project Record Completeness Score™ is a measurable view of whether the construction project record contains the information expected for the project’s stage, scope, contractual requirements, commissioning plan, and turnover obligations.
It is not a count of uploaded files. Thousands of files can exist while required records remain absent, incomplete, duplicated, unissued, disconnected, or unresolved. The score focuses attention on the relationship between what should exist and what can be confirmed in the governed record.
A folder is not certainty. A data dump is not closeout.
What construction record completeness can reveal
MISSING
Expected information that cannot be located in the record.
INCOMPLETE
Records that exist but lack required detail, approval, attachment, or status.
UNRESOLVED
Open questions, requirements, or decisions that still require action.
CHANGING
Signals developing across RFIs, drawings, submittals, meeting records, and correspondence.
DEFICIENT
Information that does not align with the defined requirement or governing source.
AT RISK
Gaps that could affect cost, schedule, commissioning, turnover, or operations.
How the score is developed
- Define expectations. Establish the records expected from contracts, specifications, project stage, owner requirements, and turnover criteria.
- Govern the record. Collect and organize project information into a consistent owner-controlled structure.
- Analyze with MSPai. Examine the governed record for expected information and connected context.
- Classify findings. Separate confirmed records from items requiring investigation, clarification, or action.
- Resolve and update. Put findings in front of the responsible parties, preserve the response, and update the score as the record changes.
The score is an executive indicator, not a substitute for professional judgment. Each finding should be reviewed against the project’s actual requirements and source documentation.
Construction document categories evaluated
- Contract documents and owner requirements
- Drawings, specifications, revisions, and addenda
- RFIs, submittals, logs, and approvals
- Change events, directives, and decision records
- Quality, testing, and inspection records
- Commissioning, training, warranty, and O&M records
- As-built information and asset data
- Compliance and turnover documentation
Why measure completeness before closeout?
Waiting until substantial completion compresses the time available to recover missing records and resolve open requirements. A completeness score creates a recurring management signal during construction. Owners can see where record risk is accumulating and direct attention while the responsible parties and supporting facts are still available.
Questions the score can support
- Which required documents have not been confirmed?
- Which contractors still owe project information?
- Which commissioning or warranty requirements remain open?
- Where are changes developing across the record?
- What could prevent complete turnover?
- Which findings require an owner decision?
Project Record Completeness Score questions
Is the score an industry benchmark?
No. It is a project-specific measurement based on the expected information and findings for the analyzed record.
Can the score change?
Yes. The record evolves as information arrives, issues are resolved, and requirements are completed. The score should reflect the current governed record.
When can a project be analyzed?
Analysis can begin during planning, design, construction, commissioning, or closeout. Earlier analysis creates more time for resolution.
Explore the project-record framework
What’s Your Number?™
Put an actual project record through MSPai and see what requires attention.