The Unpriced Outsourcing
How professional requests transfer labour that no budget tracks
A request arrives. It is courteous. It is reasonable. It uses the language of collaboration. It asks for clarification, for validation, for a comparison against records the requester would like to verify against. The recipient reads it, processes it, plans the response, gathers the data or re-derives the explanation, writes a careful reply, and sends it back. The exchange completes. The relationship is preserved.
Somewhere underneath the politeness, a transfer has occurred.
The information being requested often sits already within the requester's reach. A query they could run. A report they have access to. A folder where their credentials apply. The work of producing the answer, however, falls entirely on the respondent. Five minutes the requester avoids. Two hours the respondent absorbs. The asymmetry is the entire mechanism — not a side-effect of busy schedules.
This is one of the most common, and least visible, operating costs inside any organisation of meaningful scale. It appears in no budget. It is not measured. It is not regulated. And in aggregate, it consumes more time than most line items that are.
The architecture of unpriced transfer
The mechanism has four components. Each, in isolation, is unremarkable. The combination is what makes the transfer invisible.
First, the request is formulated in the language of collaboration. Words used include "could you," "would you mind," "just to confirm," "after further analysis." The register signals partnership. The recipient is positioned as a helpful colleague, not as a labour supplier. The framing pre-empts the calculation that would otherwise occur.
Second, the information being requested is at least partially accessible to the requester. Sometimes fully — a report they could pull, a query they could run, a folder where their credentials apply. Sometimes partially — they could obtain it with moderate effort but choose not to. The fact of accessibility is never named in the request. To name it would be to expose the transfer.
Third, the respondent's cost is high. Producing the answer requires recall, re-execution, explanation, or original analysis. The cost is, in most cases, at least an order of magnitude greater than the cost the requester would have absorbed by retrieving the information themselves. Five minutes avoided produces two hours absorbed. The ratio is the architecture.
Fourth, refusal is socially expensive. The request was polite. Saying "you could check this in your own system" reads as confrontational. Saying "this would take me hours, and you could answer it in minutes" reads as mercenary. The norm of collegial cooperation forecloses the calculation that would expose the asymmetry. The respondent absorbs the cost silently, and the transfer completes.
None of these four components is novel. What is rarely named is that all four reliably co-occur in a recognisable class of requests, and that the resulting transfer is essentially unmeasurable from the outside.
Why the cost is invisible
A standard organisational P&L tracks compensation, infrastructure, contracts, vendor spend, travel, occupancy. It does not track time spent absorbing requests whose burden the requester could have absorbed instead. There is no general-ledger code for "labour transferred sideways under the appearance of collaboration." The line item does not exist.
The absence is not an oversight. It is structural, and it has three reinforcing causes.
The transferred labour is fragmented. A single instance of two hours absorbed is not a finance event. It is dispersed across the day, mixed with other work, indistinguishable in retrospect from "normal interruption." Only in aggregate, across hundreds of instances per organisation per week, does the volume become visible — and aggregation requires deliberate measurement, which requires someone to be paying for the cost to be quantified. There is no such party.
The respondent is incentivised to remain silent. Visibility costs the respondent socially. Naming the transfer signals lack of team spirit. Worse, it signals that the respondent is tracking colleagues' requests, which is itself a violation of the norm. The respondent's only safe move is to absorb and continue.
The requester has no signal that the cost exists. From the requester's seat, the request was reasonable and produced the desired output. The cost on the respondent's side is, by design, invisible to the requester. There is no feedback loop that returns the asymmetry to where the decision to ask was made.
The three reinforcing causes form a closed system. The labour is fragmented, so it is not aggregated. It is not aggregated, so it is not measured. It is not measured, so it is not priced. It is not priced, so the requesters who depend on it absorbing silently have no reason to revise their behaviour. And the respondents who absorb it have no language with which to surface the cost without damaging their standing.
The legal contrast
There is one domain where this exact problem has been recognised and structurally addressed for decades. Litigation discovery.
When one party in a legal proceeding requests documents or information from another, the request creates a labour obligation on the responding side. United States Federal Rules of Civil Procedure, Rule 26(b)(1), explicitly require that discovery be "proportional to the needs of the case." The English Civil Procedure Rules contain comparable language. Requesters may seek information. Responding parties may object on the grounds of "undue burden" — that the cost of producing the requested material is disproportionate to its likely usefulness. Courts then weigh the burden against the value, and rule.
The framework is not symmetrical because the requests are not symmetrical. The party absorbing the burden has a formal right to surface it. The party requesting must justify the cost they are imposing. The system codifies the asymmetry as a measurable parameter, not as a social grace.
Inside organisations, no such framework exists. The same kind of exchange — one party demanding work from another — is treated as collegial rather than economic. Proportionality is not a recognised category. "Undue burden" objections, raised softly inside an organisation, are read as obstruction, not as legitimate analysis. The respondent's right to surface the cost is absent by social convention.
This is not because the problem inside organisations is smaller. In aggregate, it is almost certainly larger — there are more daily intra-organisational requests in a large company than there are formal discovery requests in any large litigation. The difference is only that, inside the organisation, the framework that would price the transfer never gets built.
Why the pattern persists
The pattern survives despite costing real money because the people best positioned to surface it are the people least able to. The senior side of the asymmetry has no signal that the cost exists. The junior side has every reason to keep quiet.
It also persists because the alternative — pricing the transfer — would require organisations to measure something they currently treat as moral rather than economic. The norm "we help each other out" is structurally identical, in many cases, to "labour flows downward without metering." Acknowledging the second would corrode the first. Few organisations are willing to corrode the cultural artefact they are using to keep the unpriced flow moving.
So the transfer continues, in millions of small interactions per day, across every layer of every large organisation. The aggregate cost is real. The cost line is missing. And the people absorbing the cost have no vocabulary with which to surface it that does not also damage their position.
The pattern is not concealed. It is named in every interaction in which it occurs, by the words used to dress it. "Could you check." "Would you mind." "After further analysis." These are not deceptive formulations. They are exact descriptions of the transfer being requested. The labour being asked for is, in plain English, in the verb of the request.
What is missing is not transparency at the level of individual exchanges. It is the framework that would make the aggregate visible, costed, and contestable. That framework exists in litigation. It does not exist in enterprise.
When an organisation announces that "collaboration is core to our culture," the question worth asking is which direction the unpriced labour flows. If the flow is broadly symmetrical, the collaboration claim survives. If the flow is systematic and one-directional — and in most organisations it is — then what is being celebrated as collaboration is something else.
It is unpriced outsourcing. It has just not yet been named.