Most billing teams have a general sense of where the manual work lives. The disconnect that someone has to update in two systems. The rate change that requires a verification step before the next cycle. The new install that does not appear in billing until someone notices it is missing. The work gets done, but it adds up, and it creates risk every time it happens.
The swivel-chair score is a diagnostic we use in workflow conversations with providers to put a concrete number on that exposure. It does not require a software audit or a process consultant. You can run it yourself in an afternoon.
What the Swivel-Chair Score Measures
The name comes from the physical motion: an employee turning from one system to another to re-enter or verify data. Every time that happens in a service order workflow, from initial order entry through the first accurate bill, that is one point on the score.
More precisely, count a manual touch any time a person has to:
- Re-enter data that already exists in another system
- Copy information from one screen or application into another
- Visually verify that a record matches across two systems before proceeding
- Manually trigger a step that should follow automatically from a prior action
Do not count steps where data moves between systems automatically, even if a person initiates the workflow. The score is specifically measuring human intervention points, because those are where errors originate and where time gets absorbed.
How to Calculate Your Score
First, pick your three most common service order types. For most rural and regional providers, that is new install, upgrade or plan change, and disconnect. Run the exercise on each one separately, because the scores often differ significantly by order type and the variation is informative.
For each order type:
- Map every step from order entry to the first accurate bill appearing in the billing system.
- At each step, ask: does a person have to manually move, re-enter, or verify data here?
- Mark every step where the answer is yes.
- Count the marks. That is your swivel-chair score for that order type.
Be honest about step 2. A step that requires someone to open a second application to confirm a value counts, even if it only takes thirty seconds. Those thirty seconds, multiplied across hundreds of orders, are where the hours go.
What the Ranges Mean
1 to 2: Well-integrated. Data moves between systems reliably and staff intervention is limited to exception handling. Billing errors tied to order processing are rare.
3 to 4: Moderate exposure. There are manual steps in the workflow, but they are probably contained to specific order types or specific transition points. Worth mapping in detail to understand whether they are fixable process gaps or a reflection of deeper system limitations.
5 to 7: Meaningful exposure. At this range, your billing team is absorbing a significant amount of manual work on routine orders. Errors are not inevitable, but the conditions for them are present on every order that comes through. This is also the range where staff experience and institutional knowledge are doing a lot of the work that integration should be doing.
8 and above: High exposure. At this level, the workflow has likely grown around the systems rather than being supported by them. Manual steps have probably accumulated over time as workarounds to limitations that were never resolved. The risk is not just errors on individual orders. It is that the workflow is dependent on specific people knowing specific things, and that knowledge is not always documented.
What Tends to Drive the Score Up
A few patterns come up consistently in rural and regional telecom operations:
Systems acquired at different times from different vendors. Billing and provisioning platforms that were not designed to work together often require manual bridging. Data that should flow automatically gets moved by people instead.
Workarounds that became standard practice. A manual step that was added to address a one-time problem five years ago is often still in the workflow today. Nobody removed it because nobody documented why it was added, and removing it feels like a risk.
Disconnect-heavy periods. Disconnects tend to have higher swivel-chair scores than installs because the consequences of an error, a customer continuing to be billed for a cancelled service, are visible and generate calls. Teams add verification steps as a safeguard, which adds touches.
Rate or plan changes involving legacy codes. Any order type that touches legacy rate codes or service packages that predate the current billing platform tends to require extra manual handling because the codes were not always migrated cleanly.
Using the Score in a Planning Conversation
The swivel-chair score is useful because it translates a workflow problem into a number, and numbers travel better than descriptions. “Our disconnect workflow has a swivel-chair score of seven” lands differently in a planning meeting than “our disconnect workflow has a lot of manual steps.”
Once you have your scores, a few questions are worth asking:
Which order type has the highest score, and is that the order type with the highest volume? That combination represents your highest concentration of risk.
Where specifically are the manual touches concentrated? If most of the score is in one or two steps, those steps are the starting point for any improvement effort.
Has the score changed over time? If you ran this exercise two years ago and the number is higher now, that is a sign that workarounds are accumulating rather than being resolved.
If you want to take it further, a full billing-to-provisioning workflow audit builds on the swivel-chair score and adds reconciliation steps to help you quantify the actual revenue impact of the gaps you find.
Frequently Asked Questions
Does a high swivel-chair score always mean there is a billing problem?
Not necessarily, but it means the conditions for one are present. A team with strong institutional knowledge and consistent staffing can operate reliably at a higher score than a team that has seen recent turnover. The score measures structural risk, not current performance. The reason it matters is that structural risk does not stay manageable forever.
Can I reduce my swivel-chair score without replacing my billing system?
Sometimes. If the manual touches are concentrated in process gaps rather than system limitations, documentation, workflow redesign, or better use of existing integration features can bring the score down. If the touches exist because two systems genuinely cannot exchange data automatically, that is a system limitation and a process fix will not resolve it.
How often should we recalculate the score?
Any time there is a significant change to your order workflows, your billing platform, your provisioning system, or your service catalog. Outside of those events, once a year is a reasonable baseline. It does not take long once you have done it the first time.
Where to Start
Pick one order type. Map the steps. Count the touches. That exercise alone will tell you more about your billing workflow exposure than most formal audits, and it takes an afternoon rather than weeks.
If the number surprises you, or if you want to talk through what it means for your specific setup, we are here for that conversation.