Engineering and architecture
Plan review comment letters and responses: an overlooked dataset
By SourceX Editorial · Updated
Short answer
Plan review comment letters and the firm's response letters form a valuable dataset when kept as linked correction cycles: the examiner's comment, the code section cited, the firm's response, the revised sheets and the outcome on resubmittal. A comment alone is a rule citation; a complete cycle shows how professionals resolve code questions, which is what plan-review tools need.
Key takeaways
- The useful unit is the complete correction cycle, not the comment letter on its own.
- Each cycle should link the comment, the code reference, the response, the revised sheets and the resubmittal outcome.
- Examiner comments are third-party content, so treat them separately from firm-authored responses in any rights review.
- Applicant, owner, parcel, permit and personnel details come out before any cycle is licensed.
Why plan review correction cycles are worth keeping#
Plan review correction cycles are worth keeping because they record how a design came to meet a code requirement after an examiner questioned it. Every permit submission that came back with comments produced a small, complete case: a question from the jurisdiction, an answer from the design team, and a verdict on resubmittal.
Software teams building automated plan review need exactly this kind of record. Code text tells a model what a rule says; correction cycles show how examiners apply it to real drawings and how architects close the gap. Few firms think of their permit folders this way, so the records are rarely organized for reuse.
The same records also have internal value. A firm that can see which code topics drew repeat comments, in which jurisdictions, can fix its own checklists before the next submission.
Anatomy of a correction cycle#
A correction cycle has five linked parts, and in most firms each one lives in a different place. The table shows what to capture for every comment.
Each part is weak on its own. A comment without a response is a rule citation, a response without the comment is an unexplained change, and revised sheets without either are just drawings. Linked together, they show a question, an answer and a verdict.
The outcome is the part firms most often lose. A comment repeated in the next letter is evidence the first response missed, and the miss plus the fix that followed is among the most useful parts of the record. Comments that took several rounds to close show where examiners and designers read the code differently, which is what plan-review tools find hardest.
| Element | What it records | Where it usually lives |
|---|---|---|
| Comment | The examiner's finding, usually numbered by discipline | Comment letter PDF or e-permit portal |
| Code reference | The code section or local amendment the comment cites | Inside the comment text |
| Response | The firm's answer, often with a sheet reference | Response letter in Word or PDF |
| Revised sheets | Clouded changes made to address the comment | Resubmittal set and revision schedule |
| Outcome | Accepted, partly accepted or repeated in the next round | Next comment letter or approval notice |
Where firms keep correction records#
Correction records are spread across permit folders, e-permitting portals and email, and portal access is the part most likely to disappear. Account access and download options can change after a permit closes or when a jurisdiction switches systems, so save copies while access lasts.
Jurisdictions that review electronically may keep some rounds only inside their own system, so a project folder can be missing whole rounds without anyone noticing. Compare each folder with the number of review rounds the portal or approval notice shows before treating the record as complete.
- Permit folders on the project drive, holding comment letters, response letters and resubmittal sets.
- Jurisdiction e-permitting portals, where comments may exist only as portal entries or markup sessions.
- Bluebeam Studio Sessions run by jurisdictions that review electronically, with comments and replies on the sheets.
- Email between project architects and plan examiners, often holding informal clarifications.
- Newforma, Procore or similar platforms where permit correspondence is logged.
- Code analysis sheets and code consultant reports that shaped the response.
How to rebuild correction cycles from old permit files#
Rebuilding correction cycles is a coordinator's job measured in projects, not a firmwide data project. Start small, prove the method on a handful of permits, and widen only when the cycle log reads cleanly.
Matching is mostly a matter of numbers. Examiners usually number their comments, and good response letters repeat those numbers and cite the revised sheet. Where a response cannot be tied to a comment with confidence, mark the link as uncertain rather than guessing.
- Step 1: pick completed projects that needed two or more review rounds, since their folders tend to be the most complete.
- Step 2: save every comment letter, response letter and portal record for each round while access lasts.
- Step 3: open a cycle log with one row per comment: cycle number, round, discipline, code section, code edition, response summary, revised sheet and outcome.
- Step 4: match responses to comments by comment number and sheet reference, and flag uncertain links.
- Step 5: record the outcome from the next letter or the approval notice.
- Step 6: tag each cycle with occupancy type, construction type and code topic.
- Step 7: ask the project architect to spot-check a sample of cycles from each project before the log is used.
Rights questions for plan review records#
Plan review records raise two rights questions: who wrote each part, and what the client contract says about project information. Examiner comments are written by the jurisdiction, response letters by the firm, and the drawings are the firm's instruments of service subject to client terms.
Filing drawings for a permit does not by itself give up the architect's rights. AIA A201 provides that submitting instruments of service to meet official regulatory requirements is not to be construed as publication in derogation of the architect's or consultants' reserved rights.
Permit files may also be covered by public records rules that vary by jurisdiction, but public availability does not by itself settle whether a firm may license them. Treat examiner comments as third-party content, review the approach with counsel, and exclude projects whose contracts restrict use of project information.
Where a code consultant or permit expediter prepared responses on the firm's behalf, read that agreement too. Their letters may be their work product, and the agreement decides whether the firm can include them.
Redaction notes for correction cycles#
Redaction for correction cycles removes people, places and permit identifiers while keeping the code reasoning intact. The examiner's finding, the code reference and the firm's technical response should all survive redaction.
Keep occupancy type, construction type and code edition wherever rights allow. Those fields carry no identity on their own, and without them a buyer cannot tell which rules a cycle was decided under.
| Field | Action |
|---|---|
| Applicant, owner and tenant names | Replace with roles |
| Site address and parcel number | Remove; keep only the general building type |
| Permit and application numbers | Replace with a neutral cycle identifier |
| Plan examiner names and contact details | Replace with examiner discipline |
| Firm staff names, stamps and signatures | Remove from letters and sheet images |
| Jurisdiction name | Generalize to state or code edition unless a buyer needs more and rights allow |
| Security-related comments | Exclude the cycle |
Illustrative: a COO rebuilds a permit history#
Illustrative: a fictional architecture firm designs restaurants, retail and light industrial buildings across many jurisdictions. Its COO noticed that permit corrections were a recurring source of rework and asked whether the firm's own history could help, internally or through licensing.
An operations coordinator pulled comment and response letters from permit folders, downloaded portal records while accounts were still open, and built a cycle log matched by comment number. Projects with email-only responses were set aside for later. Each cycle was tagged by occupancy type, code topic and outcome.
Internally, the tagged cycles became a pre-submission reference for project architects. For licensing, the COO approved a metadata-only fit check describing record types, jurisdictions in general terms and years covered, with no letters shared.
How SourceX approaches plan review datasets#
SourceX approaches plan review records as cycle-level packages within the SourceX five-step transaction. The Rights step separates firm-authored responses from jurisdiction comments and checks client terms, and the Preparation step applies redaction before the firm approves release.
Each package's SourceX Evidence Packet documents provenance, licensing rights, permitted use, the privacy record and release authorization.
Frequently asked questions
Do we need the drawings, or are letters enough?
Letters alone carry the comment, code reference and response, which is useful. Adding the revised sheets shows what actually changed and makes the cycle more complete, but it raises the redaction effort. Many firms start with letters and revision descriptions, then add sheet images for projects with clear rights.
What if responses were handled over email?
Email responses can still be linked if they cite comment numbers or sheet changes. Export the threads, match them to the comment letter, and note where a link is uncertain. Leave out any cycle whose response cannot be tied to its comment, because a wrong link teaches the wrong lesson.
Are records from many jurisdictions useful?
Yes. Jurisdictions adopt different code editions and local amendments, and examiners emphasize different issues. A spread of jurisdictions helps developers test whether a tool handles that variety. Record the code edition with each cycle so the context stays clear.
Should we include cycles where our first response was rejected?
Yes, where rights allow. A rejected response followed by an accepted one shows the correction that finally satisfied the examiner, and that contrast is among the most useful parts of the dataset.
Will this help our own permitting?
Usually. Tagged cycles show which code topics trigger repeat comments in which jurisdictions, and project architects can check them before submitting. The internal benefit often justifies the cleanup before any licensing decision is made.
Who should own the collection work?
An operations or permit coordinator usually owns collection, with a project architect confirming how each cycle was resolved. The coordinator handles portals, folders and naming; the architect knows which revision answered which comment. A principal approves the project list before anything is prepared for licensing.
Sources
- AIA A201 provides that submittal or distribution of the Instruments of Service to meet official regulatory requirements or for other Project purposes is not to be construed as publication in derogation of the Architect's or consultants' reserved rights. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.