We compile a complete documentation pack for your site — how it’s built, where things live, how to perform common tasks — a single, organised reference rather than knowledge scattered across emails, memory, and whoever originally built the site.
Site documentation pack
A complete documentation pack compiled — how your site is built, where things live, how to do common tasks.
- 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
- Admin and FTP access to review the site comprehensively
- Confirmation of what you already know versus what genuinely needs documenting
- Your preferred format for the finished pack
This or something else?
| You want a general, comprehensive documentation pack covering how your site works | This fix covers it |
| You specifically want deep, code-level documentation for a developer | Theme & codebase documentation generation, in the Integrations & Automation bucket, the more technical version |
| You specifically want credentials and access documented | Credentials & access inventory document, a more focused, related document |
| You want this bundled as part of a full developer handover | Onboarding pack for incoming developer, the broader bundle |
What we do
- Review the site comprehensively to understand its structure and setup
- Document how the site works, where key settings live, and how common tasks are done
- Organise findings into a clear, navigable reference pack
- Include enough detail to be genuinely useful without becoming an unreadable wall of text
- Review for accuracy before considering it final
What is included
- A comprehensive, organised documentation pack
- Clear coverage of structure, settings, and common tasks
- A navigable, genuinely usable format
- A final accuracy review
Not included
- Deep, code-level technical documentation — a separate, more technical fix
- Credentials and access details specifically — a separate, related document
- Fixing anything found while documenting — a separate, related fix if needed
- Ongoing updates as the site changes
Questions about this fix
How detailed is this compared to the code-level documentation fix?
This is a general, practically-oriented reference for understanding and operating the site; the code-level fix goes considerably deeper into actual custom code, suited to a developer's specific needs.
Will this include my login credentials?
No, that's a separate, dedicated document specifically for credentials and access, kept distinct for its own handling considerations.
Who is this actually useful for?
Anyone who needs to understand or operate the site without having built it — a new team member, a new agency, or simply future you after enough time has passed to forget the details.
Does this need updating as the site changes?
Yes, significant changes would need a follow-up update to keep the documentation accurate — it reflects the site as of when it's compiled.
Is this the same as the full onboarding pack?
No, this is one useful document on its own; the onboarding pack is a broader bundle for a full developer handover, which can include this alongside other documents.
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.