Give the sponsor, reviewer and buyer a shared task.
A program owner may need a reliable answer across policy versions. An IT reviewer needs to understand the package, device, processing locations and external dependencies. An acquisition lead needs a bounded scope, current commercial facts and a clear acceptance decision. One generic AI presentation does not settle all three questions.
Begin with a recurring document job that staff already know how to check. Examples include locating an applicable policy passage, comparing a revised internal procedure and preparing a briefing draft with a source list. The review owner remains responsible for interpreting policy and approving work.
- Federal teams: establish the agency context, system boundary, approved alternatives and purchasing route.
- State and local teams: choose a relevant policy corpus, account for device and support fit, and include accessibility review.
- Public legal and public-safety administrators: use an appropriate professional reviewer and a narrow administrative task.
Which policy version supplies the answer?
A policy comparison should distinguish changed requirements, unchanged wording and separate instruments with similar names. This editorial example compares selected official passages checked on October 17, 2026 to help plan version and scope checks for an evaluation.
Read the original clauses for their scope and conditions. For optional practice, the fictional office-policy files below offer a smaller revision exercise: identify the changed review schedule and preserve the unanswered disclosure question. Their invented rules are not agency requirements.
| Comparison | Selected source finding | Dated passage |
|---|---|---|
| Which OMB version replaces the earlier one? | M-25-21 expressly rescinds and replaces M-24-10. | M-25-21, April 3, 2025, PDF/printed p.1, Overview final sentence; M-24-10 is dated March 28, 2024. |
| Which CAIO seniority threshold changes? | For other agencies, the minimum changes from GS-15/equivalent to Grade 14/equivalent. CFO Act agencies retain the same named tiers: Senior Executive Service, Scientific and Professional, or Senior Leader level, or equivalent. | M-24-10, March 28, 2024, PDF/printed p.8, §3(b)(iii); M-25-21, April 3, 2025, PDF/printed p.10, Appendix §3(a)(i), seniority paragraph. |
| Does the selected NSS exclusion change? | Both OMB passages exclude AI when used as a component of a National Security System (NSS). This does not classify a particular system. | M-24-10, March 28, 2024, PDF/printed p.4, §2(c); M-25-21, April 3, 2025, PDF/printed p.5, Appendix §1(c). |
| Does NSPM-11 replace OMB M-25-21? | NSPM-11 names National Security Memorandum-25 and associated guidance as its replacement target. That is a different instrument from OMB M-25-21. | NSPM-11, June 5, 2026, official HTML §3(f); compare M-25-21, April 3, 2025, PDF/printed p.1, Overview. |
| What does the 90-day direction establish? | NSPM-11 directs a separate NSS AI governance policy within 90 days, consistent with §2 and seeking consistency with non-NSS requirements only to the extent appropriate. The direction and elapsed time are not evidence of issuance or implementation. | NSPM-11, June 5, 2026, official HTML §3(c). |
Keep a briefing draft traceable.
Select the permitted source packet, write a bounded question and inspect the source references returned by the candidate workflow. For a briefing draft, check each factual statement against the underlying passage. Retain unresolved conflicts rather than silently choosing the most convenient wording.
Test a missing passage and an older version alongside straightforward questions. Record whether a reviewer could identify the correct source, how much correction was needed and which facts were omitted. A fluent draft is an intermediate work product; acceptance belongs to the designated reviewer.
Scope a public-safety administrative task.
A police, fire or other public-safety administration team can begin with an approved policy-reference question: “Which revision names the reviewer for this training packet?” Select the permitted documents and require the answer to identify the exact passage, revision and any unresolved applicability question.
Pair the question with a fictional administrative handover: a document is missing, an owner is proposed but unapproved, and two records list different revisions. Require source references for each draft field, leave unknowns visible and retain the reviewer’s corrections before saving or exporting an accepted draft.
The COPS Office’s January 2025 discussion of AI-assisted police-report drafting raises review, training and accountability concerns. Those concerns help define review responsibilities for this narrower policy-reference and administrative exercise.
- Name the person responsible for checking the approved policy and accepting the draft.
- Check every source reference, missing field and proposed-versus-approved distinction.
- Retain edits and unresolved questions so the next reviewer can trace the decision.
Start with the actual device and data path.
Apple Silicon Mac is the planned first platform. A future evaluation will need to establish the package, model, hardware and installation requirements. The intended provider policy requires separate approval; parsing, indexes, logs, diagnostics, updates and exports also belong in the data-flow review.
For disconnected requirements, stage the necessary assets and test startup, restart, import, the selected task and recovery under the intended connectivity conditions. Describe observed behavior of the tested package. A proposed architecture or an offline answer by itself does not establish readiness for an agency environment.
Define a bounded evaluation and a purchasing decision.
Name the sponsor, users, IT owner and acceptance reviewer. Record the corpus, allowed actions, baseline task, acceptance criteria, duration, support responsibilities and exit plan. Separate trying the software from any later paid purchase or formal authorization.
Ask Qwerty about its actual offer and access status for the intended evaluation. This page does not establish a government contract vehicle, agency authorization or approved deployment. The useful next step is a workflow and environment review based on current facts.
- Identify the staff task and current alternative.
- Agree on data ownership, device conditions and review responsibilities.
- Measure actual correctness, source support, omissions and correction time.
- Retain failed runs and unresolved deployment requirements.
- Decide whether evidence supports a further evaluation or a purchasing discussion.
Sources and further reading
- OMB M-24-10 — March 28, 2024 (archived official memorandum) · Reviewed 2026-10-17
- OMB M-25-21 — April 3, 2025 · Reviewed 2026-10-17
- NSPM-11 — June 5, 2026 · Reviewed 2026-10-17
- COPS Office: AI-assisted report drafting — January 2025 · Reviewed 2026-10-17
- Qwerty product and selected-file workflow · Reviewed 2026-10-16
- Qwerty deployment and supported environment · Reviewed 2026-10-16
- Qwerty evaluation methods · Reviewed 2026-10-16