Return to the employee with the unfinished inventory. His manager now asks him to come in over the weekend for a review. The company has paid him on time, the manager points out. Surely he can cooperate. He does not want to sound ungrateful. Yet payment and this particular instruction do not seem to be the same question.

The point is not to deny exchange or the conditions an actual agreement may establish between payment and performance. It is to ask what disappears when ‘we have already given you something’ begins to justify every subsequent demand. A general balance sheet can conceal the details that determine what a relationship actually permits.

Two directions do not make one universal bargain

One line runs from the company toward the employee: the applicable arrangement gives it a basis for requiring the inventory. Another may run from the employee toward the company: his position gives him a basis for requiring agreed payment and specified working conditions. Both lines need their own grounds. Neither acquires unlimited content because the other exists.

Paying everything agreed does not establish an entitlement to every possible task. A missed payment does not, merely by occurring, tell us that every demand running in the opposite direction has vanished. A particular agreement may make one performance conditional on another. That connection must be identified within the arrangement, not supplied by a universal formula exchanging rights for obedience.

This is not advice to keep working without pay, or a ruling about any actual employment contract. It rejects two shortcuts: I met this requirement, therefore I may demand anything; you failed that requirement, therefore no distinctions remain to be made. Remedies and protective arrangements need real grounds. They cannot be settled by either slogan.

The organization also needs a careful description. In this account, a company can be the address to which a demand is attributed and the address from which an answer is due. The work still happens through people and procedures. Saying that ‘the company decided’ cannot erase the decisions of the people exercising the relevant authority.

The reverse mistake is just as serious. An organizational failure does not establish that the receptionist, the new manager, or every ordinary employee personally committed the same failure. Work being carried out through people is one question. The independent grounds on which a particular person must answer or face consequences are another. An organization must be neither a shield for established personal accountability nor a device for placing an entire failure on the nearest available person.

An organization does not acquire a person's first-person life in order to answer for an arrangement. Nor does its lack of that life exempt it from answering. If a requirement reaches through the organization to a particular individual, that person's protections must be examined there. Organizational attribution cannot absorb the human boundary that the requirement actually encounters.

Having your position changed is not the same as being at fault

Everyday talk of responsibility often already means fault: who caused the problem, who must pay, who deserves blame? The source paper separates out a narrower relation. Someone's power can alter your relational position even when it has not placed a specific task before you. It uses liability in this stipulated sense, not as a definition of every ordinary or legal use of that word.

Imagine an internal appointment being changed through an authorized procedure. The person affected need not have failed at anything, and the change need not ask them to perform a task. Being exposed to a change in position is therefore distinguishable from carrying a particular demand for an answer. The first can exist without the second having been filled with content.

The inventory requirement adds that content. It identifies what is asked, where it applies, and what would fulfill it, and it becomes operative for this appointment. The employee now carries something to answer. Actually completing the inventory is another step. A position subject to alteration, a particular demand within it, and a performance that answers the demand cannot all be compressed into ‘responsibility.’

These distinctions earn their place by preventing premature judgments. A change in someone's position does not establish their fault. An unfinished item does not establish culpable nonperformance without attention to its terms and circumstances. Before passing judgment, we have to identify whether the change concerns a position, a requirement, or an act.

Suppose the company closes access to an old system while the employee is preparing the handover. Two facts must be preserved: access was blocked, and the delivery did not occur. Those facts alone establish neither his fault nor an automatic exemption from every possible consequence. Who was to provide access, whether another route existed, and whether the requirement changed remain separate questions.

Nor does an obstructed task automatically create a new kind of right called the right to fulfill one's accountability. A protected interest or right may indeed be affected: the employee's, the recipient's, or somebody else's. Its grounds must be established independently. Renaming a burden as an asset does not identify what needs protection.

Classification does not supply justification

Now suppose the weekend review does have an identifiable source, scope, and place within the employee's actual appointment. We still do not know whether it will help him understand his work or merely assemble a file that can later be used against him. Identifying how a demand operates does not answer what it is doing to the person who carries it.

Neither does preserving a minimum opportunity to object or leave prove that everything within the relationship is acceptable. A demand can exceed the role or damage a person's basic rights long before all their standing has been destroyed. We must not wait until someone has lost every possible position from which to say no before recognizing an intrusion.

At the other boundary, if the person's standing to respond, refuse, or withdraw has been erased, or the relevant grounds and operating conditions no longer hold, continued pressure cannot preserve a demand's identity merely by remaining effective. It may have become bare force; it may have failed in another way. Which description applies needs evidence. The absence of accountability does not itself prove the presence of coercion.

The classification therefore supplies no endorsement. Changing the classification supplies no practical rescue either. An intrusive requirement may still exert pressure. If the employee refuses it, non-delivery is a fact, not an already completed finding of dereliction. We have to continue examining the demand rather than use its name to end the inquiry.

Consider another familiar phrase: greater power naturally brings greater responsibility. It can express a direction worth pursuing in institutional design. It is not an automatic law describing every organization. A position may exercise substantial authority while facing weak requirements to explain, answer questions, or correct its decisions. Calling the missing accountability natural will not put it into place.

The employee and manager therefore need a more particular conversation. What makes this review applicable? Which hours does it claim? Who can question its purpose? Which conditions need to be changed? Some of the work may be worth doing carefully. Some arrangements may need revision. Some objections must remain available even where a demand is operative.

No single word needs to do every job. Acknowledging that a demand has really reached you can help you face it accurately. It must not give the demand permanent immunity from being questioned.