| Pay date | Client | Period | Progress | Stage | Status | Owner | Emps | Gross |
|---|
| Client | Period | Label | Files | Rows | Status | Started |
|---|
| Period | Filename | Employees | Uploaded by | Uploaded | Compare | NMW | |
|---|---|---|---|---|---|---|---|
| Pick a client above to see the reports on file for them. | |||||||
| Item | Period A | Period B | Change | % |
|---|
| Employee | Field | Before | After | % |
|---|
Loading…
| Client | From the export | Below the new rate | Who |
|---|
Hourly staff only: gross pay less tips over hours worked, set against next April's rate for their age band where the export carries a date of birth or age, else the 21 and over rate (said on the row). Salaried staff are not checked. A schedule with no export inside the keeping time is not checked, never counted as nobody affected. This never passes or fails a run, and the names stay on this screen.
Load is runs a month times the workload index. Capacity is full-time equivalents times the standard figure on People and settings. Unassigned is work nobody owns, counted like a person with no capacity and shown first, so a healthy team total cannot hide it. Click a person for their clients.
| Date | Days | Window | What | Who or what | Owner | Action required |
|---|
A suggestion is only ever a suggestion: the person with the most room in the same pod at the horizon, counting what has already been suggested. Nothing here moves any work. To move it, plan the handover on the Team screen, which uses the one reassignment there is and takes the open runs with the client.
| Client | Why | Now with | Move by | Load | Could take it |
|---|
| Priority | Gap |
|---|
Notice dates and leaving plans are kept here and nowhere else, and only the people this screen is switched on for can see them. A person is joined to their work by the lead name that appears on their clients. A vacancy has no lead name.
| Name | Lead name | Pod | FTE | Status | Start | Notice given | Last day | Handover |
|---|
A setting nobody has confirmed is a starting guess, and any utilisation resting on one says so. Confirm capacity by finding somebody fully loaded today and setting the figure to what they carry.
| Setting | Value | Confirmed |
|---|
Every run paid in each week, done or not, with how many are still open. Earlier is work still open from before this week, which may only be waiting on sign-off; the Overdue column above says how much of it is late. Overdue in a week is shown in red.
Pick whose schedules are moving and when they leave. Tick who takes them: one name mirrors the whole book onto that person, several spreads it, heaviest schedule first to whoever is lightest at the time. Any schedule can then be sent somewhere else by hand. Mirroring is the receiver sitting beside the leaver on their runs before the leaving date; the timetable below shows which.
How many pay days each person carries each week once the moves are made, worked out from every schedule's pay day rule. The figure in brackets is the change from today's book.
| Client | Frequency | Emps | Load | Goes to | Runs to mirror before leaving | First run alone | Check |
|---|
| Client | Group | Frequency | Pay day | Lead | Emps | Complexity | Rota system | WI | Tier | Next pay |
|---|
| Due | Client | Tax period | Runs | From the runs | Paid | Status | Reference |
|---|
| Client | Lead | Frequency | Emps |
|---|
| Tier | Schedules | WI | Share | Fees | £/WI |
|---|
| Lead | Schedules | WI | Share of the load |
|---|
| Client | Frequency | Emps | Complexity | WI | Tier | Fee | £/WI | Lead |
|---|
An input missing reads as a low score, which is the dangerous direction: it hides work rather than inventing it. Biggest headcount first, because that is where a wrong index costs the most.
| Client | Emps | WI as scored | Tier | What is missing |
|---|
| Group | Schedules | Emps | WI | Fees | £/WI |
|---|
Every priced client, fee per WI against what the book earns per WI overall — with a pill against the ones worth a look, so a pricing conversation starts with the right dozen without losing sight of the rest. Where one fee covers several schedules — several sites billed as one client, or a Monthly/Weekly pair — they are consolidated into one row, with the schedules that make it up underneath, rather than left to scatter across this list as several unrelated-looking fractions of what the group is really worth.
Four of these seven have a real data source in the Delivery Tracker — inputs chased, an amend's cause, and sign-off against its deadline — computed over the window below. The other three (Response time, Payroll profitability, Client satisfaction) need a query timestamp, a cost figure and a survey mechanism this board does not have yet, so they say so rather than showing a number that is not really there. Payroll profitability is read from Firm performance > Profitability once its costs and budget are set there.
| KPI | Measure | Target | This period |
|---|---|---|---|
| Client-caused sign-off delay | Payrolls delayed past the agreed deadline due to late or incomplete client information | Track initially | |
| Client correction rate | Payrolls requiring correction because of late, missing or incorrect client information | Track initially | |
| On-time payroll sign-off | Payrolls approved and submitted by the agreed deadline, excluding client-caused delays | 100% | |
| Final payroll accuracy | Scheduled client pay runs completed without a WS&Co-caused correction after client approval | 100% | |
| Response time | Payroll queries receiving an initial response within one working day | 95% | No data source yet |
| Payroll profitability | Actual monthly contribution against budget | Budget target | See Profitability |
| Client satisfaction | Payroll-specific NPS or CSAT | +30 to +39 | No data source yet |
The open backlog right now — not affected by the Search filters.
Loading…
Every ticket raised with the payroll team, from HubSpot. The weekly report is a summary of these; this is all of them.
Loading…
OpsDesk's are matched on the schedule's contact email domain (or the address itself, for a public one like gmail.com) and any OpsDesk mailbox WSOP links to the client. HubSpot's are the tickets tagged to it here.
Click a row to see that client's tickets in Search.
{{contactName}} {{payDates}} {{replyBy}} {{yourName}}.
Placeholders: {{client}} {{owner}} {{period}}
{{payDate}} {{dataDue}} {{approvalDue}} {{fundsDue}}
| Company | Contact | Pay dates | Where it stands |
|---|
| Client | Scheme | Troncmaster | NICs | Set-up | What needs attention | Latest period | |
|---|---|---|---|---|---|---|---|
| Loading… | |||||||
Drop the Xero Account Transactions report for the Tronc Revenue account. Every Tronc Master invoice on it is a scheme the firm runs. Each line is matched to a client on the board where the name makes it clear; check every match, pick the rest, and untick anything that should not be added. Adding marks the client Tronc: Yes and records the scheme with the firm as independent troncmaster, with its Xero code and monthly fee. A scheme already here by that name keeps everything and only has its fee updated, so the same report can be brought in again. A business we run only the tronc for, with no payroll of ours, can be added from its line: pick Add as a new tronc-only client. It goes on the client list with no payroll runs. A payroll client that is missing is added on Clients, never from an invoice.
Read off the figures below, worst first. Each line is a question worth an answer: fix it, raise an action, or decide it is not worth fixing.
Anything that would stop a delay happening again, or stop a ticket being raised at all. An administrator answers every one, and a declined idea says why.
Every place somebody set aside what the board or the tronc engine worked out: a colour pinned, a deadline or pay date moved, a tronc guarantee typed in, a tronc period approved with checks still for review. An override is not wrong. One with no reason, or one that keeps happening on the same client, is a rule the work does not fit.
| When | Kind | Client | What | Who | Reason |
|---|
Steps marked as done by a client's own arrangements on every run. Counted apart from the window, because each one is set once and then holds.
| Client | Step | Set by | When |
|---|
Nothing here changes an owner. Put the board's lead right with Move their schedules (Admin > People) or Edit client, and HubSpot's Payroll Person in HubSpot. A company is matched by its client code, then by its name exactly as the register reduces it, never by a resemblance.
| Client here | Lead on the board | HubSpot company | HubSpot Payroll Person | OpsDesk | What differs |
|---|
| Name | Job | May change | Sees | Screens | Last seen |
|---|
They get a one-time password, shown above once, which they replace at first sign-in. Start from the job they do; every line can then be changed before the account is made.
Sign-ins, failures, password resets and every change to who has access. Failed attempts record the address that was typed, never the password.
Who confirmed the weekly briefing for the week chosen, worst first. Signed in, not confirmed means the account log has a sign-in for them that week and no confirmation. No sign-in recorded means neither: a session carried over from an earlier week is not a sign-in, so it does not prove they stayed away. Click a name for their account log.
What needs a decision, what Tidy up looks after, who holds the keys, and how every screen is controlled. Worked out afresh each time the Admin screen is opened. Nothing here changes an account on its own: a decision about somebody's access is always a person's.
Tidy up removes expired sessions and the sessions of closed accounts, old failed sign-in attempts and test accounts the access matrix left behind, and marks import drafts nobody has touched for a month as abandoned. It also removes the parsed rows of dropped files whose run was signed off longer ago than the keeping time on Import set-up, keeping each file's record and counts. Nothing anybody is using is removed.
| Screen | Decided by | What switching it off does |
|---|
Moving a schedule moves its open runs with it, so the new operator sees the work immediately. Signed-off runs deliberately keep the name of whoever did them — that is the record of who did the work, not an assignment.
| Lead | Account | Schedules | Employees | WI | Share | Open runs |
|---|
How a client's payroll is actually run, written down once so somebody picking up a client they have never done does not have to ask. The timetable and the settings are derived from the client record rather than retyped — the written half is only the part the app cannot know. Biggest client first, because an unwritten COM for three hundred employees is a bigger hole than one for a single director.
| Client | Lead | Emps | WI | Written | State | Last reviewed |
|---|
Imports, Reconciliations and the pre-draft check keep each file parsed, and its rows hold names, NI numbers, hours and pay. The rows are removed this many days after the file's run is signed off, by Tidy up on the Health check and by the schedule each morning. The file's name, headings, mapping and row count stay, so it is on record that it was here; the combine cannot be run again from it. Nothing is removed for a run that is not signed off, nor for a file tied to no run.
Off until somebody types next year's rates here, once, with the date they take effect. Then Reconciliations > April minimum wage and, from 1 February, each lead's Home list show the hourly staff paid below the new rate, from each schedule's latest pre-draft export. The board holds no rates otherwise; this never passes or fails a run.
The columns written into the files BrightPay is given. These start as a sensible guess — open your own BrightPay import once, correct the headers here to match it, and every import afterwards comes out right. Money goes out as plain numbers to two decimal places and dates day-first, whatever the headers say.
| Name | For | Columns | Last changed |
|---|
Every time somebody ticks “remember this mapping” on a dropped file, it lands here, and the same export next month arrives already mapped. Delete one if a client changes the shape of what they send.
| Client | Kind of file | From | Matches on | Columns | Used |
|---|
The other systems the board works with, and the settings that pair it with them. A value entered here takes effect within a minute and wins over the one set on the deployment. A secret is never shown again once saved: to change one, enter the new one. Every change is on the Account log.
These are still set in Vercel, not here. Shown so this is the one place to see what the board is connected to.
| Connection | What it is | State | Settings |
|---|
Every email the app sends comes from payroll@williamsstanley.co, and replies go back there: client messages, tronc letters and password resets.
When a change to the app needs new tables, this puts them in. It runs against the database this app is connected to, and refuses unless that database is recognisably the board's, so it cannot touch WSOP's or any other. Nothing that exists is removed or overwritten, and pressing it twice is the same as pressing it once.
One scheme per client pool. The rules here are the ones the engine runs, and the rules document is written from them.
While the client still runs its own workbook, import each period's workbook as well: the period then shows the board's answer against the workbook's, person by person. Once periods match to the penny, set the date the board takes over. Periods starting on or after it are not imported from the workbook.
The promised rate and house pay must be confirmed in writing by the employer before the first payment.
One change, one owner, one date, and how we will know it worked.
One episode, for one client. Dates come from the letters, so add the first one once it is open.
The firm’s way of running this kind of case. Anything going to HMRC, a tribunal or a client in writing on a contested point is reviewed by a qualified adviser first. Nora knows these steps too.
Arrears are owed at today’s rate where it is higher than the rate that applied: the shortfall divided by the old rate, times today’s. Type the rates; the board keeps no table of them. HMRC’s penalty is 200% of the arrears, capped at £20,000 a worker, at least £100, halved if paid within 14 days.
| Worker (a reference, not a name) | Shortfall (£) | Rate that applied (£ an hour) |
|---|
How the board opens for you, on any computer. They change nothing about what you can see or do: that is set on Admin > People.
Add the board to Claude once, and you can ask about your payrolls in plain words, beside Client Operations. Claude reads what your account sees here, and it never changes a payroll.
Marks the client Offboarding with its final pay date. It stays live and paid until then; Generate periods stops at that date, and its exit checklist is on Admin > Clients and workload > Offboarding.
Puts every period that pays inside the window onto the board. Periods already there are left exactly as they are, so this is safe to run twice.
For a period the generator will not produce — a correction run, or an off-cycle payment.
The cycle set here is what the generator uses, and the two lead times are what the board chases on.
Pick whose schedules to move, tick the ones to move, and say who they go to. Open runs move with them; signed-off runs keep the name of whoever did the work.
| Client | Frequency | Emps | WI | Tier |
|---|
| Scheduled | Schedule | Answer | New date |
|---|
One row per column of the CSV, in the order BrightPay expects them. Leave the field blank and give a fixed value to write the same thing into every row.
| Column header | Filled from | Fixed value |
|---|
Switching a screen off, or dropping somebody to read-only, signs them out, so the change takes effect the next time they open the app.
Claude never changes a payroll for anybody: steps, flags, dates, figures and imports are always done on the board by a person. Notes and drafts are recorded in their name marked "via Claude", and they allow the connector again in Claude before it takes effect. Editors and administrators only.
At least 8 characters. Changing it signs your other devices out.
What has been added, and what the board can already do for you. About a minute, once a week.
Loading…
Sign in with your Williams Stanley email.
Put in the address you sign in with and we will email you a link. It works once and stops working in an hour.
Norareads this board — she cannot change it