Mobilising a new contract without a bad first month

A new contract is the only point at which a client has no baseline of trust to draw on. Every problem in the first month is evidence about the contractor; the same problem a year in is an exception against a known record. That asymmetry is why the first four weeks deserve resourcing that looks disproportionate.

The compliance work happens before day one or not at all

Mobilisation has a fixed date and a variable amount of preparation, and the parts that slip are the ones with no immediate visible consequence: confirming licence status for every officer who will work the site, collecting screening records for transferred staff, and writing assignment instructions that somebody unfamiliar could actually use.

None of those stop the contract starting. All of them are considerably harder to do once officers are on site and the operation is running, and each is the sort of thing a client audit in week nine asks about.

Cover in the first month is a specific risk

New sites generate more cover than established ones — officers who accepted the role and did not start, early departures, people discovering the commute. The cover pool for a brand new site is also the weakest it will ever be, because nobody has worked it and nobody has been briefed.

Which is the argument for briefing more officers on the site than the rota strictly needs, in the first month. It costs a few hours and it is the difference between cover being a phone call and cover being an unfamiliar officer working from assignment instructions nobody has tested.

Ask the client before they tell you

A deliberate check-in in week two, before the client has a reason to make one, changes the relationship's opening. It surfaces small irritations while they are still small, and it establishes that the contractor is paying attention rather than waiting to be told.

In practice: the site nobody had walked

A contractor mobilises a site having written assignment instructions from the client's specification and a floor plan. In week one the officer discovers the described patrol route passes through a door that is locked after six and a yard that is not lit.

The instructions were accurate against the documents and wrong against the building. Nobody had walked it at night, which is when it would be worked.

Common mistakes

• –Resourcing month one at the same level as month twelve
• –Writing assignment instructions from the specification without walking the site
• –Not walking it at the hours it will actually be worked
• –Briefing only the officers on the initial rota, leaving no cover pool
• –Leaving compliance confirmation until after the start date
• –Waiting for the first scheduled review to ask the client how it is going

One practical test: walk it at three in the morning

Before writing assignment instructions, walk the site at the hours it will actually be worked — not during the afternoon handover meeting.

Locked doors, unlit yards, gates that are chained after six and routes that exist on a plan and not in practice are invisible in daylight with the client present. Every one of them becomes a problem in week one, when the contractor has no record to draw on and the client has no reason to be forgiving.

• –Walk the site at the hours it will be worked
• –Resource month one above the steady-state level
• –Brief more officers than the rota needs, for cover
• –Confirm licence and screening before the start date
• –Check in with the client in week two, unprompted

Worth adding: agree the reporting format at mobilisation

Reporting format is almost never specified in a contract, so contractors invent one and then vary it as different people produce it. Agreeing it during mobilisation — what the client wants, how often, in what shape — takes one conversation and avoids months of sending something nobody reads.

It also establishes early that you intend to report proactively, which is the impression worth setting in month one.