How to Respond to a Plan Check Correction Letter

A response matrix is the itemized document you submit alongside your revised drawings. It lists every correction from the plan check letter in the jurisdiction's original numbering, and against each one states what you changed and exactly where the reviewer will find it. Most jurisdictions call it a response letter, comment response, or correction response; the structure is the same. It exists so the plan checker can verify your work without re-reading the entire set — which is why a weak matrix costs you a full review cycle even when the drawings are correct.

Because they are not verifiable. The reviewer has to confirm each item, and a one-word response gives them nowhere to look — so they go hunting, and if they cannot find it quickly the item comes back open. Multiple jurisdictions say this outright in their handouts: Alameda, San Leandro, and Danville all publish guidance rejecting single-word responses. Write the change and the location instead: "Exit travel distance reduced to 245 ft by relocating the Suite 210 corridor. See revised plan and travel-distance diagram, Sheet A-201, Detail 3."

Three things, in this order: what you changed, where it now appears, and what it complies with. "Revised" is a claim; "Revised — see Sheet A-201, Detail 3, per CBC 1017.2" is a verifiable claim. If the correction was based on a misreading of the original drawings, say that plainly and point to the sheet that already showed it, rather than making a change you do not need.

Call the plan checker before you resubmit. Every jurisdiction handout that addresses this says the same thing: contact the reviewer for clarification rather than arguing in writing. A disagreement resolved on a phone call takes ten minutes; the same disagreement litigated through the matrix costs a full review cycle, and you will likely lose it anyway because the reviewer is the one who signs off. If you do resolve it verbally, record it in the matrix — "Discussed with [reviewer] on [date]; item withdrawn" — so the file shows why nothing changed.

Yes. The matrix is a roadmap, not the work. Every change it describes must be reflected on the construction documents with revision clouds, delta tags, an updated revision schedule, and an updated title block. A matrix that describes changes the drawings do not show is the fastest way to a second correction letter — and it damages your credibility for the rest of the review.

Anything touching a licensed professional's design has to be answered by that professional — the architect or engineer of record, not an admin or a junior drafter compiling the package. Several jurisdictions state this explicitly. Practically it also means structural, mechanical, and electrical responses should come from those consultants in their own words, then be assembled rather than paraphrased by whoever owns the submittal.

It varies by jurisdiction, workload, and whether your original submittal was clean. The number that matters more is how many cycles you take, not how long one takes — each additional round trip is typically measured in weeks, and on fixed-fee work those weeks come out of your margin rather than the client's budget. A complete, verifiable response matrix is the single cheapest way to keep the count at one.

The assembly can. Most teams build the matrix by hand in Excel — retyping each correction from the PDF, then tracking which ones are answered. Olumba Align parses the correction letter into structured items with their code references and department attribution, so the matrix starts already numbered and matched to the jurisdiction's letter, and you write only the response text. The judgment stays yours; the transcription does not have to be.