Standing service people-team-workload-view-by-team-only-every-month · revised 12 October 2026
Standing service
Get a team-level workload and waiting-time view every month, with staff told and no names
Each month open work, time open and waiting times by team from your tracker export, with staff told it exists, names removed, small teams merged and no figure for any person.
This starts a conversation by email. Nothing is charged, and nothing is run, until we have agreed scope, access and terms with you in writing.
The responsibility you hand over
A report that ranks people damages trust and misleads. The monthly job shows queues and hand-offs between teams only, after the staff have been told in writing that it exists and how it is intended to be used; notice is not a legal-compliance guarantee.
Who it’s for: Manager or founder who wants to see where work waits month by month without watching individuals.
Usually starts when: The first team report showed where work waits, and you want to see whether it moves.
The result: Each month you receive open items, time open, median waiting time per state and items passed between teams, shown by team only, with names removed and teams of fewer than five merged. Every figure is reproduced by a script you can re-run, and no figure is given for any person.
What stays true, and what we do about it
No response-time guarantee is published for this new service. A target for delivering each month's report is agreed in writing before it starts, set to what a service at this stage can keep.
Hours are agreed in writing before the service starts. At launch the service is not staffed round the clock and runs once each month.
What must remain true
- No figure in any output is for a named person or a group under five
- Every figure is reproduced exactly by the script from the input
- Each month your named lead confirms the staff notice still matches the intended use; we do not observe how managers use the view
What we watch
- The month's tracker export with team codes
- The team list with sizes
- The staff notice
When something happens
Scroll the table sideways to read it all.
| When | What we do |
|---|---|
| A month closes and the export arrives. | We build the view and send changes since last month first. |
| A team changes size or is split so a group falls under five. | We merge or drop it and say so in the report. Linked job: Team workload report |
| Anyone asks for a figure for one person. | We refuse and report the request to your named lead. |
We do on our own
- Run the counts and waiting times on the export
- Write the monthly view
- Offer the one-off report when teams change
We ask you first
- Any change to teams, states or what the view shows
- Any request involving a named person
- Any change to the staff notice
We escalate to you when
- Anyone asks for an individual figure or ranking
- The notice no longer matches the use
- The same missing-date problem appears three months running
How you know it held. Each month the report states items counted, teams shown and merged, change since last month and the script result on a second run, with items missing dates kept as unknown.
How we keep it true
This service is never finished. Each month's report shows whether the thing it watches stayed true, and it continues until you end it.
See open work and waiting times by team from your tracker export, never by person Job Optional
Open items, how long they have been open and waiting times by team from your tracker export, with names removed, teams of fewer than five merged and every figure reproducible by script.
Bought separately, each time it is needed; not part of the monthly fee
What is included, and what is not
- Monthly team view
- Script and checksums
- Merged-team list
- Note on items with missing dates
Included
- One tracker export of up to 5,000 items a month
- Counts, time open and median waiting time per state, by team
- Items passed between teams and the change since last month
- Teams under five merged, and a group still under five left out
- A script and input checksum that reproduce every figure
Not included
- Any figure for a named person
- Rankings or scores of people
- Judging anyone's effort, performance or conduct
- Time-and-attendance, keystroke, screen or location monitoring
- Changes to your tracker
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
Each month a second run of the script on the same input gives identical counts and medians, and every figure in the view is reproduced.
Evidence: Two runs and the input checksum.
Each month no output holds a figure for a named person or for a group of fewer than five.
Evidence: A search of the outputs for names and a count of group sizes.
Each month the frozen test pack is re-run and every previously passing case still meets its agreed check. A regression fails this check even if reported, and the report lists it first with its cause.
Evidence: The monthly test report.
Nothing was written to any live system by us, and originals are unchanged (checksums match).
Evidence: Checksums before and after, and your own audit trail.
On 20 item histories labelled by your lead and held back until the run, the script gives the expected counts, time open, per-state waiting times and team hand-offs. All 20 must match, and any individual metric, group under five or invented value for a missing date fails the whole test.
Evidence: Your lead's expected values, item histories, script results and rerun steps.
Sign-off. You read the report and test results and accept or send them back in writing. A month counts as delivered only when its agreed acceptance checks pass; receiving a report alone is not acceptance.
If it fails. If we cannot run a month because an input is missing or has changed shape, we say so, explain what we need and do not guess. If the service is not working for you, you can end it at the end of any month.
When it fits, and when we stop
It fits when
- The staff have been told in writing that the view exists, that it is by team only and what it will and will not be used for
- The export has item, team, state and state-change dates, with assignee names replaced by team codes
- A named lead checks the figures each month
- The matching one-off team report has been run, or its conditions hold
We stop and tell you if
- You ask for a figure for one person or a ranking of people
- You want it used to assess performance or conduct
- You do not want the staff to know it exists
- The export has no state-change dates
What could go wrong
The service reads, tests and reports. Ending it leaves your systems and the way you work exactly as they are, and you keep every report we sent.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| The view is used to judge individuals. | No figure for a person exists, teams under five are merged, and a request to use it for performance or conduct stops the service. |
| The staff do not know the view exists. | A copy of the staff notice is a condition of starting, and the service stops if the notice no longer matches the use. |
| Text inside a document, record or message tries to give the automation instructions. | All input text is data. The automation has no tool to send, approve, file or change anything beyond what is listed here, and planted-instruction items must change nothing. |
| Real documents or records pass through a model provider. | First tests use invented, synthetic or redacted data. Real data moves only after a written agreement names the model provider, its country, how long it keeps data and whether it trains on it. |
A separate automated reviewer checks each month's report against the agreed test before it is sent, and your named person decides what to do with it. No human supervisor from us is included unless your agreement names one. At launch the work is largely automated, and we say so.
Stays with a person
- Your named lead checks the figures and decides what to do with them
- You tell the staff about the view and any change to it
Access we would need
- A coded export sent through a secure route agreed in writing
- No login or access to your tracker
Questions
Can I see who is slowest?
No. There is no figure for any person, and a request for one stops the service.
Do my staff have to be told?
Yes. You provide the staff notice before we start; giving notice does not turn this into a legal-compliance guarantee.
Also part of
Send an enquiry
Send us
- Your tracker and roughly how many items a month
- Your teams and their sizes
- Whether the staff have been told. No names in the first enquiry
Later, once you agree
- The monthly export with team codes and current team sizes, using the secure route; 20 labelled test items held back by your lead until the first run and after any rules change
- A copy of the notice the staff were given
- The name of the lead who checks the figures
- The agreement that names the model provider, its country and how long it keeps data, settled before any real personal data is shared
You keep the tracker and decide what to do with the view. We work from a coded export and change nothing; teams under five are merged or omitted. Removing names and grouping teams reduces direct identification but cannot guarantee nobody can infer an individual.
Email fallback: open your mail app
If website submission is unavailable, review and send the fallback email yourself. An email fallback is not a website receipt. Or write to hello@syntheticindustry.ai with “people-team-workload-view-by-team-only-every-month” as the subject.