Prioritize with three questions: is the finding supported, what could happen if it is left unresolved, and when does the team need an answer? Group related findings, assign a responsible reviewer, and verify the correction in the next issue.
Verify enough evidence to understand the issue
Open the affected drawing and linked references. Confirm that the finding describes the correct location, tag, revision, and design condition. Read enough surrounding context to identify a schedule note, exception, or alternative detail that may explain the difference.
Separate a supported inconsistency from a question that needs more information. Both can deserve follow-up, but they should not be presented as equally certain. If the source link is wrong or the conclusion is unsupported, record the reason instead of forwarding it as a confirmed defect.
The hotel door-rating example illustrates why the source pair matters: the schedule, plan location, surrounding separation, and applicable requirement all contribute to the review decision.
Assess consequence and urgency separately
Consequence is what could happen if the issue remains unresolved. Urgency is how soon the project needs a decision. A relatively small equipment discrepancy can become urgent before procurement; a major coordination question may need a longer design review even when installation is months away.
| Dimension | Ask |
|---|---|
| Safety and performance | Could this affect a required protective function, structural criterion, or intended system operation? |
| Design and scope | Could the answer change an opening, layout, equipment selection, or responsibility boundary? |
| Project timing | Is submission, purchasing, fabrication, or affected work approaching? |
| Confidence and context | Do the sources establish a conflict, or is key information still missing? |
Have the appropriate designer or specialist assess technical consequences. Do not infer a final safety or compliance decision from the software’s wording alone.
Group duplicates without losing affected locations
Several findings can share a root issue, such as the same equipment requirement repeated across plans and schedules. Group them around the decision that will resolve the conflict, while retaining every affected source and location.
Do not merge findings only because they have similar titles. Two door-rating questions may involve different wall conditions or exceptions. The grouping should help a reviewer resolve the underlying requirement without hiding separate design decisions.
A practical review log can include a parent question, related finding IDs, affected documents, responsible discipline, required decision date, and current response. Use your team’s existing issue or coordination process to maintain that record.
Write a question the designer can answer
Keep the follow-up specific: identify the conflicting information, show the sources, explain the possible consequence, and ask for the intended requirement. Avoid forwarding a long AI explanation without checking whether it supports the question.
The structural and mechanical plans show different elevations at the same floor area. Please confirm the governing datum and intended level, then identify any opening or connection details that need to change.
The reviewer should attach the actual sheet and location references from the project. This wording is an example, not a substitute for the source evidence or a formal design instruction.
Use explicit review decisions
In your review record, distinguish findings that are accepted for correction, rejected with a reason, awaiting information, or duplicated by another question. Record who made the decision and which evidence supported it.
For accepted findings, identify the responsible designer and the documents that need to agree after the correction. For rejected findings, preserve the context that resolved the question; it can explain an apparent inconsistency when the package is reviewed again.
Track uncertain findings until the missing information is supplied. Marking them “resolved” simply to shorten the list hides the work the team still needs to do.
Check the correction before closing the finding
Open the revised set and verify the intended change. Then check the dependent schedule, detail, specification, or consultant drawing. A correction in one source can leave the original conflict unresolved elsewhere.
The revision review guide describes how to trace these dependencies. Save the checked issue and closure decision so the next reviewer can understand what was resolved.
To evaluate the review process itself, track valid findings, duplicates, unsupported findings, and time to a decision. These measures are more useful than celebrating a shrinking queue or a growing finding count.