HelonicHelonic
Best Practices

Permit Set vs IFC Set: They Are Not the Same Document, and Reviewing Them the Same Way Is a Mistake

The permit set proves the building can be built legally. The IFC set proves it can be built. They serve different audiences and need different reviews.

Two Documents, Two Audiences, Two Purposes

A permit set is reviewed by a plan checker. The plan checker has 15 minutes per sheet. They're looking for code compliance, egress, fire ratings, accessibility, structural calcs, energy code, not coordination quality. A drawing can be perfectly permittable and unbuildable.

An IFC set is read by a contractor. The contractor reads every detail to prepare the bid, then again to build the work. They need dimensional accuracy, complete sections, every interface detailed, and a coordination story across all disciplines. An IFC set that's only as detailed as the permit set will generate hundreds of RFIs.

Many design firms use the same drawing file for both, just at different completion levels. The permit set is the design at 75%, the IFC set is the design at 95-100%. The reviewer has to know which version they're reviewing and what to look for. A common mistake is reviewing a permit set as if it were the IFC set, finding hundreds of incompletenesses, and confusing everyone. Or reviewing an IFC set as if it were the permit set, missing coordination problems because the reviewer is focused on code compliance.

What the Permit Reviewer Cares About

The plan checker focuses on items that affect public safety and code compliance. Their checklist is jurisdictional, but it generally includes:

  • Occupancy classification, construction type, and allowable height/area
  • Egress paths, exit widths, and travel distances per IBC 1005
  • Fire-rated assemblies and the listed UL designs they reference
  • Accessibility per ADA and local accessibility codes
  • Energy code compliance (envelope, HVAC, lighting, water heating)
  • Structural lateral and gravity load resistance with stamped calcs
  • Plumbing fixture counts, water service sizing, and backflow protection
  • Electrical service sizing, panel schedules, and grounding

The reviewer is not looking at how the drawings interrelate. They're not flagging that the structural plan shows a column the architectural plan doesn't. They're not noticing that the mechanical plan shows ductwork in a corridor that the architectural plan shows is finished height 9'-0". Those are coordination issues. They live in the IFC review, not the permit review.

What the Contractor Cares About

The contractor reads the IFC set with one question: can I build this? Their checklist is different:

  • Are dimensions complete and self-consistent?
  • Is every detail referenced and drawn?
  • Do the discipline drawings agree at every interface?
  • Are schedules complete with no "TBD" or "by others" gaps?
  • Are specifications cross-referenced correctly to the drawings?
  • Are sequence-dependent items detailed (waterproofing, fire-stopping, vapor barriers)?
  • Are the existing-conditions and demolition drawings reconciled?
  • Is the project phasing buildable with the means and methods available?

The IFC review needs to come from a contractor's perspective. If your reviewer is a designer, they will tend to confirm what they drew was right rather than question whether it's buildable. The most effective IFC reviews bring in someone who has built similar projects and can spot the constructability gaps the design team can't see.

The Permit-to-IFC Delta

Between permit submission and IFC issuance, the drawings change. Sometimes a lot. Plan check comments come back. Owner-driven scope changes happen. Value engineering happens. Coordination work happens. The IFC set is a different document from the permit set, and the team needs to track what changed.

The right approach: maintain a delta log between the permit set and the IFC set. Cloud the changes on the IFC drawings. Issue an addendum or revision narrative that explains what moved, what got added, what got deleted. Without this, contractors bid the IFC set without realizing what changed since they may have started planning from the permit set or an earlier draft. See our coverage in drawing version control.

Permit Review vs IFC Review

  • Permit review: code compliance, life safety, structural adequacy, accessibility
  • IFC review: coordination, constructability, schedule completeness, dimensional accuracy
  • Permit set is a hypothesis. IFC set is a contract.
  • Different reviewers, different checklists, different deliverables

When the Same Drawings Have to Do Both

Some jurisdictions allow combined permit-and-construction documents, especially on smaller projects. In those cases, the design team is producing one document that serves both purposes. The reviewer has to do both reviews simultaneously: code compliance from a plan-checker perspective, coordination from a contractor perspective.

That's twice the review work, not the same work. The teams that handle this well allocate two separate review passes. Pass one is code compliance against the published checklist for the jurisdiction. Pass two is coordination, dimensional, and constructability. Trying to do both in one pass guarantees you miss things in both directions.

Practitioner insight

The permit set proves you are allowed to build it. It does not prove you can. I have had jobs where plan check cleared in one round and we still wrote two hundred RFIs, because nobody ever asked whether the details closed. Those are two different questions and they want two different readers.

Source: Conversations with project managers and plan check consultants handling commercial permitting, 2026.

Permit Set and IFC Set FAQ

What is the difference between a permit set and an IFC set?
A permit set is prepared to prove code compliance to a plan checker, and an issued for construction set is prepared to build from. The permit set has to carry occupancy and construction type, egress, rated assemblies, accessibility, energy compliance, and stamped calculations. The IFC set carries all of that plus complete dimensions, every interface detailed, and agreement across disciplines. The same drawing files often produce both at different completion levels, which is where the confusion starts.
Can you build from a permit set?
You can start work the permit covers, but a permit set is rarely complete enough to build a whole job without generating a large volume of RFIs. Plan check confirms the design is lawful, not that it is coordinated or dimensionally resolved. Teams that go to the field on a permit set usually end up pricing the gaps as change orders. Where schedule forces it, limit exposure to scopes that are genuinely finished, such as site work and foundations.
What changes between permit submission and issuance for construction?
Plan check corrections, owner scope changes, value engineering, and the coordination work that finishes the set. That delta can be small or it can be a substantial redesign, and bidders often started from the permit set. Keeping it from becoming a claim takes a delta log, clouded revisions, and a written narrative saying what moved, what was added, and what was deleted. Without that, contractors price one document and build from another.
Who should review an IFC set, and what should they look for?
Someone who has built the building type, reading for whether it can be built as drawn. That means dimensional consistency, details actually drawn rather than just referenced, agreement between disciplines at every interface, schedules with nothing left to be determined, and sequence dependent work like waterproofing and firestopping detailed in the right order. A designer reviewing their own set tends to confirm intent rather than test buildability.
How do you run a code review and a coordination review without doubling the schedule?
Run them as two passes with two checklists, and avoid having one person hold both in their head at once. Code compliance against the jurisdiction's published criteria and coordination against a constructability checklist are different reading modes, and blending them means missing items in both directions. Helonic runs both kinds of pass over the same set and reports them separately. The plan checker and the engineer of record still decide compliance.
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: This review checked plan review scope, drawing issuance terminology, and constructability review practice against common jurisdictional plan check criteria and contractor bid practice.

Last reviewed by Milind Sagaram · July 2026

Run Both Reviews Without Doubling the Time

Helonic runs separate code-compliance and coordination passes on the same set, surfacing the items each kind of reviewer would flag. The permit reviewer and the contractor see different reports.

Book a Demo

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.