Once the contract is signed, run a compact mobilisation checklist, agree the service commencement date and book the client kickoff, all before any engineer visits site. Record the dates in your contract register and attach the mobilisation plan to it. Success during onboarding means named contacts, a confirmed start date, access arrangements agreed and a first asset list in your system.
TL;DR:
- Send the intake form before kickoff, then use the meeting to resolve gaps; confirm contacts, access rules, purchase order details, and the first recurring schedule.
- Build a mobilisation plan with named owners, dated milestones, completion evidence, and risks; tie any milestone payment to accepted evidence before invoicing.
- Define each SLA’s clock start and stop and its data source, then embed targets in job types and review performance monthly with the client.
- Reconcile asset records against the client list and contract schedule; if handover records are late, survey sites, document gaps, and agree a fallback.
- Track notice dates separately from expiry dates and set reminders well before each deadline, since renewal windows can close before the contract ends.
Table of Contents
- What should your onboarding checklist cover in the first 3–14 business days?
- How do you build a mobilisation plan that turns contract language into milestones?
- Which SLAs, KPIs and clauses should you make operational?
- What do you need to capture at intake: asset data, site rules and access?
- How do you set up governance, a RACI and a meeting rhythm?
- What should the first 90 days look like, and how do notice periods fit in?
- Which templates and quick tools should you reuse?
- How should you keep the client informed during onboarding?
- How do you capture and manage client feedback during onboarding?
- How do you define roles and responsibilities between client and provider?
- What risks should you plan for during onboarding, and what is your fallback?
- Why disciplined onboarding is worth the effort
- Curcle: contract terms connected to day-to-day work
- FAQ
- Sources
What should your onboarding checklist cover in the first 3–14 business days?
The gap between signature and service commencement is where momentum is won or lost. Treat it as a short, ordered project with an owner, not a pile of admin. Work through these steps in sequence:
- Confirm the signed contract and pull out the clauses that drive operations: commencement date, notice periods, acceptance criteria and any change control wording.
- Capture the client's contacts, billing details, purchase order requirements, single point of contact and escalation contacts.
- Record site access rules, keyholding arrangements and emergency contacts for every location.
- Create or update the asset register to the minimum fields you will need to plan and invoice work.
- Set up system access for your team, then test mobile logins and permissions on a real device before day one.
- Schedule the kickoff workshop and initial site visits.
Alongside the ordered steps, keep a short list of items that must exist before the first job is dispatched:
- A named account owner on your side and a named single point of contact on theirs
- A confirmed service commencement date in the contract register
- A shared list of sites with addresses, access windows and contacts
- A first draft of the recurring schedule for planned visits
Pro Tip: Send the intake form to the client before the kickoff, not at it. Meetings then spend their time resolving gaps instead of collecting basics.
How do you build a mobilisation plan that turns contract language into milestones?
A mobilisation plan converts what the contract promises into dated, owned activities. Public sector guidance describes what a good one holds: supplier mobilisation plans should include a mobilisation team, a communications plan, IT set-up, trialling of systems and processes, handover from the previous contractor, an asset register and clear milestones, and should be submitted before service commencement. Tender documents follow the same pattern: published tender requirements ask for a mobilisation plan with milestones, mobilisation meetings and deliverables to be met by service commencement. For complex or high-risk services, the Model Services Contract guidance recommends preparing an outline implementation plan and aligning mobilisation activities with the contract schedules.
Even for a modest maintenance agreement, the same building blocks apply:
- A master programme of works showing what happens in which week
- Milestones tied to the acceptance criteria in the contract
- Resource allocation by role and by named person
- A short risk register, owned by one person
- Deliverables for each milestone, so "done" is not a matter of opinion
If the previous supplier held the site records, ask early. Request the asset list, last service dates, certificates and open defects in writing, give a return date, and chase it at every weekly meeting. A named representative on each side should chair mobilisation meetings and keep the action log.
| Milestone | Owner | Evidence of completion |
|---|---|---|
| Contract terms extracted into register | Account owner | Register entry with key dates |
| Asset list received and loaded | Operations lead | Asset count reconciled to client list |
| System access tested | Office manager | Test job completed on mobile |
| Kickoff held | Account owner | Minutes and action log issued |
If the contract includes milestone payments, link each milestone to its evidence in the plan so invoicing follows acceptance rather than argument.
Which SLAs, KPIs and clauses should you make operational?
Contracts are only useful when their terms show up in daily work. Start with the service levels: response time, fix time and availability are the usual measures, and each needs a definition of when the clock starts and stops, plus a named source for the figures. If you cannot measure it from job records, rewrite it before you agree to it.
Then move to the clauses that cause trouble later:
- Scope: what is included, what is excluded, and how out-of-scope work is quoted
- Change control: who can approve variations, and in what form
- Acceptance testing: what the client signs to confirm work or a milestone is complete
- Dispute resolution: the steps and timescales before escalation
Maintenance agreements often include a rolling maintenance schedule agreed with the buyer and notice for planned downtime. A published contract template shows this pattern, with arrangements that minimise disruption to the buyer's operations. Translate those terms into job categories, recurring schedules and alerts so they trigger on their own.
A short operational checklist for acceptance and disputes keeps everyone consistent:
- Log every client sign-off against the job and the milestone it closes
- Record any disagreement the day it happens, with photos and notes
- Route disputes to the named escalation contact before they reach the contract clause
- Review SLA performance monthly with the client, using the same figures both sides can see
Pro Tip: Build each SLA into the job type itself, so the target and the deadline appear when the job is created, not when someone remembers to look at the contract.
What do you need to capture at intake: asset data, site rules and access?
Poor intake data is a common cause of a rough start. Capture a minimum dataset for every asset so jobs, compliance and invoices can be tied together from the outset:
- Asset ID and a clear description
- Location within the site
- Make and model
- Warranty and planned preventive maintenance schedule
- Last service date
Site information matters just as much: keyholding arrangements, permitted working hours, parking and induction requirements, and emergency access instructions. An engineer arriving at a locked plant room needs the answer on their phone, not in a contract appendix.
Missing records are normal, so plan to recover them in this order:
- Ask the client for their own asset list and any commissioning documents.
- Ask the outgoing supplier for service history, with the client's written permission if needed.
- Survey the site on the first visit and fill the gaps with photos and data plates.
- Reconcile the count against the contract schedule and flag differences to the client in writing.
Why does this matter beyond tidiness? When assets are linked to jobs and invoices, you can see which items are overdue, which have never been serviced under your contract and which are about to fall out of warranty. Our guide to maintenance contract management explains how that link protects margin, and a specialist inspection supplier, such as aerial roof inspection services, can fill gaps on hard-to-reach roofs where a ground survey cannot.
How do you set up governance, a RACI and a meeting rhythm?
Governance sounds heavy, but a compact version fits on one page. A RACI shows, for each mobilisation task, who is responsible, who is accountable, who must be consulted and who is informed. The Contract Management Playbook highlights contract management plans, RACI assessments and documented handovers as vital during mobilisation, and that applies at any contract size.
A workable meeting rhythm looks like this:
- A post-award meeting to confirm scope, dates and contacts
- A short weekly mobilisation call until service commencement
- A monthly service review that looks at SLA performance, open actions and upcoming renewals
Each meeting produces the same outputs: minutes, an action log and an updated risk register, stored where both teams can find them, ideally against the contract record rather than in someone's inbox.
Name a single point of contact on each side, and agree the escalation path in plain terms: first contact, second contact, and the point at which a director gets involved. When the escalation path is written down before the first problem, problems cost less to resolve.
What should the first 90 days look like, and how do notice periods fit in?
A realistic timetable keeps the plan grounded. Early on, confirm contacts, load sites and assets, test systems and hold the kickoff. Once initial planned visits are complete, close the asset gaps and issue a progress report. Later, run a full SLA review, confirm recurring schedules are firing correctly and agree any changes to scope.
- Early stage: contacts, access, system tests, kickoff
- After initial visits: asset register reconciled, first report issued
- Later review: SLA review held, schedules validated, scope changes agreed
Track notice periods separately from expiry dates. A contract ending in December may need notice in September, and a renewal window can close long before the date everyone remembers. Set reminders well before each key date.
Missing a notice window is a process failure, not a client failure. Practitioners note that managing contracts in spreadsheets often leads to missed renewal dates and compliance gaps, which is why the register belongs in a connected system.
Milestones feed invoicing too: when a milestone is accepted, the invoice follows, with the acceptance record attached.
Which templates and quick tools should you reuse?
A small set of simple documents carries most of the load. An intake form captures client contacts, billing and purchase order details, escalation contacts, site access rules and emergency instructions. A compact mobilisation checklist lists the steps above with an owner and a due date against each. A contract register records the essentials in one row per contract.
For the register, keep columns minimal so it actually gets updated:
- Client and contract reference
- Start date, end date and notice date
- Key contacts and escalation contact
- SLA summary and next review date
- Linked sites and asset count
Version your templates. Keep one current copy in a single location, date each revision, and retire older copies so field teams never work from an outdated form. Our free compliance templates are a practical starting point for building your own intake forms and registers.
How should you keep the client informed during onboarding?
A communication plan answers three questions: who hears what, how often and through which channel. Public guidance on mobilisation lists a communications plan among the core components of a supplier plan, and it earns its place because silence is how small worries become complaints.
Agree the plan at the kickoff, and keep it short. Name the sender and the recipient for each update, and fix the rhythm: a brief written update after each weekly mobilisation call, a heads-up before any planned visit, and an immediate call when something goes wrong. Choose one channel for routine updates, usually email with a shared action log, and a phone number for urgent matters.
Match the message to the audience. The client's contract owner wants progress against milestones and risks. Site contacts want to know who is arriving, when and what they need to provide. Finance wants confirmation of purchase order references and invoicing dates. Writing one message for all three satisfies none of them.
Make bad news early news. If the asset list from the previous supplier is late, say so in the next update, with the impact and your fallback. Clients forgive delay far more readily than surprise.
Close each stage with a short confirmation: what was completed, what is next and what you need from them. By service commencement, the client should already know the engineer's name, the contact for emergencies and how to raise a job.
How do you capture and manage client feedback during onboarding?
Onboarding is the one period when clients will tell you what they expected, so ask on purpose rather than waiting for a complaint. Build feedback points into the plan: ask a question at the end of the kickoff, check in after an early site visit, and hold a review after the client has had time to experience the service.
Keep the questions concrete:
- Was the arrival and access process smooth?
- Did the engineer have the information they needed?
- Is the reporting format useful to you?
- Is there anything we have not yet covered?
Record each answer against the client and the contract, not in a personal notebook. Give every item an owner, a due date and a status, and report back at the next meeting what has changed as a result. Clients who see their comments turn into action trust the relationship faster than clients who only see a survey.
Separate feedback into types. Process issues, such as access or paperwork, can often be addressed promptly. Scope issues, such as work the client assumed was included, go through change control. Relationship issues, such as tone or responsiveness, belong with the account owner.
Review the log at the monthly service review, then use it to improve the next onboarding. Patterns repeat: if clients struggle with the same step, the checklist needs changing, not the clients.
How do you define roles and responsibilities between client and provider?
Many onboarding delays are really unclear ownership: the client assumes you will chase the previous supplier, and you assume they will. Write down who does what before the first week ends.
On the provider side, define an account owner accountable for the relationship and the plan, an operations lead responsible for scheduling and resourcing, an office contact for billing and records, and engineers responsible for accurate job records. Public guidance on mobilisation plans names a supplier representative as the point of contact during mobilisation, and the published tender attachment also asks plans to integrate with other suppliers' plans where relevant.
On the client side, agree a contract owner who can approve changes, a site contact for each location who can grant access, and a finance contact for purchase orders and invoice queries. Also name who holds the authority to sign off milestones, because an acceptance nobody is empowered to give stalls both invoicing and progress.
Capture all of this in a one-page responsibilities matrix and attach it to the contract record. Include client obligations explicitly: timely access, supply of records, prompt approvals and notice of site changes. Where the contract makes those obligations conditional, say what happens to dates if they slip.
Revisit the matrix at the first monthly review. Roles drift as people change jobs, and a matrix updated early saves an awkward conversation later.
What risks should you plan for during onboarding, and what is your fallback?
Risk assessment at this stage is short and specific. List what could go wrong between signature and a stable service, rate each item by likelihood and impact, and assign an owner and a fallback to the ones that matter.
The common risks are predictable:
- Missing or inaccurate asset data: fall back to an early site survey and a written reconciliation with the client
- Late handover from the previous supplier: escalate through the client, and plan initial visits around the records you do hold
- Access problems: confirm keyholders and permitted hours in writing, and keep an emergency contact list for each site
- Resource gaps: identify a named backup engineer for each site before commencement
- System issues: test logins, permissions and mobile use on real devices, and keep a paper fallback for the first week
- Data protection: treat UK GDPR as a continuing obligation, not a one-off check at tender
Tender documents note that failing to meet mobilisation criteria typically needs justification and mitigation, which is a useful discipline even where nobody asks for it: if a milestone slips, write down why, what you are doing and the new date.
Keep the register alive. Review it at every weekly mobilisation call, close items that have passed, and add new ones as they appear. A risk register that was last opened at the kickoff is decoration.
Finally, agree a contingency trigger. If the asset reconciliation is not complete by the agreed milestone, for example, the account owner calls the client contract owner promptly. A trigger turns a vague worry into an action.
Why disciplined onboarding is worth the effort
Most onboarding failures are not dramatic. They are small gaps that compound: an unconfirmed contact, an asset nobody recorded, a notice date that lived in one person's head. Disciplined onboarding closes those gaps early, and the payoff shows up months later as renewals that happen on time and compliance dates that never surprise anyone.
The contrarian point is that most teams over-invest in the contract and under-invest in the period immediately after it. The contract sets the promise, but mobilisation sets the rhythm the relationship will follow. A late, messy start becomes the pattern clients remember.
Measure the early outcomes rather than assuming they are fine: time to the first completed job, how complete the asset data is at the end of month one, and how many actions are still open at the first service review. If those numbers look healthy, the rest tends to follow.
— Luke Herridge
Curcle: contract terms connected to day-to-day work
We built Curcle to bring operational information together. Jobs, assets, compliance records and invoices sit in one connected system.
If you are mobilising a new maintenance contract, our product page shows how jobs, assets and compliance work together, and you can see the Starter plan from £99 per month alongside the other options on our pricing page. Our field service management software page explains how we support teams through mobilisation, and our job handover guidance covers what a clean audit-backed handover looks like. Start with the pricing page, pick the plan that fits your team and book a demo when you are ready to map your first contract.
FAQ
What are the best practices for client onboarding?
Agree the service commencement date early, collect contacts and site access rules before the kickoff, and hold a short weekly call until the service is stable. Keep every record against the contract so nothing depends on one person's memory.
What is a client onboarding process?
It is the structured period between contract signature and service commencement. In it you formalise the agreement, capture client and asset information, set up systems and align expectations on communication, service levels and responsibilities. The aim is a smooth first job, not just completed paperwork.
What is the client onboarding (KYC) process?
KYC, or know your customer, means verifying who a client is and checking relevant details before work starts. It sits alongside the operational steps of onboarding, so the identity and billing checks happen early, and the contract owner's details are recorded in your register.
How do I onboard a new maintenance client quickly?
Send the intake form before the kickoff, confirm named contacts and commencement date, and load the sites and assets you already know. Fill gaps with a first-week survey. Speed comes from preparation, because the dates and contacts are already agreed when the kickoff begins.