From DRE Comment to Coordinated Response: A Public-Report Comment-Control System

1. Capture the Comment Verbatim

Enter the complete comment in the log and preserve the source document or email. Record:

• the DRE file number and project name;
• the filing and public-report type;
• the phase, map, lots, units, or interests affected;
• the reviewer, communication date, and response reference;
• the exact comment text;
• any cited form item, regulation, statute, document, or prior comment;
• attachments or examples supplied by the reviewer; and
• the date received by the project team.

Maintain the agency’s numbering. Add an internal ID when one agency comment contains several separable actions. The original comment should remain visible beside the internal action lines.

Control principle: preserve the agency language and create internal sub-actions only where separate ownership, evidence, or decisions require them.

2. Classify the Underlying Issue

Assign one primary issue category and any secondary categories. A practical taxonomy includes:

1. filing scope, identity, authority, or application completeness;
2. title, legal description, map, phase, or subdivision-interest information;
3. access, utilities, use, improvement status, or completion arrangements;
4. common-interest structure, governing materials, easements, or maintenance responsibility;
5. budget, reserve, assessment, subsidy, start-up, or financial information;
6. purchase agreement, escrow, deposit, security, or closing material;
7. hazard, condition, facility, or other purchaser disclosure;
8. document consistency, execution, recording, certification, or professional review;
9. amendment, renewal, changed project fact, or changed offering; and
10. response-format, indexing, or procedural item.

Classification helps route the comment to the right professionals and reveals patterns. Several comments in different sections may arise from one unresolved project assumption.

Control principle: use classification to identify the project issue connecting several comments.

3. Assign the Responsibility Chain

For each comment or action, identify:

• the response coordinator;
• the person producing the first draft or deliverable;
• the sponsor decision owner;
• counsel and other professionals whose review is required;
• the source-document owner;
• the person authorized to communicate or submit to DRE; and
• the records custodian.

A comment concerning an association budget may require updated physical quantities from the design team, phasing information from the sponsor, maintenance assumptions from operations, financial work from the budget preparer, legal-document review from counsel, and final filing coordination through the responsible public-report professional.

The responsibility chain should show the sequence and due dates for each contributor. A single assignee field can obscure the handoffs that determine response timing.

Control principle: assign production, decision, professional review, submission, and records roles separately.

4. Identify the Source of Truth

Locate every current source that supports the response. Depending on the issue, the source set may include:

• current title information and legal descriptions;
• tentative, final, parcel, or condominium mapping;
• civil, architectural, landscape, utility, and facility plans;
• approved conditions, agreements, and agency correspondence;
• governing and transactional documents;
• budgets, reserve studies, operating assumptions, and quantity takeoffs;
• improvement-completion records and security instruments;
• utility or access evidence;
• natural-hazard information and technical reports;
• prior DRE submissions, comments, and responses; and
• current sponsor decisions and change records.

Record the document date and version. If two sources conflict, open an issue and pause final response drafting until the responsible professionals and decision makers resolve the conflict.

Control principle: a response should trace to a current source and the person responsible for that source.

5. Resolve the Project Issue

Write a decision question that isolates the issue underlying the comment. Examples include:

• Which phase contains the facility, and when will owners in the filing phase receive use rights?
• Which entity owns and maintains the private street during each stage of development?
• Which units or lots share a budgeted cost, and when does that allocation change?
• Which improvement remains incomplete, and what completion arrangement applies?
• Which recorded or proposed document carries the access right?
• Which version of the purchase agreement and escrow instructions governs the offering?
• Which changed project fact triggers an amendment review?

Then identify the decision maker, required professional input, options, deadline, and downstream consequences. Record the answer in the project decision log and distribute it to every affected document owner.

Control principle: resolve one project fact once and carry the answer through every dependent material.

6. Define the Response Package

For each comment, specify the complete package required for a coherent response. The package may include:

• a concise written response;
• a revised form item or application page;
• a clean and redlined document;
• an executed, acknowledged, recorded, or certified instrument;
• a revised map, exhibit, plan, or legal description;
• a professional letter, budget, reserve analysis, or technical memorandum;
• evidence of completion, security, service, access, or authority;
• a sponsor certification or decision record;
• a revised disclosure or special note; and
• an index showing each enclosure and its relationship to the comment.

State the required format and naming convention before contributors begin. Confirm whether the filing system, reviewer, or public-report professional requires a specific response table, certification, or submission sequence.

Control principle: define the finished response package at assignment so contributors work toward one visible completion standard.

7. Run a Cross-Document Consistency Review

Before submission, compare the proposed response against every affected project material. Confirm consistency in:

• project and phase names;
• map, tract, parcel, lot, and unit references;
• ownership and maintenance responsibility;
• facility descriptions and availability;
• unit counts, quantities, percentages, and allocation assumptions;
• budget, assessment, reserve, subsidy, and start-up information;
• completion status and security;
• access, utilities, easements, and recorded rights;
• dates, versions, exhibits, and defined terms; and
• statements in purchase, escrow, governing, disclosure, and marketing materials.

Use a review signoff for each responsible discipline. Record open qualifications and the person authorized to resolve them.

Control principle: treat the response as an update to the project record and test every dependent representation.

8. Submit One Indexed and Version-Controlled Package

The final package should identify the file, submission date, response cycle, comments addressed, enclosures, document versions, and authorized submitter. Preserve the exact package transmitted to DRE.

The submission index should show:

• comment or action ID;
• response summary;
• enclosure title;
• version or execution date;
• clean or redline designation;
• professional approval status; and
• file name or repository link.

Record the transmission channel, confirmation, and any delivery issue. Freeze the submitted versions in the project repository so later edits remain distinguishable.

Control principle: the project record should reproduce the complete agency submission without reconstruction from individual email chains.

9. Track Follow-Up, Closure, and Project Changes

After submission, update each action as DRE responds. Useful statuses include:

• received;
• classified;
• assigned;
• project decision required;
• professional work in progress;
• professional review;
• ready for submission;
• submitted;
• agency follow-up;
• revised response;
• accepted or resolved for the current review cycle;
• continuing into amendment, renewal, or later phase; and
• closed.

Closure should record the supporting agency communication, report issuance, accepted document, or other evidence. A comment can also reveal a project change that requires attention across another filing, phase, budget, governing document, completion arrangement, disclosure, or implementation plan. Route that change through the project’s change-review protocol.

Control principle: preserve both the agency-review outcome and the downstream project action.

Establish the Comment Taxonomy

Adopt a controlled set of issue categories that reflects the project’s filing, document, budget, facility, completion, and amendment workstreams.

Build the Responsibility Chain

Assign a coordinator, producer, sponsor decision owner, professional reviewers, authorized submitter, and records custodian for each open action.

Create the Source and Decision Links

Connect every comment to the current source documents and any project decision required to reconcile them.

Define the Submission Standard

Use one response template, enclosure index, file-naming convention, signoff sequence, and submission archive.

Review the Full Project Impact

Before closure, identify every other document, phase, filing, representation, or implementation action affected by the response.