Mobilisation is where contracts are won or quietly lost. This is the seven-step process Pyrex runs for every start-up — the same one being run at Birmingham now.
A team picked for the contract, not a standing department
A dedicated mobilisation team is formed according to the needs of each contract. Members are chosen for relevant collective experience and domain expertise, so that the people writing the plan are the people who have delivered one before.
The seven steps
One: confidential, sensitive communications — because in most cases a station is changing hands and the incumbent’s staff have not been told. Two: the recruitment drive. Three: full one-to-one interviews, not a group sift. Four: vetting and licensing. Five: uniforms delivered. Six: training. Seven: the model commences.
Steps four and six are the ones that set the timetable. A CTC and DBS check is completed before an applicant is offered a post, and a full five-year screen normally completes within twelve weeks of induction. No amount of commercial pressure moves those.
Meetings, on dates, with names against them
The mobilisation team and the airline meet to agree timeframes and the tasks to be completed within them. Once the plan is finalised, ongoing meeting dates are set to review progress against it, so that “ready for the agreed start date” is a fact somebody has checked rather than an assumption.
The review after go-live
Mobilisation does not end when the model commences. A post-mobilisation review begins a change cycle: digitisation of current deployments, a complete review of security-related policies to establish gaps, an assessment of the supporting security equipment infrastructure, and change recommendations that align tasks with the technology available to support them.
That last stage is the one most providers skip. Standing an operation up is the easy half; improving it afterwards is where a contract stops costing the airline money.
