One of the things I have learned from spending most of my career around compensation and employee benefits is that mature professions become very good at measuring the things they have decided matter. Compensation is no exception. We benchmark salaries against the market, measure internal equity, calculate the value of benefits, analyze incentive plans, retention, participation and employee preferences. Total Rewards statements can tell an employee, sometimes down to the dollar, how much their employer spent on them in a given year.
There is a great deal of sophistication behind all of this, but there is a question we rarely ask: what happened to the value after we delivered it?
That question sits at the heart of Temporal Compensation Theory (TCT), and it led me to what I call the Delivery Assumption: the implicit belief that compensation's obligations end when pay is delivered, that what is delivered is what is received, and that whatever happens to the value afterward belongs to some other discipline.
I don't think anyone consciously decided this. You won't find the Delivery Assumption in a compensation textbook or hear someone teaching it in a Total Rewards course. That is exactly why it matters. The most durable assumptions in any profession are the ones nobody realizes they are making.
You Can See It in What We Measure
Consider the standard compensation toolkit. Salary benchmarking compares what employers deliver. Total Rewards statements calculate what employers deliver. Pay equity analysis compares what different groups receive at a particular moment. Retention analytics ask whether particular combinations of pay and benefits influence whether someone stays or leaves. These are all legitimate and important questions, but they share the same basic frame: the compensation event.
An employer pays $100,000. Another employer pays $105,000. One provides a 5 percent retirement contribution. Another provides 7 percent. One offers equity. Another offers a larger bonus. We can compare those packages with considerable precision.
What we generally cannot answer is a different kind of question: of the value an organization delivered to an employee over ten years, how much purchasing power arrived when that employee needed to use it?
Our instruments are very good at measuring departure. They are much less developed at measuring arrival. That distinction becomes important once we define compensation as the transfer of purchasing power through time.
If compensation is only a transaction, delivery may be a perfectly reasonable endpoint. The employer promised $100,000, paid $100,000 and completed the bargain. But if compensation is a transfer, delivery is not the end of the process. It is one point in a longer journey between the work that created the value and the life in which that value will eventually be used.
The Difference Between Nominal Value and Economic Value
There is a simple example that exposes the problem. Imagine an employee receives a 3 percent raise during a year in which their cost of living rises by 5 percent. From the employer's perspective, compensation increased. The payroll system records a higher salary. The compensation survey records a higher salary. The employee's Total Rewards statement records a higher salary. Nominally, all of that is true. Economically, the employee can purchase less.
Payroll is accurate to the cent, in a unit it does not audit.
TCT calls this the nominal fallacy: treating a change in nominal value as though it represents the same change in economic value. This isn't an argument that employers should somehow guarantee employees against inflation. They cannot. It is an argument about measurement. If the purpose of compensation is to transfer purchasing power in exchange for labor, then nominal delivery tells us only part of what happened.
The longer the intended horizon of the compensation, the more important that distinction becomes. For money intended to pay next week's grocery bill, the gap may be small. For compensation intended to fund retirement thirty years from now, it can become the entire problem.
A Boundary, Not an Error
This is where the history matters. It would be easy to describe the Delivery Assumption as a mistake compensation professionals have been making for decades. I don't think that's fair, and I don't think it's historically accurate.
For much of the twentieth century, treating delivery as the boundary of compensation was a reasonable division of labor. Defined benefit pensions handled much of the long-term journey. Actuaries and investment professionals managed assets, modeled liabilities and pooled longevity risk. Long careers meant that the institution paying the employee and the institution helping provision their retirement were often the same institution.
Compensation could focus on the event because someone else was managing much of what happened after it. The Delivery Assumption was not an error. It was an organizational boundary.
The problem, as I discussed in the previous article, is that the architecture changed. Defined contribution plans moved investment and longevity risk toward individuals. Careers became more mobile. The purchasing power of value carried across decades became more dependent on choices and conditions outside the compensation function. The long-term problem didn't disappear. What changed was who became responsible for solving it.
Where Does Compensation Actually End?
This raises an uncomfortable question. If compensation does not end at payroll, where does it end?
The answer is not that it extends indefinitely. An employer cannot be responsible for every financial decision an employee makes after receiving compensation. If someone spends rather than saves, invests badly, buys a house at the wrong time or works for six other employers, those outcomes cannot reasonably be assigned to the company that once employed them.
TCT draws the boundary somewhere more practical: the employer is responsible for the architecture of the compensation it designs, not for the employee's ultimate financial outcome.
That means asking whether the employer's contribution was appropriate for its intended horizon, whether it was portable, what defaults shaped employee behavior, what risks were embedded in the design and, where value was deliberately intended for future use, what carried that value forward.
The distinction is between architecture and outcome. Employers control the first. They do not control the second. It sounds like a subtle distinction. It changes the question compensation professionals ask. Instead of only asking, "What did we provide?", we can also ask, "What did we design?"
The Question Hidden in the Total Rewards Statement
This is where the Delivery Assumption becomes practical. Imagine looking at a Total Rewards statement showing $150,000 of annual compensation across salary, bonus, health benefits, retirement contributions and perhaps equity. The statement answers an important question: what did the employer deliver this year?
TCT asks us to add another question: what jobs are those different dollars supposed to perform, and over what periods of time?
Some are intended to be consumed almost immediately. Some protect the employee from financial shocks. Some create alignment with the organization. Some may be intended to preserve the value of today's labor for use decades into the future. If those dollars have different destinations in time, evaluating all of them only at delivery starts to look incomplete.
A $10,000 retirement contribution and $10,000 of salary have the same value on the day they are delivered, but they are not solving the same problem. One may be intended for use this year. The other may need to carry purchasing power through thirty years of inflation, market cycles, job changes and changing financial circumstances before it performs the job for which it was designed.
The amount matters, but so does the journey.
A Small Change in the Question
Temporal Compensation Theory doesn't require the compensation profession to abandon the tools it already has. Most of them remain essential. The change is smaller than that. It asks us to stop treating delivery as the only moment that matters.
That means supplementing the questions we already ask. What is the market rate? Is the package competitive? Is it equitable? Does it motivate? Does it retain? Then we add one more: how effectively does this compensation carry the value of an employee's labor to the point in time when it is intended to be used?
That question doesn't have a simple answer yet. In many cases, we don't even have the measurements required to answer it. But asking it changes what we notice. It turns portability from an administrative feature into a design question. It makes the time horizon of compensation relevant. It makes defaults more important. Eventually, it forces us to consider whether the thing carrying deferred value matters too.
Above all, it shifts our attention from a single transaction to something much larger: the employee's compensation journey. That's where I'll go next.