WS Operations Platform
← Back to the plan

Internal handbook

WS Operations Platform Handbook

How to find your own work on the Improvement Plan, move it on, and use every other area of WSOP.

Where
operations.williamsstanley.co
Viewing
Your own sign-in, firm accounts only
Plan owner
Lee Redshaw
Access
Set per person on the Admin screen

Getting in

Everything here needs an account. The service issues name clients and carry risk ratings, so nothing is open to the link alone.

  1. Open operations.williamsstanley.co and click Sign in.
  2. Sign in with your work email address and the one-time password you were given.
  3. You will be asked to set your own password before you can continue. Choose anything at least eight characters.

You stay signed in on that browser for 30 days. Password in the header changes it later; Sign out ends the session everywhere on that device.

Two things worth knowing about the one-time password you are given. It stops working after 14 days if you never use it, because until then it is a live credential sitting in whatever message it arrived in — ask for another and you will get a fresh one. And five wrong passwords for the same address locks that address for fifteen minutes, so if you are guessing, stop and use the reset link instead.

Forgotten your password

Click Forgotten your password? on the sign-in box, put in your work email, and add a line about how urgent it is if that helps. A fresh one-time password is emailed to you, and you choose your own the next time you sign in. If no email can be sent, the request shows up for the administrators instead, who set one and pass it to you.

Worth knowing

What you see depends on your account. Some people get the improvement plan and the service issues; some get the escalations only; some can read but not change. If something described here isn't on your screen, that is why.

Your own tasks

The Improvement Plan opens on My tasks when any task has your name as owner.

Your tasks are grouped in the order they are owed: overdue, due in the next seven days, at risk, in progress, not started and parked. Tasks where you are a sponsor or participant but somebody else is the owner are listed apart, and what you completed in the last 30 days is at the foot.

  • Move a task on from its card: Start, the progress steps (0% to 100%), ✓ Complete and Post an update all save straight to the plan and go in the task's history.
  • A task in progress that has not changed for three weeks says so on its card. A line on where it has got to is all it needs.
  • A task is yours when its owner is written as your full account name, or a spelling the register holds for you. An owner written as a first name ("James") reaches nobody, so the plan marks it and the By owner tab lists every such name.

The other views

  • Overview: what needs attention, what is in flight, each workstream (press one to see its tasks), what is coming up and recent activity.
  • Board: Not started, In progress and Complete as three columns. Drag a card across, or use its buttons.
  • By owner: each person's open, overdue, at-risk and due-soon tasks. Press a name or a number to see exactly those tasks.
  • All tasks, Timeline and Sprints: the full register, the Gantt chart and the load per sprint.

The figures along the top are filters too: press Overdue or Nobody named to see exactly the tasks counted.

Workstreams

Every task sits in a workstream. Adding a task asks for one, and starts on the workstream you are filtered to. A task changes workstream by moving it under the other one, so it never sits outside all of them and drops out of every workstream view.

Only the plan owner adds, renames or merges a workstream, and each change needs a reason that goes on the plan's history. The plan keeps to eight at most, so a new one waits until two have been merged. If you think the plan needs one, ask the plan owner, who sees Merge and Rename or add a workstream under the workstreams on the Overview. See what moves shows every task's old and new number before anything is merged; nothing outside the two workstreams is renumbered.

Finding tasks

Every filter takes more than one value, and they combine.

Only these answers whose and what state: mine, named on, open, nobody named, in progress and not moved in three weeks, linked to an issue, idea or procedure, or complete. Pick as many owners, workstreams, RAG values, statuses or sprints as you like. Within one filter the values are an or — Brix or Georgia. Across filters they are an and — those owners and that workstream.

  • Each option shows how many tasks carry it, so you can see the size of a slice before you pick it.
  • Owner and Sprint have a type-ahead box, useful with 22 owners and 26 sprints.
  • Your choices appear as chips underneath with a running count — 31 of 259 tasks. Click the × on a chip to drop just that one, or Reset to clear everything.

Filtering by deadline

Deadline reaches both ways. Ahead covers the next 14, 30, 60 or 90 days or 12 months from today; Back covers the last 30 days, 3, 6 or 12 months; Custom range… opens a From and a To box for any two dates. It starts on Any deadline, which is every task, so nothing is hidden until you ask.

It matches a task's Finish date, so a task with no deadline set is in no window at all. The line under the rail says which dates are in and how many tasks have no deadline, so a task cannot go missing without the screen telling you.

Why owners look different

A task owned by "Lee Redshaw, Brix" used to appear in the filter as its own entry, so filtering by Brix missed everything he shares with someone else. Owners are now split into individuals — filter by Brix and you get all 15 of his tasks, shared ones included.

Updating one task

Click any task, on any view, to open it.

The top of the panel is for moving it on: the status and progress buttons save at once, and the owner, due date and progress sit beside them. Under that is the latest update with a box to post the next one; posting replaces the latest, and the one before stays in the history.

Linked work

Where a task came from a service issue or an improvement idea, revises a procedure, or is the systemising work behind a tax job, the panel says so and opens it. You only see the links your account can open.

Edit details

Everything else is under Edit details: the task's name, owner (picked from the accounts), who else is on it, status, RAG, progress, priority, start, due date, sprint, milestone, objective, dependencies and notes. Save changes writes it, and closing the panel with something unsaved asks first.

Or capture it for the roll-up

Use Capture for the roll-up when you want to note something for a plan review without changing the plan yet. That is covered next.

Every change is logged at the bottom of the panel under History — who changed which field, from what to what, and when.

Capture and roll up

Jot progress down as it happens through the week, then fold it all into the plan in one pass.

This is for running a plan review: note things as they move, rather than editing each task live, then reconcile at the end of the day or week.

  1. Open a task and type into Capture for the roll-up. Optionally set status and % complete alongside the note.
  2. Click Capture. Nothing on the plan changes — the task still shows its old status and percentage.
  3. Keep going through the week. The Roll-up button in the toolbar shows how many are waiting.
  4. When you are ready, open Roll-up. Each captured item shows what it will change, old value struck through and new value in bold, with the note underneath.
  5. Drop anything you have changed your mind about with Discard, then Apply all to the plan.
What happens to your notes

Notes are appended to each task's latest update, oldest first, each stamped with the date and who wrote it — so a week of jottings becomes a readable trail rather than each one overwriting the last. Where two captures set the same field, the later one wins.

What changed

The + button, top right (or press N), starts anything your access allows from any screen: a task for you or a colleague, a CoSec matter, a tax job or case, a review point, an onboarding, a proposal, an ad hoc invoice, a plan task, a procedure, or a report to the MLRO or about a data breach. A task you set lands on their Tasks list until they mark it done, and you are told when it is.

The second tab in Roll-up summarises what has already been applied over the last day, week, fortnight, month or quarter — grouped by task, with who did what. This is the one to read from for a weekly update.

Changing many at once

Filter to the set you mean, select it, apply once.

  1. Go to the Tasks tab and filter down to what you want — say Leanne Lally's not-started items.
  2. Tick individual rows, or use the tick-box in the table header to take everything the filters are currently showing.
  3. A bar appears at the top. Set only the fields you want to change; everything else stays on — leave unchanged —.
  4. Click Apply to 12. Delete 12 removes them instead.
Worth knowing

Setting a field to the value tasks already have records nothing. Applying "High" to a set that is already High reports no changes needed rather than filling everyone's history with edits that changed nothing.

Adding tasks

One at a time, or a batch straight out of a workshop.

A single task

+ Add task asks for a name, workstream, owner, dates, status and priority, then opens the new task so you can fill in the detail.

A batch

+ Add several is for a post-workshop load — the way the 52 balance-sheet items under 1.6.1.6 and 1.6.1.7 went in. Choose the parent task first; the new items are created beneath it.

One per line — paste task names, one to a row, and optionally set a single owner and finish date for the whole batch:

Agree BS reconciliation scope Draft control matrix Walk through with Leanne

Columns — paste straight out of Excel with a header row. Tabs or commas both work.

name owner finish priority BS control matrix Leanne Lally 2026-10-31 High BS walkthrough Kecea Silva 2026-11-14 Medium

Recognised columns are name, owner, start, finish, priority, status, sprint, objective, notes and days. Dates must be written YYYY-MM-DD.

Always Preview first — it shows exactly what will be created. New tasks continue the parent's existing numbering and inherit its workstream.

If a row is wrong

The whole batch is checked before anything is created, so a bad date fails the lot with the row number rather than half-loading 65 items and leaving you to work out where it stopped. Fix that row and paste again.

Reordering the plan

Move a task among its siblings, or in and out a level.

On the Tasks tab each row has four arrows. Up and down move a task among its siblings; left and right move it out a level or nest it under the task above. Children always travel with their parent.

The arrows disappear when you filter

Reordering acts on the real plan order, so it is only offered on an unfiltered list. On a filtered view "move up" would mean "above the row you can see", which is a different task — an easy way to shuffle the plan by accident. Clear the filters and the arrows come back.

Only the siblings either side of the move are renumbered. Moving something under 1.1 will not renumber anything under 1.2 — outline numbers get quoted in conversation, so they stay put unless the move genuinely affects them.

How RAG is worked out

It is calculated from the real date, not stored and left to go stale.

Done
Status is Complete, or 100%.
Overdue
Past its finish date and not complete.
At risk
In progress, past the middle of its window, still under half done.
Active
In progress and running to time.
On track
Not started yet, finish date still ahead.
Unscheduled
No finish date set.

An open task with no owner or no due date is waiting to be picked up. Accepted ideas and issues raised onto the plan arrive like this, so the Overview lists them at the top, the figures strip counts them, and Only these filters to them. Open one and give it an owner and a date. Adding a task without either asks you first.

You can override any task by picking a RAG value yourself — useful for Parked and At risk, which are judgements no rule can infer. Choosing Auto (from dates & progress) hands it back to the calculation. Tasks running on the calculation show a small auto marker.

The RAG and Status filters each have a Show / Hide switch beside them. Tick Parked with Show to see only the parked tasks, or with Hide to take them out of view and leave everything else.

Reports

The SLT pack, built from the plan and the compliance position.

Reports assembles what normally gets transcribed by hand: the performance scorecard, completeness, timeliness and turnaround, the weekly pair, plan health, each workstream's progress, and what has moved in the month you pick.

The window is a calendar month, because that is the unit the pack is built in. It opens on the first and closes at the end of the last day, so a change belongs to exactly one month and never to two. The month you are in is offered and reads so far, since it has not finished yet.

Download PowerPoint gives you the whole pack as a slide deck with real, editable charts — not pictures of charts, so they can be adjusted in the meeting. Copy as text puts the same thing on the clipboard. What is on screen is the deck: the slides are described once and drawn both ways, so the file cannot show you a figure the page did not.

It shows the halves you already have. With the plan but not compliance you get the plan half and a line saying why the other is missing, rather than nothing at all.

What the four measures mean

P&L, balance sheet, AP weekly run and VAT are all read the same way. Submitted is the share of what was due that came in. On time is the share of those that came in by the deadline. Turnaround is the average days late, counting only the late ones — including the on-time ones as nought would flatter it. A client the book excuses, such as one marked No BS Required, leaves that measure altogether rather than counting as either a success or a miss.

A measure the workbook does not carry is not scored. If an extract has no AP or VAT columns in it, those rows are named on the last slide instead of being drawn at 0% — nought is a claim about performance, and having no figures is not one.

Three things it deliberately will not do. It will not write the highlights — which of the week's changes mattered is a judgement, so it gives you what finished, started and slipped and leaves the sentence to you. It will not score a week that has not happened yet. And it says out loud what it cannot answer, rather than leaving the rows out, because a scorecard quietly missing a row reads as a complete one.

Profitability

What each client earns and what it costs to serve them, month by month, for each team.

The strip at the top chooses the book. Accounts is the MA, FC and AP team, read off the monthly profitability workbook as it always was. Payroll, Tax and Insights (which covers all our software delivery) each load one sheet a month, one row per client: the button on their tab offers the template. Whole firm puts the four side by side for the month and adds each client up across them. A client is joined across the books on its name, with capitals and spacing ignored and nothing looser, so spell a client the same way in every sheet. A book not loaded for the month is said, never counted as nought.

Within a book, five tabs (four on the team sheets, which carry no People). Dashboard is the month at a glance. Clients is the full matrix — revenue, IT, labour, office recharge, profit and margin per client — which you can filter, sort and search. Movement compares the months loaded and names who turned a profit and who turned a loss. By controller totals each person’s book. People is hours against contract.

Loading a month

Load a workbook takes the monthly .xlsx. It is read in your browser — the file itself never leaves your machine, only the figures do. You are shown what was found and asked which month it is for before anything is saved, because not every edition of the workbook says.

On a team sheet, type costs as positive numbers and leave the two profit columns blank if you like: they are worked out as revenue less software, labour and other costs, then less the office recharge, and the screen says which clients’ profit was worked out that way. A profit you type yourself is kept, and the load tells you where it does not equal the row’s own sums.

A load replaces that team’s month only. Every other month stays, so the book builds into a history rather than being whichever file went in last. The month-on-month movement is worked out from what is held here, not copied from the workbook’s own trend sheet.

What is yours and what is the workbook’s

Every figure comes from the workbook and is replaced whole when you load that month again. Action, Owner, Status and Notes are yours: type them on the Clients tab and press Save. No import ever overwrites them, and the Change log shows who wrote what and when.

This is the most closely held area in the app. It carries per-client margin and what each person costs, so nobody can see it until an administrator grants it on the people screen — administrators included.

Client scorecards

One client at a time, across everything the app knows about them.

A client losing money is one thing. A client losing money every month while filing late and raising service issues is another — and no single screen could tell you that before. The book lists every client worst first, with the months of profit as a small bar chart, the filing record beside it, and a line or two saying what stands out. Filter to Where we have money and compliance to see only the clients both systems know.

You see the halves your account already has. Without profitability the money is simply not there — not hidden on the screen, not sent.

Reading the book

Order matters more than it sounds. Sorting by the size of the loss shows you where the money is going; sorting by Worst margin shows you which relationships are actually broken, and they are rarely the same clients. A client losing £1,632 on £583 of fees is a worse relationship than one losing more on far more.

Each card carries two small charts on the same months — profit, and the share filed on time — so a client going backwards on both at once stands out. Open gives you everything behind it: the figures month by month, every month-end with its deadline and submission date, and the people whose biggest client this is.

An opened card starts with a summary: three or four sentences, written by AI from the figures on that page, saying what needs attention first. It is written from what your account can see and nothing else, so somebody without profitability gets a summary with no money in it. It is kept until the client’s figures move, so the next person to open the card reads it straight away. It is a starting point, not a source: check anything that matters against the tables under it.

Under it, Open items lists what is still outstanding for that client: open service issues, live statutory and tax work, month-ends still out, and proposals not yet decided. Open on a row brings up that item’s own panel from its own area, so you can read the issue or the job, act on it, close the panel and be back on the client. You see a list only if your account holds that area.

Those people are who, not how much. The workbook records each person’s largest client and their total client hours, so the hours shown are theirs across every client — the hours that went into this one are in the figures above.

Service issues come from a different system that writes a description rather than a name. The screen says how many of those it could not attach to anybody, because a count of zero everywhere looks like good news and usually is not.

Names to link

Each system calls a client something different: the workbook groups it as Allsopps Group, compliance files it under ALLSOPP’S TAVERNS LIMITED across three codes. A spelling the registry already knows is linked for you. Everything else waits on this tab.

A close match is not proof. Big Mamma UK, US, Germany, Spain and Dubai all score 90% against “Big Mamma”, and they are five separate businesses with five separate P&Ls. Keep separate is the right answer for those, and it is remembered — it is a decision, not a way of putting the question off.

A name that is not linked yet still appears in the book, marked as such. It is better to see a client unresolved than not to see it at all.

Requests

Requests, under My work, is the firm’s one way to pass on a lead. Anybody signed in can raise one, from + New › Pass on a lead / request a quote or the button on the screen: say who the client or lead is, what they said (in their words — the proposal is drafted from it), which services they asked about, any timing and a contact if you have one. It lands on whoever covers business development, on their Tasks, with a time limit of one working day to first contact; if no cover is set it reaches everybody with Proposals edit as a counted line, never silence.

You are told the outcome on your own Tasks: contacted, quoted, then won, lost, or declined with the reason. Won and lost are read from the proposal itself, never typed twice, and a win records the client’s lead source as a referral from you, by name. Whoever works the request presses Contacted when first contact is made, and Make the proposal turns the request into a draft proposal with your notes carried in, so the usual drafting from notes runs on it.

Everybody sees their own requests; the owner, the business development cover and anybody mentioned see the ones they carry, and Proposals edit sees every quote request. A note on a request is a conversation — @Full Name brings a colleague in and puts it on their Tasks. The figures at the top are the measures the firm reviews monthly: quote requests a month and how many become won proposals, time to first contact, and requests with no owner, which should be near nought. A system administrator names the cover and the time limit at the foot of the screen.

Client register

Every client the firm holds a record for, and what we do for each of them.

Each service has three marks. A tick means we do it, a cross means the book says we do not, and a dash means nothing has said either way. A paler tick under CT600 means the CT600 is taken to go with the statutory accounts, because the tax tracker has no CT600 sheet of its own; state it as We do not on the client to say otherwise.

The search reads the name, every spelling the register holds, the client code, the controller, the MA, the group and the Companies House and PAYE references, and every word typed has to appear somewhere. Enter opens the client when only one is left. The filters narrow together: The books carry, We said we do, Only these (nothing recorded, disagreements, nothing stated yet, overdue tax work, no controller, archived), Controller and MA. The figures above the table are filters too.

The register is one table, looked at through a lens along the top: Mine (clients you lead or work on, or where you are the FC or MA, worst first), All clients, At risk, To settle, Fee review due and On notice. It opens on Mine if you have clients of your own. Each lens carries its count, orders the table the way that question wants, and brings one column forward beside the name: why the client is at risk, what is to settle, the review date, when the offboarding opened. The figures under the lenses count what the lens holds, and pressing one opens that lens, keeping Mine as a filter if you came from it. Group by on the filter bar puts the clients under headings by client group, controller, MA or risk level, each with how many and their risk score added up. The bar carries + Add a client, Export (this view to Excel, or the risk register to Excel or PDF) and More, which holds the other views (the risk register risk by risk, the disagreements one at a time, fee reviews, by person, groups, directors and PSCs, retention, possible duplicates, people and clients), the change log and grouping by workbook. Columns sits above the table it changes. On another view, a line at the top says which, with the way back to the register.

Open a client to see what the books carry beside what the firm has stated. Each stated choice saves as it is made; stating the accounts also states the CT600 unless the CT600 has been decided. + Add a client asks what we do for them at the same time, and ticking the accounts ticks the CT600. Changing either takes Client records edit, set on the Admin screen.

To change many clients at once, tick their rows (or the box at the top for every client shown). A bar appears above the table: choose under Change whether to state a service, add or take off a person, put them in a group or take them out of one, fill in the boxes that change needs, and press its button. Each is recorded against its own client. How many the filters leave is said once, under the filter bar, beside its Reset. A decision can carry a note, such as which engagement letter agreed it. The client's references (Companies House number, PAYE and Accounts Office references) are typed in their panel.

Where what we said and what a book holds disagree, the service is marked to settle and the client's panel has a box for it: what we said and who said it, what the book holds (a Stat & Tax job opens from there), and the ways to end it. Raise a CT600 job opens Stat & Tax's own form with the client chosen; Set Stated to "We do not" changes our side instead. A change made on another screen shows here straight away.

When a service has ended, set it to We do not and write why in the note beside it, such as "Client has left". With a reason, your answer is what the register shows: the tick goes, nothing is left to settle and it counts towards no risk. If the book still holds the service, the client's panel says which team closes it there (for payroll, setting Payroll to No in HubSpot). A "We do not" with no reason stays marked to settle. On the two internal rows, the profit book and a fee proposal, We do not needs no reason: they are the firm's own books, not services, so your answer stands. Clear selection only unticks the rows chosen for a bulk change; it does not change any service.

A client's panel says how long they have been with us, when their fee was agreed and is next reviewed, and their engagement letter: set any of them there and press Save these. The Fee reviews view lists every review due (each is on the client lead's Tasks), the Retention section shows how long clients stay and who left, and Possible duplicates lists names that read alike for you to merge or keep apart. Columns chooses what the table shows, Save this view keeps the filters under a name, Whose narrows to your clients, and a dot marks a client that changed since your last visit.

A client's page, the risk register and notes

A client opens as a page with tabs: Overview, Services, Relationship, Risk, Notes and Record. Press the widen button to give it the screen.

The Risk register tab lists what the books say could go wrong with each client, in five kinds: delivery, money, relationship, regulatory and records. The highest warning is a client whose management accounts have not been sent for 75 days (45 days is a medium warning). Others are tax work overdue, a client on stop, a loss, billed less than agreed, a fee review due, work with no fee, open service issues (red when one is rated High or three or more are open), open HubSpot tickets for a team you can see (red at six open or one a month old), no engagement letter, no contact, AML gaps, Companies House findings, a disagreement on services, and no client lead. Each risk scores by its level (high 10, medium 4, low 1) and a client's score is the sum; the tab lists clients highest score first, with the score in the first column, and How the score works at the foot says what raises each risk and at what level. A client with a high risk, or two medium ones, about the work, the money or the relationship is counted as at risk; AML, Companies House and register gaps, and our own margin on the client, are listed and scored but do not make a client at risk, and nor does a client still being onboarded. A client who has given notice is not scored and is listed apart under Given notice. Each risk is resolved in one of two ways: In hand, with an owner and a date, which puts it on that person's Tasks; or Accepted, with a reason, for up to 180 days, after which it comes back. You see only the risks from books you can read.

The register is read every night. High risks nobody has in hand are on the client lead's Tasks, so are the facts the register is missing for their clients, and a short summary is emailed every Monday morning.

Export to Excel and Export PDF on the Risk register tab download the list as it is filtered: clients highest score first, every risk, who has given notice, and how the score works. Each file says when it was taken, by whom and with which filters.

Notes keeps what anybody who reads the register knows about a client, oldest first, with who wrote it and when. Notes are never edited. To ask a colleague something about the client, choose them under Ask somebody or type @ and their full name: see Notes and questions for the team.

To settle lists every service where what we said and what a book holds disagree, with the buttons to end each one.

On the table, / goes to the search, the arrow keys (or j and k) move between clients, Enter opens one and Escape leaves the table. The filter bar stays in view as you scroll.

Change log on the toolbar shows every change to the register, newest first; the same button in a client's panel shows theirs alone. Export to Excel downloads the table as it is filtered and ordered on screen.

What we charge, where they stand, and how complete the register is

Under the figures, The register is n% complete counts the facts the register should hold for every live client: what we do stated, a client lead, somebody stated as working on them, a Companies House number (companies only) and a contact. Each box is a filter: press it to list the clients missing that fact, and press it again to put the register back. Clients who have left or are archived are not counted.

Not every client has a Companies House number, and the register says why rather than leaving a gap. A group with companies inside it needs none of its own: its companies carry theirs. On a client’s References, No UK company number says it is an overseas company, not a company at all (a partnership or sole trader), or a brand. A brand counts as answered only once the companies that trade under it are added and put inside it; until then it asks for them, and the client lead sees it on Tasks. Anybody owning Stat & Tax work for a company with no number sees that on Tasks too.

If your account reads Proposals, each client shows the fee on their latest won proposal, line by line, and which services have no fee on record: work we do that no line charges for. The figure Doing work with no fee on record lists them. A client with no won proposal at all shows every service as having no fee on record until one is put through Proposals. Annual accounts cover the CT600; bookkeeping covers the P&L, BS, AP and VAT; payroll and company secretarial lines cover their own columns.

A client on stop shows a red On stop on its row and at the top of its panel, with since when and who placed it; only an account that reads Billing sees why. The panel also says where the client is (onboarding, live, offboarding or left, and since when, from their cases), their key dates (year end, next accounts, CT600 and personal return deadlines, VAT quarters and the next return), and anything the nightly Companies House check found.

Contact on the panel is the one place for the person at the client we deal with. Until somebody types one, the management accounts book's contact or the onboarding case's is shown and marked as theirs; Save contact makes it the register's own. Payroll and CoSec are columns now: CoSec is carried from the company secretarial book, and payroll is what the firm states, because no book here carries it.

To change many clients at once, tick them: the bar above the table states a service for all of them, or adds one person in one role to all of them (or takes them off). Group by workbook says how many companies the compliance workbook files under a group they are not in yet; open it, untick any you are not sure of, and group the rest.

Who works on each client

Open a client and use Who works on them: one row per role (client lead, financial controller, management accountant, AP and payments, payroll, Stat & Tax and company secretarial). Pick a person from + Add, or press the cross on a name to take them off. Each change saves as it is made and goes in the change log. People are picked from the WSOP accounts, never typed. Where nobody is stated as FC or MA, the FC and MA the compliance books carry stand in and are marked as the books’; State beside them confirms that person in one press. Where the stated person and the books disagree, the row says differs from the books and neither is changed: the books are put right in the workbook. Changing who works on a client takes Client records edit.

The FC and MA stated here are who does the client across WSOP: VAT Returns, the P&L close, Payment Runs, the Work Planner, Client Scorecards and the lines on Tasks all read them first, and the compliance books’ names only where nobody is stated. The Compliance screen itself still shows the workbook’s own names.

The By person tab, on the strip beside the views, is the same list turned round: each person, the clients they work on and in which role, with a search and filters for the role and for where the answer comes from. A name the books carry that no account answers to is marked no account. Adding a client to a person, or taking one off, there is the same change as doing it on the client.

When somebody is away, open them on By person and choose Set cover while they are away: who covers them, the day it starts and, if known, the day it ends. While it runs every client stated for them goes to the person covering, on every book and on Tasks, each saying whom they cover for; the register still shows them as the client's MA or FC, marked away. Their clients go back to them on the day it ends, or when you press End the cover. Never write why somebody is away.

The People & clients tab is the registry the escalations board opens: names to review, and the people, client and private client records with their spellings, where two records for one name are merged. It shows for an account that reads service issues.

Press a name on that tab to open it out. It lists every spelling that resolves to the record and, for a client, every line from the profitability and compliance books linked to it. Each one has a Move button: choose the record it really belongs to, or make a new record of its own. A workbook line can also be unlinked, which puts it back on the names to link. Moving changes where that spelling or line resolves from now on; tax jobs, proposals and everything else already recorded against the record stay with it, and both records' change logs say what moved. The record's own name cannot be moved: rename the record, or merge it, instead. Moving a spelling takes Service Issues edit; moving a workbook line takes Client records edit.

Archiving a client, and putting one back

Archive a client that has left, or was never a client. Nothing is deleted: the record keeps its history, and it can be put back at any time.

  • One client: open it, and at the foot of its Overview press Archive this client. Say why, then press Archive it with this reason.
  • Several at once: tick the boxes on the left of the list (the box at the top ticks every client shown), write the reason under Why are they being archived? and press Archive them. This works on every tab: Mine, All clients, At risk, To settle, Fee review due, On notice and Former clients.
  • Putting one back: open the Archived tab, which lists every archived client with why, when and by whom. Open the client and press Restore to the register, or tick several and press Restore them to the register. Change the reason corrects a reason.

A reason is always asked for, because the Archived tab is read by people who did not do it. A client still carrying live tax work, or that is the group for other live clients, is not archived, and the register says which and why; close or move that first. Archiving and restoring take Client records edit.

Compliance

Month-end submissions, weekly reporting, and the root causes behind the late ones.

Five tabs. P&L and BS Dashboard is the month-end position by client, with the outstanding list and the root-cause analysis behind it. Weekly Delivery Control is the same month by working day. Weekly Report & Cashflow is the weekly reporting and cashflow cadence, week by week. VAT and Payment Runs (AP) are the same month-end view for those two.

VAT and Payment Runs

Both read the same way as the P&L and balance sheet: submitted is a dated submission, on time is that date on or before the deadline, and a client marked as owing none that month leaves the rates altogether rather than counting as either a success or a miss. Filter by month, FC, MA, and by what you want to see — everything outstanding, overdue only, submitted late only, or still pending.

The VAT tab also says where each return stands: Not yet started, In progress, Awaiting approval or Submitted. A return on VAT Returns takes its live step from there, and Open goes to it; any other takes the VAT Status on the register as at the last upload, and one where neither says reads Not recorded. Filter by VAT status, and read each FC's returns by status in the table under the by-FC charts, which goes in the emailed review too. VAT Returns has the same four words on every return and the same filter.

Payment runs are kept week by week. View on the Payment Runs tab switches to Month by month: every week that ends in the month is added together, a client owing a run each week is counted once for each, and the runs that did not go out say which week they were. A Month by month table under the overview gives the last twelve months side by side over every client you can see; press a month to look at it. Picking a month there moves the other tabs to it too.

The Root cause and Comments cells on the outstanding rows are boxes, not readouts — click one and type, and it saves when you press Save changes. Each measure keeps its own, so a note about a late payment run never overwrites one about a late P&L for the same client. Each tab's Change log shows who wrote what and when, for that measure alone; the Change log button above the tabs still shows everything. The Weekly Report & Cashflow tab works the same way, except that a note there belongs to one client, one metric and one week.

Neither is in the workbook yet. Until an extract carries them the two tabs say so and name the columns that would bring them, rather than showing empty charts or nought per cent. A payment run nobody has told us about is not a payment run that was missed.

The month, and why one might be missing

Pick a month on any tab and every tab follows, so two screens never show different months without telling you. The two sheets do not cover the same ground — the monthly sheet stops where the workbook stopped, the weekly one runs to the end of its last week — so if a tab cannot show the month you picked it shows its own latest and says so in a line above the tabs.

A month you cannot see is a month the workbook has not brought. The app holds what the extract gives it. Months now carry their year, so this June and next June are different months and a root cause written against one never reappears against the other, and each import adds its months to what is already here rather than replacing the lot. The weekly sheet works the same way, a week at a time, so a week that drops out of the workbook's window stays on this screen.

Recording a reason

In the Outstanding / Pending Items table the RCA and Comments cells are boxes, not readouts. Click one and type; it saves when you click away. They start blank because a root cause only exists once something has actually gone in late — an item still outstanding has no cause on record yet, which is exactly what you are there to supply.

The root-cause breakdown further down is a different population: submissions that went in late, and the causes already recorded against them. That is why the same client can be blank in one and filled in in the other.

Who changed what

Change log, at the top of the Compliance tab, is every edit anybody has typed: when, who, which client and month, which field, and both sides of the change. It is written on every save and cannot be turned off. If your account covers your own clients you see your own changes; if it covers everybody you see everybody's.

An update to the figures does not appear there, because it is not an edit. It has its own line in the provenance stamp above the tabs.

What an update keeps

Update figures replaces every number that comes from the workbook. It never touches anything typed in the app — root causes, comments, risk, the action plan — so a manual edit can never block or be overwritten by an update. Before you confirm, the preview names the clients whose typed fields will be kept, so you can see exactly what is carrying over rather than being told a number.

Your clients, or everybody's

Both the P&L and BS Dashboard and Weekly Delivery Control carry the same Deadline window as the improvement plan, over the month-end submission deadlines. A client is in the window if either its P&L or its BS is due in it. It starts on Any deadline, and every figure on the page — not just the tables — is recomputed from what the window leaves in, so the denominators move too. Where there is nothing to measure the rings read —, in grey, rather than a red nought.

Weekly Report & Cashflow counts whole weeks rather than deadlines, so it has a Week range instead: the next 2, 4 or 8 weeks, the last 2, 4, 8 or 13, or a custom range. A week is in if it overlaps the range at all — half a week of work is still that week's work — and a range crosses months on purpose, since a month holds only four or five weeks. While a range is set it is the authority, so Month and Week grey out; The month chosen above hands control back to them. The day-by-day schedule still needs a single week.

An account can be scoped to its own clients. Scoped that way, you see the ones where you are the FC or the MA and nothing else — every donut, table, root cause and count on the page is yours, not a filtered view of the company's. A line at the top says so, so a short list is never mistaken for data that failed to load.

Anyone who sees the whole book gets a roll-up by controller instead: a row per person, with their clients, what is overdue, what is still outstanding, what went in late, their submitted and on-time rates, and how many of their late items still have no root cause. It opens best first. Click any heading to sort by that column, and click it again to reverse; Best first / Worst first flips the order, Find a person searches by name, and the ticks keep only the people with something overdue, outstanding or waiting on a cause. Your choice is remembered on this browser; Reset puts it back. Click a row and the whole page narrows to that person; click it again for everybody. It is built from the same rules as the cards below it, so the two can never disagree.

Scope is set per account in Admin → People, from the names that actually appear on a client. It is separate from what an account may change: somebody can read the whole book without editing any of it, or edit their own clients and see no others.

Late items with no cause yet

Open Show Root Cause Analysis and an amber panel lists every late item nobody has worked out a reason for. They are not blank — they carry the code Unknown, which is a real entry in the taxonomy, and they count as Unknown in every chart on the page until someone decides otherwise.

Pick a cause from the list beside each one. Choosing sets all five levels of the taxonomy together, so the combination is always a valid one, and it saves the moment you choose. The item drops off the list, the charts recount, and the next import of the workbook leaves your answer alone.

What is yours and what is not

The figures come from the compliance workbook and are replaced whole every time it is imported — deadlines, submission dates, statuses, the counts. Nothing you type here can change them, and nothing an import does can delete what you type. The line at the top of the page says when the figures were produced and when they were loaded.

Yours to fill in: root cause and comments on the outstanding list, risk and projected completion, and the whole action plan — suggested action, owner, target date, status and notes. Click into a cell, type, and press Save changes. Until you do, a red line says how many rows are waiting, and leaving the page will warn you.

Worth knowing

Saving is immediate and shared. There is no export step and nothing to paste anywhere — everyone with compliance access sees your root cause the moment you save it.

Updating the figures

Update figures sits beside the line saying when they were produced. Two ways in, and they do exactly the same thing.

WayHow it works
By handChoose the extract file. Before anything is written you are told what it holds — the date, the months, how many rows — and what it will replace. Nothing changes until you press Replace the figures.
On a scheduleAt 6am on weekdays the site fetches the extract from a configured link and imports it. It refuses an extract older than the one already loaded, and records a failure rather than failing quietly. Until a link is configured it runs, finds nothing, and says so on the Automatic refresh tab.

Either way, the numbers move and your analysis stays attached to the client and month it was written against. A field you have changed by hand keeps your value rather than reverting. What has been loaded lists every import, who did it, and the date of the figures.

Worth knowing

An import is all or nothing. If it fails part way — a bad file, a dropped connection — the figures stay exactly as they were rather than ending up half replaced.

Stat & Tax

Accounts and returns by client and period — where each one has got to, what it is waiting on, and who would pick it up.

One row per obligation, per client, per period: statutory accounts, CT600, personal and partnership returns, P11Ds, confirmation statements, ATED. Five views across the top. Work tracker is the book. Hung is what has stopped and who it is waiting on. To-do list is every next action, the ones on a job and the ones that belong to nobody’s job. Handover is who holds what and who would take it on. Procedures is how the work is done, with the CIP task behind it.

Deadlines work themselves out

Give a job its period end and the deadline follows from the rule: nine months after the accounting reference date for accounts, twelve for a CT600, the 31 January after the tax year for a personal return, and so on. The payment date rides alongside where there is one. The drawer shows the rule it came from, so if you think a date is wrong you can see what it was derived from.

Where you have the registry’s own filing date, put it in and it wins. That is the ordinary case rather than the exception: Companies House counts from the actual accounting reference date, which is whatever day the company was incorporated on rather than a month end, and a first or shortened period moves it again. On our own book the rule and the registry agree on 341 accounts jobs and differ on 184. It costs no reason, because it is not a judgement — it is the fact the rule was trying to approximate. The rule is still worked out, and where the two disagree the row is marked registry and the drawer says what the rule would have given, which is worth knowing: it means the period is not what it looks like.

Where neither is right — an agreed extension — you can set the date by hand. That one costs a reason, which is what tells the next person why this job disagrees with the rule, and the job is marked as set rather than derived.

A job with no period end has no deadline and says so. It is never shown as due today, and the strip at the top counts how many are in that state, because an unknown deadline is a gap to fill rather than a date.

Open means live work

A real book carries rows that are not work at all: the client has left, the company is in liquidation, we are not doing it, they file it themselves, it is not required, or nobody has decided yet. About a fifth of ours. Every one still has a year end and a real filing date, so counting them as open would report a backlog nobody owes.

Say so on the job under Is this ours? and it drops out of the open count, the chase list and the handover, and its deadline stops being counted against anybody. It is never deleted — that is a decision somebody made, and a row that disappears is a decision nobody can find again. The strip shows how many there are, so Open jobs can be trusted to mean open jobs, and the Not ours filter finds them again.

The chase list

Everything where the ball is in the client’s court: the draft is with them, they have come back querying, or we asked for records and nothing has arrived. Ordered by deadline, not by how long they have had it — a fortnight on a draft due in March is not this morning’s call.

Days with them are counted from the last thing we did: the last chase, or the day the draft went out, or the day we asked for records. Where nobody recorded any of those it says not recorded rather than reading as a client who replied instantly. A job with no next chase date is not a chase due today; it is nobody having said when.

Stage and hold are different questions

Stage is how far the work has got. Waiting on is why it stopped, and who it stopped on — the client, HMRC, Companies House, another adviser, or us. A job can be at In progress and waiting on records, and both are true. The clock starts when the hold is recorded and does not restart when somebody re-states the same reason: three weeks waiting stays three weeks waiting.

Loading it from a workbook

Your own tracker will do — it does not have to be our template. Columns are found by name so you can put them in any order; a tab that is all one kind of work needs no Work column at all, because you tell it which kind the sheet is; and a workbook of several tabs is loaded a tab at a time. A tax year written 2025/26 is read as 5 April 2026.

Nothing is written until you have seen what it would do: which clients it found, which it did not, which jobs are already on the book, and every row it could not read with its line number. A cell it could not read is named by its column with the rows counted, and the row itself still loads — a phrase in an optional column is not a reason to refuse a real job. Running the same file twice adds nothing and overwrites nothing anybody has typed since.

Working papers

Each kind of work carries a checklist, and the drawer shows what is held and what is missing. What is recorded here is where the paper is, not the paper: the papers stay in the document management system, and a slot counts as held once somebody has said where to find it. A link that opens nothing is worse than no link, so a slot with nothing behind it stays empty.

The handover

Every job has a Successor — who would take it on. The handover view counts, per owner, how many of their open jobs have somebody named against them, how many are overdue, how many are hung, and how many have no deadline. An owner with nothing open reports nothing rather than 100%. Naming a successor is a field on the job, so the list fills in as the work is done rather than living in a separate spreadsheet.

Where it meets the rest

Procedures are held per kind of work and per stage, so one procedure is written once and shows on every job of that kind at the step it belongs to. A procedure can name the CIP task systemising it, and a job can link to one too — which is how somebody picking up unfamiliar work reads the method next to the step, and how whoever is improving that step can see everything it touches.

This area names clients’ tax affairs, so nobody can see it until an administrator grants it on the people screen — administrators included.

Company secretarial

Company secretarial has its own place under Delivery and is the team’s CS Tracker, managed by Helen Henry. Each row is a matter: one piece of work for a client, with its lead, fee, billing stage, target and the date it was done. Confirmation statements, formations, officer and PSC changes, share work, registered office moves, VAT, PAYE and ICO registrations, payment plans, SEIS and EIS all sit here. The service is kept in your own words and filed under a kind, so the book can be counted.

+ New, top right of Company secretarial, starts anything from one place: a director joining or leaving, a PSC change, identity verification, allotting or transferring shares, a share certificate, a change of registered office or name, approving the accounts, dormant accounts, a strike-off, the confirmation statement and its questionnaire, a document or a signature, and a matter, a roster company or a load. Choose what, then which company, and the company opens on that form, filled where the registers can fill it, with a line saying what to press next. Nothing is saved until you press the form’s own button.

Where the law sets a window the deadline works itself out from the date of the event: an officer or PSC change fourteen days, a resolution fifteen, a charge twenty-one, an allotment a month. Where it does not, the target you set is the date. The row says which it is, and a matter with neither says no date rather than pretending.

Complete, not billed is the list to clear: work done, with a fee, and no invoice raised. Recharges within the group are recorded as that, with who they are charged to in the billing note. Nobody leading goes to Helen; so does anything raised without a lead.

The Roster is who the firm gives a registered office or a company secretarial service to. The Confirmation statements view reads the tax tracker, where each statement’s deadline and next year are worked out, and names any roster company with none live there. Load the tracker takes the CS Tracker workbook, shows what it would add, asks who each first-name lead is, and loads it; loading the same file again adds nothing.

Billing. A matter completed from the Billing screen’s tracking date onwards, with a fee, appears on Billing as an invoice to raise; recording it there shows on the matter. Anything completed before that date is the record of the old tracker and is never pushed through.

What recurs. Completing a confirmation statement raises next year’s, aimed a year on; correct its date to the review date on Companies House. Next year proposes the statements the history owes, one per client, and raises only the ones you tick. A client whose last one is over two years old is named, not proposed.

Waiting on. Say who has the next move (the client, Companies House, HMRC, somebody else). A week waiting is a chase, on the figures and on your Tasks.

Raise a matter offers the usual fee for that kind of work, from the last year of the book.

Confirmation statements load themselves. Every night Companies House is read for each company with a number, and where the register expects a confirmation statement for a company on the roster (or one we already file for, or that the Client Register says we do the company secretarial work for), the job is raised on the tax tracker with the register's own review date and due date. Six weeks before one is due the CoSec lead is told on Tasks, so the client can be asked what has changed before the statement confirms it. Filing it raises next year's.

Companies House is a tab here and on Stat & Tax, the same on both. It shows what the nightly check of the public register found for a person to act on (filed there and open here, expected and missing, no longer active, overdue there), with a search; Look up reads one company’s dates now; Check now (Stat & Tax edit) reads the next forty and puts their accounts due dates on the tax jobs; and Find company numbers (Client records edit) searches the register by name for clients with no number, ticks only an exact match by one active company, and saves nothing until you press Save. Each figure at the top is a filter: press No number yet and the list below shows exactly those companies. Every row has an Action button that opens the company, reads the register again and shows it beside the tax book. There you agree a finding (mark the job filed on the register’s filing date, raise the job the register expects, or mark a company that has closed as not ours) or say it is not right, with a reason, which takes it off the list. For a company with no number it searches by name and lets you choose or type one. Nothing is changed until you press a button and confirm.

Registers. The statutory registers live here now: directors and secretaries, people with significant control, members, allotments and transfers, and charges. Open a company under Registers. Who holds what is worked out from the allotments, transfers and cancellations, never typed. Nothing is deleted: an entry typed in error is struck with a reason, and every change is in the company’s history. For an empty register, Take the register from Companies House starts it from what Companies House names.

What changed at Companies House. Every night the directors, PSCs and registered office of each company we keep registers for (or that is on the roster) are read. A change since the last night is listed on the company and on the manager’s Tasks: Apply to our register, Noted, or Not right with a reason. Where our register and Companies House disagree it says so; either side can be right, so a person decides.

Documents. Board minutes (an allotment, appointing or losing a director, a new registered office, approving the accounts), a written resolution, a share certificate and a stock transfer form (J30), filled from the company’s registers and downloaded as Word. Templates holds the firm’s wording, which anybody with edit can change or put back to the standard.

The questionnaire. Six weeks before a roster company’s confirmation statement is due, the client’s contact on the Client Register is emailed a short set of questions (what has changed, the registered email address, and the lawful purpose statement). They open it with a code sent to their inbox. What they send back is listed on the company, one item at a time, to apply to the registers or mark done.

Filing. Draft a confirmation statement, a director appointment or resignation, a PSC notice or cessation, a change of registered office or a return of allotment on the company, and send it to Companies House. The company’s authentication code is held sealed and never shown again. Until the firm’s presenter account is live, every filing goes as a gateway test, which Companies House checks and does not register. Its answer comes back the next night; an accepted confirmation statement files its job on the tax tracker.

Annual fees. A registered office or company secretary service is billed once a year through a recurring schedule in Billing, set up from the company (it takes Billing edit too). Annual fees lists every roster service that bills nothing yet.

Inform Direct. Load the Inform Direct export (officers, PSCs, shareholdings) once, matched on each company’s number. For the month after, Inform Direct lists every company where the two disagree; when the list is empty or explained, Inform Direct can go.

Directors & PSCs. A tab on the Client Register lists every director, secretary and person with significant control once, however many companies they serve, from our registers and from Companies House. Record each person’s email and phone there, and choose for each company the one we ask. The confirmation statement questions go to that person, and a document to sign offers their address. Choose a billing contact for each company as well: one of its people, or somebody else such as the finance contact. A new customer in Xero takes that address. Companies House is read every night for every client with a company number, so the list fills itself.

Deadlines. One calendar for everything company secretarial owes: a director appointed or leaving (14 days), a PSC (28), an allotment (one month), a charge (21 days), identity verification and the confirmation statements on the tax tracker. A change read from Companies House or loaded from Inform Direct is already on the public record and owes nothing.

Identity. Every director and individual PSC verifies their identity with Companies House. The tab lists each person once, across every company they serve, with the date the law gives them; record what they tell you on the company. A confirmation statement does not go in bulk while a director is not verified.

A director joins or leaves, in one press. On the company, the change pack makes the board minutes and drafts the AP01 or TM01. Send the form; the register entry goes on by itself when Companies House accepts it.

Statements in bulk. Every company whose questionnaire came back saying nothing has changed, with its code held and its directors verified, can be ticked and filed together. Each company that cannot go says why.

Signing. A director who works here signs a document in WSOP, as the officer the register names. A director outside the firm is sent a link to that one document with a code to their inbox; they never get an account.

Companies House’s record. The filing history, with each document linked, and the charges are read every week and on request. A charge that disagrees with the register is listed to settle. Each filing accepted for real is an invoice on Billing at the fee set on it, else the usual fee for the form.

Record. Every filing and register change in a period, as PDF or Excel, and whether Inform Direct can be retired: one full month of running both with every company agreeing. The registers themselves download as a PDF on the letterhead, as at any date, from the company.

Also filed from here now: a change of name (NM01) and dormant company accounts. A strike-off application (DS01) is a document to sign; Companies House does not take it from software.

Access is Stat & Tax’s: view reads it, edit changes it.

P&L

The management accounts close. Called Management Accounts until 11 October 2026.

Every client’s month-end close, from the request we send at WD−5 to the client signing off the pack.

Our promise to clients is the 3-day close: the P&L in their hands on the third working day, while the numbers can still change a decision. What delivers it is everything before that date landing on time, so each close is shown as a timeline rather than a single deadline, and it always says the next thing to do. One close per client per month, worked in the app so everybody sees the same position. Tick things the day they happen. A date nobody has recorded is shown as not recorded, and late means a working day has actually passed.

It opens with Compliance access: read to see the book, edit to work it. A compliance account scoped to its own clients sees only those.

The timeline, in working days

WD1 is the first working day after the month ends. WD−1 is the last working day on or before it, so WD−5 is five working days before the month is out. Weekends and England and Wales bank holidays never count, and the app works them out, Christmas included. The firm’s standard, for a client whose pack goes out on WD3, shown for September 2026:

WhenWhatWho
WD−5, Thu 24 SepMonth-end request sent to the clientMA
WD−5, Thu 24 SepPayroll changes for the month: starters, leavers, pay changes, overtime, troncClient
WD−1, Wed 30 SepRota and hours worked to the month endSystem (rota export)
WD1, Thu 1 OctBank statements, EPOS takings and Z-reads, delivery platform statementsSystem
WD1, Thu 1 OctPurchase invoices, card receipts and petty cash, stock count, costs not yet invoicedClient
WD1, Thu 1 OctPayroll journal and reportsPayroll
WD1, Thu 1 OctAP closes: anything later is accrued, not waited forMA
WD1, Thu 1 OctSales and takings posted; purchases posted and AP closedMA
WD2, Fri 2 OctWages; bank and cash; accruals, prepayments and stock; balance sheet; P&L pack and commentaryMA
WD3, Mon 5 OctFC review, then the pack sent to the clientFC, then MA
WD5, Wed 7 OctClient signs offClient

A client on a later send day keeps the same shape: the team’s sections move with the send day (a WD10 client posts wages on WD9), while the dates we give the client for their information stay where they are.

The pack’s deadline comes from, in this order: a date set by hand on the close (it needs a reason), the compliance book’s P&L deadline for that client and month, then the client’s send day. Where the compliance book and the send day disagree, the close says so.

Your month, if you are the MA

You prepare the close. Unless somebody has chosen otherwise, the MA named in the compliance book is the preparer and the FC is the reviewer.

  1. WD−5: send the request. Open the close from your Tasks list or the Closes tab. Under Email the client the month-end request is already drafted from what that client owes. Read it, adjust it, press Send the email. The WD−5 step ticks itself.
  2. WD−5 to WD1: mark what arrives. Set each item to Received as it comes in. If something does not apply this month, set Not applicable and say why in the note. Press Save the close.
  3. Chase what is late. Anything past its day turns red and appears in the Late list on the Today tab. Open the close, pick Chase for what is outstanding and send it; it lists only what is still missing.
  4. WD1 to WD2: work the sections. Sales, purchases and AP, wages, bank and cash, accruals and stock, balance sheet, then the pack and commentary. Answer every item Done or Not applicable, and save as you go.
  5. Submit for FC review. The button works once every item is answered. If the FC sends it back, their points show at the top of the drawer. Fix them and resubmit.
  6. WD3: send the pack. Once the FC has approved, attach the pack under Send the pack to the client and press Send the pack. It goes from the platform, always copied to you and to the compliance mailbox; the MA and FC on the close are filled in under Also copy, and you can add anyone else there. The files are kept on the close, and only then is the close marked sent: the P&L is recorded as submitted on the compliance book, so nobody uploads it, and next month’s close is raised. If the pack went another way, open Sent it another way?, press Mark as sent to the client with the date, and copy the compliance mailbox into the email you sent.
  7. Record the sign-off. When the client confirms the figures, press Record the sign-off with who signed, the date and how. Until then the close stays on your list.

If a close is stuck on somebody else, set Waiting on in Details and pick who: the client, the payroll, a feed that is down, or an internal query. The clock on that hold runs from the day you set it.

Your part, if you are the FC

A pack waiting for you appears on your Tasks list as your review, and on the Closes tab under With the FC. Read the timeline: every answer is there with who gave it, when, and any note. Approve if it is right. If it is not, write the points in the box and press Send back with these points; it will not go back without them, because an MA with no points cannot fix anything. Be specific: which balance, which variance, what you expect to see. You cannot approve a pack you prepared yourself. While a pack is with you the answers are fixed, so what you approve is what you read.

How each step is done

Every input, section and item on the timeline lists the procedures that say how it is done: MAC-01 to MAC-07 for the close itself (the request, sales, purchases and AP, wages, bank and cash, accruals and stock, the pack and review), with the balance sheet procedures where an item leans on one, such as TRC-04 for tronc or ACR-04 for run rate accruals. Press one to read it in place, without leaving the close; Open it in the procedure manual takes you to the full page. A procedure not yet in the manual is named as not there yet. You see the titles only if you can read the manual.

Complete

Complete, at the right of The close, day by day, answers every close item still to do as done in one press. Anything already answered, and its note, stays as it is. It saves the close; it does not send it to the FC, who still reviews it. The history records that the close was completed in one press.

Close it all out, under that heading once the period has ended, is for a close whose work was done and whose pack went to the client outside the platform. It marks every input and item still to do as done, records the pack as sent on the date it went (the compliance book's date where it holds one, otherwise the date you give), and closes it with no client sign-off recorded, so it leaves the open list and your Tasks. It does not record an FC approval, so it is not counted in the learning loop, and it is not offered while the pack is with the FC. Reopen it if it was closed by mistake.

Evidence

+ Attach evidence under an item puts a file on it: a screenshot of the bank balance, the payroll report, the stock count sheet, the email a client sent. Screenshots (PNG, JPG, GIF, WebP), PDFs, spreadsheets, Word documents, saved emails and text files, 3MB each, six to an item and forty to a close. A picture opens in the page; anything else downloads. Anybody who can open the close can see what is attached. The preparer and the FC can attach until the pack is sent, because what the FC approves is what was attached; only the person who attached a file can take it off, and the record that it was there is kept. Balance Sheets has the same button on every account.

Sending it back, and the learning loop

When you send a pack back, open Name what to look at again and tick the items or whole sections the points are about. The MA sees each one marked on the timeline with its procedures beside it. The Learning loop tab counts those ticks over 3, 6 or 12 months, with the same figures and the same rules as Balance Sheets: first time right, bounce rate, bounces per bounced pack, whether each MA is getting better, the items that bounce and for how many people, and what the FCs said. An MA sees their own closes, a scoped account its own clients, and anybody who sees every client the whole firm.

Emailing the client

EmailOfferedWhat it lists
Month-end requestUntil the request has goneEverything the client sends us, each with its day, when AP closes, and when the pack goes out
ChaseOnce the request has gone and something is lateOnly what is still outstanding, with the day each was due

What arrives by itself (a bank feed, EPOS, captured invoices, a rota export) is not asked for; the request names it as automatic and asks the client to say if a feed has stopped. The draft is a starting point: change anything, and what is in the box is exactly what the client receives. It goes from the app’s address, copied to you, with replies to you. Several addresses can go in, separated by commas, and the first one you use is saved for next month. Every email is logged on the close, including any that failed. Emails are not sent while working as somebody else.

The wording of both emails is set once for the firm on The timeline tab, by anyone who writes compliance and sees every client, with a button to go back to the standard wording. Placeholders such as {{client}}, {{period}} and {{items}} are filled from each close, and an email that still has one in it is not sent.

Setting up a client’s own timeline

Most clients run on the standard. Where one does not, record the difference once on the client (the Clients tab, or Open the client and its timeline from a close) and every close of theirs follows it.

SettingWhat it does
Send dayThe working day the pack goes out. Blank reads the compliance book’s WD_PL, then WD3.
NeededUntick what this client does not have, such as delivery platforms or stock. It stops being asked for, in the timeline and the emails.
Working dayMoves an item this client sends on a different day, for example payroll changes at WD−7.
How it arrivesAutomated or sent by hand. The Clients tab counts how many inputs are automated and how many more could be.
NoteWhere it comes from, for example “via Dext” or “from the GM”. It appears beside that item in the client’s email.
Contact and emailWho receives the request and signs off the pack.

The “could be automated” count on each client is the list to work through with them: every input moved from sent by hand to a feed is one less chase every month.

How it joins up

AreaWhat happens
ComplianceThe deadline is the compliance book’s P&L deadline. Marking a pack as sent records the P&L as submitted for that month, unless the workbook already carries a date, and a later upload cannot put it back to outstanding.
Balance SheetsWhere QC holds the client and month, its checklist answers the balance sheet item: submitted to the FC or approved in QC is done here.
Work PlannerEach close shows with where it has got to, in place of the bare P&L date.
TasksThe preparer has each close from WD−5 until sign-off, worded as the next thing to do. The FC is asked when a pack waits for review. Both hear when it is late.
Client RegisterThe P&L tick follows this book.

The MA and FC come from the compliance books, so a client moved to another MA in the monthly pack is theirs here the same morning.

The screens

TabUse it for
ClosesEvery close with its track (Info, Close, FC, Sent, Signed), the deadline, working days left and the next action. The figures across the top are filters.
TodayThe morning stand-up: what is due in today, what the team should finish, which reviews and packs fall today, and everything already late. The arrows step a working day at a time.
ClientsEach client’s frequency, send day, how many inputs are automated, and the current close.
The timelineThe firm’s standard close written out, and the two email templates.
Learning loopBounce-back over the last months: first time right, who is getting better, and the items the FCs point at, with their procedures.
Load and roll forwardFor whoever runs the book: load clients from the compliance book, and raise the month’s closes for clients whose last pack is still out.

In each row’s track, green is done, blue is under way, red is late, and the outlined step is where the close is now.

Rules of the road

  • Tick it the day it happens. A timeline updated on Friday for the whole week tells nobody anything on Tuesday.
  • Not applicable always carries a reason. The FC reads it, and so will next month’s MA.
  • Send the request from the app, not your own inbox, so it is logged against the close.
  • Chase from the Late list first thing in the morning.
  • Never mark a pack as sent before it has gone. It records the P&L as submitted, which is how the firm is measured.

Common questions

QuestionAnswer
The deadline is not what I expectedThe line under the date says where it came from. If the compliance book’s date is wrong, fix it there; if this month is genuinely different, set the deadline by hand on the close with a reason.
A client does not have one of the itemsUntick it on the client’s timeline once, rather than marking it not applicable every month.
I ticked something by mistakeSet it back to To do or Outstanding and save. Every change is in the history at the bottom of the close.
I marked a pack sent too earlyReopen takes one step back at a time: the sign-off first, then the send. Reopening a send clears the compliance entry this book wrote.
Next month’s close is not thereIt is raised when the current pack is sent. If this month’s is still out, raise it from Load and roll forward, or Raise the next period on the client.
The balance sheet item will not tickIt is answered by Balance Sheets for that client and month. Submit the QC checklist to the FC and it ticks here.

Payment runs

Delivery › Payment Runs is every client whose supplier payments we make: one run per client per run date, on the client’s cadence (weekly, fortnightly or monthly). It comes with compliance access, like the VAT book, and a scoped account sees its own clients.

Taking a run through

  1. Invoices posted and approved. Everything due by the run date is in the ledger and approved in the AP tool.
  2. Payment list prepared. Open the run and paste the payment list out of the AP tool or Xero’s bills to pay, heading row first. Hold back anything disputed, with the reason. A line put on by mistake is removed, and stays on the list struck through.
  3. Sent to the client with Send the list for approval.
  4. Client approved. Record the client’s approval approves every line still listed. Hold back first anything they took off.
  5. Paid. Mark as paid once the batch is released at the bank. It records the run on the compliance payment-runs register for its week, so nobody uploads it, and raises the next run.
  6. Matched back. Tick each payment off against its bill and its bank line, or tick mark them all matched. A payment that is not matched, or a paid total that differs from the approved one, needs a sentence before the run is finished. Aim to do it within three days of paying, so the bank is reconciled before the month-end AP cut-off.

A run with no list can be taken through on its totals alone: type the list total, the approved total, what was paid and how many payments, and how many were matched.

Why it was late

A run is late when it does not go out in its week, or goes out and is not matched back in time. A management accounts close is late when it went to the client after its deadline or is past it. Either one shows Why it was late in its drawer: pick the cause from the list both books share, add a sentence, and save. The panel suggests a cause where the books say one, for example a close whose payment runs were not matched back by the AP cut-off, and lets you tick the runs it was waiting on.

Root causes, on both the Payment Runs and the P&L screens, adds the two books together: which causes come up, how many are ours to fix, which clients are late on both, and how often a late pack was down to the payment runs. Late work with no cause yet is on the preparer’s Tasks list.

The Work Planner shows each run on this book where it has got to, in place of the compliance register’s line for the same client and week, the way it shows a management accounts close in place of the P&L. A run counts as done on the planner once it is paid.

Balance Sheets

The balance sheet QC checklists. Called Balance sheet QC until 11 October 2026.

The MA works through the balance sheet reconciliation checklist for each client each month, and the FC approves it or bounces it back.

The checklist is the firm’s v3: 21 accounts in four sections, fixed assets, current assets, current liabilities and non-current liabilities. Every account is answered Done, N/A or To do, and N/A needs the reason, because an FC reading N/A needs to know why. A checklist that is not fully answered cannot be sent. A checklist already started before v3 keeps the items it was started with.

How each account is done

Under each account is its one-line standard. How to do this opens the working guidance for it, and the account lists the procedures in the manual that say how: ACR-04 for run rate accruals, the CDP notes for customer deposits and the VAT on them, CT, DLA, LON, PAY, PEN, STK and TRC for the rest. Pressing one opens it in the procedure manual’s drawer over the checklist, so you do not lose your place. A procedure not yet in the manual is named as not there yet.

Complete

Complete, at the top right of the checklist, marks every account still to do as done in one press and saves it. Accounts already answered, and their notes, stay as they are. It does not send the checklist to the FC, who still reviews it, and the history records that it was completed in one press.

Flags for the FC

Under the accounts is Flags for the FC: one place for the six things the procedures say to flag to the FC. Enter the client’s total assets from the latest month-end balance sheet once, then Raise a flag, choosing the flag, the account it is on, the amount and a note saying what it is.

FlagProcedureWho decides
Reclassification madeFA-03Goes to the FC with the checklist.
Run rate accrual postedACR-04Goes to the FC with the checklist.
Dividend routed through the DLADLA-06Goes with the checklist if you tick that reserves clearly cover it; otherwise the FC decides.
Unresolved variance carriedG-04Below 0.5% of total assets it goes with the checklist; at or above, the FC decides.
Missing payoutSLS-05The same G-04 test.
Wages holdWAG-03Always the FC: wages has no threshold.

The checklist cannot be submitted while a flag has no note, a sized flag has no amount, or total assets are missing. A flag the FC decides is marked FC decides; the FC writes a decision against each one before Approve will go through, and the decision is kept beside the flag and on the history. Change a flag after the FC has decided it and it is asked again.

Bouncing a checklist back

A bounce needs a comment saying what to fix. Tick the accounts to look at again, or a whole section: the MA sees each one marked on the checklist, and the ticks are what the learning loop counts. A bounce that names no account still goes back, but it teaches the loop nothing.

The learning loop

The Learning loop tab shows bounce-back over the last 3, 6 or 12 months: an MA sees their own checklists, an FC the clients they review, a Director everybody.

FigureWhat it means
First time rightOf the checklists approved, the share approved without ever being bounced. The quality measure.
Bounce rateOf the checklists an FC has decided at least once, the share bounced at least once.
Bounces per bounced checklistOne bounce is a correction. More than one is the same conversation again.
Getting better?Each MA’s first time right in the earlier half of the window against the later half, in points.
The accounts that bounceWhich accounts the FCs point at, for how many clients and MAs, with the procedures that say how. Many MAs on one account is a procedure or training gap; one MA is a coaching conversation.
What the FCs saidThe latest bounces, with the comment and what was ticked.

A month with nothing approved shows a dash, never nought. An FC whose bounce rate stays at nought over many decisions is a question for the review, not a clean bill.

Evidence

+ Attach evidence under an account puts a file on it: the statement it was reconciled to, the loan schedule, the tronc report. The same kinds and limits as the management accounts close: 3MB each, six to an account and forty to a checklist. The MA or FC on the checklist can attach until it is approved; only the person who attached a file takes it off, and the record that it was there is kept.

Review points

The queries statutory and the management accountants raise with each other on a set of accounts, a month-end pack or a VAT return: who owes an answer, and what keeps coming back.

Review Points is its own line on the Admin screen. View reads the points you raised and the ones asked of you; View & edit raises them, answers them and settles them. Whoever a point is asked of can always answer it. The QC Director reads every point and the figures per person.

A team lead sees their team’s points too: everybody who reports to them on the org chart, directly or further down, with the points they raised and the points asked of them, under a My team’s figure and filter. A lead holding edit can answer or settle one for somebody who is off. Who is on the team is the org chart on People & Development, so a person missing from it, or placed under the wrong lead, is missing here too.

Every Monday a team lead gets one note on Tasks: how many of their team’s points are open, how many have waited more than five days, how many are answered and waiting to be settled, and who each is with. A lead who cannot open Review Points gets the same counts and nothing more.

Raising one

Press + Raise a review point. Choose what it is about (a statutory or tax job, a month-end pack or a VAT return), type a few letters of the client to narrow the list and pick them, then pick the job, the month or the return. The form says who the books name for it. On most tax jobs the books name no management accountant, so choose who it is for from the list; a point is never sent to nobody, and never to yourself. Then say whether the accounts need changing (a correction, which counts in the quality figures) or you need information (a question, which counts in nobody’s), what it is about, and the query itself. You can also raise one from the tax job, the VAT return or the balance sheet checklist it is about.

Screenshots and files

A point can carry what you are looking at. While raising one, use + Add a screenshot or file, or take a screenshot (Windows key, Shift and S) and paste it into the form with Ctrl+V; it goes on the point the moment the point is raised. On an open point, either side attaches more the same way, so the person answering can show what they changed. Pictures are shown in the point; press one to see it full size. PDFs, spreadsheets, Word documents and saved emails download. Each file is at most 3MB. Only the person who attached a file can take it off, and once a point is settled what is attached to it is fixed.

Answering and settling

Press a row to open the point on the right. The person it was asked of writes the answer there; it goes to whoever raised it, on their Tasks. Only the side that asked settles it, choosing how it was settled: The accounts were changed is the one outcome that counts as a defect. Withdrawing says it should not have been raised and counts in nobody’s figures. While a point is open or answered, the accounts cannot go to the client, the VAT return cannot be filed and the month-end cannot be approved.

The Waiting on me figure is the points whose move is yours: asked of you and not answered, or answered and waiting for you to settle. The Figures tab holds the rates, the categories and, for the QC Director, the figures per person.

Sending accounts for sign-off

  1. When a set of accounts is ready to be checked, press Send for sign-off, on Review Points or at the top of the job’s review points on Stat & Tax.
  2. Choose the job (yours are at the top), then who is to check it. The job’s reviewer, or your line manager on the org chart, is chosen for you.
  3. Add a note if there is anything they should know, and press Send for sign-off. It goes on their Tasks, they are emailed, and the job moves to With reviewer on Stat & Tax.
  4. The reviewer opens it from the Sign-offs tab or Tasks and presses Approve it, or writes what needs changing and presses Send it back.
  5. Sent back, it is on your Tasks. Make the changes, open it and press Send it again.

You cannot approve work you sent yourself. A team lead sees the sign-offs of the people under them on the org chart.

Work planner

How much work falls due on any day or in any week, whose it is, and where each piece has got to — so the team can plan the work before it lands.

It reads every book that carries a deadline: the month-end P&L and balance sheet packs, the VAT returns and payment runs, the statutory and tax jobs, and the service issues. Nothing is typed here; every figure comes from the book that owns it, so fixing a date means fixing it where it lives.

Four views

Demand is a bar per day or per week, stacked by the kind of work, with the part already done drawn pale. Press a bar to list what is in it. By person is the same buckets, one row per person, shaded by how much falls on them. A month-end pack counts for its FC and its MA both, so the rows add up to more than the firm total, and the bottom line counts each item once. Where it has got to is the payroll board’s shape: the same work grouped by stage, from not yet under way to done. The compliance books only record whether a pack went in, so everything outstanding from them sits in the first column. Every item is the list.

Planning on the planned date

Choose Plan on: the planned date to use the tax tracker’s planned completion where somebody has set one. Anything without a plan still lands on its deadline, and a plan that falls after the deadline is marked at risk.

It feeds your Tasks list

Every day of the coming week with something of yours falling due appears on Tasks, counted by kind and naming the clients. You are matched on the name the book uses for you as FC, MA, owner or reviewer.

Enablement

How we manage and implement our own solutions and every other change: rolling Insights out to every client, payment lists on Insights, AutoAP, the move off Lightyear, and any change to how the team works.

Every change is one row on the register, with an owner who answers for it and a sponsor, the senior person who wants it. It is given to people by name on the Admin screen; nobody holds it by default.

Stages and gates

A change moves through Proposed, Scoping, Approved, Pilot, Rolling out and Embedded. Three of those moves are gates, and a gate is where somebody other than the owner says yes:

  • Approve gate, from Scoping: the problem, how success is measured, the business case, the scope, the risks, client data, who builds and runs it, and whether it changes the fee.
  • Go live gate, from Pilot (or straight from Approved if there is nothing to pilot): the pilot reviewed, the procedure published on SOPs, the team trained, the client message, the support route, a rollback plan, the rollout order and the access checked.
  • Close gate, from Rolling out: the benefits measured, the old way switched off and its licences cancelled, a named owner for running it, and the lessons written down. A change that reaches clients cannot close until every client on its rollout is live or marked not applicable.

Answer each item on the checklist as done, not applicable or to do. Not applicable needs a sentence saying why. When every item is answered, press Ask for the gate. One of the named approvers decides it; nobody approves their own change or their own request, and a decline says why. While a gate is with an approver its answers are fixed.

The rollout

On a change that reaches clients, add clients one at a time or press Add every live client, which adds each group on the Client Register once. Move each client through Not started, Scheduled, In progress and Live. Blocked and not applicable each need a note. The bar on the register is live clients over the clients in scope.

Status updates

The owner posts an update, on track, at risk or off track, with what has happened and what is next, at least every two weeks while the change is being worked. When one is due it is on the owner’s Tasks, as is a change past its target date or a client blocked on a rollout. Approvers see every gate waiting on them on theirs.

How we govern change on the area sets all of this out, drawn from the same rules the server checks.

AML & MLRO

How to report a concern about money laundering to the MLRO, and how the firm keeps its own anti-money-laundering records: client risk, training and the firm’s controls.

Reporting a concern

Everybody has AML & MLRO in the sidebar, whatever else they hold. If you know or suspect, or have reasonable grounds to suspect, that somebody is laundering money or financing terrorism, press Report a concern to the MLRO and say what you saw and why it worried you. You do not need to be sure and you do not need to investigate. Telling the MLRO is how you meet your own legal duty under the Proceeds of Crime Act.

If work for the client is waiting on it, such as a filing or a payment, tick the box and hold that work until the MLRO tells you what to do. The instruction appears on the report and on your Tasks: hold, carry on, or stop acting.

Do not tell the client, or anybody outside the firm, that you have made a report. That can be the offence of tipping off. If the client asks why something is taking longer, speak to the MLRO first.

Only the MLRO reads what you send. You see your own words, that it was received, and what you are told to do. The MLRO’s decision, and anything sent to the National Crime Agency, stays with the MLRO. A report is never edited once it is sent; to add something, raise another or speak to the MLRO.

The MLRO’s register

The MLRO sees every report on the MLRO register tab. Each one is acknowledged, then decided with the reasoning written down: no SAR, a SAR, or a SAR with a request for a defence (a DAML) where the firm is about to do something that needs one. For a DAML the screen counts the NCA’s notice period, seven working days after the day it was submitted, and the 31-day moratorium if the NCA refuses. While a defence is owed the person who raised it can only be told to hold. Every step is kept in the report’s history, which only the MLRO reads.

Tom Stanley is the MLRO, Georgia Simpson the deputy, and James Couch the deputy who decides a report where the MLRO is conflicted or the report concerns him. Any of them reads your report.

The watch list

The MLRO and the deputy keep a Watch list of potential issues that are not, or not yet, a report. Each item is reviewed every week, and the review records what was looked at and whether to keep watching, raise it as a report on the register, or close it. A review falling due is on their Tasks. On a service issue, the MLRO sees Add to the MLRO watch list; nobody else sees that the issue is being watched.

Client risk, training and controls

These three tabs are given to people by name on the Admin screen; nobody holds them by default.

  • Client risk: every live client, with the risk assessment in force. An assessment is never edited: a new one replaces it and the old one stays. A politically exposed person, a high-risk third country or an uncleared sanctions match makes the client high risk, with the enhanced due diligence written down. Reviews follow the rating: high every year, medium every two, low every three. A new client’s onboarding cannot be signed off until they have an assessment here.
  • Proposed ratings: every client nobody has assessed yet, with a rating WSOP proposes from what it holds: a company person with significant control, no PSC or one living abroad, no company number or one Companies House cannot find, a company under two years old, late filings at Companies House, and no identity evidence on the client’s form. A group is rated through the companies inside it, at the highest of them; a company marked overseas on the register counts two points, because Companies House holds nothing on who owns it; one marked as not a company is not asked for a number. Each reason carries points; two or more is medium, four or more is high. Anything WSOP could not check is listed as a gap. The MLRO approves low and medium ratings in batches, and each high rating one at a time from the client’s own record. Approved reviews are spread across the year by client group, so a whole book does not fall due on one day.
  • Training: everybody’s last AML training and when the next is due, once a year. You can record your own from the Your training tab.
  • Firm controls: the firm-wide risk assessment, the policies, the MLRO’s annual report, the independent review and the supervisor’s return, each with the date it was last reviewed and a link to where the document is kept.

Overdue reviews and controls are on the Tasks of whoever keeps the register, and your own training is on yours when it is due.

The same rating shows on the Client Register, in its own column and on each client’s record, for whoever keeps the AML register. Assess this client there opens the same assessment without leaving the register.

The documents for the AIA

The Documents tab holds the firm’s PCP (the policies, controls and procedures), the firm-wide risk assessment and the AIA submission pack, each as a series of versions. The Word files the firm had written are the first version of each.

  • The draft is where the next version is written. Figures WSOP holds fill themselves in: the client risk counts, training completion, the independent audit position, where staff report a concern, and the review log. They are written as a field in braces, such as {{clients.summary}}, and the list of fields is under the draft. Anything WSOP does not hold stays as [TO BE COMPLETED BY WS] for a person to write in.
  • Publishing fixes the text and that day’s figures as the next version number, with who approved it, when, what prompted it and what changed. A published version never changes, so it downloads the same for as long as the firm keeps it. Publishing the PCP or the risk assessment also records the review on Firm controls. The risk assessment counts the reports to the MLRO, so the MLRO publishes it.
  • Download as Word works on any version and on the draft. The version in force downloads under the name the AIA return asks for, such as WS_408958_AML_CTF_CPF_PCP.docx; an older one carries its number and says what superseded it; the draft says DRAFT on every page. Word builds the contents and page numbers when it opens the file.

The AIA’s thematic review of policies and procedures is on the same tab: Open the answers lists every question on the AIA’s form in its order, with the answer to give, the section of the PCP it rests on, and anything to put right first. An answer is only Yes where the section is there in the PCP in force. The form takes the date as month, day, year, and the PCP is best uploaded as a PDF so its page numbers cannot move.

If the PCP names a different MLRO or deputy from the people WSOP sends reports to, the draft says so at the top. One of the two is wrong and has to be put right before the document goes to the AIA.

Training

What training each of us owes and when, a log of everything we do with its hours, and our CPD for the last twelve months.

Everybody has Training in the sidebar, under People. My training lists the courses you owe: those the firm asks of everybody, and any given to you with a due date. Each says whether it is done, due soon, overdue, or, for a course done again every year or so, expired. Press Record it done when you have done one.

Press Record training for anything else you do: a webinar, a technical update, a course outside the catalogue. Give the date, the hours, who ran it and a link to the certificate or your notes, and tick Verifiable where there is evidence it was done. That log is your CPD record. A record is never edited once saved; if one is wrong, strike it out and say why, and it stays on the log struck through.

Money laundering and data protection training are still recorded on AML & MLRO and GDPR & Data Protection, which are the record a supervisor reads; your Training page shows them alongside.

If people report to you on the org chart, My team shows where each of them stands. Whoever is given the Training line on the Admin screen sees Everybody; with edit they keep the Courses catalogue, give courses out with a due date (or set one date for everybody who has not done a course yet), record training for anybody and set the firm’s CPD target. Overdue and expiring training appears on your Tasks.

GDPR & Data Protection

How to report a personal data breach and log a request somebody makes about their data, and how the firm keeps its own data protection records: requests, processors, training and the firm’s controls.

Reporting a data breach

Everybody has GDPR & Data Protection in the sidebar, whatever else they hold. Personal data sent to the wrong person, a lost laptop or phone, a client’s payroll file open to the wrong people, a phishing email that got into an account: press Report a data breach as soon as you know, even if you are not sure it counts. Say what happened, whose data it was (the firm’s own, or a client’s that we hold to do their payroll, books or tax), what kind of data, roughly how many people, and when you found out. The firm has 72 hours from finding out to tell the ICO where it has to, and where the data is a client’s the client has to hear from us sooner still.

Only the data protection lead reads what you send. You see that it was received, and anything the lead asks you to do, such as asking for an email back. You do not see the lead’s assessment or who was told. Do not contact the people affected or the ICO yourself.

Logging a data request

Anybody asking for a copy of their data, for it to be corrected or deleted, or to stop it being used, in any words and to anybody at the firm, is a data subject request, and the one calendar month to answer runs from the day it reached the firm. Press Log a data request the same day, say what they asked and how it came in, and do not answer it yourself. You see the request’s reference, when it is due and when it is closed.

The data protection lead and the register

  • Breach register, for the data protection lead only: every breach with its 72-hour clock, the risk, the decision (recorded only, reported to the ICO, or the client told as controller) and the reasons, and whether the people themselves were told where the risk was high.
  • Data requests: every request, who has it, whether proof of identity was asked for (the clock waits for it), the due date, an extension of two more months with the reason, and how it ended.
  • Processors: everybody who handles personal data for the firm, with the contract, where the data goes, and a review each year.
  • Training and Firm controls: as on the AML tab, for data protection: the record of processing, the privacy notices, the ICO fee, the policy, the retention schedule and the rest.

The register is its own access line on the Admin screen, off for everybody until it is given by name. Who the data protection lead is is set in the code.

People and access

Admins can add colleagues and manage accounts.

If you run accounts you will see Admin in the account menu, under your name at the top right. A number on your name means someone is waiting for a password reset.

Access is held per area, so the presets are only a starting point: pick one, then change any line that needs it. Somebody who should read the plan but work the escalations, or see compliance and nothing else, is a couple of dropdowns rather than a new kind of account.

Everything is granted on the Admin screen, and administrators hold nothing by standard. Being a system administrator runs accounts and the system; it does not let anybody change anything inside an area. An administrator who edits the plan, links client names or approves a QC checklist is given that on their own Access panel, the same as anybody else, and every change there is in the account log. The panel also sets the QC role on the Balance Sheets line, the three People & Development tabs, and Weekly Reporting membership, department and reporting admin.

PresetWho it is for
Management accountantMonth-end compliance and the balance sheet checklists for their own clients, as the MA.
Financial controllerCompliance for their own clients, and reviews and approves the MAs’ balance sheet checklists, as the FC.
Tax teamThe statutory and tax tracker: accounts, returns, deadlines and what each is waiting on.
Client serviceThe service issues register: raising, updating and closing escalations.
Improvement teamThe improvement plan and the service issues, for the people running the programme.
Business developmentQuotes and their fees, for whoever prices and sends proposals.
BillingThe billing list, clients on stop, credit notes and the billing conversations, with the service issues and the client register to read.
Marketing & partnershipsThe Marketing screen (campaigns, the weekly product emails, Customers, website traffic and event guests), with the client records to read. A system administrator chooses it, because it switches on a page.
Weekly reporterWrites a weekly report and nothing else.
Compliance onlyThe compliance book on its own, with no balance sheet QC.
Read-onlyReads the plan, the issues, compliance, the procedures and Review Points, and changes nothing.
AdministratorRuns accounts and the system, and reads the plan, the issues, compliance, the client records, the procedures and Review Points. Changes nothing inside an area until given it by name.
CustomAnything the presets do not cover: each area is set on its own to no access, view, or view and edit.
ActionWhat happens
Add someoneCreates the account and emails them a one-time password, which the screen also shows once. They set their own on first sign-in.
Reset passwordAsks first, then issues a new one-time password, emails it to them and signs them out everywhere. Clears any outstanding request from that person, and restarts the 14-day clock.
DisableAsks first, then blocks sign-in and ends their sessions. Their name stays on the history of what they changed. For a leaver, run the handover on their Access panel first so their work moves to somebody.

The last active admin cannot be disabled or demoted — promote someone else first.

The Admin tabs

People is everybody with an account, with figures that filter it, a search, and the Access panel for each person. Add someone makes an account. Screens lists every page in the sidebar, what opens it, and who can. Access review and Controls are below. Health check names what needs a person (unused accounts, expired passwords, powers held without the access they need) and lists who holds the keys. Usage shows how often people sign in and use WSOP. Account log is every sign-in and access change. Claude connections lists who has connected Claude to WSOP and lets you end a connection.

Password requests

When someone uses Forgotten your password? on the sign-in box, an amber panel appears at the top of People naming them, with whatever note they left. Reset password there does the same as the button on their row and shows the one-time code to pass on; Dismiss clears the request without changing anything, for when they got back in another way.

A request from an address with an account is answered by email with a fresh one-time password; the panel is where a request lands when no email could be sent, or when the address has no account.

Accounts nobody has signed into yet

A new account carries a tag saying how long its one-time password has been waiting and how many days are left — amber under three days, red once it has expired. An expired code cannot be used; Reset password issues a fresh one. This is why nothing is lost by adding people ahead of time: the account stays, only the code goes stale.

Service issues

Escalations from the shared mailbox and Teams, alongside the plan.

The Service Issues tab shows the live escalation register. It is fed by the service-issues pipeline, which sweeps the mailbox and Teams on a schedule and applies its own triage and closure rules — the issue text itself is written there. Everything else about an issue is set here, in its drawer, by anybody with Service Issues edit.

Linking the client

The mailbox cannot tell who an issue is about, so the client is set by a person. Open the issue and use the Client section at the top: choose from the list (the clients the board already files things under, and the client register if your account reads Client records), then Link client. The client has to be one on the list, so a client is one name in every count: one that is not goes on the Client Register first. The section says who linked it and when. Where the board can tell who it is about it offers the name with Assign it; check it before you press. The client, risk, theme and root cause all reach the Root Cause Tracker.

Asking somebody, with @

Every issue has a Conversation under its history. Write a note for the team there; type @ and a person's full name, or pick them from Mention somebody, and the issue goes on their Tasks list until they reply on it or press Mark done. A first name alone mentions nobody, because two people here share several. Anybody who can read the board can write there. The conversation is kept in WSOP and is not added to the issue's history or the weekly pack.

Filters, and the figures at the top

Each figure at the top is a filter: press High risk open to see exactly those, press it again to go back. The bar filters by risk, status, owner, client, theme, type, source, what is missing (no client, no root cause, risk not set and so on), when it was raised, and Only mine. What is on is listed above the cards, each with a cross to take it off, and the board remembers your filters in this browser. Deadline, soonest first is one of the orders.

Root causes

The Root causes tab groups the issues by theme, root cause, client, type or owner over a period, biggest first: how many, how many still open and high risk, the last 30 days against the 30 before, a bar per month, how many clients it reaches and how long it takes to close. Open a group to see its issues, show exactly them on the board, ask for Suggest improvements (written by a model from those issues and saved nowhere), and Raise a CIP task with the issues and the suggestions in its notes. The table is only as good as what is recorded, so it says how many issues have nothing recorded and shows them on the board to be filled in.

Reassigning the owner

The Owner section offers the register's people. The owner decides who may close an issue, so it can be reassigned by the owner handing it on, by the two people who may close anything, or by an administrator; everybody else is told who can. The change is written on the issue's history and in the change log. A later email about the issue does not change the owner back.

Area owners

Area owners, beside the change log, says who owns each area's escalations: Payroll, Tax, Company secretarial, FC / MA, and Systemic / control failure. The pipeline decides an item's area when it raises it, from the item's type and, where the type says nothing, the words it was raised with, and gives it to that area's role head. Set somebody as an area's owner (for example Michelle Hollingworth for Payroll) and the area's new items move to them on the weekday run, written on each item's history as a reassignment. Items already open move when you press Move. Nothing moves that somebody reassigned by hand, or that the pipeline gave to anybody but the area's head. The owner is chosen from the firm's accounts that can read the board, and is put on the register's people if they are not on it already, so they can own and close items. Setting one is for the two people who may close anything, or an administrator; everybody can see who owns which area, and each issue says whose area it is.

When somebody leaves, the handover on the Admin screen moves their escalations with the rest of their work: each open issue they own alone is reassigned to whoever takes over, an area they own (or head for the pipeline, as Tammy heads Payroll) gets the new person as its owner, and they come off the board's list of owners when the account closes. An issue they own with somebody else is listed for you to reassign by hand.

A note typed in the conversation is sent with Send, Ctrl+Enter, or Save changes, which sends it with any fields that moved.

Where it stands, and pausing an item

The Where it stands section in the drawer says what is happening with an open item, so it is not chased while somebody is dealing with it. Anybody with Service Issues edit can set it; it goes on the item's history with their name.

  • Being worked (In progress): we are on it. It is only chased, on the Monday and Thursday escalations email, if nothing has been recorded on it for 14 days. Any update counts, an email included.
  • Paused: waiting on somebody outside the firm (Blocked): the next step is not ours, for example HMRC, the client or the bank.

To pause an item:

  1. Open the item on the Service Issues board.
  2. Under Where it stands, choose Paused: waiting on somebody outside the firm.
  3. Say who it is waiting on, and the date it is Paused until: when you expect to hear, or want to check again. Add a line on where it is if useful.
  4. Press Save where it stands.

Until that date it is not chased on the Monday and Thursday email (it is listed separately as paused), it does not show as due or overdue on the board or on anybody's Tasks, and in the weekly pack it sits under its own Paused heading in grey rather than in red with the outstanding items. If nothing is recorded by the date, it comes back and is chased as normal, so nothing is lost. A pause can be up to three months; if it is still waiting then, pause it again with an update. An item set to waiting before pausing had a date is not paused until it is given one.

The history, and emails

Each email and each change made here is its own entry, marked by email or on the board. The earlier emails a reply quotes are folded under it; open the fold to read them. In short, above, is two lines written from the whole item every two hours on weekdays. When a new email arrives it is written again at the next run, and until then it says it was written before the latest update.

Closing

In the drawer: say how it was resolved (paste the closing email if it says so) and what caused it, then Close it. The owner, and the two people who may close anything, close; anybody else pressing it moves the issue to Pending closure for the owner. By email: reply in the issue's thread, or quote its ISS number, with a phrase such as "please close", "can be closed", "ok to close" or "resolved, close". A bare "close" or "closed" is read as narrative, not a request, so it will not close anything. The email's text becomes the resolution, on the issue and on the Root Cause Tracker. An email closure does not set the root cause, so set that in the drawer.

Held on a strand. An issue whose history mentions work beyond it (a "wider piece", "to be picked up by", "separate case") with no other issue number beside it does not close, so that work is not lost inside a closed issue. The drawer lists each piece under Work held on this issue. The owner, or anybody who may reassign it, says where each one lives: another issue number, a plan task number, or what happened to it with a note. Once every piece has a home it closes. The two people who may close anything, or an administrator, can also close over it with a reason, which goes on the history.

Unlike the plan, it needs a sign-in: issues name clients and carry risk ratings.

Turning an issue into a CIP task

Issues the triage rules flag as candidate improvement work are marked Potential. The amber CIP pill on the tab is how many of those are still open — not an unread count or a fault. Click it and you go straight to them; the same list is behind Only issues flagged as potential CIP.

The change log

Change log shows everything typed against an issue here, newest first, and every time two people or clients were merged into one record — both are changes to the same data. What the pipeline writes on its own sweep is not an edit made here and does not appear, so a change you expected and cannot find was almost certainly made in that system rather than this one.

Open one and use Raise a CIP task from this. The task is created pre-filled — the issue text as the name, its owner, priority from the risk rating, and the root cause in the notes — and the two are linked. The issue then reads In plan and links straight to the task.

Why the link lives on this side

The connection is recorded against the CIP task, never written back to the issues database. Two systems, one direction of travel: a change over there can never corrupt the plan here.

Tools & Partners

Every system the team signs in to, one square each, under My work › Tools & Partners.

Each square opens the tool’s own sign-in in a new tab. There is no single sign-on, so each asks for its own password. Pin the ones you use most with the star and they sit at the top in the order you choose; drag them or use the arrows to reorder. With nothing pinned, the top row is the tools you open most. Your arrangement is kept in that browser only.

A tool that is missing

  1. Press Suggest a missing tool above the squares.
  2. Give its name, the address of its sign-in page (copied from the browser bar on that page, not the company’s home page) and what it is for and who uses it.
  3. It goes to the approver’s Tasks. If the tool is already on the page you are told so straight away; if yours is something different, say how and send it again.
  4. The approver asks William to draft the square (its label, heading, initials and colour), checks the address opens the sign-in page, changes anything that is wrong and approves it. It is then on everybody’s Tools page.
  5. You see the decision on your Tasks. A decline always comes with the reason. Your requests shows every tool you have asked for and where each one stands.

A tool added this way shows its initials rather than its logo. Only the approver can add a tool or take one off the page again; being an administrator does not do it.

A link that is wrong

A system administrator or the approver sees a pencil on each square. It opens the name, the label under it and the sign-in address; saving changes the square for everybody straight away. Every change is kept with who made it, and a corrected square can be put back to its standard link. If you find a wrong link and cannot correct it, suggest it as a missing tool and say which square is wrong.

The partner directory

The Partner directory tab lists the firms we work with and recommend to clients: payroll and people, payments and spend, accounting systems, EPOS and technology, stock and procurement, property and funding. Each card says what the partner does and opens their site, or our referral link where we have one. When a client needs one of these services, send them through this link. Where we have a named contact at the partner, the card shows them with their email underneath: press the email to write to them.

Suggesting a partner

  1. Press Suggest a partner above the cards.
  2. Give their name, their website or our referral link, what they do, and why we should point clients to them.
  3. It goes to the Tasks of the system administrators and the approver. If they are already in the directory you are told straight away.
  4. You see the decision on your Tasks; a decline always comes with the reason. Your suggestions shows where each one stands.

Changing the directory

A system administrator or the approver sees a pencil on every card and an Add a partner button. The pencil changes the name, the label, what they do, the heading, the link, which is where a referral link goes, and the contact at the partner. A card can be taken off the directory and put back, and every change is kept with who made it.

E-signatures

Send a document to be signed, under My work › E-signatures. It replaces Adobe Sign and Yoti Sign. You see the documents you send, and any filed on a client or piece of work you can open.

  1. Put the PDF in. Choose a PDF, or drop it on the box. A Word document (.docx) is made into a PDF first, in your browser. Up to 50MB; a large one goes up in pieces, and the screen says how far it has got.
  2. Check the places to sign. WSOP finds them itself: signature lines, dates, printed names and initials, the PDF’s own signature boxes, and tags such as {{signature:1}} or Adobe Sign’s own. Each box is coloured for the person who fills it. Drag a box to move it; click one to change who it is for or take it away; choose a kind under Add a field for and click on the page to add one.
  3. Name who signs. Under Who signs, add each person’s name and email in the order they sign, then press Find them again so each box goes to the right person. Untick Sign in this order to send to everybody at once.
  4. Send. Press Send for signature. Each person gets their own link, opens it with a code sent to their email, adopts a signature by typing or drawing it, fills their boxes and ticks to agree.

When everybody has signed, the signed copy, with a certificate of who signed, when, from where and how they were checked, is emailed to everybody on it and anybody you copied in, and you can download it from the document. While it is out you can send a reminder to whoever’s turn it is (WSOP also reminds them every three days, three times), or withdraw it with a reason. A decline comes back to you by email and on your Tasks. A sent document is never deleted: it is the record of who signed what.

Several documents signed in one go

Drop several PDFs at once and WSOP asks whether they go together, signed in one go, or as a separate draft each. Together, they are one draft: one set of signers, one link and one code for each person, and every document signed in one sitting, in the order you added them. You can also press + Add another document under Documents in a draft; what you have typed and placed is kept, and WSOP looks for the places to sign on the new pages only. Take one out with the cross beside it, or move it up or down with the arrows. The signer sees a list of the documents at the top with how far they have got in each, ticks that they have read each one they sign, and may decline one with a reason and sign the rest; you are told which at once. If somebody declines the whole of it, you are told why, and everybody else who was sent it or copied in is told it is no longer going ahead. A template saved from several documents keeps them separate. Together they must stay under 50MB and 200 pages. A signed copy over 25MB is too large to email, so each signer and each person copied in is sent a link to download it, and you have it on WSOP.

The signers see each document under its own name, and the email lists them. The certificate names each document, its pages and its fingerprint. Once everybody has signed, the signed copy holds them all, and each document also downloads on its own, with the certificate after it, from the document’s page.

More than a signature

Beside signatures, dates, names and text, a box can be a tick box (a statement they tick, required unless you say not), a choice from a list you type, one a line, or an attachment, a PDF, PNG or JPEG up to 3MB they put in, such as a passport or a bank letter. An attached file travels inside the signed PDF and is named, with its fingerprint, on the certificate.

File it on the client

Under Filed on, type a client’s name and choose them. The document then shows on their record on the Client Register (Relationship tab, Documents for signature), with the signed copy to download. Better still, start from the work: on a client’s record, a proposal or an onboarding or offboarding case, press Send a document for signature. E-signatures opens already filed there, with the client’s contact put in as the signer to check.

Send to many

Beside a template, Send to many sends one document per person. Paste one line each: the name and email of each person the template does not keep, separated by commas or straight from a spreadsheet, and, to file it on a client, a bar and the client’s name as the register has it, for example Jane Smith, jane@client.co.uk | Big Mamma. Press Check them to see every line before anything goes, then Send them. They go ten at a time; if the connection drops, press Send them again and it carries on without sending anybody twice. The batch is listed under Batches you sent.

A code by text

Where texting is set up, each signer has a box for a mobile number. Give one and they can choose to have their code texted rather than emailed. The certificate says which.

Every document

Team leads can be given Every document, a second tab listing every document out across the firm: who sent it, who it waits on and for how long. It is read only; a reminder sent from it goes from you, under your name. It is switched on person by person on the Admin screen’s Pages panel.

Editing a PDF

Change a PDF without another program, under My work › E-signatures › Edit a PDF, the second tab beside Send for signature. Everything happens in your browser: the file is never sent to WSOP or kept anywhere, so it is safe for a client’s ID or payslips.

  1. Drop one or more PDFs, a Word document (.docx), or a PNG or JPEG photo of a document, onto the page, or press Choose files. Several files are joined in the order you add them, a picture becomes a page, and a Word document is made into a PDF as it is added, then Download PDF saves it. It is set as Word sets it, in Word’s own fonts or ones drawn to the same measurements, so lines and pages fall where Word puts them. If anything could not be carried across, such as a chart, it says so under the files.
  2. Click a page to choose it, or type numbers such as 1-3, 5 and press Choose these. Then turn, move, duplicate or delete the chosen pages from the bar. Drag a page to put it somewhere else. Add a blank page puts one after the last chosen.
  3. Press Edit on a page to add to it. Add text: type it, then click where it goes. White-out: drag across what to cover. Signature or picture: choose a PNG or JPEG, then drag where it goes. Each one is listed under the page with a Remove button.
  4. A PDF with a form shows Fill in the form. What you type is written onto the page in the copy you download.
  5. Name the file, tick Number the pages if you want page numbers, and press Download PDF. Download the chosen pages makes a file of only those pages, which is how a PDF is split.

White-out covers words; it does not remove them, and they can still be copied out of the file. Do not use it to hide anything confidential. A PDF locked with a password has to be unlocked before it can be added.

Events

The firm’s own days, such as the Friday Fun League, under People › Events. You take part with your own WSOP account.

Open an event to see how the day works, the prizes and how entries are judged. On the day:

  • Enter. When entries open, upload one photo and add a line for each category on the Enter tab. You can change your entry, or withdraw it, until entries close. Entries open and close by themselves at the times the event gives.
  • Judging. If you are on the judging panel, the Judging tab shows your scorecard. Score each criterion from 1 to 5; scores save as you go. You never score your own entry, and only the host sees the totals.
  • Winners. The host reveals the winners on the call, and they appear on everybody’s screen at once.
  • Escape room. When the host starts it, pick your team on the Escape room tab and type each answer there. The right answer opens the lock for your whole team. Each hint adds a minute to your time.

The host runs the day from the Host desk at the top of the event: moving the day on, adding an entry for somebody who sent their photo in Teams, the all-day check, taking somebody out of the running, revealing the winners and starting the escape room. A link to an event, such as #events/fright-night-friday, opens it after you sign in.

Marketing

Screenshots of our own products for proposals, decks, the website and posts, and the weekly product emails, under Marketing › Product marketing.

There is a tab for each product: WS Insights, TeamPay, Signal and AutoAP. Each is grouped by that product’s own sections; WS Insights shows the new Forecasting and Board Pack first. Narrow them with Section or by typing in Search, which reads the captions. Click a picture to see it large; the arrows, or the arrow keys, move to the next one, and Download saves the full-size file under a name that says which product it is.

Every figure in them is dummy data from an invented hospitality group, named on each tab, so they are safe to use outside the firm. The page is switched on person by person on the Admin screen’s Pages panel.

Weekly emails

Every Tuesday morning WSOP reads what was merged into each product’s code in the week before and drafts three emails for each of WS Insights, TeamPay, Signal and AutoAP: one for customers (what is new, a tip or two, then everything it does), one for new customers (what it can do, and an invitation to a demo) and one for our team (what shipped, with every change listed). Nothing is sent by itself.

  1. Open Weekly emails at the top of the page. A line on Tasks says when there are drafts to read.
  2. Pick the product, then the email. The editor is on the left and the email exactly as it will arrive on the right; the preview follows your typing. Change the words, the labels, the order of the cards and the picture on each, then Save.
  3. Email me a test, beside the preview, puts what is on screen in your own inbox, changes not saved yet included, and saves nothing. When it is right, press Approve. Changing anything after that takes the approval away.
  4. Add the people it goes to underneath, one a line as Ellen Smith <ellen@business.co.uk> so it greets them by name. The team email takes firm addresses only; Add every colleague fills it.
  5. Send sends it one person at a time, a couple a second. A long list may need a second press to finish; nobody is sent it twice. It goes from hello@ with your address to reply to.

Customer and prospect emails carry an unsubscribe link; anybody who uses it is struck through on the list and never sent to again. Draft this week now writes this week’s if Tuesday’s run has not, and Draft this product again writes one product again, leaving anything approved or sent alone.

Event guests

Everybody who RSVPs to one of our events on the website, such as the WS Hospitality Summit, appears here as they RSVP. The website has already emailed them their confirmation and added them to HubSpot.

  1. Open Event guests at the top of the page and pick the event.
  2. The figures at the top say how many are coming, cancelled and attended, and how many have dietary requirements. Press a figure to show only those guests.
  3. When a guest says they cannot come, set their Status to Cancelled. On the day, set each guest who arrives to Attended. Your name and the time are kept beside the change.
  4. Download CSV saves the guests shown, with their dietary requirements, for the door list and the venue.

Somebody who RSVPs twice is one guest, with their latest details; a guest marked Cancelled who RSVPs again is put back to Confirmed.

Lead generation

Prospects from four channels, scored and checked, and the outreach emails James approves before anything is sent, under Marketing › Lead generation.

Where they come from. New openings (the openings pipeline, every morning), Companies House (each company matched and checked daily for overdue filings, new charges, new officers and new companies in the group), finance hires and vacancies (a CSV from Sales Navigator or anywhere, and a daily web check of the best prospects) and competitor clients (each competitor’s own case studies and logos, monthly). Each company is one record; every reason to approach is a trigger with its date, source and link, kept rather than overwritten, and marked needs checking until somebody confirms it.

The checks. A company is matched first on its Companies House number, then its website, then its name; a near match is a Duplicate? for you to merge or keep apart. A client of ours or a company with an open HubSpot deal never becomes a lead: its owner gets a task instead. Do not contact and every unsubscribe apply on every channel.

Fit and timing. Fit is how well the company suits us; timing is whether there is a reason to approach now. Anything not known is shown as not known, never counted as a no. Priority is a strong fit with a timely reason, Standard is worth approaching but not urgent, Excluded is outside our criteria or cannot be contacted. The criteria, weights and thresholds are on Settings, and saving them rescores everything.

From prospect to email. A Priority company with no decision-maker gives its owner a task to find one. Once a founder, MD or finance contact is added with where they came from, WSOP drafts the three emails from the Content library and puts Approve sequence on James’s Tasks. On Sequences he reads the evidence and all three emails, edits them, can send himself a test, and approves. They then go from his own mailbox, Monday to Friday between 08:30 and 16:30, four then five working days apart, plain text, each with a line to unsubscribe. A reply stops it and gives a follow-up task (a positive one says book a discovery call); a bounce or an unsubscribe stops it too, and every email is checked again just before it goes. The LinkedIn note is in the task to send yourself.

What is never said. No competitor’s name, no fee figure, never “matter”, and only approved opening lines, proof points and resources. Companies House signals, finance departures and competitor links are for research: they are never mentioned in an email. Sole traders, partnerships and personal email addresses are never emailed. A request to see, correct or delete someone’s details is handled on Settings › Data protection.

The Dashboard shows leads per week by source and trigger, conversion by stage, days in each stage, win rate and fees by source, how the sequences did, and when each channel last ran. James gets a digest every Monday. The page is switched on person by person on the Admin screen’s Pages panel; a link such as #leadgen/12 opens one company.

Clients joining and leaving

A client joins once and appears on every book; a client leaves once and comes off every book.

  1. When a proposal is marked won, or the client signs it, an onboarding case opens on Clients › Onboarding & Offboarding, owned by the proposal’s owner, with a target 30 days out. A client already onboarded is not onboarded again.
  2. State the services on the Client Register and send the client their form. The form asks for their year end, VAT frequency and current VAT period end, which are what date the first returns.
  3. The form is the client fact find, in place of the Word document. Before you send it, say where the client is (United Kingdom or United Arab Emirates) and tick the services in scope: bookkeeping and VAT, management accounts, accounts payable, payroll, annual accounts and corporate tax, company secretarial, and taking over from a previous accountant. The form then asks only those questions, in that country’s words. The ticks start from the proposal they accepted and the departments scoped on the onboarding. Everything the client gives is kept on the case, and the department trackers read it, so nobody types it twice. It never asks for a password, a login or a bank account number: systems questions ask to add us as a user, and supplier and employee lists come without bank details. You can change the country or the services after it has gone, under the form on the case; nothing the client has already given is lost.
  4. The case shows What signing off does to the books before you sign off: which books the client goes onto, from which period, and anything that cannot be done yet and why.
  5. Signing off puts the client on management accounts, the VAT book and the tax book for the services stated, and Billing lists them to start billing. Each book takes your own edit on that book; one you cannot write is named in the case history.
  6. Anything not done, for example a VAT quarter end nobody gave, is added and then Set the books up again is pressed on the case. Nothing is made twice.

Where the fact find stands (not sent, link made, emailed, opened or back) is shown on each onboarding in the list, on the onboarding’s Overview and Intake tabs, and on the client in the Client Register. A company covered by a group’s fact find shows the group’s form, sent from the lead company’s case. An onboarding open five days with nothing emailed is on its owner’s Tasks. Open the fact find goes straight to the form on the case.

Signing off an offboarding ends the client’s management accounts and VAT cycles, marks their live tax work client left, sets every service on the Client Register to We do not with the offboarding as the reason, and Billing lists them to stop billing. The checklist's "Services cleared on the Client Register" step is answered by WSOP for that reason and cannot be pressed. Nothing is deleted: what was filed stays filed.

On an offboarding, tick Services they had with us and the checklist asks only those departments’ steps, so a payroll-only client is not asked about CoSec, tax or bookkeeping. With nothing ticked it goes by what Xero invoiced them for in the last year, and with no invoices it asks everything. A step left to do with a note is never hidden, and the checklist only ever shows the answers people give.

Letters

An onboarding sends the engagement letter and the professional clearance request to the previous accountant. An offboarding sends the disengagement letter and the professional clearance reply to the incoming accountant.

Draw the letter writes it from the case, the client’s form, the accepted proposal and Companies House (the registered name, number and registered office): the services and fees are the proposal’s own figures, and the previous or incoming accountant is the one the client named. There is no engagement letter until a proposal is marked won.

Tailor with the model rewrites it for the client from the same facts, and may not add a fee, a date or a term. Check against the case reads the letter as it stands and lists anything wrong, unsupported or missing. Any fee the accepted proposal does not carry stops the send whatever the model says, so does any {{write here: ...}} left in the text, and so does a clearance letter without the client’s authority.

Two things are always left for a person to write: which open work we will finish when a client leaves, and whether there is a professional reason the incoming accountant should not act. Both are the firm’s statement, and no template answers them.

Send with PDF works only on a letter checked exactly as it stands. It goes under your name, copied to you, with the letter attached as a PDF, and the case history records it. Sending does not tick the step; that is still yours.

Onboarding by department

Offboarding a whole group. Press Start an offboarding (or Client has given notice) and choose any company in the group. Under The whole group every company in the group on the Client Register is ticked; untick any that is staying. Below that, What belongs to the group lists every company WSOP files under it (from the compliance book, the VAT register, P&L, Xero, HubSpot and Companies House), so nothing is missed. Press Start it: the group is one row, and the checklist, notice, details and sign-off on it are done for every company. A company already being offboarded on its own keeps its own case, and joins a group’s case only when its answers and notes are the same, so nothing written on it is ever replaced. In the case, Take out makes a company its own offboarding again, and Bring into this offboarding adds one of the group’s other companies.

An onboarding case is worked department by department. Each department’s tab ends with Client notes, for anything to come back to or that the next person should know. Each note shows who added it and when, and is never changed afterwards. An offboarding has Comments after its checklist, before sign-off, for each person to record what they did on their part; they work the same way, so the case keeps its own audit trail. Anyone who can open the case can add notes and comments, even without edit access to the rest of it. Open the case: its tabs sit above the checklist, which stays as the shared set-up every department relies on (engagement letter, AML, clearance, agent authority).

The checklist answers what WSOP already knows, and says where from: a department’s tracker task completed, the HubSpot deal won (engagement), a risk assessment on the AML register, invoices raised in Xero (billing), a P&L pack the compliance book records as sent (first management pack), and the FC and MA named on the Client Register. A step only some departments do is N/A when none of them is onboarding the client, so a payroll-only client is not asked about bank feeds or EPOS. Anything you answer yourself wins.

  1. On Overview, tick the departments the client is taking on: Payroll, AP, Bookkeeping, CoSec and Tax. A smaller client is run on one SB&CO tracker instead, with its services ticked on that tab. Where the Client Register already states services, press Put these in scope.
  2. Fill in Intake once. Anything WSOP already holds, from the register, Companies House or the client’s own form, is shown and counts; type over it only where it is wrong. Directors and shareholders come from the registers on Company secretarial, so only whether each director’s self assessment is with us is chosen here. Passwords, logins, authentication codes and account numbers are never typed into WSOP.
  3. On each department’s tab, set the go-live and the owner, and work the tasks. Each phase shows its target week before or after go-live, and a gate phase has to be signed off before go-live.
  4. Checks on Overview flag risks as you go: a Companies House deadline close with the accounts job not set up, credentials not confirmed as held in the password manager, a director missing from the Companies House register, and more.
  5. Hand over lists the recurring jobs that take over from onboarding. A job whose book already carries the client reads On the book; signing the case off sets up the tax, VAT and management accounts books. The rest are ticked as set up.
  6. The case is signed off once every department in scope is Ready (70% or more, with its readiness gate signed off) and the checklist is complete. The close-out steps carry on after that.

The Onboarding dashboard view shows readiness by department, the go-lives for the next eight weeks and the risk register; Onboarding by client lists each client with a figure per department. A department past its go-live, or close to it and not ready, is on its owner’s Tasks.

The Offboarding dashboard view is the same one look at everybody leaving: how many are going and what they are taking, who is carrying each one, the last days in the next eight weeks, why clients go, and a Needs somebody list of cases past their last day, due within four weeks, or on notice with nobody yet having spoken to them about staying. A row opens the case.

When a client gives notice

Notice is where an offboarding starts. Until the last day of notice the client is still a client: the work is still owed and the fee is still billed.

  1. Press + Client has given notice on Onboarding & Offboarding. Choose the client, then say who gave notice, the day it was given and the notice period in the engagement letter, in whole months (nought is immediate).
  2. The last day is worked out from the period and shown as you type. If the two sides agreed a different last day, give it and say why.
  3. The offboarding starts with the notice on it: the last day becomes the target date if there is none, and the checklist’s notice step is answered.
  4. Speak to the client about staying. Until somebody records that conversation under Keeping them, it is on the owner’s Tasks, and red after five days. If they stay, choose They are staying and say what kept them: the offboarding is cancelled with that as the reason.
  5. Clients on notice, above the book, lists everybody on notice with their last day, soonest first, and whether anybody has spoken to them. The On notice figure and the On notice choice under Show do the same.

An offboarding already open takes its notice in the case itself, under Notice.

The client’s FC and MA are told on their Tasks list, and Billing shows the last day beside the client wherever it lists them. Billing’s On notice tab says what still bills each one, and flags recurring billing that runs past the last day.

When a client leaves some services and stays for the rest

A client moving their payroll, or their VAT, is not leaving the firm. Record it as a partial offboarding, never as a client leaving: a full offboarding ends every service and stops all their billing.

  1. Press + Client has given notice (or + Start offboarding), choose the client, and under Leaving choose Certain services: the client stays for the rest. Tick the services they are leaving and record the notice as usual.
  2. The case has its own shorter checklist: only the steps for those services, such as the final RTI submission for payroll or the last VAT return. Nothing about the direct debit or the AML records, because the client carries on.
  3. Their FC and MA are told which service is ending, and Billing shows Payroll ends and the date beside the client, so nobody stops billing the rest.
  4. Signing it off states those services as not done on the Client Register, takes the client off only the books those services live on, and puts a stop for those services alone on Billing. Everything else stays as it is.
  5. On the Net revenue tab it appears under Not on the report yet as a reduction, in the departments of the services ending. Record the monthly figure there.

The net revenue report

Billing’s Net revenue tab is the firm’s net revenue report: clients on notice first, then the movement month by month, by department, and every client won and lost over thirteen months from a January.

  1. A client joining or leaving with nothing recorded is listed under Not on the report yet, with what recurring billing or the won proposal suggests. Press Record it, check the figure for each department, and save. It is not counted until you do.
  2. + Record a client won or lost adds one the cases do not carry. Click any line to change it or take it off.
  3. Download the workbook gives the report in the sheets it has always had. Load the old workbook reads the hand-kept file, shows what it will load, and loads it on a second press. Loading it again is the latest word: a line already on the report is updated, not added twice, and the preview lists every line it would overwrite, which happens only once you tick to confirm. A client’s lost lines and their notice follow each other, so moving the last day on either moves the other.
  4. Under Sending it, choose every Monday or the first working day of the month and who it goes to (firm addresses only). It arrives with the workbook attached. Email it now sends it straight away.

Invoices in Xero

Billing reads and writes the firm’s own Xero every ten minutes. WSOP makes drafts; approving and sending an invoice is always done in Xero, by a person.

  1. Open an invoice to raise and press Create the draft in Xero. It goes to the client’s Xero contact for the fee on the job, before VAT.
  2. Approve it in Xero. At the next sync it is recorded here as invoiced, with Xero’s invoice number.
  3. No button? The client has no Xero contact linked. On the Xero tab, link the contact Xero already has, or press Create it in Xero to make it from the Client Register.
  4. The Xero tab also lists contacts that need a person to say which client they are, clients whose name differs between Xero and the register, and approved invoices in Xero that are not on Billing.

Notes and questions for the team

Ask a colleague about a client or a piece of work on the work itself, so the question and the answer stay with it. Teams is still the place for general chat.

A client (its Notes tab), an Improvement Plan task, a Stat & Tax job or case, a P&L close, a VAT return, a payment run and a proposal each have Notes for the team. Write a note and press Send. It stays on the work for good, under your name, and is never edited.

  1. To ask somebody, choose them under Ask somebody, or type @ and their full name, as it is on their account. A first name alone asks nobody.
  2. The note goes on their Tasks, and they are emailed a link back to it. The email cannot be answered: they answer on the note in WSOP.
  3. Writing on the same work answers what you were asked there. If nothing needs saying, press Mark done on the note or open it from Tasks.

Only colleagues who can open that client or piece of work can read its notes or be asked, whatever is typed. Notes are not written while working as somebody else. When somebody leaves, what they were asked moves to whoever takes over their work.

The daily email

At about 08:30 every weekday, everybody gets one email from their own Tasks list.

It lists what is overdue, what is due today and what has arrived on your list since the last one, then how many other things are waiting and a button to open Tasks. On a Monday it covers the week as well: what falls due in the next seven days, clients on stop and tax cases that have gone quiet. It is built from your own Tasks list, so it says exactly what Tasks says and nothing you could not already see.

Every email ends with a Did you know: one thing WSOP can do, on a screen you can open, a different one each day. On a day with nothing waiting on you, that is the email. A system administrator can leave somebody out on the Integrations screen.

Integrations

Every system WSOP reads from or writes to, one line each, with whether it is on.

Under Settings, for system administrators. Each line says what the system is and its state: Connected, On, Off, Switched off, Not set up or Planned. Each heading counts how many of its lines are on, so the first look answers what is running and what is not.

The groups

GroupWhat is in it
AutomationsWhat happens between the books by itself: a proposal won opens the onboarding case, a case signed off sets the client up on every book or takes them off, and how far compliance has moved off the upload.
ConnectedThe outside systems with a live connection: Xero, Employment Hero, OpsDesk, Timely, Companies House and single sign-on into other apps.
MessagesWhat WSOP sends to people: Microsoft Teams, the daily email and handover emails.
PlannedSystems agreed but not yet built, with what they will do and the rules they will keep. Nothing reads or writes them yet.
Running quietlyServices with no switch here, listed so nothing is invisible: Microsoft 365, Resend, Make, the service issues pipeline and Anthropic.

Opening a line

Press a line to open it. Inside are what it feeds, its switches, the steps to set it up, the buttons that test or run it, and Rules it keeps. A switch saves the moment it is changed and every change is in the account log. A line you opened stays open when you save or press a button inside it, so the message saying what happened is in front of you. Press the line again to fold it away.

Credentials

Each connection holds its own credential on Vercel, never on this screen, so turning one off touches nothing else. The screen only says whether a credential is set. The one exception is the Companies House presenter account for filing, typed on the Companies House line and held sealed: it is never shown back, only whether it is held.

HubSpot tickets

Each department’s HubSpot tickets, read the way the Payroll Command Centre reads them.

Under My work. One tab per department: Support, CoSec, Payroll and Tax, and OpsDesk’s mailboxes. You see the ones switched on for you on the Admin screen’s Pages panel. Under each department are four views, the same four as the Payroll Command Centre.

The four views

Dashboard is the open backlog right now, whatever the Search filters say: how many are open, their average age, how many have nobody on them and how many have no client, then open tickets by person and the unallocated count, with the department’s month and week underneath. Search is every ticket, open, closed or both, filtered by owner, age, client or words, with a link into HubSpot on each. Client view ranks the clients by open tickets, with the unallocated first; a row opens Search on that client. Insight is what the tickets say is going wrong over the last one, three, six or twelve months against the window before: themes, the clients raising the most, and the signals worth acting on.

Giving a ticket its client

HubSpot does not say which of our clients a ticket is about, so WSOP works it out. Every fifteen minutes each untagged ticket is read and, where its words clearly name one client on the register, it is tagged to that client and marked matched. The reading is the one the service issues board uses to suggest a client: the company's name or any spelling the books hold, whole words only, and where a ticket names two clients equally it is left alone. Private clients are matched on Tax tickets only, and a colleague's name never counts.

A person always has the last word. In Search, press the client cell on a ticket to pick a different client, or choose Unallocated to say it has no client: the matching never puts back a tag somebody took off, and never changes one somebody chose. Every figure by client reads from these tags. You cannot tag a ticket while working as somebody else.

OpsDesk tickets, worked here

OpsDesk’s mailboxes sit beside the HubSpot teams. The Payroll, Support, CoSec and Tax mailboxes each have a tab of their own, shown when OpsDesk lets you open that mailbox and that department is switched on for you; every client mailbox is on the one OpsDesk tab. The lists and counts are read from OpsDesk every fifteen minutes. In Search, Whose narrows an OpsDesk tab to your tickets or the unassigned ones.

Open a ticket and it is read live from OpsDesk: the email thread, newest first, and the internal notes. If your OpsDesk permission on the mailbox lets you write, the panel also has:

  • Work it: change the status (closing it included; an unassigned ticket is assigned to you as it closes, as in OpsDesk), set the priority, or assign it to a colleague or to nobody.
  • Reply to the client: plain text, sent from the mailbox through OpsDesk so it threads in Outlook. The mailbox’s signature is added and their email quoted underneath unless you untick them. It goes to whoever sent the newest email, as OpsDesk’s own Reply does; tick Reply to everyone on it to copy the rest. You are asked before it goes, and it shows as sending until Outlook confirms it.
  • Internal note: marked Internal, never sent to the client. Mention a colleague by picking them, or by typing @name@williamsstanley.co; they are told in OpsDesk.

Everything is done as you, with your own OpsDesk permissions. If OpsDesk refuses (you have no OpsDesk account, the mailbox is not yours, or your permission there is read only) the panel says so in words; mailbox permissions are given in OpsDesk by an OpsDesk administrator. Nothing is sent to OpsDesk while working as somebody else. On the Client view of an OpsDesk tab, One client across OpsDesk lists a client’s tickets in their own mailbox and every department mailbox you can open, matched by their linked mailboxes and their email domains.

The OpsDesk Inbox

An OpsDesk tab opens on its Inbox, a help desk laid out like a chat. OpsDesk is the one place a ticket lives: everything you see is read from OpsDesk as you, and everything you send goes to OpsDesk, so a reply sent here is the same reply in OpsDesk and the Payroll Command Centre, never a copy.

  • The list, on the left: Mine, Unassigned, each department mailbox you can open, and All I can see, with a search and Open, Closed or Any status. Each row shows the client, the subject, the start of the latest message, how long ago, a dot if you have not read it, the SLA, the priority and whose it is.
  • The conversation, in the middle: the client’s emails on the left, ours on the right, a line for each day, and small grey lines for changes such as a new status. An internal note is yellow and labelled Internal note, never sent to the client. The earlier emails a reply quotes are folded under Show the earlier messages; attachments download when pressed.
  • The composer, at the foot: choose Reply to client or Internal note (mentions are for notes), attach up to five files (3MB together), and press Send or Ctrl+Enter (Cmd+Enter on a Mac).
  • The details, on the right (under Details on a smaller screen): the reference, the client, the SLA, the status, priority and assignee to change, Merge into another ticket, and Open in OpsDesk.

What you send shows at once as Sending, then Sent once Outlook has it. If it did not go it says Not sent with a Retry button: retrying can never send it twice. If a colleague replied since you opened the ticket you are asked before yours goes, and the line under the subject says who else is viewing or replying, in WSOP, the Payroll Command Centre or OpsDesk. While the Inbox is open it follows OpsDesk within seconds; until OpsDesk’s instant updates are switched on it reads again every 15 seconds and says so above the list. On a phone the list, the conversation and the details are one screen at a time, each with a way back.

How a theme is read

A theme is a keyword rule read off the subject and the start of the message, in a fixed order, first match wins. It is not a model, so the same tickets always give the same answer. The rules are listed at the foot of Insight. A ticket that matches none is counted as not recognised, never guessed: a high not-recognised share means the rules are missing words, and the rules can be changed.

Support and ideas

Stanley answers how-do-I questions and takes your ideas for doing things better.

The button in the bottom-right corner opens a panel with two tabs. William looks up the firm’s work as you: what is overdue, where a client stands, what changed. Support is Stanley, who explains how to do things in the app and how the firm does a piece of work. Each tab keeps its own conversation. Stanley is there for everybody signed in, whatever areas your account holds.

Super administrators see a third tab, Operator. It works across every area their account holds, as them: it looks things up freely, and when something needs changing it shows a card with exactly what will be sent. Nothing changes until you press Confirm, and Cancel leaves everything as it was. It cannot change accounts or access, which stay on the Admin screen.

Stanley answers from this handbook and from the published procedures, and from nothing else. Where neither covers a question he says so rather than guessing, and names who is likely to know. That is deliberate: an answer that sounds right but that nobody decided is worse than none, because it gets repeated.

Writing a procedure with Stanley or William

When no procedure exists for what you asked, Stanley offers to write one with you there and then. William does the same, on the same rules, if you ask him. You are usually the best person to write it, because you are the one who does the job.

  1. He asks one question at a time: the outcome it produces, what starts it and how often, who does it, which systems it uses, then the steps in the order you do them, what done looks like, and where it usually goes wrong.
  2. He writes each step as one instruction, naming the screen or button, and asks about any gap rather than filling it himself. He never adds a step you did not describe and never decides the outcome for you.
  3. He shows you the whole draft. When you say yes, he saves it as a draft on the Procedures tab, owned by you. Open the draft takes you straight to it.
  4. It is not the firm’s procedure until it is published, which you do yourself. Until then it sits on your Tasks as never published.

Publishing is yours to do: open the draft on the Procedures tab and press Publish when you are happy with it. Either of them can also write a revision of somebody else’s procedure with you and send it to its owner. William can also raise proposals for anyone who holds Proposals edit; everything else they only read.

Raising a proposal with William

If you hold Proposals edit, William can raise and work on proposals for you. Paste the email thread between you and the client into the panel (Shift+Enter starts a new line; Enter sends) and ask him to raise the proposal.

  1. He finds the client on the register, and asks before adding one if they are not there or a similar name is.
  2. He matches what the client wants to the rate card. Prices always come from the rate card; for payroll he uses the headcount and how often they are paid. He sets a discount only if you ask, and anything the rate card does not cover is left unpriced unless you or the email state a price.
  3. He shows you the whole proposal, covering note included, and saves it as a draft when you say yes. Open the proposal takes you to it.
  4. You read it through and issue it from the Proposals screen, which makes the client link live. Recording won or lost is also yours.

A discount of more than 30% on any line needs approval from James Couch or Tom Stanley before the proposal can be issued. Either of them may approve any request, their own included, and nobody else can. Ask for it on the proposal (or tell William to), give your reason, and it appears on both their Tasks; the first to decide settles it. The approval covers the lines exactly as they were: change a price, quantity or discount afterwards and it has to be asked for again.

You can keep going in the same conversation: change a quantity, add a line, rewrite the note, and he shows you the change before saving it. Proposals and procedures are the only things William or Stanley can save.

A proposal for several companies

Many clients are more than one company: a group, its trading companies, a property company. One proposal can bind all of them, so one engagement covers the lot and each company is billed for its own work.

  1. Open the proposal and find Legal entities at the top. The proposal’s own client is always first.
  2. Type a company’s name or number and press Search Companies House. Press Add beside the right one. Only an active company can be added.
  3. Each line then asks which company it is for. Lines start on the proposal’s own client.
  4. The panel shows what is quoted for each company, and the totals add up to the proposal’s.

Adding a company uses its registered number. If a client record already holds that number, the proposal uses that record. If one record has exactly that name and no number, it takes the number. Otherwise a new record is made under the registered name. Nothing is matched on a similar name: a holding company and its trading company are two companies. A proposal cannot be issued while a company on it has no number or nothing quoted for it. The client’s copy lists every company with its number, and the engagement letter on the onboarding case sets out each company’s work and fees. William does not add companies; that is done on the proposal.

Writing and changing procedures

Everyone can write a procedure, save it and publish it. What you write is yours: you own it, you publish it, and you can change it whenever the work changes.

Somebody else’s procedure is theirs to change. If it is wrong or out of date, open it and press Propose a revision: write it as you think it should read and say why. Its owner accepts it, which publishes it as the next version in your name, or declines it and tells you why. Either way the answer arrives on your Tasks. Stanley can write the revision with you and send it.

To hand one of your own procedures to a colleague, open it and choose them under Hand this procedure to a colleague at the top. Somebody with Procedures edit can give any procedure an owner there, or press Make it mine; on the list they can give every procedure shown one owner at once, so filtering the Owner picker to Nobody and pressing Set the owner puts the unowned ones into somebody's work. A procedure whose owner has left says so until it is handed on.

A proposal waiting on you appears on your Tasks as a review. Accepting publishes it straight away, so read the proposed text first; if you have a draft open on the same procedure, publish that first.

Why revisions are proposed, not written over

A procedure has one owner who answers for it. If anyone could publish over anyone else’s, the manual would say whatever the last person believed, and nobody would know which version to trust.

Putting an idea forward

  1. Tell Stanley the idea, in your own words: what would change and why it would help. He may ask one question to be sure he has it.
  2. He writes it up as a card in the conversation, with Submit idea and Not now.
  3. Nothing is saved until you press Submit idea. It goes in under your name.

Showing Stanley a screenshot

  1. On the Support tab, take a screenshot (Windows key, Shift and S) and paste it into the box with Ctrl+V, or press the paperclip beside the box and choose a picture.
  2. It shows above the box. Press its × to take it off. Up to three go with one question; a large picture is made smaller first.
  3. Ask your question. Stanley sees the screenshot with it.
  4. If he writes up an idea in that chat, the card says the screenshots go with it, and pressing Submit idea attaches them. Whoever decides the idea sees them in its drawer.

A screenshot that never goes with an idea is deleted after seven days, like the chat it was in.

Every new idea appears on the Tasks list of the system administrators as a review. Each one either accepts it, which puts it on the Improvement Plan as a task under the workstream they choose, with your words and name in its notes, answers it with It is already there and where to find it when WSOP already does what you asked, or declines it with a reason. Either way the decision arrives as a notice on your own Tasks, and the Ideas tab on Tasks shows every idea of yours and where it stands. You can also ask Stanley what became of an idea.

Seeing where your ideas stand

Open Tasks and choose the Ideas tab. Your ideas lists every idea you have put forward, open ones first, each with where it stands:

  • Waiting for a decision, with how many days it has waited. An idea should be decided within a week; past that it turns red here and overdue on the deciders' Tasks. The line at the top names who decides.
  • On the plan, not started or Being built, with the plan task it became, how far along it is, and who owns it. "Nobody owns the task yet" means it was accepted but nobody has picked it up.
  • Done, Already in WSOP with where to find it, or Declined with who declined it and why.

Press Open it on any idea for the full text and its task. The same tab shows the system administrators Waiting for a decision, oldest first, and Accepted, but nobody owns the task. Whoever owns a plan task that came from an idea sees it under Ideas behind your plan tasks, with who asked for it.

Why accepting needs plan edit

Accepting an idea adds a task to the plan, so it takes plan edit, exactly as adding a task on the plan does. A system administrator without it is told so; plan edit is granted on the Admin screen like any other access.

WSOP in your own Claude

Ask your own Claude about your work in WSOP: what is overdue, where a client stands, how to do something. It reads WSOP as you and changes nothing.

Connecting it

  1. In Claude (claude.ai, the desktop app or Claude Code), open Settings, then Connectors, and choose Add custom connector.
  2. Name it WSOP and give it the address https://operations.williamsstanley.co/api/mcp.
  3. Press Connect. A WSOP page opens: sign in if it asks, then press Allow.
  4. Start a conversation and ask: “What can you see in WSOP for me?”

What to ask

  • “What is waiting on me?” or “What is overdue for my clients?”
  • “Where is Bird House on September’s P&L?” or “Which tax returns are due this month?”
  • “How do I send the fact find to a new client?” It answers from this handbook and the walkthroughs, step by step.
  • “Who runs Bird House’s payroll?”, “Are this week’s product emails ready?”, “What training do I owe?”
  • “What can you see for me, and what can’t you?” It lists every screen, which it can read for you, and why the others are closed.

What it can and cannot do

It sees exactly what your account sees: the same screens and the same clients. A screen your account does not open is closed to it too, and it says so. It only reads. It cannot change, approve, send or delete anything; for that, use WSOP itself. Admin, Integrations, the Board Pack and the Payroll Command Centre are never read through it.

Access is given per person, area by area, by a system administrator on the Admin screen. Ask them, not Claude, if you need to see more. To stop the connection, remove WSOP from Claude’s Connectors settings.

Audit trail

Two logs: what changed in the plan, and who had access.

Change log

Every edit is recorded as its own entry — which task, which field, the value before and after, who made it and when. Nothing overwrites it, and a person’s name stays on their entries even if their account is later removed.

Read it three ways: History at the foot of any task panel for that one task, Recent activity on the Exec Summary for the whole plan newest-first, and What changed in Roll-up grouped by task over a period you choose.

Account log

Admins get an Account log tab in Admin recording sign-ins, failed sign-in attempts, and every change to who has access — accounts created, enabled, disabled, access changed, password resets, and password requests. Failed attempts show the address that was tried; the password never is.

It can be searched, filtered to a kind of event or to one person, and paged back with Load more. A change of access says what moved in words, for example “Compliance: view → edit”.

Access review, temporary access and the second approval

Access review lists every area, who holds it and when it was last reviewed. Once a quarter somebody who hands that area out goes through its holders, keeps or takes off each, and the review is recorded. An area due a review is on that person’s Tasks.

On a person’s Access panel, Temporary access grants a level until a date; it goes back on its own the morning of that date. The same panel shows how they last signed in, their open sessions with Sign them out everywhere, and, for an account unused for 120 days, Keep open with a reason.

Controls holds the second approval. It is off. Switched on by a system administrator, raising somebody in a guarded area (fees, margins, people data, passports, AML and GDPR by default) waits until a different system administrator approves it; everything else in the save goes through at once, and taking access away is never held. The tab also lists who the org chart says works here without an account, with Make their account.

On the People list, tick several people to set an area, switch a page, or reset their passwords together.

What is not recorded

IP addresses are deliberately not logged. Say if you need them and they can be added.

Exporting

For sending on, or working offline.

Export CSV downloads the plan as it currently stands — outline, task, workstream, owner, participants, dates, sprint, percentage, status, RAG, priority, days, milestone, objective, latest update and notes. It opens cleanly in Excel.

Export PDF and Export PowerPoint give the whole plan as a pack you can send outside the firm: where it stands, what needs attention, the milestones, then every workstream’s actions with owner, dates, progress and status. They leave out notes, updates, objectives, steps and the change log, which stay inside the firm. People & Development has the same for its action plan, as Action plan PDF and Action plan PowerPoint.

The export reflects the live plan, not your current filters.

The two audit exports

Change log — the button under Recent activity on the Exec Summary. Every plan edit with when, who, task, field, and the before and after values. Needs a sign-in, because it names people.

Account log — in the Account log tab of Admin. Admins only.

Questions about the plan itself go to Lee Redshaw. Questions about the tool go to Tom Stanley.

Never share your password. Each person has their own so the history shows who did what.