Approval register

Verify When Design and Approvals Are Required

Organize the project facts the City, engineer, geotechnical professional, surveyor and utility contacts may need to route the work.

Decision file

Build a clearer project record

01

Record geometry and loads

Prepare approximate wall height and length, grade difference, slope context and nearby uses. Do not use an uncited height threshold to decide the permit route.

02

Resolve the property line

Mark whether the wall, excavation, drainage or access may approach a boundary. Existing fences and occupation are not a substitute for survey evidence.

03

Ask the City from project facts

Describe whether the work is new, repair or replacement and identify related structures, guards, driveways and grading. Request the current application and review path.

04

Clarify professional responsibilities

Ask which design, field review and closeout documents are required and who prepares them. Engineering, geotechnical and survey roles are not interchangeable.

05

Locate utilities and access limits

Document known services, easements, overhead constraints, equipment routes and staging. Use current utility-locate and authority processes before work.

06

Keep an approval record

Log source, date, contact, project facts supplied, answer, required document and open question. Recheck if geometry or scope changes.

07

Build a responsibility matrix

List each decision that may involve the City, surveyor, structural engineer, geotechnical professional, utility owner or another reviewer. For every item, record the trigger, required input, expected deliverable and responsible person, then update the matrix whenever geometry, access or proposed work changes.

  • Reference the exact drawing revision
  • Record conditional answers
  • Track every open dependency
08

Prepare one authority brief

Use the same wall length, retained height, slope relationship, nearby uses and proposed intervention in every inquiry. Save the response date, department and documents referenced. Answers based on different facts should not be combined as though they govern one unchanged project.

  • Distinguish repair from replacement
  • State boundary uncertainty
  • Recheck after scope changes
09

Sequence submissions and field records

Map when survey, design, geotechnical inputs, utility information, permit submissions, inspections and field-review documents are needed. Connect every approval or letter to a drawing revision and wall segment so a superseded response cannot silently authorize changed work.

  • Log submission and response dates
  • Name required construction evidence
  • File final accepted records
10

Close the approval register without losing conditions

For every City or professional response, capture the project facts supplied, date, reviewer, document revision, conditions and next action. Connect survey, structural, geotechnical, drainage, utility and inspection outputs to the exact wall segment they govern. A conditional answer remains open until its required evidence is filed; an earlier response should be superseded when geometry or scope changes. At closeout, retain submissions, accepted drawings, field-review records and outstanding maintenance responsibilities so future work does not restart from an incomplete or mismatched approval history.

  • Use one project identifier
  • Track conditional responses separately
  • Withdraw superseded drawings
  • Reconcile final wall geometry
  • Archive authority closeout documents

Primary references

Verify current rules at the source

Links checked in the approved research packet on August 26, 2026. Applicability still depends on the property and proposed scope.