We write a formal, step-by-step standard operating procedure for publishing content — the specific sequence your team should follow every time, including checks (proofreading, image optimisation, category assignment) that are easy to skip under time pressure without a written checklist.
Publishing standard operating procedure
A formal, checklist-style publishing procedure, so quality checks don't get skipped under time pressure.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Confirmation of your actual, intended publishing process and any steps you already know should be included
- Access to review the site’s actual publishing workflow
- Your preferred format (a document, a checklist)
This or something else?
| You want a formal, checklist-style procedure for publishing content | This fix covers it |
| You want a general, plain-language editor guide instead of a formal SOP | Editor guide for content team, a less formal, broader-purpose document |
| You want this specific to WooCommerce product publishing, not general content | WooCommerce operations manual, if product listings are the actual focus |
| You want a recorded video instead of a written procedure | Recorded admin walkthrough video, a different format |
What we do
- Confirm your intended publishing process and any specific quality checks
- Document the process as a clear, sequential procedure
- Include a checklist format for the checks that matter most
- Review for practicality against how your team actually works
- Finalise in your preferred format
What is included
- A formal, step-by-step publishing procedure
- A practical checklist for key quality checks
- A review for real-world practicality
- Delivery in your preferred format
Not included
- A general, less formal editor guide — a separate, related document if that better fits your needs
- WooCommerce-specific product publishing procedures — a separate, related document
- Enforcing adherence to the procedure — that’s your team’s ongoing discipline
- Ongoing updates as your publishing process evolves
Questions about this fix
How is this different from the general editor guide?
This is more formal and procedural — a specific, sequential checklist meant to be followed the same way every time, rather than general, explanatory guidance on how the site's editing works.
Will this actually get followed, or just sit unused?
That depends on your team's own discipline and how the procedure gets introduced — we can make it as clear and low-friction as possible, though adoption itself is beyond what a document alone can guarantee.
What kind of checks would typically be included?
Common ones include proofreading, verifying images have alt text, confirming correct category and tag assignment, and checking the post displays correctly before publishing — we'd tailor the actual list to what matters for your site.
Can this be a physical checklist, not just a document?
Yes, we can format it as a genuinely usable checklist rather than a dense paragraph of instructions, if that's more practical for your team.
Does this need updating if our publishing process changes?
Yes, a procedure that no longer reflects actual practice loses its usefulness — worth updating whenever the underlying process genuinely changes.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.