Job people-team-workload-and-waiting-times-report-from-your-tracker-export · revised 12 October 2026
See open work and waiting times by team from your tracker export, never by person
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.
You might be seeing
- Items sit for weeks in one state and nobody knows why
- People argue about workload from anecdote
No passwords, keys, card details or admin invites needed to start.
What usually happened
Trackers hold the data on where work waits, but reports built on them tend to rank individuals, which damages trust and misleads. A report by team shows queues and where work passes between teams without judging anyone.
Who it’s for: Manager or founder who wants to know where work is waiting without watching individuals.
Usually starts when: Work is late and nobody can say whether a team is overloaded or items are waiting on another team.
The result: From your tracker export you receive open items, how long they have been open, median waiting time per state and items passed between teams, shown by team only. Names are removed before sending, teams of fewer than five are merged, and no figure is given for any person. Every figure is reproduced by a script you can re-run.
Check whether this job fits
Answer these without sending files, logins or personal data. Nothing is submitted unless you choose to contact us.
What you get
- The team report
- The script and input checksum
- The merged-team list
- A note on items with missing dates
Included
- One tracker export of up to 5,000 items
- Counts, time open and median waiting time per state, by team
- Items passed from one team to another
- Teams of fewer than five people merged into one group, 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
- Judgement of anyone's effort or performance
- Changes to your tracker
- Time-and-attendance monitoring
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
Every figure in the report is reproduced exactly by running the delivered script a second time on the same input, with a matching checksum.
Evidence: Both outputs and the input checksum.
Your lead traces 20 random items back to the tracker and finds each state and date correct.
Evidence: Your marked sample.
A search of the report for assignee names or person codes finds none, every team of fewer than five is listed as merged, and any merged group still under five is left out and listed.
Evidence: The search result and the merged-team list.
Sign-off. Your team lead checks the sample and signs off in writing. The report describes queues at one date and says nothing about any person. Payment follows sign-off.
If it fails. If a test is not met, you do not pay for this fixed scope. We hand over what we found and agree whether to stop or re-quote; no surprise work.
When it fits, and when we stop
It fits when
- The export has item, team, state, state-change dates and the team at each change (without that, items passed between teams are listed as not covered)
- Assignee names are replaced by team codes before sending
- Your team leads know the report exists and how it is used
- A named lead checks the figures
We stop and tell you if
- You ask for a figure for one person or for a ranking of people
- The export has no state-change dates
- You want it used to assess performance or conduct
What could go wrong
This job reads files you send and writes a report. It changes nothing in your systems, so there is nothing to revert. Our copies of your files are deleted when the job ends.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| The report is used to judge individuals. | No person figure exists in it, small teams are merged, and we stop the job if asked to rank people. |
| A team figure points to one person. | Teams of fewer than five are merged, and the report lists which were merged. |
| Staff feel watched. | Your team leads are told what the report contains before it is made, and the report says what it does not measure. |
A separate automated reviewer checks every output against the agreed test before hand-over. No person on our side reviews unless your agreement names one. Your named team lead approves what is used.
How we deliver
We arrange the work and independent review, then show you the result against the agreed checks. You keep authority over your systems.
- Agree the states, the team list and the merge rule for small teams
- Replace assignee names with team codes before the export is sent
- Compute counts, ages and median waits by script
- Merge teams of fewer than five and list the merged groups
- Separate automated review; twenty items traced back to the tracker
- Hand over the report and script; delete our copies
This is a one-off job, not emergency cover or a subscription. We confirm eligibility, the total price, a start window and a delivery date before you accept, and an enquiry creates no charge or booking. Work starts only after agreed inputs, secure access and any needed permissions are in place.
Need to keep it working?
Discuss a monthly repeat of the report.
Ongoing work is separately scoped and quoted: no monitoring, response-time guarantee or automatic subscription is included in this job.
Explore an ongoing managed lane, or mention the responsibility you need in your enquiry.
What you can check
This is a new service. We have not delivered this job for a client yet.
Other ways to get this done
- Most trackers offer cycle-time charts of their own; try those before buying anything.
- A pivot table of state-change dates gives waiting times in a spreadsheet.
Questions
Can I see who is slowest?
No. The report is by team and we do not produce figures for one person.
Is this employee monitoring?
No. It shows where work waits between teams, with names removed. We stop if asked to measure a person.
Can I re-run it myself?
Yes. You get the script and the input checksum.
Send an enquiry
Send us
- Your tracker and roughly how many items a month
- Your teams and their sizes
- The states an item moves through
Later, once you agree
- The export with assignee names replaced by team codes, through an agreed secure route
- The team list with sizes
- 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 report. We work from a coded export and change nothing. Teams of fewer than five are merged so no figure points at one person.
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-and-waiting-times-report-from-your-tracker-export” as the subject.