Microsoft Teams Shifts: staff scheduling and timesheets

Can Microsoft Teams Shifts manage a staff rota?

Microsoft’s Shifts introduction distinguishes the standalone app from a connected workforce-management system. Confirm which arrangement you are evaluating: a connector can change where the schedule is maintained and which actions are available.

This guide reviews public documentation on 16 October 2026. Its rota, people references, requests and clock records are fictional exercises. They are not observations from a completed Microsoft trial or real employee records.

Check the actual Teams licence and account type

Microsoft’s Shifts administration guidance says users need a Teams licence and that Shifts does not support Teams guests. Being able to join a team or chat is not evidence of access to its shift schedule. App availability can also be controlled by the organisation’s administrator.

Before a pilot, inventory who needs to manage schedules, view their rota, request changes, clock time and review exports. Confirm the actual licence and permitted role for each account. A Microsoft 365 product name alone does not establish that the required Teams entitlement is assigned.

The practice brief uses four member references, W01–W04. G01 is a guest-account access check only and is assigned no shift. These are proposed evaluation roles, not real invitations or licence assignments. If external or agency workers need access, resolve that requirement explicitly rather than assuming guest chat covers scheduling.

What does “staffing software” mean for your business?

The term staffing software can refer to different work. This article focuses on arranging existing workers’ shifts. It does not evaluate an agency recruitment platform, calculate wages or establish payroll compliance. For hiring, use the HR software versus ATS guide; for personnel records, use the employee database checklist.

A saved draft and an open request are different from a staffed rota

Microsoft’s schedule publication instructions require sharing a new or updated schedule to make the changes visible to workers. Review the shared date range and the notification choice; saving a manager’s draft is not the same event.

The shift-request instructions describe open shifts as unassigned positions that workers can request. Requests go to a manager for approval. For a swap, a colleague’s acceptance precedes final manager approval. A pending request should therefore remain a separate state in the staffing review.

Decide which view the operational team will rely on. For each required position, ask whether it is assigned, shared and compatible with the worker’s stated availability. Keep unresolved positions visible. A total of assigned hours can hide a draft, an open position or an availability conflict.

Reconcile an eight-position rota before calling it covered

Assume a fictional service team needs a supervisor and a service worker in each four-hour morning and afternoon block on 19–20 October 2026. Times are local Europe/London. There are no overnight shifts or daylight-saving transitions in this example. Gross position-hours exclude planned breaks and any additional break cover.

• 32 gross position-hours required: eight positions × four hours.
• 28 hours assigned: S04 remains open.
• 24 hours shared and assigned: S05 is still a draft.
• 23 hours shared, assigned and within the stated availability: S06 includes one hour before W02 is available.

The unresolved total is nine gross position-hours: four open, four draft and one outside the stated availability. Those three gaps are separate in this fixture, so they are not double-counted. Pending R01 does not fill S04. This is editorial reconciliation, not a Shifts-generated coverage report or proof that the app automatically detects every conflict.

In a real evaluation, add the required skills, breaks, leave, location and approval rules. Record how the proposed system exposes exceptions and who resolves them. Do not replace that review with a single scheduled-hours total.

Compare original, edited and employee-confirmed time

The three hypothetical clock records below refer only to Monday’s S01–S03, with 720 gross planned minutes. Net recorded minutes subtract all stated breaks from the clock interval; this is an arithmetic convention, not a rule for paid hours.

The original net total is 715 minutes (11h 55m); the edited total is 705 minutes (11h 45m). The employee-confirmed subset contains 465 edited net minutes (7h 45m). C01’s remaining 240 edited net minutes are unconfirmed.

C01’s edit removes ten minutes from the original interval. C02 retains its fifteen-minute break. Gross planned intervals and net clocked time have different bases: these figures do not establish absence, underpayment or a payroll-ready total. Employee confirmation also does not establish manager or payroll approval.

The records use our editorial schema. They are not a reproduction of a Microsoft export or an import file for Shifts.

Export the schedule or the timesheet for the right purpose

Schedule export offers an Excel format intended for re-import, or a reporting view with selected daily-hours, time-off and shift-note information. For re-use, Microsoft says to update the relevant start/end dates before importing. A reusable rota template and an account of recorded work are different deliverables.

The separate time sheet report applies when the team uses time clock. Its workbook includes Original Time Clock Report, Final Time Clock Report and total worksheets. “Final” includes worker edits; the Confirmed column indicates whether the employee confirmed the entry. Neither label substitutes for the organisation’s payroll approval.

Reconcile the original and edited intervals, break fields, date range and employee references before handover. Agree which fields the receiving process uses and where exceptions are reviewed. An exported workbook is not proof that a payroll integration is configured, that every row is approved or that the receiving service interprets the fields as intended.

Test the phone, time zone and visibility settings

Microsoft’s schedule settings guidance covers the team time zone, enabled request types, time clock and controls for colleagues’ shift notes and time-off detail. Some controls can be managed by IT. Record the settings actually used in the pilot instead of assuming a missing control is available to every manager.

Check the intended worker phone and the manager’s desktop or web client separately. Have an authorised participant locate the right date, read the shift, make a permitted request and inspect its status. Review the visibility of colleagues’ information with fictional data. The worker should see the agreed operational context without unintended notes or reasons.

This example deliberately avoids overnight and clock-change arithmetic. If either matters to your operation, add a dedicated case in the actual team time zone. Do not extend same-day subtraction into an untested overnight, time-zone or pay calculation.

Use the same ten checks in the retained plan

The worksheet is a proposed evaluation. Confirm permission before operating any vendor account, inviting anyone, publishing notifications or exporting employee information. Record the actual product, plan, client, role and observed result; no check below is reported as a completed product pass.

For cost, list the actual Teams entitlement, any connected workforce system, configuration, support and payroll integration separately. Use the software total-cost guide with quoted amounts. This guide does not invent a standalone Shifts price or assume that every Microsoft 365 package supplies the same scope.

Download the practice files and define the next handover

Download the fictional eight-position rota ↓

Download the three-record time review ↓

Download the blank trial-review worksheet ↓

Read the assumptions and mapping instructions ↓

The files contain original editorial data, not real employee information or universal vendor templates. Observed results and approval decisions remain blank. No account, schedule, notification, licence, clock entry, export, payroll or integration was operated for this article.

Use the Microsoft Teams profile for wider collaboration context and the HR directory to explore related systems. After the rota and time-review requirements are clear, the HR reporting guide helps define the population and metric behind a report. A rota position, an employee record, a recorded time interval and a payroll result are different units.

Frequently asked questions