01 / Define the proposal
Define one proposed procedure change.
Begin with a specific proposed change rather than a broad request to “improve the policy.” Describe the procedure as it works today, the reason for considering an update, and the decision that still belongs to a responsible person. A narrow scope helps reviewers see what the draft does and does not claim to change.
- What procedure is being considered, which team or location does it affect, and what is explicitly out of scope?
- What prompted the proposed update: a recurring issue, a new requirement, a process observation, or another documented reason?
- What would be different if the change were approved, and who has authority to propose, review, and approve it?
- What date, trial period, affected cases, and success or stop conditions should reviewers understand?
A clear proposal is a starting point for review. It is not evidence that the change is needed, safe, compliant, accurate, or ready to approve.
02 / Establish the source
Gather source context and authority.
Collect the current approved procedure and the context that explains the proposed change. Include real handoffs, local variations, constraints, and the people who can resolve questions. The source record remains authoritative when a summary, draft, or recollection disagrees with it.
- Current approved procedure
- The version staff currently rely on, including its owner, effective date, related instructions, and known local variations.
- Reason and evidence
- The stated reason for the proposal plus the records, observations, requirements, or examples that support it. A claim in a draft is not evidence by itself.
- People and constraints
- The roles, permissions, dependencies, safety concerns, confidentiality rules, and practical constraints that shape what can change.
- Authoritative record
- The approved policy, procedure register, handbook, controlled document, or other record that remains authoritative when summaries and drafts conflict.
Do not fill missing context with plausible wording. Mark it as missing and route the question to the person who owns or understands the procedure.
03 / Summarize with care
Use AI to prepare a traceable review summary.
If the organization chooses to use AI assistance, limit the task to a reviewable summary of the proposed change and its supplied sources. Ask for explicit separation between source-supported statements, interpretations, assumptions, open questions, and recommendations. Keep the source context available to the reviewer.
- State the procedure and proposed change in plain language, with the source context and time period used for the summary.
- Separate what the source says from an interpretation, open question, assumption, or recommendation.
- Point reviewers to the relevant source passages or records rather than presenting a summary as a replacement for them.
- Keep the output as a draft for review. It must not silently change the approved procedure or trigger an operational action.
A generated summary can help a person organize a review; it does not establish what the organization’s procedure is and does not authorize a change.
04 / Prepare a draft
Prepare a draft that makes review easier.
Turn the proposed change into a clearly labeled review draft. Show what is proposed, what stays the same, what depends on another decision, and what still needs evidence or clarification. A draft should make correction easy, not make an unresolved decision look final.
- Purpose and scope
- Why the change is proposed, what it covers, and what it does not cover.
- Proposed procedure
- A step-by-step draft that makes changed, unchanged, and unresolved instructions visible.
- Impact and dependencies
- Roles, training, records, timing, equipment, approvals, and communications that may need attention.
- Questions and risks
- Ambiguities, conflicting sources, exceptions, possible consequences, and items requiring subject-matter input.
Keep the draft separate from the approved procedure until the responsible staff have completed their review and recorded the decision through the organization’s normal process.
05 / Verify before approval
Give responsible staff the final say.
A person who is accountable for the work must compare the summary and draft with the source context, correct errors, and decide whether the proposal is acceptable. Include staff who perform the procedure or own its risks when their knowledge is needed. Do not treat a fluent draft, a confidence signal, or a quick review as approval.
- Compare every material statement with the current procedure and the cited source context.
- Correct omissions, invented details, wrong owners, incorrect dates, and language that overstates certainty.
- Ask the people who perform or oversee the work whether the draft matches actual practice and feasible constraints.
- Record unresolved questions and route them to someone with the right authority instead of filling gaps by guesswork.
- Reject or pause the draft when the source is incomplete, the change is too consequential for the review, or the reviewer cannot establish what is accurate.
Verification is part of the workflow, not a final formality. If the reviewer cannot establish what is accurate or acceptable, the update must not affect the organization.
06 / Make the decision durable
Approve, record, and communicate the update.
Only the person or group with authority should approve the change. Record the approved version, decision date, owner, effective window, supporting sources, and any follow-up review in the organization’s existing procedure record. Then communicate the approved update through the normal channel and make clear which version staff should follow.
AI-assisted summaries and drafts are working materials. The approved record and the accountable staff decision are what make an update operational.
07 / Keep a safe exit
Handle exceptions and know when to stop.
The workflow should have a clear stop condition. Pause the review, keep the approved procedure in force, and escalate when the source is incomplete, the proposal is consequential, or the draft cannot be checked well enough. Never let an AI-assisted draft become the organization’s procedure by default.
- Conflicting procedures
- Two approved-looking versions, local instructions, or records disagree. Stop and identify the responsible owner before drafting a final update.
- Missing or restricted context
- A source is unavailable, incomplete, confidential, or outside the reviewer’s access. Do not infer the missing instruction or expose content unnecessarily.
- High-consequence change
- The proposal could affect safety, employment, legal obligations, eligibility, access, finances, or another consequential outcome. Use the organization’s qualified review path.
- Unacceptable or uncertain output
- The summary or draft cannot be traced, corrected, or understood well enough for the responsible staff to approve it. Discard it or return to the source review.
Practical checklist
- Name the proposed procedure change, its owner, scope, reason, effective window, and approval authority.
- Collect the current approved procedure and the source context needed to understand the proposal.
- Keep AI assistance limited to a traceable summary or review draft; do not treat generated text as an approved instruction.
- Give responsible staff the source, summary, draft, assumptions, and unresolved questions to inspect.
- Correct or reject the draft before approval, and pause when reviewers cannot establish that it is acceptable.
- Record the approved version, decision, date, owner, and any follow-up or review date in the organization’s existing record.
- Communicate the approved update through the organization’s normal channels and confirm that affected staff know which version applies.
This guide is a planning aid, not a guarantee, compliance advice, records policy, or substitute for qualified guidance. It assumes no particular vendor, model, system, or third-party integration. Organization-specific access, confidentiality, retention, legal, privacy, safety, and high-consequence questions need qualified review.
Want to discuss an internal procedure update? Discuss an AI opportunity with the procedure, source context, review roles, and boundaries in view.