On sheet JS-00a, the drawing index says 1:500. The title block says 1:100. The label beside the drawing says 1:500 again. What goes in the register? A document coordinator should keep all three readings and their source locations, then refer the difference to the drawing issuer. Picking one value would hide the question the reviewer needs to answer.
Construction document control keeps teams working from the right, approved information. Here we focus on one job worth handing off: turn a scanned drawing set into a register, a field-by-field comparison, and an exception list a project team can check.
Key Takeaways
- Received does not mean approved. Record the printed revision, intake status, and release status separately.
- Keep both sides of a discrepancy. A useful handoff shows what each source says, where it appears, and who should check it.
- Check more than the rows AI flags. In the run below, the model flagged the scale difference but marked a drawing title as matching when the original wording differed.
What Is Construction Document Control?
Construction document control is the process for identifying, reviewing, approving, issuing, and retaining project documents. It applies to more than drawings: specifications, requests for information (RFIs), and submittals also need a reliable record of what was received and what was authorized.
On a small project, one person may fill several roles. The document coordinator logs the files and routes open questions. The designated reviewer checks flagged and decision-critical fields against the original. Only the authorized issuer can release the confirmed revision through the project's agreed process. AI can prepare the first pass; it does not assume either approval role.
Review an Incoming Drawing Set in Five Steps
- Keep the originals. Record the received date, filename, and package identifier. Note whether the index is a separate file or a page in the PDF.
- Build the drawing register. Record each sheet number, title as printed, discipline if stated, printed revision, source filename and PDF page. Keep intake and approval statuses separate. If the same sheet number occurs under multiple revisions or drawing areas, preserve the distinct rows rather than merging them.
- Compare matching fields. Check the index and title block side by side. Record a drawing-view label separately from the title block. Log missing and unreadable fields instead of filling them from another sheet.
- Assign exceptions. Give each discrepancy an ID, source locations, next action, assigned reviewer, and status. Leave the reviewer unassigned if the project has not named one.
- Verify before release. Check the fields that affect release against the original even when AI reports a match. Record the reviewer, outcome, and date. Then use the existing approval, distribution, and retention process.
What to Hand Off to an AI Document Assistant
Start with the scanned drawing package and its index. Give the assistant a job with three deliverables, not just a request to convert a PDF:
| Deliverable | What to ask for | What stays with the team |
|---|---|---|
| Drawing register | Sheet identity, printed revision, source pages and intake status | Confirm the packet is complete and record approval separately. |
| Index-to-sheet comparison | Index value, title-block value and any distinct label on the drawing | Confirm the locations and whether each value really refers to the same field. |
| Exception list | Conflicting or unreadable values, sources, reviewer, status and next action | Assign a reviewer, resolve the discrepancy and document the decision. |
Build a drawing register, an index-to-sheet comparison, and an exception list. For each reading, record the source file, PDF page, and location on the page. Keep the index, title block and drawing-view labels separate. Flag missing, unreadable or conflicting entries without guessing. Use Unassigned when there is no named reviewer and Unconfirmed when approval is not evidenced. Do not authorize any drawing for use.
Before using a new scan, test a few easily checked fields to see whether the image is readable enough for this method. That is a pilot, not a substitute for checking the fields the project will rely on.
Worked Example: A Scanned Drawing Register
This example comes from a ChatExcel Max test on a scanned elevator addition drawing set. The PDF had 14 pages: a cover and 13 indexed sheets, including the drawing index on page 2. The original run logged 13 sheets, marked four as matching and nine for review, and listed 24 items to check. These are the model's initial classifications, not confirmed defects or a measure of accuracy. This was not a test in the international hiData web app.
What went into the register
| Sheet | Title on sheet | Printed revision | Source | Intake status | Approval status |
|---|---|---|---|---|---|
| JS-00a | Site Plan | First edition | Scanned drawing set, PDF p. 3; index on p. 2 | Needs review | Unconfirmed |
The fields in this English register excerpt have been normalized for the handoff. In the original output, the model used the index title for JS-00a and reported it as a match. The excerpt above uses the wording on the sheet itself, translated for this guide.
What made it onto the review list
| Item | Values and evidence | Finding | Assigned reviewer | Status / next action |
|---|---|---|---|---|
| H-01 · JS-00a scale | Index, p. 2: 1:500. Title block, p. 3: 1:100. View label, p. 3: 1:500. |
Flagged by Max | Unassigned | Open. Route to the drawing issuer to confirm the intended scale record. |
| QA-01 · JS-00a title | Index, p. 2: Site Layout Plan. Title block, p. 3: Site Plan. Both titles are translated from the original. | Added during review; the model marked it as matching | Unassigned | Open. Confirm the title to record; keep both originals in the meantime. |

The useful result was a starting point for review, not a release decision. The assistant put the scale readings in one row. A reviewer could then trace them to two PDF pages and catch a separate title difference the model missed.
What the Team Still Needs to Verify
Ask a colleague to retrace one flagged row and one row the model called a match. Check the sheet number, revision, source page, and value against the exact location on the scan. If the assistant used the index wording in place of the sheet wording, record both and reopen the comparison.
Use this construction document review packet as a working file. Keep open questions out of the approved record until the authorized reviewer confirms the decision. The intake output is not a drawing approval, an engineering review, or a measurement taken from the scan.
Frequently Asked Questions
Is a drawing log the same as construction document control?
No. A log is an inventory of drawings and revisions. The control process also ensures that the right people can review, authorize, distribute, and retrieve the correct version.
What if a scale or title appears differently in two places?
Record the readings and label the exact locations. Do not assume a view label, a title-block field, and an index entry are interchangeable. Ask the drawing issuer which value belongs in the official register. Do not use the scan to infer unmarked dimensions.
Did this test verify the international hiData app?
No. The case was run in ChatExcel Max. The graphic is an English transcription of that run, not a product screenshot. To try the method in the hiData workspace, use an approved sample and verify the extracted fields and page references before adopting the workflow.
Start With One Drawing Package
Choose a small set your team is authorized to upload. Use the brief above and check the output against the originals. For general project folders rather than drawings, see the project file register workflow.
Learn about hiData AI Sheets or open the hiData workspace to test a small sample.
