Source hierarchy • Local verification • Human review • Safety-conscious guidance
Our Editorial Standards for Building, Permit, Planning, and Code Information
Building information can affect property rights, construction cost, safety, project schedules, insurance, resale, and enforcement. We therefore treat accuracy and jurisdiction as essential, not optional.
Authority Before Convenience
We prefer the agency that actually controls the process over a more convenient third-party summary.
Jurisdiction Before Generalization
We identify the local authority before describing permit, zoning, or inspection requirements.
Effective Date Matters
Code editions, ordinances, fee schedules, and forms may be current only after a specific effective date.
Human Review
Important local-source claims and practical steps are reviewed before publication.
Our Editorial Workflow
- Define the user intent. We identify whether the article is about department contact, permit search, application, inspection, zoning, code, fees, contractor information, or building supplies.
- Resolve location and jurisdiction. We distinguish city limits, unincorporated county areas, townships, special districts, and other local structures when relevant.
- Find the controlling source. We prioritize official department pages, permit portals, forms, ordinances, adopted-code documents, and fee schedules.
- Check practical usability. We review the page or portal as a user would: what menu to open, what field to enter, what form to download, what office to call.
- Cross-check material details. Where appropriate, we compare the department page with related official sources such as code adoption, planning, GIS, inspection, or public-record pages.
- Write in plain language. We explain complex administrative steps without pretending technical or legal distinctions do not matter.
- Human review. Important links, material claims, and action steps are reviewed before publication.
Source Hierarchy
| Source type | How we generally use it |
|---|---|
| Official local building/planning department | Primary source for department responsibility, applications, inspections, fees, and local procedures |
| Official permit portal | Primary source for permit lookup, application status, inspection history, and project records |
| Official ordinance/code-adoption page | Primary source for locally adopted rules and effective dates |
| Official GIS/zoning map | Useful for understanding zoning and parcel context, subject to agency disclaimers |
| State licensing or code agency | Used when state-level rules, licenses, energy, accessibility, or statewide code requirements apply |
| Manufacturer/technical documentation | Used for product specifications, listings, installation requirements, and technical limitations |
| Third-party website | Secondary context only when an authoritative source is unavailable or additional explanation is useful |
Claims We Avoid Without Strong Support
- “No permit is required” without local support.
- “This product is code approved everywhere.”
- “This contractor is licensed for your project” without the relevant official license context.
- “This property is buildable” based only on a general zoning map.
- “This project will pass inspection.”
- “This fee is final” when a fee schedule shows variable valuation, plan-review, impact, or supplemental charges.
- “This code edition applies” without checking local adoption and effective date.
AI-Assisted Content Policy
AI tools may assist with research organization, outlines, drafting, language cleanup, comparison tasks, or quality checks. AI is never treated as a legal authority, code official, planning authority, engineering source, or final verifier of project-specific requirements.
Important source-based instructions and claims are reviewed by people before publication.
Corrections and Material Updates
We may revise a page when a department moves, a permit portal changes, an adopted code is updated, a fee schedule changes, a form is replaced, or a jurisdiction alters its process.
See our Sources & Corrections Policy.