HelonicHelonic
Lean Construction

Lean Construction Meets Plan Review: Eliminating Waste in Preconstruction

Helonic is an AI construction drawing analysis platform for teams researching lean construction plan review during drawing review.

Applying lean principles to document review for faster, more reliable preconstruction outcomes

What are lean principles in construction plan review?

Lean construction, adapted from the Toyota Production System, has transformed how forward-thinking teams approach project delivery. The core principle is simple: maximize value while minimizing waste. In construction, lean practices have been shown to reduce project costs by 6% to 16% and improve schedule performance by 10% to 20%.

Yet most lean construction efforts focus on the field, Last Planner System, pull planning, daily huddles, and visual management. Preconstruction activities, including plan review, remain largely untouched by lean thinking. This represents a massive opportunity, because waste in preconstruction compounds throughout the project lifecycle. An error missed during plan review doesn't just waste review time, it generates RFIs, rework, and delays during construction.

Lean Construction Impact

  • 6% to 16% cost reduction on lean-managed projects
  • 10% to 20% schedule improvement with lean practices
  • 57% of preconstruction time is non-value-adding activity
  • 10x cost multiplier for errors caught late vs. in preconstruction

How do the eight lean wastes apply to plan review?

Lean manufacturing identifies eight categories of waste (DOWNTIME). Here's how each manifests in the plan review process:

1. Defects: Missed Issues

The most consequential waste in plan review is failing to catch an error. Every missed conflict, dimensional error, or code violation that reaches construction becomes an expensive defect, an RFI, change order, or rework event. Studies show that manual plan review catches only 40% to 60% of reviewable issues, meaning 40% to 60% of catchable problems pass through to construction.

2. Overproduction: Reviewing What Doesn't Matter

Not all review comments carry equal value. Spending time flagging minor drafting inconsistencies while missing major coordination conflicts is a form of overproduction, producing review output that doesn't contribute to project quality. Effective review prioritizes high-impact items first.

3. Waiting: Review Queue Delays

Documents sitting in someone's inbox waiting for review is pure waste. On many projects, drawings spend more time waiting in queue than actually being reviewed. The average submittal review cycle of 14 to 21 days often includes only 2 to 4 hours of actual review time, the rest is queue time.

4. Non-Utilized Talent: Experts Doing Clerical Work

When senior engineers and experienced project managers spend hours on mechanical tasks, checking dimensions, verifying cross-references, counting schedule entries, their expertise is wasted. These are tasks that technology can handle, freeing human experts for the judgment-intensive analysis where their experience is irreplaceable.

5. Transportation: Document Handling

Every time a document is emailed, downloaded, printed, marked up, scanned, and re-uploaded, waste accumulates. Modern cloud-based review platforms eliminate these non-value-adding document movements, but many teams still rely on email-and-PDF workflows.

6. Inventory: Backlog of Unreviewed Documents

A growing pile of unreviewed submittals and drawing sets is the plan review equivalent of excess inventory. It represents work that's been started (by the design team) but not completed (by the review team), creating risk and consuming mental bandwidth.

7. Motion: Inefficient Review Workflows

Flipping between multiple PDF files, manually cross-referencing sheets, and searching for related details across a 500-page set, these are all non-value-adding motions that consume reviewer time without producing useful output. Digital tools that keep the whole set in one view cut this motion waste substantially.

8. Extra Processing: Redundant Reviews

Multiple people reviewing the same items without coordination, re-reviewing unchanged portions of revised sets, and conducting reviews at levels of detail that exceed what the project requires, all represent extra processing waste.

How does kaizen change a plan review process?

Kaizen, the practice of continuous, incremental improvement, can transform your plan review process when applied systematically.

  • Measure current state: Track review turnaround time, issues found per sheet, issues missed (discovered during construction), and rework events attributable to document errors. You can't improve what you don't measure.
  • Identify root causes: When issues are missed during review, conduct a brief root cause analysis. Was it a process gap, a knowledge gap, a time pressure issue, or a technology limitation?
  • Implement small changes: Don't overhaul your entire review process at once. Introduce one improvement per project cycle, a new checklist item, a technology tool, a changed workflow step, and measure its impact.
  • Standardize what works: When an improvement shows measurable benefit, standardize it across all projects and teams. Document the improved process and train the team.
  • Repeat: Lean is never "done." Each improvement cycle reveals new opportunities. The goal is a culture of continuous improvement, not a one-time optimization.

What is value stream mapping for plan review?

Value stream mapping (VSM) is a lean tool that visualizes every step in a process, categorizing each as value-adding, necessary non-value-adding, or waste. Applied to plan review, a typical value stream map reveals that only 15% to 25% of the total review cycle time is actual value-adding review work. The rest is queue time, handoffs, document handling, and rework of the review process itself.

A simplified plan review value stream might look like this:

  • Documents received → Queue time (2 to 5 days), Waste
  • Downloaded and organized → Setup time (30 to 60 min), Necessary non-value-adding
  • Initial review and analysis → Review time (4 to 8 hours), Value-adding
  • Comments compiled and formatted → Processing (1 to 2 hours), Necessary non-value-adding
  • Sent to design team → Queue for response (5 to 10 days), Waste
  • Response reviewed → Follow-up review (1 to 2 hours), Value-adding

Total elapsed time: 10 to 20 days. Actual value-adding time: 5 to 10 hours. That's a value ratio of less than 10%, meaning over 90% of the elapsed time is non-value-adding. This is where technology and process improvement can make a dramatic difference.

How does Helonic cut waste in the plan review value stream?

Helonic directly addresses multiple waste categories in the plan review value stream. By automating the mechanical aspects of document analysis, dimensional checking, cross-reference verification, code compliance screening, and coordination analysis, Helonic eliminates motion waste, reduces defects (missed issues), and compresses the value-adding review cycle from days to minutes. Your team's experts can focus on the high-judgment analysis where their experience matters most.

Practitioner insight

We mapped our own submittal process once and it was embarrassing. Eleven days end to end, four hours of somebody actually reading the thing. Everybody had been arguing about how to review faster, and the review was never the problem. The package sat in an inbox for a week because nobody had said out loud whose week it was. Naming the owner fixed more than any checklist we wrote.

Source: Conversations with preconstruction managers and lean practitioners who have value stream mapped their own document review cycles, synthesized from Helonic customer interviews, Q2 2026.

Lean Plan Review FAQ

How do you measure waste in a document review process?
Compare elapsed time against hands-on review time. Log when a set arrives, when a reviewer actually opens it, how many hours they spend, when comments go out, and when the response comes back. On most projects the hands-on portion is well under a quarter of the calendar time, and the rest is queue. That ratio is the number to attack first, because shortening a review that spends nine days in an inbox changes nothing.
What is a realistic turnaround target for plan and submittal review?
Set an internal target at roughly half your contractual allowance, so seven days against a fourteen-day clause. The buffer absorbs the one complex package per month that genuinely needs design team input, and it keeps the routine ones from drifting to the deadline because the deadline exists. Publish the running average weekly. Visibility does more for turnaround than any process change, because nobody wants to own the slow column.
How does the Last Planner System apply to preconstruction?
The same way it works in the field: the people doing the work commit to specific handoffs, and you track how many commitments they keep. Applied to reviews, that means each reviewer commits to which packages they will complete next week, constraints get named out loud before the week starts, and missed commitments get a root cause rather than a shrug. Percent plan complete works as a metric for a review team too.
Does a faster plan review mean a lower quality review?
A faster plan review keeps its quality if the time comes out of queue and handling rather than out of analysis. Cutting the days a set sits in an inbox, the hours spent cross-referencing sheets by hand, and the duplicated passes by three reviewers on the same items leaves more time for judgment, not less. Quality drops when you compress the analysis itself, which is why the metric to protect is hands-on hours per sheet, not calendar days.
Which parts of plan review should be automated first?
The mechanical cross-checks: schedule against plan, dimension against dimension, callout against detail. They're repetitive, they follow rules, and they're where a tired reviewer at sheet 180 stops being reliable. Helonic handles that layer and returns findings with sheet references. Keep constructability, sequencing, and design intent with your people, because those depend on project context no tool has and carry consequences somebody has to own.
MS

Milind Sagaram

Co-founder & CEO, Helonic

Milind is the co-founder and CEO of Helonic, where he leads product and go-to-market for AI-powered construction drawing analysis. He works closely with general contractors, project managers, estimators, and owners to understand how drawing quality drives project outcomes - and where AI can reduce RFIs, change orders, and rework. Milind has interviewed hundreds of construction professionals across project delivery roles, from preconstruction estimators at ENR top-400 contractors to facilities directors at institutional owners, and uses those conversations to shape both product direction and the way Helonic talks about the work.

Areas of focus
  • Construction project delivery and preconstruction
  • RFI and change order economics
  • Owner and GC workflows for drawing QA/QC
  • Estimating risk and bid-stage scope assessment

How this page was researched: Re-checked against Lean Construction Institute guidance on the Last Planner System and percent plan complete, published lean construction cost and schedule outcomes, and value stream mapping practice applied to document review cycles.

Last reviewed by Milind Sagaram · August 10, 2026

Keep exploring

See what Helonic catches on your drawings

Upload your PDF set and we'll walk you through every coordination conflict, code gap, and dimension mismatch our AI flags.