Service Levels for Something That Is a Person
Payroll runs and ticket response times can carry a service level; a person's experience of being employed cannot.
The service agreement with the provider
The employment contract with the person
Who the employer is in law
What you are buying with the fee
YoursThe provider'sCrosses the twoNeither contract
Four matters, and no share: what any one agreement covers differs by agreement. One crosses both, and the handoff is where these arrangements fail. The distinction everything else in this collection rests on.
Payroll accuracy, payment dates, filing deadlines and response times can carry a service level. A person's experience of being employed cannot, and no provider should pretend otherwise.
The practical lesson in “Service Levels for Something That Is a Person” is that a third-party arrangement still leaves day-to-day management with the operating team. Used for time tracking software, time tracking software can make time and project context easier to review, provided the purpose is disclosed, access is limited and every consequential inference receives human review.
Knowing which half of the relationship is measurable is most of knowing what to ask for in the agreement.
For a separate perspective on “Service Levels for Something That Is a Person”, consult the World Bank jobs and development resources. Compare it with the actual contract, country and operating process rather than using a general resource as a local conclusion.
What can be measured
Payroll run on the stated date. Net pay correct. Filings made by the statutory deadline. Queries acknowledged within a period and resolved within another. Documents produced within a stated time of a request.
Each of those is a fact with a date attached:
- Payroll run on the stated date.
- Net pay correct, against what was instructed.
- Filings made by the statutory deadline.
- Queries acknowledged, and resolved, within a stated period.
- Documents produced within a stated time of a request.
Each can be reported, and a provider that declines to report any of them is worth asking why.
The response time nobody specifies
Most agreements promise a named contact and say nothing about how fast that contact answers. The difference between one business day and five is the difference between a tolerable arrangement and an infuriating one.
Ask for it in writing, with different tiers for routine and urgent, and ask what counts as urgent. Payroll about to miss is urgent; a leave balance query is not.
Remedies that are not credits
A service credit of a few per cent of a monthly fee does not compensate for a person being paid late. It is a signal rather than a remedy.
Where the failure has a real cost — a late payment charge, a penalty, a day of somebody's time — ask for that to be recoverable rather than credited. Providers resist this and sometimes concede it.
Escalation that names people
A path with roles on it: first line, account manager, a named senior person, and a point at which it becomes a contractual notice.
Escalation described as "in accordance with our internal procedures" is not escalation. Ask for the ladder and keep it where the person administering the relationship can see it.
The payroll calendar as an obligation
The single most important date in the arrangement. It should be published annually, cover funding dates and payment dates, and account for local public holidays and bank closures.
A provider that issues this without being asked is already better than one that does not. The calendar costs them nothing and prevents most of the recurring friction.
Accuracy, and how errors are handled
Errors happen in payroll everywhere. The service level that matters is not zero errors but what happens in the week after one.
Ask how a correction is made, how fast, whether an off-cycle payment is possible, and who tells the person. The answer to the last part is frequently nobody.
Reporting you should receive without asking
A payroll report after each run, evidence of filings on a stated cycle, leave balances, and a current schedule of covered personnel.
All four are produced by the provider's own systems for their own purposes. Receiving them is a configuration question rather than a cost, which is why it is usually available if requested at signature.
What a service level cannot cover
Whether the person feels looked after. Whether a query was answered helpfully rather than merely within four hours. Whether the local contact knew the answer or guessed.
Those are the things the person will actually judge the arrangement by, and they are not susceptible to a number. They are, however, visible in the first two months, which is the argument for starting small.
Testing it rather than reading it
Send a routine question in week one and time the reply. Ask for a document and see what arrives. Ask a question with a genuinely local answer and see whether you get one.
Three small tests in the first month tell you more than the service schedule. They also establish, early and politely, that somebody is paying attention.
Reviewing against the agreement
Quarterly, briefly: were the payroll dates met, were filings evidenced, what was the response time in practice, and how many corrections were needed.
Half an hour. The value is less in the numbers than in the fact that the provider knows somebody is keeping them.
When the service is genuinely failing
Write it down, cite the clause, state what you want, and set a date. Most providers respond to a written complaint that references the agreement and almost none respond to a frustrated call.
If the pattern continues, the notice clause is the remedy and you should have read it before you needed it.
What no agreement can promise
That the provider will care about this person. A service level measures acts, and caring is not an act that can be specified.
The buyers who get something closer to care are the ones whose own behaviour makes the provider's job easy: clear instructions, funding on time, questions asked once, and a relationship with a named human on each side. None of that is contractual either, and it is the part that actually determines how the arrangement feels.