How Town Planning Works | TPW-0128 — The Administrative Adjustment: How Small Zoning Deviations Get Solved Without Pretending Every Imperfect Site Needs a Variance

Series ID: TPW-0128

A zoning code can be perfectly reasonable at city scale and still fit one ordinary parcel badly.

A setback misses an existing wall by 18 centimetres. A narrow infill lot cannot meet a standard written around wider suburban parcels. A heritage tree occupies the only place where a compliant driveway would fit. A public road dedication removes a sliver of land and turns a previously legal lot fractionally noncompliant. A small addition needs a 6 per cent adjustment to lot coverage but changes nothing meaningful about the neighbourhood.

One response is to send every case to a formal variance hearing.

Another is to pretend the code has no flexibility.

A third response is the administrative adjustment: a tightly bounded mechanism allowing planning staff or another delegated official to approve small deviations from specified dimensional or numerical standards without changing the zoning district and without opening the full variance process.

Names differ. Jurisdictions use terms such as minor adjustment, administrative variance, administrative modification, project adjustment or minor deviation. The exact legal authority also differs. The operating idea is consistent: small departures should have a small process when the policy consequence is genuinely small.

The reader job: distinguish bounded flexibility from an unofficial rewrite of the zoning code

This article explains when administrative adjustment works, what may be adjusted, how percentage limits function, why use and density usually remain off-limits, how findings and notice protect neighbours, how appeals work, how repeated adjustments reveal bad code, and where the mechanism must stop before it becomes a substitute for variance, rezoning or code amendment.

The neighbouring owners are important. The Zoning Variance owns hardship-based relief from zoning standards. The Zoning Interpretation owns ambiguity in what the code means. The Site Plan Review owns whether a project’s layout complies with applicable standards. The Rezoning Map Amendment owns changing the district itself.

The Administrative Adjustment owns a narrower job: when the policy remains correct and the proposed use remains allowed, can a small numeric deviation solve an ordinary site problem without invoking a much larger decision process?

The core idea is proportional process

Planning systems often create the same procedural burden for very different decisions.

A 2 per cent setback adjustment can require the same application, public hearing, board agenda and legal notice as a request with much larger neighbourhood consequences.

That is inefficient for applicants, staff, hearing bodies and residents.

Modern unified development ordinances increasingly create bounded administrative pathways for minor deviations. A recent draft Unified Development Ordinance for Sumter, South Carolina, for example, describes administrative adjustments as slight modifications that staff may approve so minor deviations do not automatically require a formal zoning amendment or variance. Rock Hill, South Carolina, publicly identifies numerical standards that staff may adjust up to stated percentages. Coconino County, Arizona, lists specific dimensional categories and maximum adjustment ranges.

The lesson is not the percentage chosen by any one jurisdiction. The lesson is architectural: the code can define a small box of delegated flexibility in advance.

The adjustment should change a number, not the planning policy

Administrative adjustment works best for measurable dimensional standards.

Setbacks.
Lot width.
Lot depth.
Lot coverage.
Building height within a small percentage.
Fence or wall height.
Parking dimensions or small parking-count adjustments.
Loading-space geometry.
Build-to zones.
Transparency or frontage dimensions.
Separation distances.

The mechanism is weakest when used to change categorical policy.

Is this use allowed? Should density increase? Can protected habitat be disturbed? May a public road requirement disappear? Should a condition imposed after a hearing be removed?

Those are not naturally minor numeric questions.

Use changes should usually be off-limits

A 10 per cent setback adjustment and a new land use are not the same species of decision.

If the zone permits homes but not a nightclub, staff should not be able to “adjust” the use table administratively merely because the applicant describes the nightclub as small.

Use permissions express compatibility policy. They should change through the procedure the code assigns to use decisions: by-right approval, conditional use, temporary use, rezoning, code amendment or another recognised mechanism.

A good administrative-adjustment section says this explicitly.

Density changes should usually be off-limits too

Density affects infrastructure, neighbours, land value and housing supply.

A staff-level mechanism designed to solve small geometry problems should not quietly become a second density-bonus system.

Some codes allow limited dimensional changes that incidentally improve yield. That is different from authorising more units directly.

The distinction keeps the adjustment focused on physical fit rather than policy expansion.

The percentage cap is a jurisdiction’s definition of “minor”

Administrative-adjustment codes often use percentage limits.

One jurisdiction may allow a 10 per cent change in setbacks, height or lot coverage. Another may allow 20 per cent in a historic centre but only 10 per cent elsewhere. Maryland law authorises local legislative bodies to delegate administrative adjustments for height, setback, bulk, parking, loading and similar requirements subject to locally developed criteria and procedure.

The percentage is not a universal planning constant.

It is a governance boundary: below this line, staff may consider relief through a simpler path; beyond it, the application enters the ordinary variance or amendment system.

A percentage cap should not be the only test

A 10 per cent deviation can be trivial in one context and significant in another.

Ten per cent of a 3-metre setback is 30 centimetres. Ten per cent of a 30-metre height limit is 3 metres—potentially an additional floor.

The code should therefore pair numerical limits with substantive findings.

The adjustment remains consistent with the purpose of the district.
It does not materially harm neighbouring property.
It does not increase a use, density or intensity category the code reserves for another process.
It does not remove required public infrastructure.
It is the minimum adjustment reasonably necessary.
It preserves the overall intent of the applicable standard.

The minimum-necessary test prevents convenience from becoming entitlement

An applicant may be eligible for up to a 10 per cent adjustment.

That does not mean every applicant automatically receives 10 per cent.

If 3 per cent solves the documented site problem, the decision should not casually grant 10.

This keeps delegated authority tied to the reason the mechanism exists: solving a minor constraint without creating unnecessary additional development rights.

Administrative adjustment is different from hardship variance

Variance law in many jurisdictions requires unusual property conditions and a finding of hardship or practical difficulty. The applicant may need to show that strict compliance creates a special burden not generally shared by neighbouring property.

Administrative adjustment is often intentionally easier.

The code may permit a small numerical departure because rigid precision creates unnecessary friction, even where the situation would not satisfy the legal hardship test for a variance.

That distinction is valuable. It prevents formal variance law from being stretched to excuse everyday design tolerances.

Do not call an adjustment a variance if the findings are different

Names matter less than legal substance.

A jurisdiction may call the mechanism an “administrative variance”. Another calls it “minor adjustment”.

The useful question is: what criteria must the decision-maker apply?

If the law requires statutory hardship, treat it as variance relief. If the code instead authorises bounded staff discretion for listed standards based on compatibility and intent, it operates more like administrative adjustment.

Delegated authority needs a bright boundary

Administrative adjustment transfers decision authority from a board or elected body to staff.

That can dramatically reduce delay.

It also raises a governance question: how much policy discretion should one official exercise without a hearing?

The safest delegation is specific.

List the standards that may be adjusted.
List the maximum amount of adjustment.
State required findings.
State prohibited outcomes.
State whether conditions may be imposed.
State whether notice is required.
State how the decision can be appealed.

“The planning director may waive any requirement when reasonable” is not a minor-adjustment system. It is uncontrolled discretion.

Notice can be scaled to impact

Some administrative adjustments are decided without neighbour notice. Others require mailed notice or a posting period before the decision becomes effective.

The appropriate approach depends on local law and the type of standard.

A 5-centimetre side-setback adjustment to regularise an existing wall may warrant little process. A 15 per cent height adjustment near a residential boundary may deserve notice even if staff retains decision authority.

The goal is proportionality: enough process to protect affected interests without recreating a full variance hearing for every small departure.

Appeal is the safety valve

A delegated administrative decision should ordinarily have a defined appeal path where local law permits.

The appeal may go to a zoning board, planning commission, hearing examiner, council or court depending on jurisdiction.

The important design point is that the appeal should review the administrative decision against the standards that governed it. It should not become an opportunity to invent a different policy test after the fact.

The existing Zoning Appeal article explains why the record, standard of review and remedy matter.

Cumulative adjustments need an anti-stacking rule

A project can defeat a percentage cap by applying repeatedly.

First 10 per cent. Then another 10 per cent after redesign. Then a separate adjustment to another standard that effectively produces the same outcome.

Good codes prevent stacking.

The adjustment limit should apply cumulatively to the original standard or original approved plan, and a project should not use multiple adjustment categories to circumvent a process that would otherwise require variance or amendment.

A previous variance should not automatically become the new baseline

Suppose a site already received a variance reducing a setback from 5 metres to 4 metres.

Can the applicant then request a 10 per cent administrative adjustment from 4 metres?

If allowed, the system can compound relief beyond what either procedure contemplated.

Many codes therefore prohibit adjusting a standard that was already modified by a separate variance or prior adjustment unless the governing rule expressly allows it.

Approved site plans need their own minor-modification rule

Administrative adjustment of a zoning standard is not exactly the same as a minor change to an already approved site plan.

During detailed design, a building may shift one metre, a driveway may move, a landscape area may be reconfigured or utility coordination may change a parking aisle.

Codes can establish a separate minor plan-modification pathway when the revised plan remains within zoning standards and preserves the concept and conditions of the approval.

Do not mix this with adjustment from the zoning code itself. One modifies an approved design. The other modifies how a regulation applies.

Infill is where administrative adjustment earns its keep

Older urban parcels were often created before modern dimensional codes.

Lots are narrow. Buildings sit close to boundaries. Alleys complicate setbacks. Utility easements occupy strange locations. Historic structures do not align with modern parking geometry.

Forcing every small infill project into a variance hearing can make reuse disproportionately expensive compared with greenfield construction.

A carefully written adjustment mechanism can reduce that penalty while preserving the public purpose of the code.

But infill flexibility should not erase neighbour protection

Small lots do not make impact impossible.

A side-setback reduction can change fire separation, privacy and drainage. A height increase can affect shadow. Reduced parking can alter curb pressure. A driveway adjustment can create a pedestrian conflict.

The finding should test the actual function of the standard being adjusted.

Why does the setback exist? Fire? Light? Privacy? Streetscape? If the alternative design still achieves the purpose, a small adjustment may be reasonable. If it defeats the purpose, numerical eligibility alone should not control.

Alternative equivalent compliance can be a sister tool

Sometimes the issue is not that the standard should be reduced. The applicant can achieve the same public outcome differently.

A landscape rule may require one buffer configuration, but site conditions allow an alternative planting and wall system with equal or better screening. A façade standard may require one form of articulation, but another design creates the same pedestrian effect.

Alternative equivalent compliance differs from numeric adjustment. It keeps the performance target and permits a different method.

This can be more intellectually honest than pretending every alternative design is merely a percentage reduction.

Environmental protection standards should rarely be adjustable by convenience

A wetland buffer, floodway restriction, habitat protection line or drinking-water safeguard may reflect risk that does not scale like an ordinary setback.

The administrative-adjustment section should identify protected standards that cannot be modified through the minor pathway.

If technical evidence justifies a change, use the environmental review or specialised waiver process designed for that subject.

Public infrastructure standards should usually remain outside the shortcut

A private setback can sometimes move slightly without public consequence.

A fire-access width, road connection, sewer easement or stormwater facility may affect system performance beyond the parcel.

Administrative-adjustment authority should not casually waive standards owned by another technical agency.

Where flexibility is appropriate, the code can require written concurrence from the responsible agency or use a separate engineering-deviation process.

A good application is small because the evidence is targeted

Administrative adjustment should not require the documentation package of a rezoning.

Typical evidence can include:

A site plan showing the standard and requested deviation.
A numerical table showing the required, proposed and percentage change.
A short planning rationale.
Photographs of site conditions.
Survey information if boundaries matter.
Evidence of tree, easement, topographic or existing-building constraints.
Any technical agency comment required by the code.

The process should be proportionate without becoming casual.

The decision should be written even when the process is simple

A staff email saying “looks fine” is weak administration.

The written decision should identify the property, standard, approved deviation, findings, conditions, plan revision date, appeal period and expiration if applicable.

Future reviewers need to know why the building sits closer to the boundary than the code table suggests.

The approval should attach to a defined project or property

Does the adjustment run with the land? Does it expire if construction never begins? Does it apply only to the approved plan? Can a later owner use the same deviation for a different building?

The code should answer these questions.

Small decisions still need lifecycle rules.

Repeated adjustments are code diagnostics

Imagine that 70 per cent of new main-street projects request the same 10 per cent build-to adjustment.

Perhaps developers are unusually uncooperative.

More likely, the standard does not fit common parcel geometry, fire access, utility placement or existing building patterns.

Track adjustment requests by standard, district, percentage, reason and outcome. A concentration of similar requests is feedback for the next code amendment.

A flexible code should learn from how often it needs flexibility.

Approval rates can reveal rubber-stamping

If virtually every request receives the maximum adjustment, the process may no longer be applying findings.

If almost no request is approved, the mechanism may be too narrow to justify its existence.

Monitor outcomes. Compare requested percentages with approved percentages. Review whether conditions are common. Examine whether appeals overturn staff decisions.

Administrative systems deserve performance review just like public infrastructure.

Equity matters because process cost is not evenly distributed

A formal variance may require fees, drawings, consultants, legal notice and attendance at an evening hearing.

Those burdens are easier for a large developer than for a homeowner, small landlord or local business.

A minor administrative path can reduce unequal transaction costs for genuinely small requests.

But discretion can create another equity problem if applicants with professional representation receive better informal access to staff.

The antidote is published criteria, standard forms, written decisions and searchable precedent.

Precedent should guide consistency without freezing judgment

Two similar parcels should not receive opposite adjustment decisions without a reason.

Maintain a database of prior decisions. Staff can compare site conditions, percentages, findings and imposed conditions.

Precedent does not mean every case is identical. It means difference needs explanation.

Automation can help with the arithmetic, not the judgment

A digital permit system can calculate whether a request falls inside the authorised adjustment range.

Required setback: 5 metres. Proposed: 4.6. Difference: 0.4. Percentage reduction: 8 per cent. Eligible threshold: up to 10 per cent.

That is easy to automate.

Whether the 8 per cent reduction harms a neighbouring window, conflicts with fire separation or remains consistent with district intent may still require professional judgment.

Worked example: the narrow infill lot

A code requires a 3-metre side setback. A narrow pre-war lot has an existing house positioned so an accessible addition can fit only with a 2.76-metre setback.

The requested reduction is 8 per cent. The code allows administrative setback adjustments up to 10 per cent if the adjustment is the minimum necessary, remains compatible with adjoining property and does not affect fire-access requirements.

The planner confirms the property line by survey, checks the adjoining windows, obtains fire-review concurrence and approves 2.76 metres with a condition that roof drainage remain onsite.

No hardship hearing was needed because the code deliberately created a smaller proportional tool.

Worked example: the request that should be a variance

A restaurant wants to reduce a required 6-metre rear setback to 3 metres to add more dining area.

The code permits administrative reduction only up to 10 per cent. The proposal requests 50 per cent.

Staff should not split the request into several administrative adjustments or reinterpret the standard. The applicant must redesign or use the variance procedure and satisfy its separate findings.

The boundary protects the legitimacy of both mechanisms.

Worked example: the request that should be a rezoning or code amendment

A residential zone permits two storeys. A landowner asks staff to administratively approve six because nearby property has recently redeveloped at greater intensity.

This is not a minor geometric fit problem.

The appropriate question is whether planning policy for the area has changed. That belongs in rezoning, area planning or code amendment—not administrative adjustment.

An administrative-adjustment audit

Authority: What law authorises staff or the designated official to grant minor relief?
Eligible standards: Which dimensional or numerical standards may be adjusted?
Excluded standards: Which uses, density, environmental protections, public infrastructure or prior conditions are off-limits?
Maximum deviation: What percentage or absolute change is allowed for each standard?
Baseline: Is the percentage measured from the original code requirement rather than a previous variance?
Anti-stacking: Can multiple adjustments be combined to evade the formal process?
Findings: Must the decision remain compatible, minimum necessary and consistent with district purpose?
Function: Does the alternative still achieve the public purpose of the standard?
Evidence: What survey, site plan, photographs or technical review are needed?
Notice: Do affected neighbours receive notice for more consequential adjustments?
Decision: Is approval written and attached to a defined plan?
Conditions: Can staff impose narrowly related conditions?
Appeal: What body reviews the administrative decision?
Expiration: Does approval expire if the project does not proceed?
Transfer: Does the approval run with the land or only the approved project?
Record: Can future owners and staff discover the adjustment?
Metrics: Which standards generate the most requests?
Equity: Does the process reduce cost without creating informal insider access?
Feedback: Are repeated requests triggering code reform?

Minor relief works when the code is confident about what “minor” means

A zoning system with no flexibility becomes brittle.

A zoning system with unlimited staff discretion becomes unpredictable.

Administrative adjustment is the engineered space between those failures.

It allows a small amount of movement where the policy remains intact. It makes the process proportionate to the consequence. It keeps ordinary site geometry from consuming hearing calendars. It reserves variance for true hardship and rezoning for real policy change. It produces a written record. It creates data about standards that repeatedly fail.

The mechanism succeeds when a planner can say: the code still means what it meant, the neighbourhood still receives the protection the standard was designed to provide, and this small deviation is simply a better fit for this particular piece of land.