From process notes to instructions people can follow

Clear steps. Clear checks. Know when to stop.

A standard operating procedure defines when a recurring task starts, its approved steps, checks, stop conditions and escalation path.

Make this with my agent

Bring your notes. Review a draft before sharing.

Explore the method

01
Start with prerequisites
Editor-approved copy and an approved audience label must already exist.
02
Make stopping explicit
A mismatch or failed link means pause and ask Ellis in the existing task thread.
03
Checking is not sending
Noor records findings. Sending and publishing require separate authorization.

THE REAL HTML · FICTIONAL EXAMPLEView on its own

A worked example, not a customer result. September 2026 dates are sample facts.

Now make it about your work

Your process. Your agent. A clearer procedure.

Put prerequisites, ordered checks and exception paths where an operator needs them.

Start with three things

The validated task, trigger and prerequisites.
Approved steps, expected checks and stop conditions.
Confirmed escalation owner, revision and authoritative record.

Make this with my agent

You review the facts and access. Nothing is published without your approval.

The method behind the standard operating procedureAsk your agent to document the supplied procedure without inventing actions, permissions or retry rules.

How can I turn process notes into a useful standard operating procedure?

Give your agent the validated procedure, its trigger, prerequisites and confirmed exception path. Ask for a task-first reading guide with numbered steps, expected checks and clear stop conditions. Have an authorized operator walk the draft before sharing it; the page explains the procedure but does not perform or approve it.

What to give your agent

The current authorized procedure, scope and trigger for this task.
Required inputs, access prerequisites and verified task instructions.
Expected checks, known exceptions, stop conditions and confirmed escalation owner.
Procedure owner, revision identifier, review date and authoritative record location.

Set a clear start and boundary
State when this procedure applies and what must be true before an operator starts. A request, approved input and permission to execute are not interchangeable. Keep tasks outside the scope explicit so a routine checklist does not authorize additional work.
Write steps people can verify
Use one observable action at a time, with the relevant input and expected result nearby. Preserve the validated order and exact technical detail when it matters. Do not let an agent invent tool instructions, settings or access grants to close a gap.
Put exceptions where they occur
For each material failure, explain whether to stop, retry under the approved procedure, or ask a confirmed owner. Avoid vague 'use judgment' advice when the procedure supplies a specific escalation rule. Missing or contradictory instructions should remain review blockers.
Walk the draft before calling it an SOP
Have an authorized operator verify the page against the source process, including a failure case. Show the owner and revision so readers can find the maintained version. Use HTML as a readable companion; keep execution, required records and approval in their existing systems.

Keep creating and revising in the agent you already use. Start with a saved artifact style and learn how to update HTML without changing its link.

Use the full promptReady for your agent and your notes

Use the conversation where you already did the work. Only attach material you are allowed to share.

Get the ready-to-copy creation request →

Create a standard operating procedure from only the validated process and authorized instructions I supply. Ask for missing trigger, prerequisites, steps, expected checks, exceptions and escalation owner. Preserve the approved sequence. Do not invent technical actions, permissions, safe limits, approvals or retry behavior. Put stop conditions beside the relevant step. Include the supplied procedure owner, revision and review date. Use readable static HTML with no scripts or forms and my saved style if available. This task documents the procedure; do not execute it. Keep authoritative records and approvals in the existing system. Show the draft and gaps for an authorized operator to review. Do not publish or change access without separate explicit approval.

Check before you shareAccuracy, clarity, and permission

Are trigger, prerequisites and scope explicit?
Does each step match the validated source procedure?
Are failure paths and confirmed escalation owners visible?
Has an authorized operator walked the draft, including an exception?

When HTML fits

A readable administrative task companion with checks and exception paths available where the operator needs them.

When another format fits better

Do not generate safety-critical, medical, legal or regulated operating instructions without the appropriate qualified process. Keep official controlled documents, execution logs and approvals in their required systems.

What we started withThe same facts, as a wiki page

Fictional team wiki

Fern Desk — newsletter preflight, revision 1

Owner and prerequisites

Reviewed September 7, 2026. Owner: editor Ellis. Operator: Noor. Start when a draft is ready and editor-approved copy plus an approved audience label already exist in the task record. If either is missing, pause and ask Ellis in the task thread.

Step 1 — Check the copy

1. Compare the draft with the editor-approved copy. If words or included material differ, stop and ask Ellis; do not rewrite within preflight.

Step 2 — Check destinations

2. Open each supplied link and compare its destination with the approved record. If it fails or differs, stop and ask Ellis. This fictional example includes no links and performs no checks.

Step 3 — Check the audience

3. Compare the draft audience label with the approved label. Do not inspect or expose subscriber information. If it differs, stop and ask Ellis rather than modifying the audience.

Record findings; sending is separate

Record findings and unresolved discrepancies in the task thread for Ellis to review. Preflight is not permission to send or publish; sending is a separate workflow needing separate authorization. No response-time promise or retry policy is supplied. Pause rather than guess. This static demonstration grants no access, automates nothing and claims no completed check; it is not an execution log.

Inspect the HTMLOne self-contained file

The example is sanitized and isolated from this site. No scripts, forms, or live data.

<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1"><title>Fern Desk · Newsletter preflight</title><style>
*{box-sizing:border-box}html{color-scheme:light}body{margin:0;background:#f6f8f5;color:#20352f;font:17px/1.65 system-ui,sans-serif}main{max-width:1000px;margin:auto;padding:clamp(20px,5vw,64px)}h1,h2,h3,p{margin:0 0 18px}h1{font:500 clamp(32px,5vw,58px)/1.14 Georgia,serif;letter-spacing:-.025em;overflow-wrap:anywhere}h2{font:500 29px/1.3 Georgia,serif;overflow-wrap:anywhere}h3{font-size:19px;line-height:1.4}.label{font:700 12px/1.6 system-ui,sans-serif;letter-spacing:.08em;text-transform:uppercase}.intro{font-size:20px}.lead{background:#174b40;color:white;padding:24px;margin:28px 0}.lead p:last-child{margin:0}.grid{display:grid;grid-template-columns:repeat(auto-fit,minmax(min(100%,230px),1fr));gap:20px;margin:24px 0}.card{background:white;border:1px solid #bbc5c4;padding:24px}.metric{font:500 38px/1.2 Georgia,serif;display:block;margin-bottom:12px}section{margin:36px 0}ul,ol{padding-left:22px}li{margin-bottom:12px}.note{font-size:14px}.warning{border-left:5px solid #956118;padding-left:20px}a{color:inherit;text-underline-offset:4px}a:focus-visible,summary:focus-visible{outline:3px solid #956118;outline-offset:4px}table{width:100%;border-collapse:collapse;table-layout:fixed;font-size:15px}th,td{text-align:left;vertical-align:top;border-bottom:1px solid #bbc5c4;padding:12px 8px;overflow-wrap:anywhere}caption{text-align:left;font-weight:700;padding:12px 0}pre,code{white-space:pre-wrap;overflow-wrap:anywhere}footer{border-top:1px solid #bbc5c4;padding-top:24px;margin-top:40px;font-size:14px}@media(max-width:480px){th,td{padding:10px 4px;font-size:14px}}@media print{body{background:white}.card,.lead{break-inside:avoid}h2,h3{break-after:avoid}}
</style></head><body><main><header><p class="label">Fictional administrative SOP / Revision 1 / September 7, 2026</p><h1>Check the newsletter. Do not send it.</h1><p class="intro">Procedure owner: Ellis · Operator: Noor. This reading page records no completed check and grants no permission to execute.</p></header><section class="lead"><h2>Before preflight begins</h2><p>Require editor-approved copy and an approved audience label in the established task record. If either is missing, pause and ask Ellis in the existing task thread.</p></section><section><h2>Three checks, in order</h2><ol><li><strong>Compare the copy.</strong> Check the draft against the approved version. A difference means stop; do not rewrite it within this preflight.</li><li><strong>Check supplied links.</strong> Open each link and compare the destination with the approved record. A failed or different destination means stop. This fictional page supplies no actual links and performs no checks.</li><li><strong>Compare the audience label.</strong> Match it to the approved record without exposing subscriber information. A mismatch means stop; do not change the audience yourself.</li></ol></section><section class="warning"><h2>If anything differs, ask Ellis.</h2><p>Use the existing task thread. No retry policy or response-time promise is supplied. Noor pauses rather than guessing.</p></section><section><h2>Record the findings, then hand back.</h2><p>Record checks and unresolved discrepancies in the existing task thread for Ellis to review. Sending and publishing require separate authorization through the existing sending workflow.</p><p class="note">This SOP includes no sending steps and is not an execution log.</p></section><footer>Fictional worked example by share/artifacts. Names, dates, figures and records are invented for demonstration. Static snapshot; no live data or automatic updates.</footer></main></body></html>

The original worked scenarioThe source scenario, step by step

A newsletter preflight that cannot silently become a send

A fictional, low-risk administrative procedure. It does not send email.

The original notes

Newsletter preflight starts only with editor-approved copy and an approved audience label. Noor checks that the draft matches the approved copy, opens each supplied link and compares its destination to the intended destination, then confirms the audience label matches the approved record. If a link fails or copy or audience differs, stop and ask editor Ellis in the existing task thread. Record the findings there. This preflight never sends or publishes; Ellis separately authorizes the existing sending workflow.

Before starting

Require editor-approved copy and an approved audience label.

Check

Noor compares copy, supplied link destinations and audience label with the approved records.

Stop condition

Failed link or mismatched copy or audience: stop and ask Ellis in the existing task thread.

Finish

Record findings there. Preflight never sends or publishes; Ellis separately authorizes the sending workflow.

The stop condition and scope boundary matter as much as the normal steps.

Questions, adaptations & sourcesGo deeper when you need to

Can the agent fill missing steps?

It can identify the gap and ask the process owner. It should not invent operational instructions and present them as approved procedure.

Does the page record completion?

No. Record execution and approvals in the established system. A numbered list is not a tracked checklist.

What makes this different from onboarding?

An SOP describes repeatable execution of a defined task by an authorized operator. Onboarding organizes a newcomer’s learning and first tasks, which may link to several SOPs.