A federal phase-in plan shows evaluators how your team will move from contract award to full operational readiness on schedule. Organizing transition work into dated milestones for workforce onboarding, security badging, and knowledge transfer reduces startup risk. Clear handoff checkpoints keep incumbent retention and site readiness tasks moving in parallel.

For covered service work performed at a federal facility where a succeeding contractor may hire or retain the employees, FAR 22.1020 addresses a certified employee seniority list. The incumbent prime furnishes it to the contracting officer no later than 10 days before contract completion. The contracting officer provides it to the successor at contract commencement to determine vacation or other service-length benefits required by the applicable wage determination. Record the actual release arrangements with the contracting officer; do not assume this list will arrive during early recruiting. Keep employee and security-package details in authorized HR/security channels, not in FedFinder or public opportunity notes.

Map Dependencies to the Actual Transition Period

  1. Transition governance and kickoff: Designate a dedicated Transition Manager, confirm the kickoff route with the agency’s designated contract contact, and establish daily or twice-weekly status checkpoints.
  2. Incumbent workforce capture and backfill: When the plan includes incumbents, confirm the authorized contact route and who verifies the service-date information needed for applicable benefits. Track offers, acceptances and ready-to-start personnel separately, with backfill actions for gaps. For background on wage determination mechanics on covered service work, read The Service Contract Act (SCA) and Wage Determinations, Explained.
  3. Security, badging, and system access: Identify the actual access steps, submission windows and agency decision owners. Track submission, receipt and approval separately; submitting a package does not establish a credential approval date.
  4. Facility, plant, and equipment readiness: When the solicitation requires a local project office, warehouse, or plant, document the lease, teaming agreement, or performance-site arrangement separately from your entity registration record. A legal entity's SAM business address does not need to match its plant or performance-site address; reconcile corporate identity with documented site agreements rather than assuming both addresses must be identical.
  5. Shadowing, inventory audit, and operational cutover: Confirm authorized handover, shadowing and inventory arrangements before putting them on the schedule. Escalate unconfirmed access or predecessor cooperation as a dependency rather than promising an unavailable handoff.

60-Day Federal Phase-In Milestone Schedule Template

The following hypothetical 60-day sequence illustrates a dependency log. Replace its dates and activities with the actual contract period and agency-confirmed access/handover arrangements. Its artifact names describe planned evidence, not completed approvals.

1. Days 1 to 10

  • Workstream: Governance & Security Initiation
  • Actions: Confirm the agency kickoff and access-submission windows; record milestones and pending prerequisites.
  • Planned evidence: Baseline Transition Schedule & Badge Submission Log
  • Responsible lead: Transition Manager / Security Lead

2. Days 11 to 25

  • Workstream: Workforce Outreach & Offers
  • Actions: Record the confirmed seniority-list release route/date where applicable; use authorized outreach and offer procedures.
  • Planned evidence: Signed Offer Tracker & Backfill Requisition List
  • Responsible lead: HR Lead / PM

3. Days 26 to 45

  • Workstream: Knowledge Transfer & Site Audit
  • Actions: Perform authorized handover and inventory steps; record site and system dependencies still awaiting confirmation.
  • Planned evidence: Signed GFP Joint Inventory & SOP Transfer Checklist
  • Responsible lead: Operations Lead

4. Days 46 to 60

  • Workstream: Readiness Verification & Cutover
  • Actions: Reconcile actual staffing/access readiness against the planned Day 61 start; escalate gaps to the authorized contract contact before claiming readiness.
  • Planned evidence: Operational Readiness Review Sign-Off Brief
  • Responsible lead: Program Manager

Check Processing Capacity Without Converting Calendar Days Into Workdays

In a separate hypothetical 45-day capacity example, assume each person represents 1.0 FTE and the contract calls for 40 ready FTEs on Day 46. The planning mix is 30 incumbent personnel plus 10 external hires: 30 + 10 = 40 FTEs. The 30 incumbents represent 75% of the planned 40-person team, not a measured incumbent-retention rate.

The offer window from Day 11 through Day 25 contains 15 calendar days. Count its actual working days as W after weekends, holidays and your processing schedule. If W = 11 in a particular hypothetical window, 40 offer decisions divided by 11 working days is about 3.64 decisions per working day. Issued offers, accepted offers and ready-to-start personnel remain different counts.

Days 26 through 45 leave 20 calendar days in this model. Use that window to track the remaining dependencies; it does not establish agency processing times or guarantee that credentials will be approved by Day 46. Assign an owner and escalation path to any dependency that threatens the actual required start.

When planning early capture for expiring service contracts, review The Recompete Lookahead: Contracts Expiring in the Next 6 to 18 Months. Explore public federal contracting opportunities on FedFinder, with current terms on the pricing page.

Sources

  • Federal Acquisition Regulation (FAR) Subpart 22.10, Service Contract Labor Standards (FAR 22.1020): FAR 22.1020, Seniority lists (Retrieved 2026-11-06; Acquisition.gov baseline FAC 2026-01, effective 2026-03-13; seniority-list handoff and qualifying service-length benefits on covered service work).