PNM policy

Editorial and methodology

PNM guidance is designed to make a business decision clearer without pretending a general page is a project-specific agency determination.

Active operating policyEffective / reviewed: July 28, 2026

Source order

  1. Controlling law, regulation, or official agency material when applicable and available.
  2. Current public instructions, forms, and guidance from the responsible state or local agency.
  3. Verified PNM operating knowledge and first-hand project context that can be published without exposing private information.
  4. Secondary explanatory sources, clearly distinguished from the controlling authority.

Visible review record

Substantive guides display a jurisdiction, publication date, last-review date, review role, status, limitations, and primary-source links. Dates change when content is substantively reviewed or revised—not merely to simulate freshness.

Answer structure

Guidance begins with a direct answer, then explains conditions, exceptions, responsible agencies, limits, and the next useful action. PNM does not use artificial keyword repetition, mass-generated city pages, or hidden facts that appear only in machine-readable content.

Claim boundary

PNM does not publish an outcome, approval rate, client count, testimonial, price, turnaround time, jurisdiction list, credential, government relationship, or case result without source evidence appropriate for public use. Unknown or pending claims remain unpublished or clearly labeled pending.

Local-page standard

A city or county page may be published only when it provides distinct verified local value such as responsible departments, current source links, local decision points, forms, hearing requirements, or authorized case context. Swapping city names into the same page is not acceptable.

Corrections and conflicts

When a credible conflict or error is reported, PNM reviews the cited source and affected representations. Material corrections should update visible content, metadata, structured data, public JSON, and developer surfaces together.

Questions or corrections? Use the corrections process or email sherrie@permitsnmore.org.