RFI, submittal and project action logs can appear complete while the next step remains unclear. A record may lack an owner, two unrelated entries may share an ID, or a due date may be stored as ambiguous text. This guide covers administrative record-quality checks that a project coordinator can perform before handoff or a weekly meeting. It does not determine engineering adequacy, contractual compliance, or construction readiness.
Start with an authorized export
Work from a copy of the approved register. A practical CSV might contain record ID, type (RFI, submittal or action), subject, source reference, logged date, due date, status, assigned owner, response/decision date and explanatory note. Preserve the export date and an untouched source copy. Do not upload proprietary plans, personal information, credentials, restricted owner records, or sensitive infrastructure documents to an unapproved destination.
10 administrative checks
- Blank and duplicate IDs. Flag them; do not automatically merge rows because a repeated identifier may represent revisions.
- Record category. Keep an RFI, a submittal and a decision item distinguishable. Their approval paths are not interchangeable.
- Source reference. Flag missing drawing, specification, correspondence or meeting references where one is expected. A citation field alone cannot establish that the underlying document is accurate.
- Owner assignment. Identify open actions without a named responsible party so the project lead can assign follow-up.
- Date format. Test for missing or unparsable dates and ambiguous values such as 03/04/26 if the locale is unknown.
- Due-date exceptions. Compare still-open entries with the review date, while treating approved extensions, contract calendars and schedule changes as separate matters requiring confirmation.
- Status consistency. Flag rows marked closed while a response or needed decision remains unresolved.
- Decision evidence. Separate “a reply was received” from “an authorized party accepted the decision.” Do not infer approval from silence.
- Source-version identity. Keep the original register, timestamp, filename and any checksum together. A SHA-256 fingerprint identifies file bytes, not the truth of the source facts.
- Exception handoff. Report each issue with its source ID, observed value, reason it needs review and a proposed clarification. Leave final judgment with the authorized team.
Fictional examples: what needs clarification?
These are invented rows, not client findings or verified delivery results.
| Example ID | Administrative issue | Suggested follow-up |
|---|---|---|
| RFI-014 | An open item has no owner | Confirm who is responsible for the next response |
| SUB-008 | The due-date text cannot be parsed consistently | Check the source date and the project's agreed date convention |
| ACT-021 | The entry is marked closed, but decision-needed remains true | Find the actual authorized decision or correct the register |
None of these checks classifies a construction activity as safe, approved, compliant or technically adequate.
How to make the results useful
An exceptions CSV should preserve the source ID and issue category for each flagged row. A short summary can separate missing fields, follow-up questions and entries with no exceptions under the defined checks. Every action should remain traceable to the supplied register, without inventing information or changing the source copy. The project team's controls and contractual requirements govern the actual response and closeout process.
For a separate worked example, see the fictional 12-record project evidence and decision audit. Its HOLD, REVIEW and SCREENED categories refer only to limited administrative checks.
Optional fixed-scope review
For a small approved, redacted CSV register, ATLAS Supply Co. offers a $99 Project Controls — 25-Record Action & Decision Scan. It covers one UTF-8 register of up to 25 administrative project records and 2 MB, flags defined ID, ownership, date, reference, open-item and decision exceptions, and includes human review. The stated target is three business days after the permitted input is accepted and scope is confirmed, subject to blockers.
For an agreed review of up to 50 records with limited supporting source copies, consider the $299 Evidence & Decision Pilot. To check scope before purchasing, request a preliminary project scope-fit review. Do not attach restricted project files to the initial inquiry.
Limits: This information and the named pilots are not licensed engineering, field inspection, design approval, structural or electrical safety assessment, construction authorization, contract interpretation, legal advice or permitting review. Clients retain responsibility for record accuracy and any required licensed or owner-directed review. ATLAS Supply Co. is a Bowleg Systems LLC offering.