The Problem With Reviewing a 200-Sheet Drawing Set Page by Page

That is one of the challenges of quality assurance and quality control (QA/QC) in MEP engineering. Reviewing a drawing set isn’t just about checking whether each page looks right. It’s also about checking whether the information agrees across plans, schedules, notes, and other related documents.

And the larger the set, the harder that becomes to do consistently.

Consider a project with 200 drawings. An engineer reviewing that package needs to look beyond individual sheets and verify that related information lines up. Equipment references, schedules, tags, and notes may need to be checked against information elsewhere in the set.

Now consider doing that across several active projects, with deadlines approaching and other engineering work competing for the same time.

The challenge isn’t that engineers don’t know what to look for. It’s that the volume of information makes consistent checking difficult.

Why page-by-page review has its limits

Manual review remains an important part of engineering quality control. Experienced engineers bring context, technical knowledge, and judgment that a checking tool cannot replace.

But manual review also has practical limitations.

1. Cross-sheet consistency takes work.

A detail on one sheet may depend on information shown somewhere else. Finding the relevant reference, navigating between sheets, and confirming that the information agrees takes time and attention.

The more information a drawing set contains, the more opportunities there are for inconsistencies to go unnoticed.

2. Spot-checking creates a coverage trade-off.

When a team has limited time, it may prioritize critical areas or review a sample of the available information rather than examine every possible relationship.

That can be a reasonable response to workload pressure. But it also means the team needs to understand what has been checked, what hasn’t, and where further review may be warranted.

3. Repetitive checking competes with engineering judgment.

Senior engineers need time to solve technical problems, interpret design intent, and make decisions that require experience.

Repeatedly checking information across sheets is part of the job, but it competes for the same attention. Under deadline pressure, that trade-off becomes more difficult.

4. Consistency becomes harder to maintain across projects.

Different reviewers may approach a drawing set differently. Teams can have established checklists and procedures, but the application of those checks still depends on the review process, available time, and the information being examined.

The question isn’t whether engineers are capable of doing the work. It’s whether the process makes consistent review practical at the scale of the work they handle.

Start with a better question: What actually gets checked?

Rather than focusing only on how long a drawing review takes, engineering leaders should look at how the review is performed.

A few questions are worth asking:

• How much of each issued drawing set receives a meaningful check?
• Which relationships between plans, schedules, and notes are most difficult to verify manually?
• How do reviewers record what they’ve checked and what still needs attention?
• Where does the team rely on individual knowledge rather than a repeatable process?
• What happens when project volume increases but review capacity stays the same?

These questions help distinguish between a workload problem and a process problem. Often, both are involved.

They also provide a starting point for deciding which parts of QA/QC could benefit from a more systematic approach.

Where automation can help

Automated drawing checks offer a way to support repeatable parts of the review process.

For example, a tool can help identify potential inconsistencies across supported information in a PDF drawing set, giving an engineer specific findings to investigate rather than requiring every check to begin from scratch.

The important distinction is that automated checking isn’t the same as a complete engineering review. Results still need to be interpreted in context, and the scope of the checks matters.

The most useful starting point isn’t an ambitious promise to automate everything. It’s a specific question about a real drawing set.

Which checks consume the most repetitive effort? Which are suitable for automation? Can the resulting findings be reviewed and verified by the engineering team?

Those questions can be tested on the firm’s own drawings.

Make the process measurable

If an engineering firm wants to improve its QA/QC process, it needs a baseline.

Start with a representative drawing set. Document the existing review approach, the checks performed, the time involved, and the types of issues found. Then compare that process with a more systematic or automated check.

Look at what was identified, what was missed, which findings were useful, and how much additional work was required to validate them.

That gives the team evidence to assess whether the approach improves coverage, consistency, or the use of engineering time.

It also avoids relying on generic industry estimates that may not reflect the firm’s actual workflow.

At RedMark, this is the problem we are working on: helping MEP engineering teams check PDF drawing sets more systematically and identify potential issues that deserve an engineer’s attention.

The starting point is always the drawings themselves.

How does your team approach QA/QC on large drawing packages? Do you have a repeatable process for checking consistency across sheets, or does the approach depend largely on the reviewer and the time available?