Real deficiency or reviewer preference? How to tell which comments you must fix

Not every comment in a plan check letter is a code violation. Some are. Some ask for something your drawings already show. Some cite a section that does not apply to your project. And some cannot be judged until you ask a question. Treating them all as orders to redraw costs weeks; treating them all as opinions costs the permit. The skill is telling them apart.

What are the four verdicts a comment can get?

Every comment lands in one of four places once you check it against the adopted code and your own drawings.

• Real deficiency. The code requires it, and your submittal does not show it. You change the drawings or add the document.
• Likely already satisfied. The code requires it, and your submittal shows it, but not where the reviewer looked. You point to the sheet.
• Reviewer likely mistaken. The cited section does not govern this project, or the reviewer misread the drawings. You explain, with the section that actually applies.
• Could not verify. The comment depends on a fact that is not in the drawings or the letter. You ask, or you supply the fact.

These four verdicts are also how commentletter.com labels every comment in a report, and the reasoning below is the reasoning the engine follows.

How do I tell a real deficiency from a preference?

Start from the code section the comment cites, not from the comment's wording.

1. Read the cited section in the edition your city adopted. A comment that cites CBC 1010.1.1 is a claim about a specific sentence. Read that sentence. If the letter cites no section, ask for one; a comment with no code basis is a preference until the reviewer supplies one.
2. Check the scope. Many sections apply only to certain occupancies, construction types, building heights, or project types. A requirement written for new construction often has an exception for alterations. Residential and nonresidential provisions live in different books.
3. Check your own drawings. Reviewers read hundreds of sheets a week. A surprising share of comments ask for something that is on a sheet they did not open.
4. Check the local layer. Cities adopt the state code with amendments. A comment that looks wrong against the state code can be right against the city's ordinance, and the reverse. If your city publishes its amendments, that is the second place to look.

A comment is a real deficiency when the section applies to your project, its requirement is specific, and your drawings do not show it. Everything else is one of the other three verdicts.

What does "reviewer preference" actually look like?

Preferences come in a few recognizable shapes:

• "Provide" with no section. A request for a note, a schedule, or a detail that no cited section requires. Often reasonable; sometimes optional.
• The wrong book. A residential project cited to the CBC where the CRC governs, or an alteration cited to a new-construction provision without its exception.
• Extra margin. A request to exceed a minimum: a wider door, a lower slope, more fixtures. The code sets minimums; the reviewer cannot raise them without a local amendment.
• Interpretation. A section that reads two ways, read the stricter way. These are worth a conversation before they are worth a redraw.

None of this makes the reviewer wrong to ask. It makes the comment negotiable, and the negotiation is your response.

How do I write a pushback the reviewer can accept?

A good pushback makes it easy for the reviewer to say yes.

Comment E4. Provide GFCI protection for all receptacles in the kitchen per CEC 210.8(A)(6).

Response. We respectfully request reconsideration. CEC 210.8(A)(6) applies to receptacles serving kitchen countertop surfaces. The two receptacles in question are dedicated appliance outlets located behind the refrigerator and below the range hood and do not serve countertop surfaces. They are labeled as such on Sheet E-2.1. All countertop receptacles are shown with GFCI protection. No revision has been made.

See: Sheet E-2.1, receptacle schedule and keynotes 6 and 7.

The pattern: state that you are asking for reconsideration, quote the scope of the cited section, show why your condition falls outside it, point to where the reviewer can confirm it, and say plainly that nothing changed. Never characterize the reviewer; characterize the section.

Two rules of tone. Write the pushback so it could be read aloud in the counter line without embarrassment. And offer the exit: "If the city applies a local requirement here, please cite it and we will comply."

When should I just do it anyway?

Sometimes. Pushing back costs a review cycle, and a review cycle can cost more than the change. If the change is small, harmless, and the reviewer clearly wants it, make it and move on. Save the pushback for comments that change the design, add real cost, or set a precedent you will meet again on the next project.

A reasonable test: would you rather spend the next round on this comment, or on the permit?

What about comments you cannot verify?

Some comments turn on facts the letter and the drawings do not contain: whether the existing building has sprinklers, what the soils report says, which fire flow the water district can deliver. Do not guess. Respond with the question, or supply the document, and say which one you did. "Could not verify" is an honest verdict and the reviewer will respect it more than a confident wrong answer.

How commentletter.com applies this

For every comment in your letter, the agent reads the cited section in your city's adopted code, compares it with the sheets you uploaded, and states one of the four verdicts with the reason. Real deficiencies get a step list naming the sheet to change. Likely-satisfied items get the sheet to point at. Likely-mistaken items get the provision that actually governs, drafted as a pushback. Unverifiable items get the question to ask. You decide; the report gives you what you need to decide quickly.