A service launch should not wait until contract renewal for a serious review. The first 90 days reveal whether the staffing model, supervision, site conditions, and provider processes work together.

Set the baseline before day one

Record approved headcount, shifts, role standards, historical attendance or vacancy, output, quality, safety, overtime, turnover, complaints, and cost assumptions. Define each KPI, data owner, source, frequency, and target so both parties read the scorecard the same way.

Days 1–30: stabilize the deployment

Focus on filled positions, day-one attendance, access, uniforms, tools, PPE, training, schedule understanding, timekeeping, payroll setup, supervision, and worker questions. Hold short frequent reviews and close urgent issues quickly.

Questions for the 30-day review

  • Did the correct workers reach the correct shifts?
  • Are duties and exclusions understood?
  • Are attendance, payroll, and billing records aligned?
  • Which early departures or absences have preventable causes?
  • Are any safety or quality controls missing?

Days 31–60: improve the operating system

Analyze recurring absence, overtime, rework, delay, replacement, transport, training, and supervisor patterns. Test targeted fixes rather than changing many variables at once. Update role profiles, staffing by shift, orientation, and escalation where evidence supports it.

Review service-level performance

Compare actual performance with agreed definitions and realistic baselines. Article 49 explains how to structure manpower KPIs and service levels. Add worker feedback because weak facilities, unclear schedules, or poor treatment may appear first as attendance and turnover problems.

Days 61–90: decide what to standardize or scale

Confirm which controls are stable, which actions remain open, and whether staffing should expand, reduce, or change by role and shift. Review cost per productive result—not only monthly headcount. Document approved changes to scope, rate, schedule, supervision, or reporting.

Use one action register throughout

Every issue should have a clear statement, root cause status, owner, due date, priority, next step, and evidence of closure. Keep decisions and changes in the same record. Escalate overdue high-risk items rather than repeatedly carrying them forward.

Watch for warning signs

  • High deployment counts but weak first-week retention.
  • Persistent overtime beside unfilled regular shifts.
  • Frequent manual attendance corrections.
  • Repeated replacements without cause analysis.
  • Good output with rising defects or safety findings.
  • Scores reported without source data or definitions.

Run an efficient review meeting

Share the dashboard before the meeting. Discuss exceptions, causes, decisions, and actions—not every normal transaction. Include people who can approve operational changes. End with owners and dates, then send the agreed record promptly.

Continue beyond 90 days

Move stable measures to a monthly or agreed rhythm, retain faster reviews for high-risk issues, and revisit the baseline when volume, site, role, wage order, or process changes. A 90-day review is the start of disciplined service management, not its end.

Frequently asked questions

What should be measured in the first 30 days?

Measure filled positions, attendance, access, training, timekeeping, payroll setup, quality, safety, worker concerns, supervision, and urgent launch actions.

What changes in the 60-day review?

Shift from launch problems to recurring causes, service-level performance, targeted process improvements, and updated staffing or training assumptions.

What decision should be made by day 90?

Decide which controls to standardize, which risks remain, and whether to scale, reduce, or redesign staffing by role, site, and shift.

How often should reviews continue after 90 days?

Use an agreed monthly or operational rhythm for stable measures, with faster reviews for high-risk, changing, or unresolved issues.