Templates & Examples
Turn approved process notes into a short PDF guide.
Your notes already hold the guide. What stops you sending it is the claims inside — here is the pass that settles them first.
The draft is finished. The doubt is about the claims.
Your draft is written. It has sat in a folder for a week because of one kind of sentence: the one that tells the reader what will happen to their business once they work through your steps.
You are not worried about the layout. You are worried that one overpromise turns you from the consultant who knows the work into a marketer promising outcomes. Underneath sits a second worry: if the file reads as though a machine assembled it, a prospective client learns something about your judgment, and not in your favour.
You have also downloaded workbooks that collected dust, and you do not want to spend a fortnight building the same generic checklist with your logo on it. Both worries have the same answer, and it is not software. Give every sentence a job: an instruction, an observation, or a claim about a result. Then source the claim, soften it or cut it. You finish with a file you can send, and a short record of what you changed and why.
Five steps take one small set of approved notes to an exported PDF. Every example below is illustrative: a fictional operations consultant and a fictional workshop. Nothing here is a client result.
Build your brief as you read.
Use the free 21-page fillable Lead Magnet Brief Builder: 15 lettered worksheets from finding an idea to a one-page brief and a readiness check, with three fictional worked examples.
Free: we send you a short email first. Reply VERIFY to it and we email you the workbook, then four short follow-up emails over two weeks (the last one names our own $79 Workflow Pack). Every email has an unsubscribe link.
Step 1: pick notes you are allowed to use, and nothing else.
Start with one reader and one task. Not your whole methodology: one job a client has already paid you to do, written up the way you would explain it to a colleague taking over next week.
Then sort the material into three piles before you write anything.
| Pile | What goes in it |
|---|---|
| Keep | The order you do the work in; the questions you always ask; the two mistakes you see most often; the phrasing that gets a straight answer from a busy manager. |
| Check first | Anything written during a client project, a client’s own template, a framework from a paid course or a book. Confirm you may reuse it and note who agreed, and when. Worksheet F in the free Brief Builder is a source and permission log for exactly this. |
| Leave out | Client names, staff names, revenue figures, screenshots of live systems, anything under a confidentiality agreement, and any note that only makes sense with the client in the room. |
Illustrative sorting, not legal guidance. Check permissions on your own material.
Do not guess at permission. If it is unclear whether you may reuse a client document or a third-party framework, settle it before you publish, and ask a qualified adviser where the answer is not obvious.
Step 2: give every sentence a claim decision.
This is the step most guides skip, and the one that decides whether you dare to send the file. Work through the draft one sentence at a time and give each one a decision: keep, verify, revise or remove.
| Decision | What it sounds like | What you do |
|---|---|---|
| Keep | “List the documents you already hold.” | An instruction. Check it is accurate to your process and in the right order. |
| Verify | “Most handovers fail because nobody names an owner.” | Point to something you can show, and describe it the way the source does. |
| Revise | “This will cut your rework.” | Replace the outcome with the thing the reader ends up holding. |
| Remove | “Teams that prepare this way finish in half the time.” | No source, no sentence. Delete it, and do not swap in a different number. |
Most overpromises are not dishonest. They are the shorthand you use with a client who already trusts you, written down for a reader who does not. Four decisions per risky sentence answer the question you will ask yourself at midnight: did I check this? They are also the only record you have if a reader asks where a claim came from.
Before: “This checklist will double your workshop attendance.”
After: “After using this checklist, you will have a list of the inputs you hold, the gaps to close and the questions to bring to the session.”
The second sentence names an artefact. It makes no claim about what will happen to the reader’s business, and a careful reader cannot challenge it.
Run the draft through ten checks before it leaves your desk.
Two pages: ten review checks, a worked example, and three claim records to fill in as you go.
2-page fillable PDF. Free: enter your email, then reply VERIFY to the short email we send you, so we know the address is yours. We email you the checklist, then four short follow-up emails over two weeks on using our free Brief Builder (the last one names our own $79 Workflow Pack). Every email has an unsubscribe link.
A drafting tool can tidy a paragraph. Its output is a suggestion, not evidence. Check every sentence against your own notes, delete numbers and comparisons the notes do not contain, and put back the line you say on a call that makes a client stop writing. Our guide to reviewing AI-written lead magnet claims takes this further.
Step 3: outline three ordered steps.
A short guide is finished in one sitting, so three ordered steps with one example each will carry a reader from “I have notes” to “I have done the task”. If your notes produce eight steps, you have two guides, or a checklist hiding inside a guide.
Illustrative example. A fictional operations consultant sells a process-mapping workshop. Her reader is the operations lead asked to run the first one this quarter. Her approved notes describe how she prepares for that session.
| Guide title | Prepare for your first process-mapping workshop |
|---|---|
| Reader | The operations lead running their first workshop |
| Step 1 | Gather the inputs: list the documents already approved and the people who own them. |
| Step 2 | Mark the gaps: note what is missing and who can answer it. |
| Step 3 | Build the agenda: turn each gap into one question for the session. |
| Last page | One next step: a planning call, a template, a service page. |
Hypothetical guide and reader. Not a client result, and not a template to copy word for word.
Every page should remove a decision, so the reader never has to work out what to do next. That is the test of the outline: if one step contains two actions, split it or drop one.
Step 4: rewrite the shorthand for someone who was not there.
Your notes are compressed because you were writing to yourself. The reader has none of that context, so translate the shorthand line by line.
| Working note | Reader instruction |
|---|---|
| “Confirm inputs pre-session.” | “Before the session, list the documents you already have and mark the information that is still missing.” |
| “Chase AO before kickoff.” | “Before kickoff, name the one person who approves each deliverable.” |
| “Map as-is first, no to-be yet.” | “Describe how the process works today before you discuss how it should change.” |
| “Send recap + owners EOD.” | “By the end of the day, send a short summary that names who owns each next step.” |
Illustrative rewrites. Hypothetical notes, not taken from a real client project.
Read each section aloud. Wherever you hear yourself add “what I mean is…”, that explanation is the sentence to write down. Keep examples inside the reader’s week: an agenda, an approval list, a missing document.
Then check the draft against the brief rather than against your memory of it.
- The instructions match the task promised on page 1.
- Each step carries one example, labelled as illustrative.
- Every result claim is verified, revised or gone.
- The reader can name the next step without emailing you.
Step 5: check the exported file, not the editor.
The file your reader opens is not the file you are looking at. Our guide to formatting a lead magnet PDF readers can use covers the full export list; these are the checks that catch the embarrassing ones.
- Open the PDF on a desktop and on a phone.
- Click every link and confirm none points to a preview, a draft or a local file path.
- If there are fillable fields, type in one, save, close and reopen.
- Copy a line of text out of the PDF. If it comes out garbled, the text layer is broken.
- Read the document properties: no client name, no internal file path, nothing you would not send.
- Send it to yourself once, by the same route your reader will use.
Fix anything you find in the source document and export again. Never patch the PDF.
Do you need a document tool for this?
No. A word processor that exports to PDF carries a three-step guide with answer space perfectly well. Look at software when layout is the part slowing you down, not before. If you reach that point, read the vendor’s own terms first: Designrr’s software licence agreement, for example, sets out how the licence may be transferred and states that the vendor uses tracking and cookies to measure and analyse usage inside the application. Our Designrr review and the Beacon vs Designrr comparison summarise what the vendors’ published documentation describes. Both are research summaries of vendor documentation. No product has been tested, ranked or scored, and no affiliate relationship is active.
The final check before you send it.
Run this on the exported file, not on the draft.
- One reader and one task named on page 1.
- Every step comes from notes you may reuse.
- Every claim about a result is verified, revised or gone.
- No client names, figures or screenshots.
- Three ordered steps, one example each.
- A completion statement that names an artefact.
- One next step on the last page.
- Links and fields tested on a phone.
What a settled sentence looks like
“After using this guide, you will have a list of the inputs you already hold, the gaps to close and a one-page agenda for the session.” No number, no promise about the reader’s business, and nothing a careful reader could challenge.
Questions about turning notes into a PDF guide.
How do I turn process notes into a lead magnet PDF?
Pick one task from notes you have permission to use, give every sentence a claim decision, outline three ordered steps, rewrite the shorthand into instructions, then open the exported PDF and test it on a phone before you send it.
How do I stop a lead magnet sounding as if AI wrote it?
Keep the prompts and examples in your own wording, take out every number you cannot point to a source for, and cut sentences that could apply to any business. The specific wording comes from your own client calls.
Do I need design software to make a PDF guide?
No. A word processor that exports to PDF carries a three-step guide with answer space. Consider a document tool when layout is the part slowing you down, and read the vendor’s licence terms before you commit.
How long should a lead magnet built from process notes be?
Short enough that a busy reader finishes it in one sitting. Three ordered steps with one example each makes a working guide; eight steps usually means two guides, or a checklist inside a guide.
What if a claim in my notes has no source?
Soften it to what you can show, or cut it. If the point matters, describe what the reader will end up holding rather than what will happen to their business, and keep a line recording the decision.
Sources & editorial notes
- Designrr software licence agreement, retrieved 21 October 2026. Used for the statement that the agreement sets out how the licence may be transferred and that the vendor uses tracking and cookies to measure and analyse usage inside the application.
- Source & Claim Review Checklist, version 1, published at /resources/source-review-checklist. Ten review checks, a worked example and three claim records (keep, verify, revise or remove).
- Lead Magnet Brief Builder, version 2, published at /free-starter-kit. Worksheet F is the source and permission log referred to in step 1.
All examples on this page are fictional and illustrative. No guide, file or tool has been tested or benchmarked for this article. See our Editorial Policy, Review Methodology and Affiliate Disclosure.