Priced before anybody had seen the site.

What the item is actually for

The construction management literature treats mobilisation as a financing question, and once you read it that way the item stops looking like a payment for work.

A contractor spends heavily at the start and gets paid in arrears. The gap between those two curves is financed by somebody, and where there's no mobilisation item it's financed by the contractor, out of an overdraft, at a contractor's borrowing rate.

Provide the item and the owner takes that financing on instead, at the owner's rate. An owner borrows against a balance sheet a contractor can't match, so moving the interest there lowers what the project costs in total. It isn't a concession and it isn't generosity. It is a rational transfer of interest cost to whoever borrows more cheaply.

The legitimate version of unbalancing

The same literature puts a related practice alongside it: unbalancing a bid, in which early items are priced high and later ones low so that money arrives sooner. It produces front-end loading, and where it is blatant an owner can ask a bidder to justify the prices or reject the bid outright.

A mobilisation item is the sanctioned form of the same effect. It moves money to the front, on purpose, with everybody's agreement, which is why it exists as a named item rather than being hidden inside a rate.

The difference between the two isn't the cash flow. It is that one of them is visible and can be discussed, and the other has to be detected.

Worth knowing because it explains the negotiation around it. Arguments about the size of a mobilisation item are arguments about financing, and they are conducted in the language of work. Cost & Cash Week 16 takes the curves apart properly. What matters here is that the item is settled at tender, by people optimising cash, and lands on people optimising a sequence.

One number, no sequence

Here is the delivery consequence, and it follows from the item being one line.

A lump sum carries a price and nothing else. It contains no logic, no durations, no dependencies, and no statement of what has to be finished before what. So the thing that has to happen first on the project is the thing with the least planning attached to it.

And it has real internal sequence. Power has a lead time and an application. A road wants drainage before it is trafficked. Offices need power and a foundation. Security has to exist before anything valuable is delivered. Every one of those is a dependency, and none of them is anywhere.

The result is a start that runs on somebody's judgement. It works — sites do get built — and it isn't repeatable, and it leaves no record of why anything happened in the order it did.

That's the same shape as the joins in week 12: a thing performed correctly by a person, holding together something no document holds together, and running exactly as long as the person does.

Paid on a milestone that isn't readiness

The item is released against something — a percentage of the sum, a date, an event described in a schedule of payments.

Whatever that trigger is, it was written to be administratively checkable rather than to describe a site that is ready to work. Somebody has to be able to certify it from a desk, which rules out anything requiring a walk round. So the money can arrive before the site functions, or after it has been functioning for a month, and neither tells you anything about the actual state of the place.

Which creates a reporting trap worth avoiding. Mobilisation reported against payment looks complete when the payment condition is met. Mobilisation reported against readiness — is there power, is there water, can a delivery be received, is there somewhere to put it — gives a different answer, and it is the answer the next six months depend on.

The round trip priced once

One more thing hides in the item, and it surfaces during a suspension.

Stopping work for an extended period forces a demobilise-remobilise cycle: plant off, people released, then everything back again, against labour and material prices that have moved in the meantime.

That cycle was priced once, at tender, on the assumption of a single arrival. A project that mobilises, suspends and remobilises has paid for one and performed two, and the difference is a cost with no bill item behind it.

It doesn't stop at plant and people either. A supervisor released to another job may not come back; a subcontractor who stood down has taken work elsewhere and returns at a different price or not at all. What restarts isn't the team that stopped.

Which is worth knowing before a suspension is agreed rather than afterwards, because the decision to suspend gets taken on the visible cost of standing still and the invisible one is the round trip.

System design

Row five is the one that has nothing to do with mobilisation and belongs here anyway, because the day of access is the only day it can be produced. A site recorded before anything is changed settles arguments that will otherwise be conducted from photographs taken for other reasons.

Record	Produced by	Required quality	Verified against	Feeds
Mobilisation item	The estimator, at tender	States what the sum was priced to cover, item by item	The bill it sits in	What can be bought without a variation
Breakdown into things that must exist	You, in the first fortnight	Dependency, obtaining time and buyer against every line	What is physically on site	The sequence the lump sum omitted
Utility applications	Whoever lodges them	Dated on lodging, because the queue is outside your control	The utility’s acknowledgement	Whether a generator is needed
Readiness list	Site, weekly	Reports what functions, separately from what has been paid	Walking the site	Whether work can actually start
Site as handed over	Both parties, on the day of access	Condition and extent recorded before anything is changed	The contract’s access provisions	Every later argument about the site

Row two exists because a lump sum can't hold a network. Everything the estimator knew about what the item covers is in their build-up, which stays inside the bidding organisation, and everything the site needs to know about sequence has to be rebuilt from the ground up.

Practical insight

Break your mobilisation item into a list in your first fortnight, before you order anything.

One line per thing that has to exist: your access road, the gate and fence, the power supply and its application, water, drainage, offices, welfare, the store, the laydown area, security, waste, first aid, IT. Against each, three columns — what it depends on, how long you need to obtain it, and who is buying it.

Fourteen lines, and you will be the only person holding them together.

The second column is the one that catches people. A power connection is an application to a utility, and the utility has a queue that has nothing to do with your programme. Discovering that in week two is a problem you can plan around; discovering it in week ten is a generator nobody budgeted for.

Then report your mobilisation against that list rather than against the payment. It costs one line in the monthly report — how many of the items exist — and it is the only honest statement anybody on the project will make about whether the site is ready. The payment certificate will say something different, and both statements will be right.

Key takeaways

• Before anything can be built, a site has to be built, and that work appears in a bill as a lump sum item.
• The number was set by an estimator without a site visit or a layout, so the plan has to fit a price that preceded it.
• A mobilisation item is a financing instrument: it moves the start-up overdraft from the contractor to the owner.
• Since an owner borrows against a balance sheet a contractor can't match, the item lowers the total cost of the project rather than being a concession.
• It is the sanctioned version of unbalancing a bid, which achieves the same front-end loading without agreement.
• So arguments about its size are arguments about financing, conducted in the language of work.
• A lump sum carries a price and no logic, no durations and no dependencies.
• Yet mobilisation has real internal sequence — power before offices, drainage before a road is trafficked, security before deliveries.
• The payment trigger was written to be administratively checkable, not to describe a site that works.
• Reporting mobilisation against payment and against readiness give different answers, and the second is the one that matters.
• A suspension forces a demobilise-remobilise round trip that was priced once and performed twice.

Records born here. The mobilisation item and what it was priced to cover · the breakdown into things that must exist · the utility applications, with the dates they were lodged · the readiness list, reported separately from the payment · the payment trigger and what it actually tests · the site as handed over, recorded on the day of access.

What is coming next

Once the people and the plant are arriving, the site has to be arranged, and the arrangement is a design nobody calls one.

Where things are stored decides how far they are carried. Where a crane stands decides what it can reach for the next two years. A haul route decides which areas can be worked while others are being built. And the temporary works that make all of it possible have their own engineering, their own approvals, and lead times of their own.