Markdown SOP template (standard operating procedure)
A .md file ready to fill in: purpose, prerequisites, numbered steps, checks, what to do when something goes wrong, and a change history. It opens in any editor and shows formatted in Marko.
Why an SOP in Markdown
An SOP lets a task be redone the same way, even when the person who knew it is away. In Markdown it is a plain text file: it opens anywhere, sits next to the code or the docs, and is tracked with Git. Every change is visible, dated and attributed. You know which version is the one that counts.
What each section is for
Six sections, in the order you follow a procedure.
- Purpose: what the procedure gets done, in one sentence.
- Prerequisites: the access, tools or information needed before you start.
- Steps: numbered actions, one per line, in order.
- Checks: what to verify before closing, as checkboxes.
- If something goes wrong: a symptom, then the corrective action.
- History: a table of changes, with the date and the author.
How to fill it in
- Download the template, then open it in Marko (right click, “Open with”, “Marko”) or in the editor of your choice.
- Write each step as an action: a verb, a result. If one step hides two, split them.
- Fill in the checks: they are what tells you a procedure went all the way through.
- To share it with someone who does not have Marko, use “Export as PDF…” in the File menu.
Write a step as an action
A useful step starts with a verb and ends with a visible result. Compare “handle access” with “open Settings, Accounts, then add the person’s address”. The first leaves you guessing; the second you can follow with your eyes closed. Someone meeting the procedure for the first time should be able to run it without calling you. If one step hides two, split it into two lines.
If you start from a list an AI wrote, paste it in Source mode, number the steps, then add the checks and the “if something goes wrong” section. Those are what turn a list into a procedure people can hold.
File preview
# Procedure: [procedure name] - **Purpose:** what this procedure gets done - **Owner:** role or person - **Last updated:** YYYY-MM-DD ## Prerequisites - Access, tool or information needed before you start ## Steps 1. First step, written as an action 2. Second step 3. Third step ## Checks - [ ] Verification to do before closing - [ ] Expected result confirmed ## If something goes wrong - Symptom, then corrective action ## History | Date | Change | By | |---|---|---| | YYYY-MM-DD | Created | First |
The numbered steps, the checkboxes and the history table show in Marko and in most Markdown editors. A plain text editor shows the symbols as they are.
To share the procedure, export it to PDF from Marko: the numbering, the checked boxes and the history table are kept, and the document reads without installing anything.
Frequently asked questions
How do I keep the procedure current?
On each change, add a row to the History table with the date, the change and the author. That shows which version is the one that counts and what moved since last time.
What sections does the template hold?
Purpose, prerequisites, numbered steps, checks, what to do if something goes wrong, and a change history.
How do I share the procedure with someone who does not have Marko?
Export it to PDF from the File menu. The numbering, the checked boxes and the history table are kept.
Download the template, then open it in Marko. The .md file opens formatted. Fill it in, then share it or export a PDF.
Full 14-day trial, no account or credit card. See pricing