Key takeaways
- Find every policy, including copies in unit binders and shared drives, before setting any dates.
- Get each owner's explicit acceptance; a name in a spreadsheet column isn't ownership.
- Spread out clusters of identical due dates left over from a past re-accreditation push.
- Launch with about 20% of the inventory and watch owner completion and reviewer turnaround.
Phase 1 — Inventory and ownership (Weeks 1–4)
Building a review calendar starts with a working inventory and confirmed ownership. Skip either and the calendar is built on a foundation that will collapse when the first cycle opens.
Build the inventory
- Collect every active policy across all locations — policy management system, departmental shared drives, unit binders, intranet pages.
- Deduplicate. Multiple versions of the same policy should be reconciled to one current version; older versions should be archived.
- For each unique policy, capture: title, current version, last review date (best estimate if unrecorded), policy type, audience, regulatory citations.
- Aim for 95%+ completeness on the inventory before moving on. Missing policies that surface later become exception items rather than steady-state cycle entries.
Confirm ownership
- For each inventory entry, identify the named owner. Where ownership is ambiguous, do the assignment work now rather than at first review.
- Confirm ownership with each named owner explicitly — a brief note explaining what ownership means and an explicit yes/no acceptance.
- Reassign where the named owner declines or where the assignment doesn't fit. This step takes longer than expected; allocate time accordingly.
- By Week 4, every inventory entry should have a confirmed owner who has explicitly accepted the assignment.
Phase 2 — Cadence and calendar (Weeks 5–8)
Set cadence rules per policy type
These are common defaults, not regulatory requirements. Document the rules in your policy-on-policies; they drive next-review-date calculation for every policy in the inventory, and surveyors will hold you to them.
- Clinical policies: annual review
- Operational policies: biennial review
- HR policies: annual or biennial depending on regulatory exposure
- IT and security policies: annual review (the HIPAA Security Rule requires periodic review; annual is a common choice)
- Governance and board policies: triennial review
- High-risk policies regardless of type: annual review
- Any policy with an interval set by regulation: that interval or shorter (for example, emergency preparedness policies at least every two years under 42 CFR 482.15)
Calculate next-review dates
For each inventory entry, calculate the next review date as last-review-date + cadence interval. Most calendar tools and policy management systems can do this in bulk once the cadence rules are configured per policy type.
Spread the calendar deliberately. If 80 policies all calculate to the same anniversary date — common when an organization did a big-bang re-accreditation review three years ago — distribute them across the cycle window. Group by domain or by owner load to make the redistribution defensible.
Establish the cycle window per policy
For each policy, the cycle window opens 90 days before the next-review date. The window timing produces the four-phase cadence — assessment, draft, approve, publish — within the 90 days. The Coordinator dashboard surfaces upcoming windows so notifications can be triggered automatically.
ImprovementFlow
Policy Management
ImprovementFlow imports your inventory spreadsheet in bulk, then each policy's review interval schedules its cycle automatically, so the calendar doesn't depend on a spreadsheet and a coordinator's memory.
Phase 3 — First cycle launch (Weeks 9–12)
Launch the first wave
- Identify the first wave — policies whose review windows open in the next quarter. Limit the first wave to roughly 20% of the inventory; full-inventory launches in the first cycle overwhelm coordinators and reviewers.
- Send Currency Assessment notifications to first-wave Policy Owners with: their policy list, the assessment questions, the deadline, and the available reviewer support.
- Schedule the first Governance Committee batch review at Week 11 or 12. The committee receives all first-wave policies that have moved through Currency Assessment and drafting.
- Track completion rates and friction points throughout. The first wave reveals what the structure produces and what needs refinement.
Monitor and refine
- Owner completion rate — what percentage of first-wave Policy Owners completed Currency Assessment within the 30-day window? Below 80% suggests workload, communication, or assessment design issues.
- Reviewer turnaround — how long from owner submission to reviewer return? Bottlenecks at this step usually mean reviewer capacity is overcommitted.
- Committee batch size — was the volume manageable? If reviews ran past the agenda, future committees need to receive smaller batches or meet more frequently during peak cycle periods.
- Off-cycle triggers — were any urgent off-cycle reviews needed during the first wave? If so, the off-cycle workflow works alongside the scheduled calendar; if not, the trigger criteria may need broader scope.
Move to steady state
By the end of the first quarter, the calendar should have produced the first wave at acceptable quality. Subsequent waves run on the same infrastructure with refinements applied. After 12 months, every active policy will have moved through one cycle under the new calendar — at which point the calendar is genuinely operational rather than implementation-state.
Plan the first calendar audit at the 12-month anniversary. Did every scheduled policy actually get reviewed within its window? Did off-cycle triggers fire when they should have? Were governance committee bottlenecks resolved? The audit becomes the Year 2 calendar refinement.
How ImprovementFlow supports this
- Bulk inventory import moves your consolidation spreadsheet into an operational policy library without re-entry.
- Each policy's review interval schedules its cycle automatically once owners and last review dates are confirmed.
- Drafts route through the reviewers and approvers defined for each policy type, with every sign-off captured in the audit trail.
- The coordinator's review queue shows overdue policies and reviewer bottlenecks, the first things to watch in a launch.
- Setting up the review calendar is part of onboarding.
Key terms
- Policy Cycle: A scheduled review of a policy's currency, accuracy, and effectiveness. Typically annual or biennial.
- Policy Inventory: The complete catalog of an organization's policies, with metadata: owner, last review date, next review date, regulatory citations, audience, version.
- Policy Owner: The individual accountable for a specific policy's accuracy and currency. Policy ownership is per-policy, not per-department — sometimes one department owns dozens of policies.
- Currency Assessment: The judgment made at review time about whether a policy still reflects current practice and current regulation. Outcome: keep as-is, modify, or retire.
- Approval Routing: The defined sequence of reviewers and approvers a policy update flows through before publication. Different policy types may have different routes.