A redlined plan set is not a rejection. It is the AHJ telling you exactly what to change to get approved. Most installers treat it like bad news and let it sit in an inbox for two or three days before anyone touches it. That delay, not the corrections themselves, is what turns a one-week resubmission into a three-week one. This guide covers what to do the day the redlines land: how to read the plan checker’s markup, which comments to fix first, how to keep your design team and your permit tech talking to each other, and how to track versions so the AHJ never has to ask “which set is this.”
Direct answer. A solar permit redline is the plan checker’s markup on your submitted plan set, showing exactly what fails code or is missing information. Handle it in four steps: log every comment into a single tracked list, sort by severity (code violation versus missing documentation versus formatting), route each item to the person who owns the fix, and resubmit a version-stamped set with a point-by-point response letter. Sets that resubmit with a response letter clear second review faster because the checker can confirm each item without re-reading the whole plan set.
TL;DR
- Redlines are corrections, not denials. Most jurisdictions give you a defined resubmission window, often 90 to 180 days, before the application expires.
- Log every comment in one tracked list on day one. Do not let comments live only inside a marked-up PDF that one person can see.
- Sort by severity first: code violations that block approval, missing documentation, then formatting or labeling nitpicks. Fix in that order.
- Route each comment to the owner who can actually fix it: structural PE, electrical designer, or the person who filed the interconnection paperwork.
- Version every resubmission (Rev 1, Rev 2) and include a point-by-point response letter. Reviewers approve faster when they can check items off instead of re-reading the set.
- A second rejection round almost always traces back to one thing: a fix that was made in the drawing but not verified against the spec sheet, wire schedule, or interconnection application.
This article is written for Mike, the US installer or EPC project manager who owns permit review cycles across multiple jurisdictions. If you have not yet been rejected and want to know why AHJs reject plan sets in the first place, our companion piece on common AHJ plan set rejection reasons covers the 6 failure categories. This guide picks up after the redlines already arrived.
What a Redlined Plan Set Actually Looks Like
Plan checkers do not send a plain-text list of problems. They send your own plan set back, marked up. The format depends on the intake system.
Paper and scanned PDF intake. Older or smaller jurisdictions still mark up a physical or scanned copy by hand: circles, arrows, and handwritten notes in red or blue ink directly on the sheet. You read the markup on the page it applies to.
ePlan / Bluebeam-based intake. Most mid-size and large jurisdictions now use electronic plan review software. San Diego, Los Angeles, and many county building departments run ePlan portals built on Bluebeam Revu markup tools. Comments appear as numbered callout bubbles pinned to a specific location on a specific sheet, with a linked comment list you can export.
Comment-letter intake. Some jurisdictions issue a separate correction letter referencing sheet numbers and detail callouts rather than marking the drawing itself. You cross-reference the letter against your own set.
Whatever the format, every comment carries the same three pieces of information: the sheet or location it applies to, the code section or standard it cites (if any), and the specific fix the checker expects. Missing any one of those three when you log the comment is how items get lost between rounds.
Common Markup Conventions to Know
Plan checkers use shorthand that is worth learning once so you stop guessing:
- “Provide” or “Clarify” usually means information is missing, not that the design is wrong. Add a note, detail, or spec sheet.
- “Revise to comply with [code section]” is a code violation. The design element itself has to change, not just the label.
- A circled dimension or number with a question mark flags a mismatch between sheets, most often between the single line diagram (SLD) and the structural or roof plan.
- “See attached” on an electronic comment usually links to a reference standard, a local amendment, or the jurisdiction’s own checklist. Open it. Do not assume it repeats a comment you have seen before.
- A comment with no code citation is often a local preference or house style, not a hard code requirement. It still has to be resolved, but it may need a phone call rather than a redesign.
Log Every Comment Before You Touch the Drawings
The single biggest mistake in redline handling is jumping straight into CAD to fix the first comment you see. Before any drawing changes, build one tracked list covering every comment on the set.
A simple spreadsheet works. Columns: comment number, sheet reference, code citation (if any), checker’s exact wording, severity, owner, status, and resubmission note. This becomes the backbone of your response letter later, so build it once and keep it current rather than reconstructing it at the end.
Why this matters operationally: on a commercial job with 15 to 25 comments across electrical, structural, and fire access, comments frequently touch the same underlying issue from three different sheets. If your structural engineer fixes a footing detail without your electrical designer knowing the array layout shifted, you introduce a new SLD mismatch that gets flagged on the next round. A single tracked list, visible to the whole team, is what prevents that.
Most EPCs get this wrong by treating the marked-up PDF itself as the tracker. It is not searchable across sheets, it is not assignable, and it disappears into one person’s downloads folder. Extract every comment into a structured list on day one.
Prioritize Fixes by Severity, Not by Sheet Order
Once every comment is logged, sort by what actually blocks approval.
Tier 1: code violations. These fail a specific code section, most commonly NEC 690.12 rapid shutdown labeling, fire setback distances under IFC 605.11 or a local fire code amendment, or a structural load path that does not meet the adopted ASCE 7 edition. These require an actual design change and often a re-stamp from the engineer of record. Start here, because these take the longest to turn around.
Tier 2: missing documentation. Equipment spec sheets, UL listing documentation, or a wet-stamped structural letter that was omitted rather than wrong. These are fast to close if the document already exists. Assemble and attach them before touching anything else.
Tier 3: formatting and cross-reference fixes. Dimension mismatches between the SLD and the wire schedule, inconsistent sheet numbering, or a note that references the wrong detail callout. Low individual effort, but high in count, and easy to miss one and trigger round three.
Working strictly in that order matters because Tier 1 items are what actually gate approval. A plan checker will not approve a set with an open code violation no matter how clean the formatting is. Teams that work sheet-by-sheet instead of severity-by-severity often burn a day polishing Tier 3 items while a Tier 1 structural comment sits untouched.
Route Comments to the Right Owner, Fast
Redline comments span disciplines. A structural comment belongs with your PE. An SLD comment belongs with your electrical designer. An interconnection or utility-facing comment belongs with whoever filed the utility application, which is sometimes a different person than whoever built the plan set.
Set a routing rule before the redlines even land: each comment category has one named owner, and that owner has a response SLA, ideally 24 to 48 hours for anything that does not require a full redesign. Structural comments that require a new calculation or a revised stamp take longer, so flag those on day one rather than discovering the delay a week in.
If your design work is outsourced, this is the point where communication quality separates a fast resubmission from a slow one. A design partner working off your tracked comment list, with clear ownership per item, turns a 15-comment correction letter around in days. A partner working off a forwarded PDF with no structure adds a full review cycle just to figure out what changed. This is also where a solar permit expediting partner earns its fee: someone dedicated to tracking the queue and chasing the fix, rather than a designer working it between other jobs.
Verify the Fix Against Every Sheet It Touches, Not Just the One That Was Flagged
This is the step that prevents a second rejection round, and it is the one most teams skip under deadline pressure.
When a comment flags a dimension, a panel count, or an equipment model on one sheet, that same value almost always appears on at least one other sheet: the SLD, the equipment schedule, the structural plan, or the utility interconnection application. Fixing it in one place and not the others is the single most common cause of a second correction round on resubmission, because the plan checker cross-references the same values a second time.
Before marking any comment “resolved,” check the corrected value against:
- The single line diagram
- The equipment and spec sheet list
- The structural or roof plan
- The utility interconnection application, if the project has already been filed with the utility
A short internal QA pass across these four documents, even 15 minutes per project, catches the mismatch before the AHJ does.
Version Every Resubmission
Once every comment is closed and cross-checked, package the resubmission with clear version control. Label the set Rev 1 (or Rev 2, Rev 3) on the title block and on the file name, and keep prior revisions archived rather than overwritten. Reviewers, especially at high-volume jurisdictions, are working through a stack of resubmittals and rely on the revision number to confirm they are looking at the current set.
Attach a point-by-point response letter that lists each original comment number next to the specific change made and the sheet it appears on. This single document is what lets a checker approve on second review without re-reading the entire plan set line by line. It also becomes your own record if the same comment resurfaces on a later project with the same jurisdiction, since local plan checkers tend to be consistent in what they flag.
A resubmission package should include:
- The version-stamped, corrected plan set
- A point-by-point response letter referencing original comment numbers
- Any newly attached documentation (spec sheets, revised structural letter, updated interconnection form)
- A cover note confirming the resubmission is within the jurisdiction’s response window
Most AHJs set an expiration window on open corrections, commonly 90 to 180 days depending on the jurisdiction and the adopted building code cycle. Missing that window can void the original application and force a full refiling with a new fee. Track the deadline on your comment list from day one, not as an afterthought.
What Causes a Second Rejection Round
A second round almost never comes from a brand-new issue. It comes from one of three patterns:
Partial fixes. The flagged item was corrected, but a related value on another sheet was not updated to match, so the checker’s cross-reference check fails again.
Comments read too literally. A checker’s note like “clarify rapid shutdown label location” sometimes signals a broader labeling gap across the whole set, not just the one sheet cited. Fixing only the cited instance leaves the rest unaddressed.
No response letter. Without a point-by-point letter, the checker has to re-derive what changed by comparing old and new sheets manually. That takes longer and increases the odds they miss your fix or re-flag something you already resolved.
The fix for all three is the same discipline covered above: track every comment centrally, verify fixes across every sheet the value touches, and document what changed in a response letter the checker can move through quickly.
A Sample Comment Tracker, By Severity
Here is what a working tracker looks like once comments are logged and sorted, using a representative commercial rooftop job:
| # | Sheet | Comment | Code Citation | Severity | Owner |
|---|---|---|---|---|---|
| 1 | E-2 | Rapid shutdown label placement not shown at PV disconnect | NEC 690.12 | Tier 1 | Electrical designer |
| 2 | S-1 | Structural letter missing wet stamp | Local amendment | Tier 1 | Structural PE |
| 3 | A-1 | Fire access pathway dimension below 36 in minimum | IFC 605.11 | Tier 1 | Design lead |
| 4 | E-3 | Inverter spec sheet not attached | None | Tier 2 | Permit tech |
| 5 | E-2 | Panel count on SLD does not match roof plan module count | None | Tier 3 | Electrical designer |
| 6 | G-1 | Sheet index references old revision number | None | Tier 3 | Permit tech |
Notice that only 3 of the 6 comments require an actual design change. The other 3 are documentation and cross-reference fixes that a permit tech can close in under an hour combined. Sorting the list this way, before assigning any work, is what keeps a 6-comment correction letter from turning into a multi-day scramble.
Tools That Help, and Where They Fall Short
Electronic plan review platforms like Bluebeam-based ePlan portals export a comment list automatically, which saves the manual transcription step. Some permit software also lets you attach a response directly to each markup bubble, which doubles as your response letter if the jurisdiction’s portal supports viewing it that way.
The gap most teams hit is that the exported list is a static snapshot. It does not track ownership, SLA, or whether the fix has been cross-checked against the other sheets it touches. A spreadsheet or lightweight project tracker layered on top of the export, not instead of it, closes that gap. The tool matters less than the discipline of using one tracked list consistently across every project, so comment-handling habits do not reset every time a new project manager takes over a job.
Redline Handling as a Repeatable Process, Not a One-Off Scramble
Installers running 20 or more permits a month benefit from treating redline response as a standing process rather than a reactive one. That means a standard comment-tracking template used on every project, a named owner per discipline before the redlines ever arrive, and a shared library of prior response letters so recurring comments from the same jurisdiction get resolved from a template instead of from scratch.
This is also where the upstream work matters. A plan set built against a solar permit package checklist and reviewed against known AHJ rejection triggers before first submission generates fewer redlines to begin with. Redline handling and first-pass quality are two ends of the same process, not separate problems.
If your team is spending more hours managing correction cycles than building plan sets, that is usually a signal the review workload has outgrown an ad hoc process. Download a sample permit response package to see how a tracked comment list and response letter are structured, or talk to our permit design team about a fixed 24 to 48 hour turnaround on redline responses.
Frequently Asked Questions
How long do I have to resubmit after receiving redlines? Most US jurisdictions give 90 to 180 days before an open correction cycle expires and the permit application has to be refiled with a new fee. The exact window is set locally, so confirm it on your original submission receipt or the jurisdiction’s plan review portal.
Do I need to resubmit the entire plan set or just the corrected sheets? This depends on the jurisdiction’s intake system. ePlan portals built on tools like Bluebeam Revu often accept just the revised sheets tied to the original submission record. Paper and some scanned-PDF intake departments require the full set resubmitted as a new revision. Check the jurisdiction’s resubmission instructions before assembling the package.
What is the difference between a redline and a rejection? A redline is markup identifying specific corrections on an otherwise active application. A rejection or denial closes the application outright and typically requires a brand-new submission and fee. Redlines are the far more common outcome of a first plan review.
Who should own redline response on an EPC team, the designer or the permit tech? Ownership works best split by comment type: a permit tech or project manager owns tracking, routing, and the response letter, while the licensed designer or PE owns any comment that requires an actual engineering change. The permit tech should never modify a stamped structural or electrical detail themselves.
Can a redline comment be appealed if I disagree with the checker? Yes, most jurisdictions allow a phone call or a scheduled plan review meeting to discuss a disputed comment before resubmission. This is most useful for comments without a clear code citation, which are often based on local preference rather than a hard requirement.
Does resubmitting with a response letter actually speed up second review? It reduces the checker’s own workload on the second pass, since they can verify each item against your list instead of re-reading the full set. Jurisdictions do not guarantee a faster review time for it, but a well-organized resubmission reduces the odds of a follow-up question that would add another round.
What happens if I miss the resubmission window? The application typically expires and the project has to be refiled as new, including a new plan review fee and a new position in the review queue. Track your resubmission deadline the same way you track the comments themselves.
Should structural PE comments and electrical comments be resubmitted together or separately? Together, as one version-stamped set, unless the jurisdiction’s portal explicitly separates disciplines into different review tracks. Submitting disciplines separately risks the checker reviewing an incomplete picture and issuing a new round of cross-reference comments.
