What should the transfer plan accomplish?

The first quarter should protect the capacity that justified buying. Customers need service; technicians need clear assignments and reliable pay. The company must meet its promises. The buyer also needs to learn which routines work and which rely on the seller's help. That evidence shapes the handoff and shows where training, records, or backup capacity still needs attention.

The 90-Day Transfer Plan is The Plumbing Business Broker's original sequence for continuity, knowledge transfer, verified baselines, and measured change. Its windows are planning intervals, not legal deadlines or promised results. Adjust pace to actual risks and skills.

The operations hub connects the plan to performance. Assign a person, backup, due date, and completion evidence to each task. Transfer dispatch is too broad without accounts, rights, bookings, history, reports, and trained users. Check the components. A task needs a clear result so the team can see what remains before the usual owner of the process leaves.

What must be ready on the first operating day?

Confirm authority, qualifying supervision, insurance, payroll, banking, dispatch, phones, payments, purchasing, and vehicles. Identify duties passing at closing and those temporarily staying with the seller. The License Continuity Map tracks place-specific dependencies. Authority and work capacity need separate checks.

Review open jobs and major promises. Record status, deposits, visits, permits, ordered parts, warranties, and customer contacts. Treat memberships with the same care as unfinished installations. Define who can authorize work or refunds. The closing process should leave staff able to locate each commitment and act within the agreed terms rather than guessing which owner now bears responsibility.

Use a secure access-transfer process. Verify business-account rights and assign role-based permissions. Test another person's ability to dispatch, take payment, run payroll, reach suppliers, and find permits. Do not rely on an unsecured password list. A working login can still lack needed rights. Record failed checks and arrange the permission or transfer before calling that task complete.

What should happen during days one through ten?

Focus on stability and exceptions. Hold a brief daily manager and dispatcher meeting. Review available staff, urgent customers, at-risk jobs, receipts, and critical-system problems. Give employees a route for questions about roles, pay, and schedules. Keep future-change promises within agreed terms.

Observe routines before redesign. A paper checklist may hold local knowledge absent from software. A senior technician may handle permit fixes or part substitutes informally. Capture the work and test a backup. Explain why gaps matter without blame.

Check workforce plans against actual practice. IRS worker guidance covers federal employment-tax factors. Other laws may use different tests. Ask relevant advisers to review changes in control, pay, or structure. Keeping a contractor label does not settle status if management practices change.

How do days eleven through thirty transfer knowledge?

Write how calls qualify, prices are approved, jobs assigned, parts bought, invoices corrected, and complaints resolved. Note decisions needing a licensed supervisor or specific person. Pair incoming and existing staff and test an actual case. A written procedure needs a capable user. Record what the test shows and provide training or permissions for any step the new user cannot complete.

The pricing and dispatch guide connects workflow with reports. Completed should mean the same thing in dispatch and accounts. Define partial work, deposits, refunds, and callbacks. Those choices affect comparisons and any earnout measure. Preserve the agreed policy and dates before comparing periods, so a changed status definition is not mistaken for a change in operating earnings.

Train for capability gaps beyond software use. PHCC apprenticeship resources supply education context; local licensing and supervision remain separate. Check who may perform duties and teach backups. The technician-retention guide links the handoff with staffing and pay. Match the plan to actual roles rather than assuming all experienced staff can lawfully cover every assignment or approve regulated work.

How should the buyer establish a reliable baseline?

Choose measures that reconcile and can be explained. Track eligible calls, bookings, completed jobs, billed sales, cash, direct costs, callbacks, and staffing. Define numerator, denominator, timing, and exclusions. Split lines or branches where totals hide differences. Preserve definitions with the baseline so later reporting can distinguish actual change from a new counting rule, seasonal pattern, or shift in the type of work.

MeasureDefinition to settleUseful review
Call bookingEligible opportunities and successful appointmentsMissed demand or capacity limits
Job completionCompleted work versus scheduled visitsDispatch and production interruptions
Cash receiptsPayments collected in the stated periodLiquidity and collection delays
Job contributionRevenue less defined direct costsMix, pricing, and labor effect
Callback rateDefined return visits and original-job cohortQuality and warranty obligations
Workforce capacityAvailable qualified labor by roleCoverage and retention exposure

ServiceTitan's State of the Trades offers context with vendor-survey limits. The buyer's reconciled baseline is the main transition comparison. Outside averages need further analysis to explain unusual mix or local conditions. Use the company's own records to test its change, and retain the definitions and dates rather than treating one external figure as a universal operating target.

What changes can be tested during days thirty-one through sixty?

Choose a documented problem and a limited test. It might concern missed calls, job costs, late collections, or purchasing delays. Define the intended result and service standards to preserve. Assign resources and stop-or-change criteria. The experiment should be narrow enough to trace its effect. Record other changes during the period before attributing results solely to the tested remedy.

Assume a hypothetical week: 120 eligible calls produce 72 bookings, or 60%. After a documented handling change, 125 eligible calls yield 85 bookings, or 68%. This signals a question, not proven causation. Compare staffing, leads, available appointments, completed work, and cash. These teaching inputs do not establish that the change caused more earnings or would produce the same result elsewhere.

Avoid simultaneous migrations the team cannot assess. Changing software, prices, people, and ads together can obscure a sales decline or complaint increase. Address urgent safety and compliance defects promptly with professional help. Schedule other work by evidence and readiness. Keep a record of what changed, so reviewers can investigate the actual effect without assuming every movement arose from a single initiative.

How do days sixty-one through ninety build the next operating plan?

Review transferred duties and those still needing the seller. Update management, training, hiring, and capital needs. Compare actual performance with the purchase model. Distinguish new definitions from real operating changes. Record unresolved dependencies before setting the next plan, so a favorable report does not hide work still performed by a departing owner or a cost omitted from the initial forecast.

Safety needs separate review. OSHA's construction confined-space FAQs explain assessment and entry issues. Not every space has the same regulatory category. Obtain qualified review of actual work and preserve procedures, training, and equipment records. The safety and fleet guide connects the evidence with diligence. A general source does not replace classification and procedures for the sites the crews actually enter.

Build the next-quarter plan with priorities, costs, owners, and milestones. Address the biggest constraint first. End seller involvement under the agreed terms and demonstrated handoff duties. If a gap remains, resolve it explicitly. Do not assume the seller will stay unpaid or indefinitely available. Check that the responsible staff and records can support the work when the stated role ends.

What evidence shows that the handover is complete?

  1. Critical approvals and operating permissions are confirmed and recorded.
  2. Daily service, payroll, banking, and customer escalation have responsible owners.
  3. Open work and membership commitments can be located and managed.
  4. Reports reconcile to financial records under documented definitions.
  5. Backup employees can perform the transferred routines without seller intervention.
  6. Remaining exceptions have a specific remedy, owner, and deadline.

The first-ninety-days guide covers broader buyer priorities. Keep notes and completion evidence for use after the deal team leaves. The useful result is reliable service and understood performance. Assign daily routines and remaining exceptions to clear roles, with records the team can find. The handoff should leave an operating process rather than only a completed transaction checklist.