You can plan six months of allied health content in a weekend, because a weekend is enough time to make decisions and nowhere near enough time to write. That distinction is the whole method. We ran this on our own blog. In the first 10.9 weeks we published six posts. In the next 13.7 weeks we published 63, a rate 8.3 times higher, and the median post got 11% longer rather than thinner. Nothing about the writing got faster. The decisions simply moved to the front, where they only have to be made once.
- What is a six-month content plan actually made of?
- What happened when we ran this on our own blog?
- Why does moving decisions forward change the rate?
- What do you actually do across the weekend?
- Where do the topics come from?
- Where does AHPRA and TGA compliance fit in?
- What has to be in a single brief?
- What breaks an allied health content pipeline?
- What this data does not prove
What is a six-month content plan actually made of?
Start with the weight, because most plans die from being quietly enormous. Six months is 26 weeks. Our own posts run to a median of 1,840 words. So the plan you are agreeing to looks like this.
| Publishing rate | Posts in 26 weeks | Words at our median | What it suits |
|---|---|---|---|
| One a week | 26 | 47,840 | A solo practitioner writing alongside a full caseload |
| Two a week | 52 | 95,680 | A practice with an assigned owner and a writer |
| Three a week | 78 | 143,520 | A team with a dedicated content budget |
Ninety-five thousand words is a long book. Nobody agrees to that in a planning meeting. They agree to "two posts a week", which is the same thing wearing a smaller number.
So pick the rate you can hold on your worst month, not your best. One post a week that survives six months beats three a week that stops in October. A blog that stops looks worse than a blog that never started.
What happened when we ran this on our own blog?
We are not going to hand you a client case study. This site does not publish client names or client results. What we can do is open our own books, because this blog is a pipeline we actually ran, and anyone can count the posts.
We measured every published post on this site: 69 posts carrying a publication date, across 171 days, totalling 125,946 words of prose. Here is the monthly output.
That is not a ramp. It is a step. The line falls between May and June, so we split the data there and measured both sides.
| 17 Mar to 31 May | 1 Jun to 4 Sep | |
|---|---|---|
| Weeks | 10.9 | 13.7 |
| Posts published | 6 | 63 |
| Posts per week | 0.55 | 4.59 |
| Median words per post | 1,706.5 | 1,888 |
| Posts with an FAQ block | 6 of 6 | 63 of 63 |
| Posts with two or more internal links | 6 of 6 | 63 of 63 |
The rate went up 8.3 times. The posts got 11% longer. That second number matters more than the first, because the obvious explanation for a jump in output is that the work got thinner, and here it did not.
The structural markers did not move at all. Every post in both periods carried an FAQ block, Article schema and at least two internal links. The template was never the bottleneck.
Why does moving decisions forward change the rate?
Because writing a post is not one job. It is about nine, and only one of them is writing.
For every post, somebody has to choose the topic. Decide the angle. Decide who it is for. Check it is not a repeat of something already published. Decide what it is allowed to claim under AHPRA and TGA rules. Find the sources. Write it. Check it. Publish it.
When those nine jobs happen post by post, every single one restarts from nothing. The hard part is not the writing. It is the standing start. Most practice blogs do not fail because the writing is slow. They fail on a Tuesday when nobody can remember what the next post was supposed to be.
A pipeline moves eight of those nine jobs into one weekend, once, for all 26 posts. What is left on any given Tuesday is writing to a brief that already answers every other question. That is a genuinely different task.
What do you actually do across the weekend?
Roughly eight working hours, split across two days. Do it in this order, because each block feeds the next.
| Block | Roughly | What comes out of it |
|---|---|---|
| 1. Collect the questions | 2 hours | A raw list of 60 to 100 real patient questions |
| 2. Group and cut | 1 hour | Four or five clusters, everything else parked |
| 3. Set the compliance lane | 1 hour | One page of what you may and may not claim |
| 4. Write one brief properly | 1 hour | The template every other brief copies |
| 5. Fill the remaining briefs | 2 hours | 26 briefs, thin but complete |
| 6. Date them and set the gate | 1 hour | A calendar and a definition of ready |
Notice what is missing. You do not write a post this weekend. If you start drafting in block four you will finish one post and no plan, which is exactly the trap the weekend exists to avoid.
Where do the topics come from?
From your own front desk, before any keyword tool. A practice already knows what patients ask, it just never writes it down.
- The phone. Ask reception to note every question for one week. Not categories. The actual words people use.
- The first appointment. What do you explain over and over? If you have said it 200 times, it is a post.
- The unsent enquiries. Read your contact form and email enquiries. People write down what they are too unsure to ask aloud.
- The cancellations. Why do people not book? Cost, fear, referral confusion, parking. Each is a real page.
- The referrers. Ask two GPs what their patients get wrong about what you do.
That list beats a keyword tool for one reason. A keyword tool tells you what a lot of people type. It cannot tell you what your patients misunderstand on the way to booking. We go further into the search side of this in the healthcare SEO guide, but the questions come first.
Then cut hard. Sixty questions is not 60 posts. Group them, and keep four or five clusters that each map to something you actually get paid for. Everything else goes in a parked list. A plan that covers your whole profession is a plan for a magazine, not a practice.
Where does AHPRA and TGA compliance fit in?
At the brief stage. Not at the review stage. This is the single change that saves the most time, and almost nobody does it.
The usual order is write, then check, then rewrite. Every post gets argued about twice. The compliance question is asked fresh each time, and answered slightly differently depending on who is tired.
Decide it once instead. If you are a registered practitioner, your advertising of a regulated health service falls under section 133 of the National Law. So spend an hour writing down the rules of your own lane, in your own words, and attach it to every brief.
- Testimonials. Testimonials about the clinical aspects of a regulated health service are prohibited in advertising. Decide now that no brief asks for one. We cover the detail in the guide to AHPRA and patient testimonials.
- Outcome claims. Write out the phrases your team reaches for, then the version you accept. "Fixes your back pain" becomes a description of what the treatment involves and who it suits.
- Comparative and superlative words. Best, leading, safest, number one. Put them on a banned list once and stop relitigating them.
- Prescription medicines. If your field touches them, the rules are stricter again, and they belong in the brief rather than in a late edit. Start with the TGA advertising code.
- Before and after images. Decide whether they appear at all, before anybody commissions photography.
One page. Attached to all 26 briefs. Now the writer is not guessing, and the reviewer is checking against something written down instead of against their mood. For how this feeds a whole strategy rather than one post, see the content strategy that survives an AHPRA audit.
What has to be in a single brief?
Short. If a brief takes 40 minutes to write you will not finish 26 of them. Ours fit on half a page.
| Field | Why it is there |
|---|---|
| The question, in a patient's words | Becomes the title and the first heading |
| Who is asking | A new patient and a referrer need different pages |
| The one-sentence answer | Forces the angle to exist before the writing starts |
| What this post must not claim | The compliance lane, applied to this topic |
| Two or three sources | Stops the writer inventing numbers under deadline |
| Two internal links | Keeps the cluster connected instead of orphaned |
| The action at the end | Book, call, download, or read the next one |
That last field is worth guarding. A post with no action is a post you cannot measure, and an unmeasured pipeline is the first thing cut when the practice gets busy.
What breaks an allied health content pipeline?
Four things, in our experience, and none of them is the writing.
- Nobody owns it. "The team" does not publish. One named person with a recurring hour does.
- The rate was set on a good week. Three a week feels fine in January. Choose for your worst month.
- The gate is a person's opinion. If "ready" is undefined, every post waits for the busiest person in the practice. Write down what ready means: sources checked, claims inside the lane, two internal links, one action.
- The plan was too broad. Four clusters you own beat twenty you touch. This is the same mistake practices make in allied health marketing generally.
There is a fifth, quieter one. Publishing without ever reading the thing back. A pipeline is not a conveyor belt. Once a month, open the last eight posts and check they still say something you would defend.
What this data does not prove
Worth being straight about, because we would want to know.
- This was not a controlled experiment. March to May was this site's launch period, with other work running alongside. The step in June is real, and it is not proof that a system alone caused all of it.
- We are a copywriting business, not a clinic. Writing is our billable work. A practice owner is fitting this around a caseload, so the honest expectation is a lower rate, not the same one.
- Output is not results. Everything above counts posts and words. It says nothing about rankings, enquiries or bookings, and we are not implying it does.
- Dates come from each post's own published date, which is what we control. They record when a post went up, not how long it took to make.
- Six months is the planning horizon, not a promise. Guidance changes. Any brief touching a rule should be re-checked before it is written, not just before it is published.
None of that makes the method weaker. It just means the number to take from this is the shape of the change, not the multiple.