Editorial policy

1. Primary sources control the rule

We prefer current government regulations, official program releases, NIST publications, and the National Archives CUI Registry. A secondary article can alert us to a change, but the published guide should point readers to the controlling primary material whenever it is publicly available.

2. Dates and revisions are explicit

CMMC is unusually sensitive to implementation dates and document revisions. Guides state an update date and identify major program changes. When NIST publishes a new revision while an acquisition program still operates on a different baseline, we describe both facts instead of silently mixing controls from two revisions.

3. System-specific language

We avoid unsupported statements that an entire company is 'CMMC compliant.' Articles distinguish systems, enclaves, tenants, assessment types, SPRS records, and contract requirements. Examples are framed as implementation patterns rather than representations about a reader's specific contract.

4. No invented credentials

Marcus Whitlock reviews guides as compliance research editor. This byline is not presented as a C3PAO assessor, consultant, or government official, and we do not invent C3PAO experience, government employment, customer case studies, certifications, or expert quotes.

5. Distinct intent, independent checks

Each guide must answer a specific operational question rather than restating a generic compliance page with different keywords. Before publication we check factual claims against the cited sources, look for repeated or contradictory passages, verify internal links and navigation, and review the page in the context of the rest of the site.

6. Corrections and updates

Material program changes are prioritized. We update pages when a source changes the conclusion, a clause is revised, a deadline moves, or a cited government page is replaced. Correction requests can be sent to support@getleadsnap.online.