Loading…

WS Operations Platform

Sign in to reach your work: tasks, clients, delivery and the firm’s figures.

WS Operations Platform
How it works

WS Operations Platform

Export ▾
My tasks
Overview
Board
By owner
All tasks
Timeline
Sprints

Waiting to be picked up

Open tasks with no owner or no due date. Accepted ideas and issues raised onto the plan arrive like this. Open one and give it an owner and a date.

Changes to WSOP

Open tasks marked as a change to the platform. They go to the platform owner to build and stay here, so everybody can see where each has got to.

Needs attention

In flight

Workstreamspress one to see its tasks

Coming up

Recent activity

Timeline

Click any task row to open its full detail.

Task register

Click any task row to open its full detail and record an update. A blue dot marks tasks with a progress update.
Move OutlineTaskWorkstreamOwnerStartFinishSprint%StatusRAGPri
Two-week sprints, S1 starting . Counts are open tasks (complete and parked left out). S1 holds the work that was already under way or overdue when the sprint calendar began. Press a bar to see that sprint's tasks.

Load per sprint

Load per owner, current + next sprint

OwnerS1S2Total open
Needs attention

Outstanding

No items match these filters.

Month-to-Date & Weekly Performance

By FC — Submission & On-Time Rate (current filter)

Root Cause Detail

MonthClient CodeCompany NameMAFCType / StatusRoot causeComments / Remarks

Outstanding / Pending Items

RCA and Comments are editable directly in this table -- click into a cell to update it, then use "Save changes" above. Everyone sees it straight away.
MonthClient CodeCompanyMAFCMissingWeek Deadline P&LDeadline BSOverdue (wd)StatusRCAComments
Overdue = workdays (Mon–Fri) elapsed since deadline. Due this week = deadline falls within the current Mon–Fri window. Items due later are excluded from this list until their week arrives. FC/Group/Company/Status filters narrow the By FC and Outstanding sections; the MTD & Weekly Performance section above stays month-wide for whatever FC/Group/Company/Status scope is chosen (Week filter doesn't affect it, since it's meant as a stable monthly overview).
Every deadline the books carry, counted by the day or the week it falls due and by who it falls to, so the team can plan the work before it lands rather than find out at month end.

Proposals

Client Proposal Owner Service lines Annualised One-off Status Days Issued Deal room
Export
More0
Other views
Actions

Names arrive as free text in email and in the workbooks, so the same person or client turns up several ways. These are the records they resolve to, the same list the escalations board opens.

To review0
People
Clients
Private clients
current

This week's email

Consolidated report and packs

Not submitted yet

Your written report

Wins, challenges and ideas for the week, with your KPI figures if your department reports them. Edit, then Save and submit before Friday 12:00.

Report files

Trackers and other files that go out with the Friday report. Upload yours here; a file of the same name replaces the earlier one. Up to 3 MB each.

Monthly KPI returns

One return per department each month: type the month's actual for each KPI, add a comment if it needs one, then Save and submit. Leave an actual blank if the figure is not ready rather than entering 0. Submitted returns show on Monthly KPIs.

Departments and their KPIs

Every department is set up the same way: who submits, a deputy, and each KPI as a number against a target. When somebody leaves, change who submits; the department and its history stay.

Monthly KPIs

Procedures
Policies
The loop0
Roles & reading0
Operating principles
Strategic objective
Change log

Working procedures

Code Procedure Outcome Folder Owner State Review due Steps Issues

Everybody who works for the firm: what they do, who they report to, where they are and how to reach them at work.

Loading…

Loading…

Every person on the team record: their work facts, their working pattern and when they started and left. Every change is kept with who made it, and nobody is deleted.

Loading…

Loading…

Ask for holiday and other leave, see what you have left, and record sickness. Your manager decides; People & Development keep the firm’s allowances.

Loading…

Balance Sheets

VAT returns

P&L

Payment runs

Tickets by department. The four HubSpot teams, read from the ticket database the sync keeps up to date, and OpsDesk, read from its own database. Pick a department, then its Dashboard, Search, Client view, Insight or Escalations. OpsDesk’s tabs open on the Inbox, where a ticket is read and answered as a conversation, live with OpsDesk.

Departments

The Payroll Command Centre, shown inside WSOP. You are signed in to it with your WS Operations Platform account where you hold one there. Open on its own
DevTickets, shown inside WSOP. You are signed in to it with your WS Operations Platform account where you hold one there. Open on its own

Every system WSOP reads from or writes to, one line each. Open a line for what it feeds, its switches, the steps to set it up and the rules it keeps. Each connection holds its own credential, so turning one off touches nothing else.

Loading the connections…

Planned

Nothing reads or writes it yet
AutoAPOur AP automation: supplier invoices and approvals
Planned

The firm’s own heads and managers approve the invoices waiting on them inside WSOP, from their Tasks list, without signing in to AutoAP. The approval is AutoAP’s own, recorded there against the person who pressed it; WSOP is only the place it is pressed.

FeedsTasksManagement accountsCompliance (AP)Monday brief
  • Phase 1Invoices awaiting a person’s approval appear on their Tasks as a review: supplier, amount, client, due date, and the invoice image. Approve, reject with a reason, or open it in AutoAP.
  • Phase 2An invoice waiting past its approval deadline is chased on Tasks and named in the approver’s Monday brief. Approvals still outstanding at the AP cut-off show on the client’s management accounts close as a blocker.
  • Phase 3A payment run released in AutoAP marks the week’s run as gone out on the compliance AP register, the way a filed VAT return writes the VAT register, so payment runs come off the upload.
Rules it keeps
  • Firm staff only. A client’s own approvers approve in AutoAP and are never given an account on WSOP; clients never access this platform.
  • AutoAP decides who may approve what. WSOP shows a person only the invoices AutoAP routes to them, matched on their work email, never on a name.
  • Approving follows AutoAP’s own limits and levels. An invoice over a person’s limit, or needing a second approver, is sent back to AutoAP’s own rule, never settled here.
  • A rejection needs a reason, because the supplier and the client are told it.
  • Never while working as somebody else. An approval is a statement under a name.
  • WSOP never edits an invoice, its coding, its amount or its supplier, and never releases a payment.
  • Every approval and rejection pressed here is written to AutoAP first and shown as done only once AutoAP has accepted it.
Read: invoices awaiting approval, approvers. Write: approve, reject

Running quietly

No switch here; listed so nothing is invisible
Microsoft 365Sign-in and the directory
On
ResendEvery email the app sends, from the app itself
On
MakeWeekly reporting: Teams posts, SharePoint files
On
Service issues pipelineThe escalations register
On
AnthropicWilliam, summaries, drafting
On

Every system we use, in one place. Each opens in a new tab and asks for its own sign-in. Pin the ones you use most with the star and they sit at the top, in the order you choose.

The firms we work with and recommend to clients. Each link opens the partner's own site in a new tab. Use this when a client needs one of these services, so they reach the partner through us.

Website traffic

Who visited www.williamsstanley.co: first the weekly snapshot, then the detail from the two places the site sends to. Vercel sets no cookie and counts every visitor. Google Analytics counts only the visitors who accepted cookies on the banner, so its figures are the smaller set. The two are shown apart and never added together.

Customers

Every customer WSOP knows about, in one place: the accounting clients on the Client Register with their contacts, services and tickets, and everybody on our products' email lists. Tick customers to put them on a product's email list. Adding somebody sends nothing.

Event guests

Everybody who has RSVP'd to one of our events on the website, as they RSVP. The website has already sent each guest their confirmation and added them to HubSpot. This is the door list and the kitchen's list: mark a guest cancelled when they say they cannot come, and attended on the day.

Sending safeguards

What stops a marketing email going to lots of people by mistake, and the record of everything sent and everybody who asked to stop.

Marketing emails

Emails about the firm rather than one product: the Budget, events, guides. Each is written here from blocks in the look of our website's campaign pages, with a live preview. Nothing goes until somebody here reads a test, approves it and presses Send.

Preview

Weekly product emails

Every Tuesday morning WSOP reads what shipped in each product's code that week and drafts three emails: one for customers, one for prospective customers and one for our own team. Nothing goes until somebody here reads it, approves it and presses Send.

Preview

Product screenshots

Screens from our products for proposals, decks, the website and posts. Click a picture to see it large and download it at full size.

All figures are dummy data (), so every picture here is safe to use outside the firm.

Who runs each client’s payroll. Choosing a person saves it straight to the client’s Payroll Person in HubSpot.

Loading…

Every SB&CO client in one list: what SB&CO does for them and what is due next. It reads the VAT, Stat & Tax and Onboarding books, so open a client’s work there to move it on.

Loading…

Pass on a lead and whoever covers business development quotes it; ask a team for work and its cover owns it. Either way there is one owner and a time limit on their Tasks, and you are told the outcome.

Loading…

Front door: wsop@williamsstanley.co

Every email to the firm's front door, handed into WSOP by the mailbox flow and worked here, never in the inbox. A quote request becomes a request above with one press; a client's email is answered with the template telling them where to go, never worked here. Nothing is sent by itself unless Tom switches the receipt on.

Loading…

WhatsApp inbox

Every WhatsApp to the firm's number, worked here rather than on personal phones. A known client goes straight to their MA, else their FC, from the Client Register, cover included; anything else waits for Tom or Jan to file. Each conversation has an owner, a clock and a line on their Tasks, and WhatsApp's 24-hour rule is shown on each one.

Loading…

Who covers the requests, and the time limits

A request lands on its cover's Tasks the moment it is raised. The time limit is working days to first contact. Set by a system administrator; Tom's proposed defaults stand until changed.

Every system the firm pays for: who owns it, what it costs, how many seats are used and when it renews. The owner, and whoever is named for system renewals, is told on Tasks when a renewal needs a decision.

Loading…

Every contract and key paper the firm holds, each with an owner, the last day to act and the decision made. Supplier contracts come from the System tracker and client agreements from HubSpot; everything else is added here. Only the SLT sees this page, and every change and download is recorded.

Loading…

WSOP Phone · the switchboard

Calls to the firm come in on one switchboard number and ring here, in WSOP, and on your mobile if you ask for that. You can call any UK number from here; the client sees the firm’s number. Calls inside the firm are free.

Make a call

My line

Recent calls

Loading…

Texts and WhatsApp

The team

Every laptop, phone, monitor and other piece of kit the firm owns: who has it, where it is and when its warranty ends. When somebody is on the Offboarding list, their kit is shown as to come back, and whoever is named for asset returns is told on Tasks.

Loading…

Claim back what you spend on the firm’s behalf: photograph the receipt, say what it was for, and send it. Your line manager approves it on Tasks and the finance team pays it back. Mileage is worked out at HMRC’s rates.

Loading…

Drop the files Nory exports, one day each, and they go straight into the tables the Daily Dish labour and COGS pages read. The day comes from the file's name, the site from each row's location, and anything that could not be loaded is said here and kept on the record.

The day is read from the file name: Nory writes All Location Timecards Week YYYY-MM-DD.csv and purchases-report-all-YYYY-MM-DD-YYYY-MM-DD.csv, and any name carrying one date in a usual form (2026-10-19, 19-10-2026, 19 Oct 2026) is read too. One day per file; the heading row says which report it is. Up to 40 files at once.

Locations to sort

Rows Nory files carry at a location that is not a restaurant (Hq), or one the rule does not know, are kept here in WSOP and never mixed into the Daily Dish. Map a location to a site and its held rows load onto that site, with every later file going straight there; set it aside to keep its rows out; a set-aside location can be put back to waiting or mapped later.

Loading…

What is in, day by day

Loading…

Recent loads

Loading…

How a row finds its site

People
Add someone
Screens
Access review
Controls
Health check
Usage
Account log
Claude connections

What can they do?

Start from the job they do, then change any line that needs it.

Or the same as Fills every line below from somebody already here, and gives them the same People & Development tabs and page switches once the account is made. Never Manage people or System administrator, and never their name for whose clients: their own clients means the new person’s own.

Improvement Plan The CIP plan, its tasks, the exec summary and the roll-up.
Service Issues The escalation register, and the people and clients behind it.
Compliance Month-end submissions, weekly reporting, root causes and the action plan. Names clients, MAs and FCs.
Proposals What has been quoted and for how much. Carries the firm’s fees, so it is off by default on every preset.
Stat & Tax Accounts and returns by client and period, what each is waiting on, and where the working papers are. Names clients’ tax affairs, so it is off by default on every preset — including Administrator.
Profitability Client-by-client margin, and labour cost per person. The most closely held thing here, so it is off by default on every preset — including Administrator.
People & Development Jake’s action plan (built from his own mail and Teams, so his and the sponsor’s to see), the monthly headcount pack and the leaver register. Names individual employees, records why each of them left and quotes their exit interviews, so it is off by default on every preset — including Administrator.
SOPs The firm’s working procedures, the operating principles and the strategic objective. Read is on every preset: a procedure nobody can read is not the authority. Changing what the firm says it does is the grant worth thinking about.
Balance Sheets Month-end balance sheet reconciliation checklists by client. On for the Management accountant and Financial controller presets, with their role below, and off on every other.
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. View reads the points they raised and the ones asked of them; edit raises points either way, answers them and settles them. Somebody a point is asked of can always answer it. The figures per person are the QC Director’s. Edit on the Management accountant, Financial controller, Tax team and Compliance presets, view on Administrator and Read-only.
Client records The Client Register, and which workbook name belongs to which client. Edit links names, adds and edits clients, says what the firm does for each and, with compliance edit, takes a client out of the compliance book. It changes what everybody else sees, so it is held by name.
Onboarding & Offboarding Clients joining and leaving: the cases, their checklists, and the client forms. View reads them, including the passports, dates of birth and NI numbers clients upload; edit starts cases, answers steps, signs them off and sends clients their form. Off on every preset, Administrator included.
Billing What to invoice when a tax job is filed, whose billing to start and stop when a client joins or leaves, and which clients are on stop. View reads the list and the fees on it; edit records what was billed and puts a client on or off stop. Off on every preset, Administrator included. Anybody carrying work for a client on stop is told on Tasks whether or not they hold this.
Enablement The changes the firm is making to itself, such as rolling Insights out to every client or moving off Lightyear: each change, the three gates it passes, the owner's status updates and the client-by-client rollout. View reads them; edit raises changes, answers the gates, writes updates and moves clients through a rollout. Approving a gate is not this: it is a named list in the code. Off on every preset, Administrator included.
AML & MLRO The firm’s own anti-money-laundering controls: the client risk register with enhanced due diligence, everybody’s AML training and the firm controls (the firm-wide risk assessment, the policies, the MLRO’s annual report). View reads them; edit records assessments, anybody’s training and control reviews. Reporting a concern to the MLRO is not this: everybody can, whatever they hold. Reading those reports is the MLRO’s alone, a named address in the code, with edit as well. Off on every preset, Administrator included.
GDPR & Data Protection The firm’s own data protection controls: the data subject requests, the processors with their contracts and transfers, everybody’s data protection training and the firm controls (the record of processing, the privacy notices, the ICO fee). View reads them; edit works the requests and records the rest. Reporting a data breach or logging a request is not this: everybody can, whatever they hold. Reading the breaches is the data protection lead’s alone, a named address in the code, with edit as well. Off on every preset, Administrator included.
QC role Who they are inside balance sheet QC. Set here with their WSOP access — not on the QC tab.
Weekly Reporting Its own membership, separate from the areas above. Set by a system administrator.
Department Which department they report for.
Whose clients Compliance only. Scope someone to their own clients and every figure they see is theirs; leave it on everyone for a supervisor.

Sign-ins, failed attempts, and every change to who has access. Filtered on the server, so a search reaches the whole record, not only the page on screen.

Every screen in the sidebar, in its groups, what opens it, and how many open accounts can. Read from the same rules the screens use; nothing is set here. Change somebody's access on People.

Each area’s holders are looked at once a quarter: who keeps it and who is taken off, recorded with who looked. An area is due when nobody has reviewed it for 91 days. You review the areas your account hands out.

The second approval, temporary access ending on its day, how people sign in, and who the org chart says works here without an account.

What needs a decision, what the weekly tidy looks after, who holds the keys, and how every screen is controlled. It is run again each time this tab is opened.

Claude usage

What each part of WSOP, the Make scenarios and the Payroll Command Centre ask Claude for, and how much of what it sends is read back from the prompt cache. A read from the cache costs a tenth of fresh input, so a falling share is a rising bill. Figures only: the prompts and answers are never kept.

Who uses WSOP

A sign-in and a day used are different things. A session lasts a fortnight, so somebody who opens WSOP every morning may sign in twice a month; the days used are the measure of whether people are using it.

Everybody who has connected Claude to WSOP. A connection reads as that person and changes nothing, so it sees only the screens their own access opens. Each person connects and disconnects their own from the account menu; ending one here takes it away at once and goes in the account log.

Williamreads this app and cannot change it
William looks things up as you, so sees exactly what you see. A conversation is kept for seven days, then starts afresh.