Build my week: your first draft already knows your state's rules

Released October 13, 2026.

I have kept a ratio sheet in Excel by hand. Imagine it’s Sunday night, and you’re building next week’s schedule. You put everyone’s shifts in, then check the ratio hour by hour. Then one change at 11 AM sends you back through every hour again.

That is the work Build my week takes on. It was released on October 13 for managers in RxShift. Instead of placing every shift yourself and then checking the rules, you can start with proposals that have already been checked against your state’s ratio, hour, and break rules, along with your own limits.

It is still your week to review. The difference is where you start.

Tell it what your pharmacy’s week looks like

In Settings, you can define a standard week for each location: the weekday, start and end times, whether you need pharmacists or technicians, and your minimum and target staffing levels. Blocks cannot cross midnight yet.

If you already have a published week you want to use, you can import it. RxShift shows the blocks it finds and replaces your standard week only after you confirm.

Those staffing targets are yours. They are not legal requirements, and they do not override the rules.

The draft starts from each person’s usual shifts, which you set up on their staff record. On Build Schedule, select Build my week, choose your location and week, and select Draft it. Drafting uses RxShift’s own rule check.

When the target and the rule disagree, the rule wins

Here’s the specific example from the demo pharmacy: Monday’s target from 11 AM to 2 PM was four technicians. With one pharmacist on duty, the applicable limit was three.

The draft proposed three technicians and explained the limit. It did not quietly add a fourth to make the target look met.

That distinction matters. If your requested staffing exceeds what the rules allow, then RxShift leaves hours short and tells you why. An unmet target is something you can review before the week starts, rather than a rule conflict hidden inside a full-looking calendar.

The review panel shows proposed shift and staff counts, unstaffed hours and their reasons, and usual shifts it could not place. It also reports problems in existing scheduled shifts and whether the final check found no hours out of ratio and no warnings.

You stay in charge

Proposals appear as outlined blocks marked “Proposed.” They are not shifts until you accept them.

You can accept all proposals, accept proposals for selected people, or discard them. Selecting only some people triggers another check. RxShift refuses acceptance if that selection would introduce an hour out of ratio or a warning that was absent from the whole draft.

Accepted proposals become ordinary draft shifts. Nothing is published or sent to staff until you publish, and publishing runs the usual check.

If time off, a shift, a staff record, or other relevant information changes after drafting, RxShift refuses to add that draft and asks you to build the week again. The earlier check cannot stand in for checking changed information.

There is also Undo this build. It removes shifts that remain exactly as proposed. Edited or already published shifts stay, and you cannot draft over a published week.

Where Ask AI fits

After drafting, you can use Ask AI for plain-English schedule edits. That is separate from Build my week. The first draft comes from the rule check.

Ultimately, I want you to have something useful to review, with the short hours and their reasons visible. Not a calendar that looks finished because it ignored the limit, and not a week sent to your staff before you’ve decided it’s ready.