Editorial Standards & Review Policy
A public standard for how Alliance attributes, verifies, reviews, updates and corrects permit information — while keeping technical design, code interpretation and approval decisions with the professionals and authorities responsible for them.
This policy applies across permitting guides, Permit Intelligence, commercial content and case studies.
Trust should be built into the content system, not added as decoration.
Alliance should make the source, owner, review status and freshness of important permit information visible enough that a customer, editor or search system can understand where the information came from and how it should be used.
Permit Guides
Authority, portal, codes, requirements, fees, review timing, registration, inspections, local rules, official sources and last-verified fields.
Permit Intelligence
Benchmarks, rankings and metrics need defined measurements, transparent methodology, source traceability and limitations.
Commercial Proof
Case-study outcomes, customer claims and quantitative statements should be backed by approved project information before publication.
Show who prepared the information — and never invent authority.
Attribution should reflect actual work performed. A generic research-team byline can identify the team responsible for structured research, while a named reviewer should appear only when a specific person has completed that review.
Research owner
Use “Alliance Permitting Research Team” or the actual author when that accurately reflects who prepared or maintained the page.
Named reviewer
Display a named permit professional only when that person actually reviewed the content. Do not use placeholder names, implied licenses or unverified credentials.
Role & specialization
Where a named reviewer is used, include the verified role, relevant experience or specialization needed to help readers understand the review context.
Last verified
Important jurisdiction and data pages should display when the underlying permit information was last checked against the cited source.
Use the strongest available source for each factual permit requirement.
Source quality matters because permit rules change and secondary summaries can become stale. Alliance should preserve the source behind the structured field whenever practical.
Primary government authority
Official city, county, state, agency, building department or fire authority pages.
Highest preference for current requirementsOfficial operational documents
Permit portals, application forms, fee schedules, ordinances, adopted-code pages, checklists and agency manuals.
Use for workflow-specific fieldsDirect official clarification
Project-specific or department clarification may help resolve ambiguity, but should be distinguished from generally published rules.
Document context and dateSecondary context
Industry publications and other third-party sources can add context, but should not replace an available authoritative source for a permit requirement.
Context, not primary authorityA repeatable six-step path from research to published page.
Identify scope
Define the jurisdiction, permit type, audience and fields being researched.
Collect sources
Locate the official department, portal, forms, ordinances, code pages and other primary records.
Verify fields
Match each important statement to a current source and record the verification date.
Resolve conflicts
Where sources disagree, do not silently choose one. Re-check, narrow the statement or flag uncertainty.
Review & publish
Apply editorial QA, attribution, safe service language, internal links and appropriate schema.
Maintain
Re-check high-value or high-change information and retain material updates through change history where supported.
Permit information changes. The published record should show that.
Portals, fees, forms, codes, review procedures and contacts can change after a page is published. The editorial system should make corrections reviewable and traceable rather than treating every page as permanently final.
Be precise about what Alliance knows, handles and can prove.
Editorial review is also a claims-control system. Service language should describe administrative permit work accurately without expanding into professional services or guarantees Alliance does not provide.
Use: requirements research
Jurisdiction research, document completeness review, requirement matching, submission preparation, issue identification, permit tracking and workflow intelligence.
Avoid: unsupported compliance claims
Do not say Alliance certifies code compliance, interprets building code, provides legal/zoning opinions or performs licensed architecture or engineering.
Avoid: guaranteed outcomes
Do not promise approval, fixed review speed or rejection reduction unless the statement is clearly defined and backed by approved measurable evidence.
Use: measurable proof carefully
Case-study metrics should come from verified Alliance project information. Customer names can remain confidential when necessary.
Use: metric definitions
Permit Intelligence should distinguish targets, observed averages, statutory limits and other measurement types instead of blending them into one misleading number.
Use: responsibility boundaries
Licensed professionals and reviewing authorities remain responsible for technical design, code interpretation, inspections, professional seals and approval decisions.
Make trust metadata reusable across the website.
These fields can support guides, Permit Intelligence, case studies and future editorial tooling without manually rebuilding the same trust information on every page.
| Field | Purpose | Publication rule |
|---|---|---|
| prepared_by | Research team or actual author responsible for preparing the page. | Show only accurate attribution. |
| reviewed_by | Named reviewer who materially reviewed the content. | Optional; never fabricate. |
| reviewer_role | Verified title, specialization or relevant experience context. | Use only with a real reviewer record. |
| last_verified | Date the underlying permit information was last checked. | Important on jurisdiction and data pages. |
| official_sources | Source IDs or URLs supporting material permit facts. | Prefer primary government sources. |
| source_type | Jurisdiction page, statute, ordinance, form, portal, fee schedule or other classification. | Enables source-quality filtering. |
| content_status | Draft, verified, review-needed, stale or published. | Prevents uncertain data from appearing definitive. |
| change_history | Previous value, new value, date, verifier and source. | Retain material data changes. |
| claim_evidence | Approved support for quantitative or outcome claims. | Required before strong performance claims publish. |
One trust layer should support the entire Alliance information system.
The editorial policy works alongside the Permit Intelligence methodology rather than creating a separate content process.
Permit Intelligence
Benchmarks and proprietary metrics should inherit the same source, measurement and correction standards.
How Alliance should attribute, verify and maintain permit information.
Who prepares Alliance permitting guides and research pages?
Important research-driven pages should identify the responsible content team, such as the Alliance Permitting Research Team. A named individual should be shown only when that person actually prepared or materially reviewed the page.
Does every Alliance page require a named expert reviewer?
No. Named expert review should be used where it materially strengthens accuracy or accountability and only when a specific qualified person actually completed that review. Alliance should not fabricate reviewer attribution or credentials.
What sources should Alliance rely on for permit requirements?
Official jurisdiction, agency, statute, ordinance, portal, form, fee schedule and other primary government sources should be preferred. Secondary sources may provide context, but they should not replace an available authoritative source for a permit requirement.
How should Alliance handle permit-information changes or corrections?
Pages should display a last-verified date where appropriate, retain source links, route reported discrepancies for re-checking, and update the published record when a change is verified. Material data changes should also be retained in change history where the structured database supports it.
Does Alliance editorial review include code interpretation or a guarantee of permit approval?
No. Alliance publishes permit research and administrative workflow information. Licensed professionals and reviewing authorities remain responsible for technical design, code interpretation, professional seals, inspections and approval decisions. Published information should not promise approval or substitute for an official jurisdiction determination.