Partition buyer, supplier and joint obligations across phases
7 min read
Lesson objectives
- Make a documented decision on partition buyer, supplier and joint obligations across phases with evidence and limits.
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
A contract can run into trouble before the supplier fails at any delivery task. Operations wants a firm start date, but the buyer has not prepared access permissions or asset data the supplier needs. A register field saying only “owner: supplier” makes every day of delay look like supplier failure. A field saying only “joint responsibility” tells no one what action is due next. The skill in this lesson is to break a delivery chain into separate acts and dependencies, then build a timeline that shows where work actually stopped.
Distinguish four things: the supplier’s action, the buyer’s action, the dependency between them, and the shared result both want. A shared result does not erase each party’s separate action. In the building-maintenance case, the supplier might have to provide a technician list before mobilisation, while the buyer might have to issue access passes after receiving a complete list. The supplier cannot enter without a pass; the buyer cannot issue a pass without sufficient information. That logical dependency does not, by itself, establish breach by either party in a real contract. The executed wording and evidence would govern the analysis.
Break the obligation into a five-column “operating chain”: input, provider, deadline, evidence, and activity blocked when the input is missing. A technician list is an input to the pass request; a pass is an input to the first visit; a visit record is an input to mobilisation acceptance. The final column helps prioritise. A missing list for an ordinary site may defer one task. A missing pass for a critical cooling site may threaten continuity. The documents may share a name, but their consequences are different.
Define what “complete” means for each input. A technician list missing identification required by the agreed access process cannot produce passes, even if a file arrived on time. Conversely, the buyer might object to a file format not specified anywhere and irrelevant to the decision. That objection deserves review rather than automatic attribution of supplier failure. Give operational acceptance a clear test and record the reason and date of any rejection. Where a test has not been agreed, do not add it to the contract unilaterally; seek a decision from those with authority.
Use an event timeline rather than the single sentence “the supplier was five days late.” Start with the due date, then submission, inspection, request for completion, completed submission, permission, and work enabled by permission. Separate total elapsed time from the periods during which each party could act. This is a management diagnostic, not a legal damages formula. Workstreams may overlap, so adding every delay as though they were sequential would overstate the effect.
The buyer also needs an internal verification control. A manager receiving an access-pass request should not wait until launch day to discover that security approval is required. Set an earlier operating checkpoint and a warning measure, for example, “all critical technician lists received and checked three days before go-live.” This measure tests the dependency chain. It is not necessarily a new contractual supplier deadline. Keep “contractual condition” separate from “internal control” in the register, so a dashboard or email does not quietly turn a local process target into an asserted contractual duty.
Lesson summary
If the buyer sent isolation maps on 22 May, receipt still matters. Did they reach the agreed contact channel or an absent employee? “Sent” and “received” may be different events under case documents. Put both on the timeline and inspect acknowledgement and version logs. If correct maps reached the agreed channel on 22 May but the supplier used an old copy on 24 May, supplier version control becomes a stronger explanation. If the maps went to an unagreed channel and reached planners only on 26 May, the supplier’s opportunity to revise changes. Neither branch creates a legal finding here; each identifies the evidence that would resolve the cause.