Plumbing company 90-day transition plan

What should the buyer preserve while changing the operation?

The business must answer, assign work, pay staff, control cash, and serve lawfully. Changes should support those duties. Keep required functions running while proving replacements. A purchase closes ownership terms; the operating team still needs effective people, access, funds, and permission to carry out actual work.

The buying hub gives context. The first ninety days guide covers wider planning. This working checklist records dependencies and actual proof for accepting changes.

Use the transfer framework for the wider map. Record closing date, entities, coordinator, authorized owners, and critical functions. Match tests to this handover.

Which fields make an acceptance calendar useful?

Name current function, proposed change, readiness proof, responsible person, and fallback. State accepted scope and remaining work. A date or status label alone is no acceptance test.

Mark received/unreviewed, needs clarification, accepted for stated purpose, approval required, or blocked. Save conditions and next actions. Time passing does not settle a missing test or approval.

Which eight transition checks should be assigned?

1. 1.
   Verify authority for the first operating day.

   Confirm operating entity, qualifying link, work scope, approvals, coverage, and allowed seller duties. Record effective dates and open conditions with authority and advisers. Signed purchase terms alone grant no regulated work permission. The team needs the lawful route before assigning crews under changed ownership or responsibility; keep pending steps separate from effective approval.

2. 2.
   Test customer intake and dispatch.

   Check contact channels, open jobs, shifts, skills, areas, and escalation. Use authorized representative tests and assign failures. Keep permitted fallback until receiving team accepts coverage. A route or login alone does not show the right people can receive, price, book, and deliver work. Test actual hours and duties before removing the needed alternative.

3. 3.
   Reconcile first payroll and employer duties.

   Identify employer, staff records, pay, time, deposits, filings, benefits, and access needed for handoff. Name internal owner even with payroll provider. Authorized reviewers should reconcile inputs and outputs. Federal employer taxes differ from state wage, unemployment, benefits, and insurance duties. Actual setup and funds must support the required run rather than merely exist as proposed steps.

4. 4.
   Verify profile and account control.

   Inventory primary owners, admins, provider conditions, and waiting periods. Save acceptance proof separately from legal asset ownership. Time changes around customer contact. Profile, domain, phone, ads, and customer system can have different rights and processes. One completed step does not settle every other account; record actual authority and remaining conditions for each needed function.

5. 5.
   Reconcile exports and needed read access.

   Record dates, filters, populations, permissions, and formats. Compare sample records and counts to agreed baseline. Show missing fields and exceptions before retiring access. Report export is no guaranteed full migration. A readable file does not prove duties or balances transferred correctly. Accept the tested scope while leaving other account, financial, and customer checks visible.

6. 6.
   Test access protection and recovery roles.

   Name authorized admins, authentication, backup settings, and permitted recovery tests. Record owner and response path without storing credentials here. Review seller access when its approved purpose ends. A backup supports a specific control, not guaranteed protection or lawful use of every record. Retain the actual test result and limits before relying on proposed recovery coverage.

7. 7.
   Review exceptions at chosen checkpoints.

   At 30- and 60-day reviews, check callbacks, receipts, jobs, staffing, payroll, interruptions, and report gaps with defined populations. Assign unclear results. Change only with proof and resources. A temporary gain or loss does not prove the purchase outcome or justify removed coverage. Review causes and open work rather than accept a favorable total without context.

8. 8.
   Hand open dependencies to the next period.

   At chosen 90-day review, list accepted tests, open items, coming renewals, and next decisions. Name owner and due basis. Keep needed proof and fallbacks. Window ending is no proof of full integration. The next-period plan should show actual remaining actions, responsibility, and conditions so the team can continue resolving dependencies after the worksheet's final checkpoint.

Which source-specific duties inform the checks?

California's entity-change guidance illustrates state-specific work authority. Check state, entity, person, and trade. Current seller status is not automatic proof of buyer's effective approval.

Google's primary-owner instructions give provider process and seven-day limits on specified new-owner/manager actions. They prove neither other asset ownership nor future demand. Separate account action, legal rights, and operating results.

ServiceTitan's export guidance covers filters, permissions, and formats. Its capacity workflow considers shifts, skills, zones, and time. Vendor tools define tests; they guarantee no complete migration, universal productivity, or spare capacity.

IRS Publication 15 for 2026 covers federal employer taxes and records. Assign successor-employer and processing questions to reviewers. State and benefit duties differ; allocation alone proves no completed setup, filing, or payment.

NIST's small-business guide supports access, backup, and response roles. It is voluntary guidance, not integration certification. Record actual controls, permitted tests, and their limits.

What does a worked acceptance test look like?

Suppose invented migration exports 500 completed jobs but new system shows 480. Check same entity, period, and status filters before interpreting the twenty-record gap. This is no standard acceptance threshold.

Fifteen records were filtered out and five failed import. Correct filter, resolve failures, and bridge totals and sample records before accepting the stated population test. Save fixes and scope so reviewer can reproduce the result.

This does not validate every invoice, consent, warranty, or field. Assign those separate scope and proof. Record who accepts job-count result and whether permitted fallback remains needed.

How should milestones follow dependencies rather than assumed dates?

1. Confirm authority and critical service arrangements before the first operating handoff.
2. Test payroll, accounts, reports, and recovery according to actual requirements.
3. Accept each replacement only after the responsible reviewer verifies its scope.
4. Review exceptions in the chosen 30- and 60-day windows.
5. Carry unresolved dependencies into the next period at the chosen 90-day review.

The buyer licensing guide allocates authority. The diligence guide supplies initial proof; brand review separates profile and asset rights. Connect findings without merging their scope or treating pending steps as approved.

How should changes and unresolved issues be recorded?

Record each problem's proof, affected function, owner, next date, and effect. Log changed systems, staff, or report definitions against baseline. Preserve original result and corrections.

Separate customer, cash, and payroll exceptions with their own proof and people. One successful test should not close unrelated issues under one broad integration status.

Missing proof at due date leaves an open issue. Escalate through approved process with work effect and fallback. Calendar completion replaces neither approval, coverage, nor reconciliation.

How should the calendar be printed?

Print checks and table for team. Keep detailed tests, account permissions, and private records in controlled repository, referenced on working copy. Do not print credentials or needless personal fields.

Print view removes navigation and conversion panels. Mark dates, owners, proof, open items, and actual deadlines beside chosen windows. A checkpoint creates no permission to delay required tasks.

Which mistakes undermine transition acceptance?

Avoid premature fallback removal, treating login as service test, assuming authority from purchase signature, and calling day ninety full integration. These are risks to check, not a verified frequency ranking.