For Architects · Progress Set Review

Progress Set Review That Catches Issues While They're Still Cheap to Fix

Issues caught at 30% cost minutes. The same issues caught at 100% cost weeks. Helonic shifts the curve.

MG
Manas Gandhi · Co-founder & CTO, Helonic · Reviewed May 2026

Every design firm intends to do thorough internal reviews at DD and 60/95% CD milestones. The reality is those reviews happen late, get rushed, or get skipped under deadline pressure. Helonic gives the team a tireless internal reviewer who reads the set at every milestone, surfaces the issues consistently, and gets sharper as the documentation evolves.

The economics of catching issues early

An issue caught at 30% CD is a five-minute conversation. The same issue caught at 100% CD is a sheet revision, a coordination meeting, and possibly a permit re-submittal. The architects we work with universally know this but struggle to staff thorough milestone reviews when production deadlines are competing for the same hours.

Milestone review workflow

1

Configure milestone in Helonic

Select the milestone (30/50/80/95/100%) and Helonic loads the appropriate depth of checks.

2

Upload the set

Drag in the current drawings and specs. Helonic associates them with the project record.

3

Review milestone findings

Findings sorted by severity and by whether they persist from a previous milestone. Resolved issues from prior milestones are tracked.

4

Export milestone report

Generate a structured milestone QA report for the project record and team distribution.

How Helonic helps

Catches issues earlier in the design process

Helonic runs at 30%, 50%, 80%, or any milestone. Each pass surfaces issues at the right depth for that level of development.

Tracks issues across milestones

Issues persist in Helonic across milestones. An issue surfaced at 30% that wasn't resolved by 60% gets escalated automatically.

Calibrated to the milestone

Helonic doesn't expect 30% drawings to look like CDs. The check rules are calibrated to what's reasonable at each level of development.

Documents the review for the project record

Every Helonic pass produces a structured report that becomes part of the project QA record - useful for both internal QA and E&O documentation.

Key features for this workflow

Milestone-appropriate rule sets (30/50/80/100% CD)

Issue persistence across milestones with auto-escalation

Discipline coordination depth proportional to LOD

Schedule completeness tracking through the design process

Specification development cross-check at each milestone

Project record export at each pass

Example issues Helonic catches

Real-world issues detected by AI analysis, specific to architects running progress set review:

At 30% CD: site plan shows building footprint that doesn't match the structural grid layout on S-100 - coordination gap to resolve before DD

At 50% CD: door schedule includes 247 doors but the partition plan shows 219 - count drift needs reconciling

At 80% CD: wall types W-1 through W-5 defined on the wall type sheet but W-6 appears on plans without definition

At 80% CD: equipment schedule on M-401 lists three rooftop units but only two locations are shown on the roof plan

At 95% CD: code summary still cites 2018 IBC but adopted-edition tracker shows project is under 2021 IBC for permit

At 100% CD: detail callouts on A-401 reference details 5/A-602 and 7/A-602, but A-602 only goes through detail 6

What construction professionals told us

The architects we talked with all said the same thing about milestone reviews: 'we know we should, we mean to, we don't.' The barrier wasn't will - it was time. The thing they wanted was a reviewer who could do the first 80% of the work in the background.

Conversations with principals and project architects at firms ranging from boutique residential to large institutional practices.

FAQs

What if our milestones don't follow 30/50/80?

Helonic can be configured for any milestone schedule. The check depth scales smoothly across LODs.

Does it overload the team with findings at early milestones?

No - early milestone checks are calibrated to surface only the issues meaningful at that stage. The model expects 30% drawings to be incomplete and won't flag missing details that aren't yet supposed to be drawn.

Can we share milestone reports with the owner or consultants?

Yes. Each milestone export is a structured PDF that's appropriate for sharing externally, with internal-only items kept private.

MG

Manas Gandhi

Co-founder & CTO, Helonic

Manas is the co-founder and CTO of Helonic, where he leads engineering and AI research for construction drawing analysis. He works directly with structural, MEP, civil, and fire protection engineers to translate the way they review drawings into AI systems that flag the issues that actually matter in the field. Before Helonic, he built machine learning pipelines for technical document understanding and has spent the last several years interviewing licensed design engineers and discipline leads to ground product decisions in real practice rather than industry assumptions.

Areas of focus
  • AI for technical document understanding
  • Cross-discipline coordination workflows
  • Code compliance automation (IBC, NEC, NFPA, IPC, IMC, ASCE)
  • Structural and MEP drawing review systems

How this page was researched: Conversations with principals and project architects at firms ranging from boutique residential to large institutional practices.

Last reviewed by Manas Gandhi · May 2026

Other use cases for architects

Progress Set Review for other roles

Try Helonic on progress set review for your next project

See how Helonic catches the issues that matter most to architects. Upload your drawings for a free analysis.