The short answer
Keep one place for how your agency works, give each procedure one owner and one page, and review every page on a date. A wiki fails for ordinary reasons: nobody knows where a page belongs, nobody owns it, and it is out of date the first time someone relies on it. The fixes are a structure people can predict, a standard shape for a procedure, and a review date on each one.
This guide gives you a suggested wiki structure for an agency, a checklist for writing a standard operating procedure (SOP), and one SOP written out in full. Take what fits and change the rest. The examples are illustrations, not a standard.
A suggested wiki structure
Split the wiki by who needs the page and how often it changes. Agency-wide material goes in a few top-level areas. Everything about one client goes in that client's own area, so a new person on the account has one place to start.
| Area | What goes in it | Example pages | Suggested owner |
|---|---|---|---|
| Start here | A map of the wiki, how to find things, how to ask for a change. | Where things live; Who owns what; How to write a page | Operations lead |
| How we work | Procedures that apply to every project, written as SOPs. | Kickoff; Handover to support; Change requests; Release checklist; Incident response | Delivery lead |
| Time and billing | What staff log, what counts as billable, and the weekly and monthly routine. | Logging time; Billable and non-billable codes; Retainer check; Month-end | Operations lead or finance |
| People | Joining, leave, and working arrangements. | Onboarding in the first week; Requesting leave; Working across time zones | Head of people or a director |
| Tools and access | What each tool is for and how access is granted and removed. | Tool list; Access request; Leaver checklist | Whoever runs IT |
| Sales and proposals | How you scope, estimate and propose. | Discovery questions; Estimating; SOW template; Rate card notes | Account or sales lead |
| Clients (one area each) | Everything specific to one client. | Contacts and approvers; Environments and hosting; Brand rules; Open decisions; Handover notes | The account lead for that client |
| Templates | Blank pages to copy from: an SOP, a meeting note, a decision record. | SOP template; Decision record; Post-project review | Operations lead |
| Archive | Retired procedures and finished clients, kept for reference. | Anything past its use but worth keeping | The owner of the original |
A few rules keep the structure from sprawling:
- One home per page. If a page could live in two areas, pick one and link from the other. Two copies drift apart.
- Two levels of nesting at most. An area, then a page, then sub-pages only when a procedure is long. Anything deeper is hard to find.
- Name pages for what the reader is trying to do. "Hand over a project to support" is found; "Process v2" is not.
- Client areas follow one template. Every client area has the same five pages in the same order, so staff who move between accounts do not have to relearn the layout.
- Decide who can see what before you write. Client contract details and anything about pay belong in a restricted area, not in the open wiki.
A checklist for writing an SOP
A procedure is worth writing when it is done repeatedly, when it goes wrong in an expensive way, or when only one person knows it. A task done once a year by one person who is happy to do it does not need a page yet. Use the list below as a review checklist before you publish a procedure.
- Title says the job. A verb and an object: "Hand over a finished project to support".
- Purpose in one sentence. What goes wrong if this is skipped.
- One named owner. A person or a role, not "the team". The owner answers questions and keeps the page current.
- Who it applies to, and when it starts. The trigger: "when the client signs off the final deliverable".
- What you need first. Access, documents and approvals the person must have before step 1.
- Numbered steps, one action each. Start each with a verb. If a step has an "and", split it.
- A named role on each step. Who does it, so no step belongs to nobody.
- A "done when" check on each step that can fail. Something a second person could verify.
- Exceptions and what to do. The two or three cases that come up, and who decides.
- Links, not copies. Link to the template, the tool and the related SOP rather than pasting them in.
- Last reviewed date and review interval. On the page, near the top.
- Tried by someone who has not done it. Ask a newer colleague to follow it once. Every point where they stop is a gap in the page.
A worked SOP: handing a finished project to support
Here is the checklist applied to one procedure. The names, tools and numbers are illustrative; change them to match how your agency works.
| Purpose | Support can look after a launched project without asking the project team how it works. |
|---|---|
| Owner | Delivery lead |
| Applies to | Every project that moves to a support retainer or to ongoing maintenance. |
| Starts when | The client has signed off the final deliverable. |
| You need first | The signed statement of work, access to the project's wiki area, and the support lead's availability for a 45-minute call. |
| Last reviewed | 16 November 2026. Review every six months, or after any handover that went badly. |
| Step | Who | What to do | Done when |
|---|---|---|---|
| 1 | Project lead | Create the client's wiki area by copying your standard client pages, or check the existing one. | The five standard pages exist: contacts, environments, brand rules, open decisions, handover notes. |
| 2 | Project lead | Fill in environments: where it is hosted, how to deploy, where logins are kept (not the logins themselves). | The support lead can find every environment from the page alone. |
| 3 | Project lead | List what was agreed but not built, and link the change requests behind each item. | Each open item has a link to the request or the line in the statement of work. |
| 4 | Project lead | Write the "known issues" and "how to test a change" sections. | The support lead can name the three things most likely to break. |
| 5 | Delivery lead | Check access: support staff can open the repository, the hosting account and the client's wiki area. | Each person on the support rota has opened all three. |
| 6 | Project lead and support lead | Hold the handover call and walk the wiki area top to bottom. | The support lead has no unanswered questions, or each question is written in the area as an open decision with an owner. |
| 7 | Delivery lead | Set up the support retainer and its project in the time tracker, then tell the account lead that the handover is complete. | Support time can be logged against the client's retainer. |
| 8 | Account lead | Send the client the support contact and how to raise a request. | The client has confirmed receipt. |
Exceptions
- The client wants to start support before sign-off. The account lead decides, and the delivery lead records the decision on the page.
- The project lead has left. The delivery lead completes steps 1 to 4 from the repository and the statement of work, and marks anything unknown as an open decision.
- The project had no statement of work. Escalate before step 3: there is nothing to say what was agreed.
The handover only works if the retainer around it does, so see how to track retainer hours for the check that follows, and the statement of work guide for how to write down what was agreed.
Keeping the wiki alive
A page that is wrong is worse than a missing page, because people act on it. Four habits are enough for a small agency:
- Review dates on every procedure. The owner checks the page by that date and updates the "last reviewed" line, even if nothing changed.
- Fix it where you found it. Whoever spots a wrong step corrects it or tells the owner on the same day. Do not keep a private list of corrections.
- A procedure update after an incident. When something goes wrong, finish the post-mortem by asking which page should have prevented it, and change that page.
- Retire pages. Move a procedure you no longer follow to the archive area. A short wiki that is right beats a long one that is not.
Common mistakes
- Writing every procedure at once. Start with the three that cause the most rework or that only one person knows.
- Pasting long documents. A page of 40 screens is read by nobody. Split it, or write steps and link the detail.
- No owner. A page owned by "everyone" is owned by nobody.
- Treating the wiki as an archive of chat. A decision made in chat is not recorded until someone writes it on the right page.
- Secrets in pages. Say where a password is kept, never what it is.