PROJECT REVIEW WORKSPACE

Browse source inventory and coverage

Know what has actually been checked.

Evaluate supported requirements, inspect plan text and see the evidence still needed. Start with fence and selected ADU checks. Every catalog form shows its current coverage gaps.

This tool does not yet perform a complete code review. A passing individual check is conditional on your evidence and does not authorize construction.

Saved revisions include facts, PDF extraction and site evidence. The checksum detects changes; it does not authenticate evidence or certify compliance. Original PDF bytes are not included.

Project and property facts

Use a parcel map, survey, recorded decision or other property evidence. A mailing address or point lookup alone does not establish the entire parcel’s constraints.

Fence design

Front regulated area extends to the lesser of the required front setback and the primary building line. For multiple fence segments, save a separate check for each location and height.

Requirement results

Review incomplete

Building-permit requirement is undetermined.

12 checks need evidence, implementation or review. Complete code coverage has not been established.

Review needed

Source snapshot date

This date differs from the reviewed source snapshot. Confirm applicable editions and amendments before relying on numerical results.

Oregon adopted specialty codes
Inputs and source version

Edition selection depends on project, discipline and application date

Evidence needed

Property jurisdiction

Confirm that the work is within Portland's applicable permitting jurisdiction; a mailing address alone is insufficient.

Portland Title 33 — zoning code
Inputs and source version

Applicability and referenced chapters require project-specific review

jurisdiction: Not provided

Evidence needed

Base zone, overlays, historic status and plan district

Missing or contradictory parcel facts: zoneCode, overlaysPresent, historic, planDistrictPresent. A failed layer query is unknown.

Portland Title 33 — zoning code
Inputs and source version

Applicability and referenced chapters require project-specific review

zoneCode: Not provided

overlaysPresent: Not provided

historic: Not provided

planDistrictPresent: Not provided

Evidence needed

Building permit requirement (not a zoning approval)

Supply valid height, classified material, pool-barrier status and, for wire/chain link, confirmation of typical field-fence construction.

Portland 24.10.072.B — fence permit exceptions
Inputs and source version

Public text reviewed 2026-09-09

fenceHeightFt: Not provided

fenceMaterial: Not provided

poolBarrier: Not provided

typicalFieldFence: Not provided

Evidence needed

Height measurement basis

Include posts, lattice and trellises; measure at grade immediately below the fence. Retaining walls need their separate measurement and regulatory treatment.

Portland fence construction and measurement guidance
Inputs and source version

Live guidance reviewed 2026-09-09; not a complete structural code

heightIncludesPosts: Not provided

heightFromGrade: Not provided

retainingWall: Not provided

Rule coverage missing

Single-dwelling base-zone fence height

Select the measured fence location and relevant exceptions. Other base zones and fences outside building setbacks need additional height rules. Front regulated area is the lesser of the required front setback and distance to the primary building line.

Portland 33.110.275 — fences in single-dwelling zones
Inputs and source version

Relevant pages 110-48/49: 3/1/25 and 1/1/25

zoneCode: Not provided

fenceHeightFt: Not provided

fencePosition: Not provided

cornerAlternative: Not provided

cornerLot: Not provided

entranceFacesSideStreet: Not provided

distanceSideStreetFt: Not provided

abutsPedestrianConnection: Not provided

pedestrianRowWidthFt: Not provided

Evidence needed

Prescriptive dimensions for fences over 7 through 8 feet

Provide dimensions for the supported wood/metal/wire path, or obtain project-specific Oregon engineering review. An engineered alternative is not automatically a violation.

spacing <= 6 ft; diameter >= 18 in; embedment >= 3 ft

Portland fence construction and measurement guidance
Inputs and source version

Live guidance reviewed 2026-09-09; not a complete structural code

fenceHeightFt: Not provided

fenceMaterial: Not provided

postSpacingFt: Not provided

footingDiameterIn: Not provided

footingDepthFt: Not provided

Evidence needed

Footings and fence inside property lines

All components, including footings, must remain inside property lines. A point geocode does not establish these boundaries.

Portland fence construction and measurement guidance
Inputs and source version

Live guidance reviewed 2026-09-09; not a complete structural code

allPartsInsideProperty: Not provided

Evidence needed

Pool barrier safety details

Pool barriers need opening, clearance, gate, latch and access-path checks; a height-only test is insufficient.

Portland fence construction and measurement guidance
Inputs and source version

Live guidance reviewed 2026-09-09; not a complete structural code

poolBarrier: Not provided

Evidence needed

Electrical, barbed wire, retaining wall and site conditions

Special fence construction references other titles. Utilities, access easements, tree impacts and prior approvals require additional site review.

Portland 33.110.275 — fences in single-dwelling zones
Inputs and source version

Relevant pages 110-48/49: 3/1/25 and 1/1/25

electrified: Not provided

barbedWire: Not provided

retainingWall: Not provided

Rule coverage missing

Remaining construction, material durability, site and referenced provisions

No complete executable rule pack is available for this requirement. Route for review; never infer a pass from absent rules.

Oregon adopted specialty codes
Inputs and source version

Edition selection depends on project, discipline and application date

Rule coverage missing

Survey geometry, easements, trees, hazards and previous land-use conditions

No complete executable rule pack is available for this requirement. Route for review; never infer a pass from absent rules.

Oregon adopted specialty codes
Inputs and source version

Edition selection depends on project, discipline and application date

Technical plan schedules

Check recorded residential elements, trade components and commercial energy systems. Current sheets, consistent measurements and a complete declared inventory are required. These checks do not independently interpret all drawing geometry or certify full code compliance.

Parcel and plan geometry

Use a survey-based polygon in local feet to measure a footprint against classified parcel edges. Public GIS intersections are separate evidence and are never automatically marked verified.

Measure supplied plan geometry

Download JSON example

Query public parcel constraints

Inspect a plan PDF

The file stays in your browser. This extracts page text and explicitly labelled fence dimensions, preserving the document hash and page reference. Confirm dimensions against the actual drawing before using them.

The example is a synthetic text sheet, not a construction plan.