Schedule First Quarterly Audit Cycle

This page is a worked example (a leaf). The canonical for how we audit is How we audit.

Task Library

Launch the first quarterly definitive-article audit cycle – every article assigned to a named auditor with Q3 2026 as the deadline – turning Process 1 from spec into schedule.

Category: Knowledge System Maintenance

Use this when implementing the maintenance system – this Implementation Checklist task is a gap: no quarterly audit has ever run, every status-table row still reads "Not yet audited," and Q3 2026 is the committed first deadline.

Inputs

  • The Definitive Article Guide status table with the Last Audited column in place (add-last-audited-column-to-definitive-article-guide-status-table)
  • The team roster and the assignment method (schedule-and-assign-quarterly-auditors)
  • The four Process 1 audit skills, ready to hand to auditors

Steps

  1. Verify the prerequisite: the status table has its Last Audited column, initialized to "Not yet audited." If not, run that skill first – the cycle needs somewhere to write its results.
  2. Pull the complete definitive article list from the table and assign every article to a named team auditor using the assignment SOP: one auditor per article, balanced load, fresh eyes preferred over authors auditing their own work.
  3. Set Q3 2026 as the first cycle's deadline, per the Implementation Checklist, and calendar the audit window with a midpoint reminder so misses surface early.
  4. Equip each auditor with the Process 1 run order: check-topic-coherence-for-each-definitive-articleverify-structural-completeness-against-8-step-frameworkcheck-information-currency-with-latest-datavalidate-cross-reference-integrity-across-articlesupdate-status-table-in-definitive-article-guide.
  5. Set the completion bar explicitly: an article counts as audited only when all four checks ran and the status table row shows this cycle's date and a defensible Green/Yellow/Red.
  6. At the Q3 2026 deadline, verify coverage: every article stamped, every Yellow/Red carrying a follow-up owner. Carry misses visibly into Q4 with reassigned auditors – quietly dropping them resets the system to zero.
  7. Close the first cycle by capturing what broke (load, unclear checks, tooling) as Knowledge Capture Notes and amendments, so the second cycle runs smoother – the recursive loop applies to the cycle itself.

Definition of done (QA checklist)

  • Every definitive article assigned to a named auditor with the Q3 2026 deadline calendared (window + midpoint reminder)
  • All auditors equipped with the four-check run order and the completion bar
  • At deadline: 100% of articles stamped with date + status, or misses visibly carried into Q4 with new owners
  • First-cycle friction captured as Knowledge Capture Notes / SOP Amendment Proposals
  • Linked back to the definitive article and relevant siblings
  • Complies with Blog Posting Guidelines (if it publishes content)

Example(s)

  • /knowledge-system-maintenance – the Implementation Checklist sets Q3 2026 as the first audit deadline with articles assigned to team members. Gap: cycle not yet scheduled – running this skill closes it.
  • Example needed – run the Meta-Article Prompt (/meta-article-prompt-template) after the Q3 2026 cycle completes and link the meta-article here.

File in the zip: skills/knowledge-system-maintenance/schedule-first-quarterly-audit-cycle.md. Download the Task Library zip.

Index: Task Library. Article guidelines.

Scroll to Top