A Microsoft Teams shift schedule can be drafted without opening the Shifts app by feeding four bounded inputs into a local round-robin generator: at least two unique employee names, one to four shift names, a real YYYY-MM-DD start date, and a range of one to thirty-one days. Microsoft Teams includes a Shifts app for frontline teams, but it requires setup, license assignment, and an admin who maintains the schedule inside Teams. A simpler path works when a manager just needs a transparent first-pass rotation that everyone can see, argue about, and adjust before the schedule is committed. The Shift Schedule Generator runs entirely in the current browser tab, accepts the four inputs above, fills every dated shift by stepping through employees in entry order, and exports a CSV that contains the exact rows shown on screen. The result is a deterministic draft — re-enter the same inputs and you get the same schedule — which makes it easy to review, reproduce, and hand off to whoever maintains the real Teams schedule.
How Teams Shifts Fits — and Where a Plain Rotation Draft Helps
Microsoft Teams' built-in Shifts app is the official route for frontline scheduling. It supports recurring shifts, open shifts that staff can claim, shift swaps, time-off requests, and integration with workforce management systems. For a permanent roster inside Teams, Shifts is the right destination.
The catch is overhead. Shifts requires the right Microsoft 365 license for each user, a configured team, and ongoing admin attention. When a team needs a rotation draft before that infrastructure exists — a small café covering two shifts, a student project with rotating presenters, a volunteer rota for a community event — the Shifts app is more machinery than the task deserves.
A round-robin draft serves the space between "no schedule at all" and "Shifts fully configured." It produces a dated table, keeps assignment totals close, and lets the team argue about fairness using concrete rows. Once the team agrees, the rows can be entered into Shifts manually, pasted into a separate SharePoint list, or kept as the working schedule if Teams Shifts is not on the roadmap.
The Four Inputs the Generator Requires
The generator is narrow on purpose, and that narrowness is what makes it verifiable. The Shift Schedule Generator expects exactly four categories of input, and each carries a clear rule:
| Input | Rule | Why it matters |
|---|---|---|
| Employee names | 2–50 entries, one per line, trimmed to 60 characters, unique without regard to letter case | Duplicate names such as "Alex" and "alex" are rejected as the same person |
| Shift names | 1–4 entries, one per line | Limits the table to a manageable shape and one shape per team |
| Start date | YYYY-MM-DD between 2000-01-01 and 2099-12-31, must round-trip through the UTC calendar | Impossible dates like 2023-02-29 or 2026-04-31 are rejected before any row is generated |
| Day range | Integer from 1 through 31 | Keeps the on-page table and CSV responsive on every device |
The generator also enforces a structural rule: the number of employees must be at least the number of daily shifts. This guarantees the round-robin step can place a different person on each shift of the same day, so one employee never receives two different shifts on the same date by construction. If your team runs two daily shifts, you need at least two employees; if you run four shifts, you need four or more.
Names and shift labels are kept short on purpose (60 characters max) and have control characters rejected. Spreadsheet-formula prefixes in any cell are also rejected before CSV export, which prevents a pasted name from being read as a spreadsheet formula when the file is opened in Excel.
Build a Rotating Schedule From Your Roster
Open the Shift Schedule Generator in any modern browser. The tool runs locally, so no sign-in or upload is involved.
- Type each employee name on its own line in the employee box. Use the names exactly as you want them to appear in the schedule. Two names minimum, fifty maximum, and every entry must be unique ignoring letter case.
- Type each shift name on its own line in the shift box. You can enter one shift (a single rotating role), two shifts (a typical day and evening pair), three shifts, or four shifts. Do not enter a shift twice on purpose — duplicates are rejected just like duplicate employee names.
- Enter the start date in the YYYY-MM-DD box, for example 2026-04-06. The date must be real, so 2026-04-31 is rejected because April has only 30 days.
- Enter the number of days to cover, an integer between 1 and 31. A two-week rotation works as 14, a working month as the number of weekdays or calendar days you want covered.
- Click the generate control. The table appears with every dated shift on its own row, and a totals panel counts how many assignments each employee received.
- Download the CSV. The download button only appears after a valid schedule is on screen. The file contains the header row Date, Shift, Employee followed by every row from the table, with every cell quoted.
- Open the CSV in Excel, Google Sheets, or any text editor to confirm the rows match the on-page table. Embedded commas and quotes inside a name stay data, not column breaks, because every cell is quoted and embedded quotes are doubled.
If you change any input afterwards, the previous result is cleared and the temporary download URL is revoked. Re-run the generator with the new inputs to produce a fresh schedule and a fresh download.
The Round-Robin Rule, Written in One Sentence
The assignment rule is deterministic and can be described in a single sentence: visit the slots in date order, then in the exact order shifts were entered, and assign the employee at index (day × shiftCount + shiftIndex) modulo employeeCount.
Worked example with three employees and two shifts, starting on day 0:
| Day | Morning (shiftIndex 0) | Evening (shiftIndex 1) |
|---|---|---|
| 0 | Alice (index 0) | Bob (index 1) |
| 1 | Cara (index 2) | Alice (index 0) |
| 2 | Bob (index 1) | Cara (index 2) |
Reading the index formula for the first six slots makes the pattern explicit:
- Day 0, Morning: (0 × 2 + 0) mod 3 = 0 → Alice
- Day 0, Evening: (0 × 2 + 1) mod 3 = 1 → Bob
- Day 1, Morning: (1 × 2 + 0) mod 3 = 2 → Cara
- Day 1, Evening: (1 × 2 + 1) mod 3 = 0 → Alice
- Day 2, Morning: (2 × 2 + 0) mod 3 = 1 → Bob
- Day 2, Evening: (2 × 2 + 1) mod 3 = 2 → Cara
Because the index wraps at the end of the employee list, totals over any generated range differ by no more than one. Running the same four validated inputs a second time produces the same six rows. That determinism is what makes the draft reviewable: anyone on the team can re-run the generator and confirm the numbers.
Bringing the CSV Into Microsoft Teams Shifts
The CSV is a portable artifact, not a direct Teams Shifts connector. Once the team accepts the draft, the standard handoff paths are:
- Manual entry: open the Shifts schedule in Teams, create each dated shift, and assign the employee named in the CSV. This is the most reliable path for small teams and keeps every assignment inside the official Shifts app.
- SharePoint list or Excel: paste the CSV into a shared workbook the team already uses alongside Teams, so staff can see the rotation in the same place they see other operational data.
- Compare and adjust: keep the CSV as the rotation plan and let people negotiate swaps in Teams chat, then apply the agreed changes to the Shifts schedule once the conversation settles.
The CSV format is straightforward. The first line is the header Date,Shift,Employee. Every subsequent line is one shift assignment for one date. Every cell is wrapped in double quotes; if a name itself contains a double quote, it is doubled so the column structure stays intact. Dates appear as written in the input field, so a start date of 2026-04-06 produces rows starting at 2026-04-06.
What the Generator Deliberately Leaves Out
The narrow contract is visible on purpose. The Shift Schedule Generator does not collect availability, requested days off, qualifications, seniority, contracted hours, breaks, overtime, rest periods, labor costs, union rules, accessibility needs, or jurisdiction-specific labor requirements. It is not a constraint solver, payroll system, time clock, compliance audit, or fatigue-risk assessment.
That list matters because balanced assignment counts alone do not prove a roster is safe, fair in every relevant sense, legal, adequately staffed, or suitable for a particular workplace. A round-robin draft treats every slot as interchangeable, which is rarely true in practice. Use the result as a starting point and apply the real constraints outside the tool:
- Check that every shift has the required number of qualified people for the role.
- Confirm availability directly with each employee.
- Add breaks, handoffs, and rest periods required by local rules.
- Review consecutive work patterns and any fatigue-risk limits.
- Apply overtime, contracted hours, and any collective-agreement rules.
Pair the rotation with a browser-based break schedule so each shift includes the recovery time the rotation alone cannot enforce. If someone cannot work a displayed assignment, edit the downloaded sheet or move the schedule into a dedicated workforce system that can encode the necessary constraints. The generator never claims that a simple rotation resolved those real-world requirements — the team has to do that step.
Review the Roster Before You Publish It
A quick review checklist catches most issues before the schedule reaches the team:
- Scan the assignment totals panel: every employee should be within one assignment of every other employee over the generated range. A larger gap usually means the input names did not all reach the generator.
- Read the first and last row of the on-page table and confirm the dates match the intended start and the chosen range.
- Open the downloaded CSV in a text editor and confirm the first line reads Date,Shift,Employee exactly.
- Pick two random rows from the middle of the table and verify the employee names appear exactly as typed, with no leading equals sign or quote that would be interpreted as a formula in a spreadsheet.
- Re-run the generator with the same four inputs. If the second run produces the same rows, the draft is reproducible and safe to share as the starting point for the real Teams schedule.
All names and schedule calculations stay in the current browser tab. No employee list is uploaded, stored in an account, or sent to a scheduling service. The temporary download URL is revoked after the file is saved or when the page closes, so a stale CSV cannot appear to match newer inputs.