The Approval Record Becomes the Implementation Baseline
A project approval can distribute obligations across a resolution, conditions of approval, findings, a mitigation monitoring or reporting program, approved plans, technical reports, development or improvement agreements, agency correspondence, utility requirements, and later clarifications. Each source may use its own numbering, terminology, timing, and method of demonstrating compliance.
California Public Resources Code section 21081.6 requires a reporting or monitoring program for mitigation measures and project changes adopted to address significant environmental effects. The program must be designed to ensure compliance during implementation, and the adopted measures must be enforceable through conditions, agreements, or other means. The Subdivision Map Act adds a separate implementation layer: Government Code section 66462 addresses improvement agreements and security where required public improvements remain incomplete at final-map approval, while section 66462.5 addresses certain off-site improvements on property where sufficient rights have yet to be obtained.
These sources create an implementation record with several dimensions. One obligation may affect grading plans, construction sequencing, a final map condition, a permit, a public-report representation, a budget assumption, and an operational handoff. A conditions and commitments register gives the team one place to see those relationships while preserving each adopted document as the governing source.
What Belongs in the Register
The register should begin with an explicit source inventory. Depending on the project, the inventory may include:
- the approving resolution and findings;
- the complete conditions of approval;
- the adopted mitigation monitoring or reporting program;
- project-design features and applicant commitments incorporated into the approval;
- approved plans, exhibits, and technical reports referenced by a condition;
- development, improvement, reimbursement, utility, maintenance, or other project agreements;
- tentative-map conditions and related improvement requirements;
- agency letters, hearing commitments, and formal interpretations that affect implementation;
- permits and later discretionary actions with their own conditions; and
- approved amendments, addenda, clarifications, or successor documents.
Assign a source owner and a current version to each item. Preserve the exact adopted language. The register can add a concise action statement for project management, while the source text remains available for legal, technical, and agency review.
An Eight-Part Register Framework
1. Give Every Obligation a Stable Identity
Create a unique identifier that remains consistent across meetings, schedules, plan comments, agency submissions, and closeout packages. Retain the source document, section or condition number, adoption date, and exact text.
A stable identifier allows the project team to discuss one obligation with precision even when several documents use similar language. It also supports cross-references between the register, the drawing set, technical memoranda, agency correspondence, and evidence files.
Useful fields: obligation ID; source document; source section; exact text; source date; source link or file location.
2. Translate the Source into an Executable Action
Write a concise action statement that identifies the required result. Break compound conditions into separate trackable actions when they have different owners, triggers, evidence, or approving authorities.
For example, one condition may require a plan revision, a technical review, execution of an agreement, payment of a fee, and agency acceptance before a permit or map milestone. Tracking the condition as one line can hide four independent dependencies. Separate lines preserve the common source while giving each action a clear owner and status.
The action statement should also identify any term that requires counsel, a technical professional, or the agency to interpret. Record that interpretation and its source when resolved.
Useful fields: action statement; interpretation question; decision owner; related action IDs.
3. Locate the Obligation in Place, Phase, and Time
Identify the geography, phase, improvement, building, lot group, facility, or operating period affected by the obligation. Then identify the trigger and the latest practical completion point.
Common triggers include:
- before final-map approval or recordation;
- before grading, building, encroachment, or other permit issuance;
- before construction begins in a defined area;
- before inspection, acceptance, occupancy, sale, or closing;
- before a phase opens or a facility becomes available;
- during construction or for a specified monitoring period; and
- at association transition, facility turnover, or another operational milestone.
The adopted source controls the requirement. The register can also include an internal target date that gives the responsible team enough time for preparation, professional review, agency processing, revision, and acceptance.
Useful fields: applicable area; phase; formal trigger; internal target; forecast completion; schedule activity.
4. Assign the Full Responsibility Chain
A single “owner” field rarely captures the work required to close an obligation. Use a responsibility chain that identifies:
- the person responsible for producing the work;
- the CDA or sponsor-side coordinator responsible for maintaining the workplan;
- the professionals whose review or certification is required;
- the sponsor representative authorized to make the underlying decision;
- the agency, utility, association, or other body that accepts or confirms compliance; and
- the person responsible for preserving the final evidence.
This structure separates production, coordination, professional judgment, sponsor authority, agency action, and records control. It also makes handoffs visible when personnel or consultants change.
Useful fields: action owner; coordinator; contributors; professional reviewer; sponsor decision owner; approving authority; records custodian.
5. Define the Evidence and Acceptance Standard
Write the anticipated closure evidence while the obligation is being assigned. The evidence may be an approved plan, executed and recorded document, technical memorandum, inspection report, permit, receipt, agency letter, acceptance record, photograph, certification, security instrument, payment record, or another project-specific item.
Identify the required form, signatory, reviewer, and acceptance channel. A deliverable can be complete within the project team and remain open with the agency. Use separate status fields for preparation, professional review, submission, agency review, revision, acceptance, and archival.
Where a mitigation measure or condition requires recurring monitoring, the register should identify the reporting frequency, recipient, duration, and final completion event.
Useful fields: closure criterion; evidence type; required signatory; submission path; acceptance authority; evidence location; acceptance date.
6. Map Dependencies and Decision Exposure
Each obligation should identify the activities it enables and the activities that enable it. This dependency map reveals the critical path and the project decisions carrying the greatest downstream exposure.
For each action, ask:
- Which plan, study, agreement, right, payment, construction activity, or agency decision must occur first?
- Which map, permit, construction package, public-report filing, financing event, sale, closing, occupancy, or phase release depends on completion?
- Which budget, disclosure, schedule, or operating assumption changes if the action changes?
- Which unresolved issue has a fallback path, and who may authorize that path?
A condition with a distant formal deadline may require an early decision because its design, property-rights, procurement, or agency-review path spans several months.
Useful fields: predecessors; successors; decision deadline; cost exposure; schedule exposure; fallback path.
8. Close, Preserve, and Hand Off the Record
Closure should identify what occurred, who accepted it, when acceptance occurred, and where the evidence resides. Retain continuing obligations in an active operations, association, owner, or property-management record.
At each major handoff—final map, permit issuance, construction start, occupancy, public-report issuance, closing, facility opening, association transition—prepare a concise package that identifies:
- obligations completed for that milestone;
- obligations accepted by the responsible authority;
- obligations continuing into the next phase;
- open interpretations or contingencies;
- evidence locations; and
- the person or entity assuming responsibility.
The handoff package should also identify any representation in a public report, disclosure, budget, agreement, or operating plan that depends on the continuing obligation.
Useful fields: closure status; acceptance date; evidence link; continuing obligation; receiving owner; next review date.
The Core Register Fields
A project can adapt the following field set to its size and complexity:
- Obligation ID
- Source document and section
- Exact source text
- Action statement
- Applicable area or phase
- Formal trigger
- Internal target date
- Action owner
- Coordinator and contributors
- Professional reviewer
- Sponsor decision owner
- Agency or accepting authority
- Required evidence
- Predecessors and successors
- Current status
- Open issue or decision
- Submission and response history
- Closure evidence and date
- Continuing obligation and handoff owner
- Last review date
Use controlled status terms. A practical sequence is: unassigned; scoping; in production; professional review; sponsor decision; ready to submit; agency review; revision; accepted; continuing; closed. Define each term in the register protocol so every contributor applies it consistently.
The Operating Rhythm
Approval-Record Workshop
Soon after approval, assemble the sponsor, project manager, planner, engineer, surveyor, architect, environmental team, counsel, and other relevant contributors. Confirm the source inventory, divide compound obligations, identify early interpretations, and assign the first decision dates.
Regular Implementation Review
Review obligations by milestone and exception. Focus the meeting on actions with approaching triggers, unassigned ownership, unresolved interpretations, missing property rights, professional-review needs, agency dependencies, cost or schedule exposure, and changes affecting several workstreams.
Milestone Readiness Review
Before each major map, permit, construction, filing, closing, occupancy, or phase event, confirm that the register shows the required evidence, acceptance status, and continuing obligations for that milestone.
Periodic Source Reconciliation
Compare the register against the current conditions, mitigation program, plans, agreements, agency correspondence, and approved changes. Reconciliation protects the record from silent drift as the project evolves.
Questions to Resolve
- Have all adopted conditions, mitigation measures, design commitments, agreements, and referenced requirements been captured?
- Which obligations contain several independently trackable actions?
- Which terms require legal, technical, or agency interpretation?
- Which obligations affect final mapping, permits, public reports, budgets, disclosures, sales, occupancy, or phase delivery?
- What evidence will demonstrate completion, and who accepts that evidence?
- Which obligations continue after approval, recordation, construction, closing, or turnover?
- Which open action carries the greatest cost, schedule, or redesign exposure?
Practical Next Steps
Assemble the Controlling Source Set
Collect the adopted approval documents, referenced plans and reports, mitigation program, agreements, and later written clarifications. Assign one records custodian and confirm the current version of each source.
Build the First Register at Action Level
Preserve each source reference and divide compound requirements into separate actions with distinct owners, triggers, evidence, and acceptance paths.
Hold a Responsibility and Evidence Workshop
Assign production, coordination, professional review, sponsor decision, agency acceptance, and records-control roles. Define the expected closure evidence for every near-term action.
Connect the Register to the Project Schedule
Link each obligation to the milestone it enables and the activities it requires. Establish internal target dates that account for professional and agency review.
Open the Change and Decision Record
Record interpretations, agency direction, sponsor choices, and project changes in one controlled history. Distribute each decision to every affected workstream.
