The One Who Asks, and Those Who Do Not

Treat one pay query as a question about everybody on the same arrangement. Almost every wage error is produced by a setting, and a setting applies to a group — so a single person asking why their overtime looks low is not an individual query; it is the first visible instance of something that is either affecting a population or is not.

The correction process in “The One Who Asks, and Those Who Do Not” requires a visible history rather than an overwritten total. If how teams evaluate monitask pricing supports monitask pricing, administrators should test amendment, approval and export workflows so a later review can distinguish the original entry, the question asked, the correction and the person who accepted it.

Which of those it is takes one query to establish, and establishing it before answering the individual changes what you say to them.

For an independent reference relevant to “The One Who Asks, and Those Who Do Not”, consult the monday.com work-management resources. Use it to test record quality, working-time definitions, access, retention and exception handling against the organisation’s real payroll process.

The first response

Acknowledge the same day, say who is looking at it, and give a date. Then run the check across the group before replying substantively.

If the answer is that the individual's figure is correct, say so with the working. If it is not, the answer involves more people than the one who asked, and that changes who needs to be involved in the reply.

Why correcting only the complainant is the wrong move

It is the instinctive response, it is fast, and it creates three problems.

• The error continues for everybody else, and the organisation now knows it.
• Two people doing the same job are paid differently for the same weeks.
• The organisation has a record showing it identified an issue and corrected one case.

The third is the one that is hard to explain afterwards. A correction made for one person is evidence that the error was recognised, and the decision not to extend it was taken knowingly.

The ones who do not ask

Most people do not query their pay, for reasons that have nothing to do with whether it is right: they cannot tell from the statement, they do not want the attention, they assume the system is correct, or they expect the query to go nowhere.

That is why the query log is a poor measure of accuracy. The organisations with the fewest queries are sometimes the ones where asking is hardest, and the distribution of queries across sites is usually more informative than the total.

Making it safe to ask

1. Publish a route that does not go through the line manager, as an option.
2. Say explicitly that raising a pay question will not cause any difficulty.
3. Respond within a stated time, and meet it.
4. Tell the person the outcome even when the answer is that the figure was right.
5. Explain the working, rather than asserting the conclusion.
6. Record the query and the outcome.

Step four is skipped constantly. A query that is investigated, found to be correct and never answered teaches the person that asking achieves nothing, which is the mechanism by which an organisation acquires a low query rate.

Where the query comes through somebody else

A query raised by a representative, an adviser or a solicitor is the same question and should get the same investigation. What changes is the handling: the response is more formal, it is worth taking advice earlier, and nothing should be corrected piecemeal while it is live.

What should not change is the population check. The question is still about a setting.

Patterns in who asks

Queries cluster: one site, one shift pattern, one pay group. That clustering is nearly always about the pay arrangement rather than about the people.

Look at pay queries by group rather than by individual. A pay group generating three times the queries of a comparable one is describing a configuration or a statement problem, not a difficult workforce.

The query that is about something else

Some pay queries are not about pay. Somebody asking repeatedly about small discrepancies may be raising something they cannot say directly — about a manager, a rota, or how hours are being allocated.

That is worth noticing without over-interpreting. The pay question still gets answered properly; the pattern is worth a separate, gentler conversation, because a sequence of queries from one person about trivial amounts is usually a signal about something.

Keeping a record of the answer

Every query should end with a written answer to the person, even when the conclusion is that the figure was right.

That record serves two purposes: the person has something to refer to, and the organisation can show what it said if the same question returns. Verbal answers to pay queries are the ones that get remembered differently by the two parties, which is how a resolved query becomes a dispute six months later.

The one that turns out to be right

Some proportion of queries are correct and finding one should be treated as useful rather than as a failure. The person has done, for free, what the tests described elsewhere on this site are meant to do on a schedule.

An organisation that responds to a correct query by thanking the person, correcting it for everybody and saying so, gets more of them — which is the outcome it should want, because each one is an error found early.