Remobilization: the trip you claim, and the trip you eat

Four of our trade pages describe the same loss, in four trades’ words.

Acoustical ceilings: the release comes in half-areas, and half an area costs a whole mobilization. Paving: one parking lot, four phases, and a contract that pays to mobilize once. Millwork: punch is a thousand small items, each one a trip. Drywall says what all three mean — every return trip is mobilization you did not bid.

That is remobilization. Your bid assumed a continuous run at a ready area. The job gave you a quarter of it in March, half in June, and a corridor in September. Nothing about your scope changed. What it costs you to deliver that scope went up by a number nobody wrote down.

This is how to find that number, decide which trips you can actually claim, and settle the question before you sign instead of after the third trip.

What a return trip actually costs

Most subs price a remobilization at the mileage. The mileage is the smallest line in it.

The trip. Truck, fuel, tolls, and paid drive time for everybody in it. A four-man crew driving an hour each way is a man-day gone before a tool comes out.

The gear. Scissor lift re-delivery and pickup. Scaffold erected a second time. Compressors, welders, saws, the gang box. On the trades where equipment is a business running inside the business, this line alone can be bigger than the labor.

The first two hours. Nobody is productive on the morning of a return. Find the area, find the power, find the stock, re-run the layout, re-read the drawing revision that changed while you were away, locate the cut list somebody took home. Those hours are real and they are in nobody’s unit rate.

The supervision. A foreman splitting a day between two jobs does not give you two half-days of production. The hours get charged to a job; the output does not arrive in proportion.

The material. A partial-area return means a partial order, which means delivery minimums, a second haul, and a pile of remainder that gets damaged or walks off before trip three.

The office. Someone rescheduled the crew, told the GC, chased the release, and wrote the ticket. That is overhead you already pay for, consumed by a trip you did not bid.

Put your own number on it once, with your real burden rate applied, and keep it on a card. A trade with a four-man crew, a lift and an hour of windshield time in each direction can be most of a crew day down before the first board, pipe or tile goes in. You do not need a study. You need one number you are willing to say out loud to a project manager.

The reason it has to be written down is that it hides. A remobilization never arrives as an invoice — it arrives as labor hours on a job, indistinguishable from production hours. On your cost report it looks like a crew that got slower. That is exactly the distortion the units-per-hour ratio exists to catch: same scope, same crew, more hours, and the cause is trips, not people.

The first trip is bid, the second gets eaten, the third gets claimed

There is a pattern to this and it is remarkably consistent.

Trip one is the one you priced. No argument.

Trip two gets absorbed. It looks like ordinary coordination — the electrician was not finished, the frames were not set, the floor was not ready. Nearly every subcontract has language about cooperating with other trades, and trip two looks like exactly that. So nobody writes anything down.

Trip three is when somebody in the office notices the labor and starts asking. By then there is no record of trips one and two, so the claim that goes out covers one trip of three and arrives without dates. It gets denied, and the denial is reasonable: you are asking to be paid for a pattern you cannot evidence.

The fix is not arguing harder about trip three. It is recording trip two on the day it happens, when nobody is in a dispute, when the foreman still remembers who told him the area was ready, and when a photo of the area is still a photo of that day’s condition.

Four kinds of return trip, and only two of them usually pay

Sort every return into one of four buckets before you try to bill anything. The bucket decides the route.

1. Sequencing inside your own scope. You knew the walls could not close until rough-in passed. You priced a leave-and-return. Drywall’s version is exact: you cannot close a wall the electrician has not finished, or rock around a frame the door sub has not set. That trip is yours. Log it anyway, so the ones that are not yours have something to be compared against.

2. A directed partial release. The GC hands you a half-area, one floor out of four, a quadrant of a parking lot, a corridor at night. Your bid assumed a continuous release and the direction changed it. This is usually the bucket with the most money in it and the one most often left on the table, because a release is a verbal instruction nobody treats as a direction. It travels as a change event and then, if it is recoverable, as a change order.

3. Somebody else’s damage or rework. Painting’s line is the whole bucket: you come back four times for damage you did not cause. So is paving’s — the binder course spent six months as the site’s haul road and now you are expected to surface over the dents. This is recoverable cost with a name on it: a back charge to the trade if you have privity with them, or a change event to the GC if you do not.

4. Punch and warranty. Punch is work inside your contract, so those trips are yours — which is why the punch list process is worth running tightly rather than generously. A callback after your scope has been accepted is a different obligation with a different answer, and it is covered in warranty callbacks.

Two buckets can pay and two usually do not. The expensive mistake is not misjudging a bucket. It is failing to sort, which turns all four into one undifferentiated labor overrun.

The three numbers a remobilization claim is made of

A claim that gets paid has all three. A claim that gets denied is usually missing the second or the third.

A count. How many mobilizations your bid included, per area or per building. State it in your proposal even when the contract is silent, because the moment it is written anywhere, trip four becomes arithmetic instead of opinion.

A rate. What one additional trip costs you, from the list above. Not a guess produced under pressure in month nine.

A date per trip. Which day the crew went, which area, how many people, how many hours, and who released it. This is the one that is only ever available if somebody captured it that week.

The sentence to settle before you sign

This is a negotiation item, not an argument item. Four things are worth asking for while you still have leverage, and all four are ordinary asks.

A stated number of mobilizations in the base scope. “Price includes two mobilizations per building” costs nothing to write and settles most of the argument before it starts.

A unit price for each additional mobilization. Agreed before signature, it becomes a measured quantity at a rate. Agreed after trip three, it becomes a fight.

A definition of a release. What has to be true for an area to count as released to you — continuous, accessible, a minimum size, predecessor trades signed off. A trade whose crews are sized for a floor should not have “an area” turn out to mean a room.

A notice route. Who you tell, and within how many days. The shortest clause in most subcontracts is the one that kills claims, and it belongs in the same pass as every other gating term — which is what the subcontract scope review is for.

This article is general information, not legal advice. Whether an additional mobilization is compensable, what notice is required, and what counts as a release on your job are set by your subcontract and the law where you work; have an attorney read yours.

The habit for when it happens anyway

Most of the time you will not get the clause, and the trips will happen. Four things, each small enough that a foreman will actually do them.

On the day you are turned away or handed a partial area, it goes in that day’s log with the cause named — access, or GC direction — and the area written in the GC’s own words. Photograph the condition you found. A photo of an area that was not ready is worth more than a paragraph about it.

Within your notice window, it becomes a change event, with the name of whoever directed it and the date they did. Not a change order. A dated record that a change happened, created while the facts are still cheap.

When the GC wants the trip taken now and priced later, that is what a signed T&M tag is for. Taken now and priced never is how most of this money disappears.

Never let trip three be the first written record. If you keep one thing from this page, keep that one.

How SubMark handles it

Start with what is not there. SubMark does not count mobilizations. There is no trip counter, no return-trip alert, no mobilization field on a job, and nothing that tells you a crew has been to the second floor four times. If you want that count, it comes out of your logs.

What SubMark holds is the record a claim gets assembled from.

Change events, dated the day you create them, with a Directive / Reference. A change event records a description, labor estimated in days by trade, a material description and cost, and photos — plus one field that matters more than its size suggests: Directive / Reference, prompted with RFI #, bulletin, or who directed it + date. That is the entitlement hook, and on a remobilization it is the whole argument: an area released in halves, by a named person, on a named date. It carries across when the event becomes a change order, and it prints on the change-order PDF under Reference as Directive / Ref. It is often the first line a GC reading a change order request looks for.

Daily logs with access and GC direction as fixed delay causes. One log per job per day is enforced, so there is never a competing second version of a Tuesday. A delay is recorded with its cause from a fixed list — weather, material, labor, access, GC direction, inspection, other — plus a narrative, work areas, labor hours per worker and photos. Because the cause is a choice rather than free text, “every day this year we were turned away for access” is a filter in the report builder instead of an archaeology project. Field users are free and unlimited, which is the part that makes it work: the moment a log costs a seat per foreman, you get logs from some of your foremen and not the rest.

Job photos filed by category, with the day they were taken. Every project has a photo area with filing categories — General, Progress, Before, After, Damage, Material, Inspection, Safety and Punch List, plus your own — and photos filter by category. Where the uploaded JPEG still carries the camera’s own date stamp (an iPhone HEIC file loses it in conversion), SubMark keeps that as the date the photo was taken, rather than the day somebody got around to uploading it. For a partial release, two photos filed under Before on the day you were turned away are the cheapest evidence in construction.

T&M tags for the trip taken on direction. On by default in all 29 trade setup packs, priced in the office, signed by the GC on site, and several tags convert into one change order. The honest limit: T&M hours do not feed job-costing actuals — your crew’s clocked hours still do.

A schedule of values you structure yourself. Our excavation page calls mobilization the only front-loaded line you get, and the logic runs the other way too: if returns are the shape of your job, the schedule of values should carry a mobilization line per building or per phase rather than one for the award. Build that breakdown before the SOV locks, which happens when the first pay application built in SubMark is submitted. Once a job has an SOV, approved change orders are added to it as their own lines automatically.

Job costing at wage rate. Budget versus actual per job, fed by labor hours from the daily logs and the time clock, the amounts invoiced against your purchase orders (with the committed PO total shown beside them), and the QuickBooks Online bills and purchases that pull in. It costs at wage rate, not burdened. What that gives you on this problem is the hours — the thing that tells you a job is forty percent over on labor while the quantities say you are on plan.

See the product for how the cost side fits together, and pricing for what the office side costs.

Seven things to do this week

1. Put a number on one of your own return trips. One crew, one area, burden included.
2. Ask your contract whether a mobilization count exists, on your three biggest jobs. Most of the time the answer is no, and then at least you know.
3. Write a mobilization count into your next proposal. Two lines, before signature.
4. Tell your foremen to log access and GC direction by name, on the day, every time.
5. Make a Before photo the reflex when a crew is turned away or handed half an area.
6. Open a change event on the second trip, not the third.
7. Sort last quarter’s return trips into the four buckets. What sits in buckets two and three is the size of the problem you have been absorbing.

None of that gets you a continuous release. It changes who pays for the fact that you did not get one — and when the trips keep coming after the job has been accepted, the question turns into a different one: warranty callbacks.