Writing a roster request in plain words
How plain can the request be?
Very plain. You don't need special wording. Write it as if you were briefing a new colleague who's good with spreadsheets but has never been to your workplace.
The tool works from your text. If the text is vague, the draft will be vague. It may also fill gaps with guesses, and AI tools can produce plausible but incorrect statements.1 A guessed rule inside a roster is easy to miss.
What should the request say, in what order?
Put the job first. Then the facts. Then the limits. Then how you want the answer shaped.
- The job. "Draft a roster for next week for a four-person café."
- The shifts. Each day, start time, finish time, and people needed. Use the list you made on the gathering page.
- The people. First names, role, and when each can and can't work.
- The hard limits. Things the draft must never break.
- The format. "Give me a table with days across the top and names down the side."
What counts as a hard limit?
Anything you'd have to fix by hand if the tool got it wrong. Write each one as a short sentence.
- "Sam can't work Tuesdays."
- "Nobody works a closing shift and an opening shift on back-to-back days."
- "Only Priya and Jo can run the till."
- "Every shift needs at least one person who can open up."
- "Don't give anyone more hours than I've listed for them."
Say "never" or "must" for the true limits. Say "if possible" for the wishes. The tool can then tell a rule from a preference.
Awards and agreements in Australia can set extra rules about changing rosters and how and when employees are given rosters.2 If your award has such a rule, add it in your own words after you've read it at the source. Don't ask the tool to recall it.
Should I ask the tool what the rules are?
No. Give it the rules you've already checked. Don't ask it to supply them.
If you ask "what are the break rules for my staff?", you may get an answer that sounds sure but isn't correct. Or it may describe another country's rules. Read the official page yourself. This page points to where.
What does a good request look like?
Here's a short example, with made-up details:
Draft next week's roster for a small bakery. Open Monday to Saturday. Shifts: early baker, counter opener, counter closer. Each needs one person. People: Ana (baker, any day except Sunday), Ben (counter, afternoons only), Cho (counter, mornings only). Hard limits: Ana never works more than the hours I give her. Ben never closes on a school night. Output a table, then list anything you couldn't fill.
The last line matters. Asking the tool to name the gaps makes it say so, instead of covering them over with a guess.
What if the first draft is poor?
Reply with the specific fault. "Cho is down for an afternoon, and she's mornings only. Fix that and leave everything else alone." Short, exact fixes work better than "try again".
Don't keep asking until it looks right. A table that looks right can still hide a problem. The draft needs a proper read. The steps are in How to check an AI-drafted roster.
Keep a copy of the request you used. Next fortnight you'll only change the dates and the leave.
Sources used
- Large language model, Wikipedia
- Rosters, Fair Work Ombudsman (Australia)