Questions, answered plainly

Flat, per location. $49 a month, or $470 a year, at one location or ten. Your state's meal and rest break rules are built into that price — there's one plan, so there's no higher plan to hold them back for. Never per employee either: a team of 8 and a team of 40 at one location pay exactly the same. Full details are on the pricing page.

The setup questions ask. On Where do you operate?, under the state, say how many places you schedule and name them. Each place gets its own opening hours and its own coverage; everything else stays one thing — one roster, one week, one place to look. You can add more later under Settings → Locations, which has no limit. On each person's profile you say where they can work: one place, several, or leave it blank and they can work anywhere, which is how you handle a floater or a provider shared across sites. Setup can add locations and never removes one, so answering “just the one” over a board that already has five leaves all five alone. Billing is per location, the same price at one location or ten.

Make each department's jobs a role. There is no separate department setting and there doesn't need to be one: the drafter never puts somebody into a shift for a role they don't hold, so departments keep to themselves without you managing anything. A practice with dental assistants, medical assistants and behavioural therapists is three roles, and coverage then asks for the ones each shift actually needs. The short version — locations are separate buildings, roles are the jobs inside them, and posts are the stations people rotate through during a day.

Yes, and no card. When billing opens, every new account starts with 30 days free with every feature on. Scheduling runs on a weekly rhythm, so that's four full scheduling cycles to judge it. Right now, during the tester program, everything is free with an access code.

You pick a plan, or you don't. If you don't continue, your data stays exportable — schedules, team, everything goes out as a spreadsheet (CSV) and PDF whenever you want. Nothing is held hostage.

Cancel any time, no contracts, no setup fees, no per-user fees. Canceling stops the renewal and your access runs to the end of the period you paid for; if you would rather stop now and have the unused days back, ask and we will refund them — the exact terms are in the refund policy.

There are no paid users at all. Pricing is per location, so it doesn't matter how many people manage the schedule or how many staff are on it.

Nothing changes on your bill. Add or remove people freely — the price is the same on the day you hire your 30th employee as it was with your 8th. A departing employee's history stays in your schedule records.

Yes. Under Team, switch them from On the roster to Set aside and say why — extended leave, furlough, out of season, or they have left. From then on they are in no draft, counted for no coverage rule and sent nothing, while their roles, hours, availability, licenses, time-off balances, notes and every week they already worked stay exactly as they were. Put an expected-back date on them and Weeksolved reminds you when it passes — it never puts anyone back by itself, because somebody returning from months away may have different availability. One press restores them. Setting someone aside does not touch posted weeks; deleting a role does update the role on any posted shifts that used it, so check posted weeks after a role change.

No — that's the point. Only the manager signs in. Staff get their schedules the way they already live: text, email, a printout, or a calendar file that drops shifts straight into their phone. Nothing to install, nothing to teach, nobody locked out.

Yes. Weeksolved sends a one-page form you attach to the schedule. Your person opens it on their phone — no app, no account, works with no signal — picks the shift they can't work, adds a reason if they want, and gets a short code they send back to you by text, email or however you already talk. You paste the code in and it lands on your list. Nothing on the schedule moves until you decide. Let it go and the shift comes off their week and becomes an open shift the rest of the team can ask for, through the same offer file. If two people have already agreed a trade between themselves, Check a trade tests it against every rule — hours, turnaround, availability, coverage, licenses — before you approve it.

They all arrive in one place. Six kinds of form go out from Weeksolved — an open shift, a shift somebody can't work, a request, a starter form, a vacation pick, a holiday poll — and each one gives the person a short code to send back however you already talk. On Home, A reply came back takes any of them: paste the code and Weeksolved reads it, tells you what kind it is, and opens the screen that already knows how to check it, with the code filled in. It routes; it never applies. Every rule that screen checked before is still checked, and nothing moves until you say so. A code that isn't ours, or one from an old form, is refused with the reason.

Yes, on the Day sheet. Write the lists once — one line per thing, in the order it happens — and say whether each is an opening list, a closing list or one for during the day, and which weekdays it applies on. They then show on every day sheet with tick boxes and travel with the day when you print it, copy it or send it. Each list falls to whoever actually starts first and finishes last that day rather than to a person you name, so it keeps working when somebody swaps or calls out, and ticks belong to that one date. If you haven't written any, Weeksolved offers a typical list for your kind of business to start from. It is a working list, not a signed record — there are no staff accounts, so nothing is timestamped against a person.

Team opens with a card called The paperwork. It gathers the things that are not the schedule but will bite you if nobody watches them: a licence that has run out or runs out inside thirty days, somebody with no email or phone so nothing you send reaches them, people with nothing on file yet, a time-off balance in the red, and vacation picks that have not come back. Each line explains itself in a sentence and carries the one button that deals with it. Nobody is ever drafted onto licensed work without a current date, so an expiry that slips past takes them out of the draft rather than quietly onto a shift they should not be on. The card reads what is already on your board, changes nothing by itself, and is not drawn at all when there is nothing outstanding.

It asks first, counts what would go, and gives you three answers. Set aside is offered first and is usually right even for a person who has left: they come off every schedule from now on and nothing at all is deleted. Remove from the roster, keep the record takes their file away and frees any shift still ahead of them, while every shift they have already worked stays on its week with their name still readable on it — the one to choose if you keep schedules for your records. Remove everything deletes the person and all their shifts, says plainly that any posted weeks will no longer match what you printed, and asks a second time before doing it.

Yes, and you can rotate the day off. A 9/80 sets two things on each person's profile: which day is the day off, and which of the two weeks in the period it falls in. Put some of the team on the first week and the rest on the second and the day keeps its cover both times rather than everyone being out at once. If two or more people end up on the same day in the same week, Weeksolved says so before it becomes a problem. Other patterns are there too — four by ten, three by twelve, seven on and seven off, and week on week off — and each draws two weeks of squares under the setting so you can see the shape rather than work it out.

Yes. Removing a shift is rehearsed before it happens: the change runs on a throwaway copy of the week, every check runs again, and if it would cause anything new — a coverage dip, an open shift, somebody now under their hours — you see the list and decide. For the fix list, where some options change rules and settings rather than the week, Weeksolved checks straight afterwards and tells you what the fix cost, with a one-press Put it back. Nothing is decided for you; a fix that causes a smaller problem than the one it solves is often the right call, and the point is that you know it is a trade.

Yes, two different ways depending on what you mean. On a person's profile, Hours past the guarantee can be set to ask me first: the drafter then treats their guaranteed number as the cap, and if the week comes up short you are offered the extra hours to approve for that week only — it never edits their profile and never carries forward. Separately, How they're used can be set to only called in when there's a gap, for somebody you would rather not schedule at all unless coverage demands it; the drafter builds the week from everyone else first and only then reaches for them.

Yes, by default. A full-timer contracted to 40 hours with 8 hours of holiday pay is on contract at 32 hours on the floor — 32 worked plus 8 paid is the 40 their payslip shows — so the drafter stops there and the week is not flagged as short. A holiday somebody is rostered to WORK is never counted twice: those hours are already in the week, and the holiday premium is money on top. An hour cap is unaffected either way, because a cap is about hours actually on the floor. If your guarantee is a promise of hours worked rather than hours paid, there is a switch for it under Settings → Hours, guarantees and patterns.

Yes. Print & PDF on the Week view asks how many weeks you want (one page per week, up to 26) and, for day sheets, which days — one, the whole week, or any you tick — one page per day. Every page carries the holiday's name and hours in its heading when a holiday falls in it. On a phone or in the Home Screen app the PDF opens in a new tab so you land back where you were when you close it; on a computer it downloads. The Excel workbook for the week is under Export & share.

Yes. Settings → Hours, guarantees and patterns has a row of day boxes called Which days extra hours may land on. Untick Saturday and Sunday and hours owed on a guarantee are made up Monday to Friday. If the ticked days genuinely cannot take the hours, the drafter uses the next open day and the week's checks say so, naming the day. Every day is ticked unless you change it, so nothing changes until you do.

Any modern browser — phone, tablet, or computer, Mac or Windows, iPhone or Android. There's nothing to install and everything you can do on a computer you can also do on a phone.

Yes. On the sign-in screen, press Sign in with Google. If you already have a Weeksolved account under that email address it is the same account — your board is right where you left it. New to Weeksolved? After Google confirms who you are, you enter your access code and you are in. On an iPhone or iPad, and in the app added to the Home Screen, Google opens in a sheet and brings you back; if a particular device will not, the screen says so and your email and password still work. You can add a password to a Google account under Settings → Your account.

About ten minutes, once. The setup questions ask about your hours, roles, shifts, team, and rules — most answers are just picking an option, and team lists can be pasted in whole. After that, a week is one button.

Pick your state and every drafted shift gets its meal placed to that state’s rule, rest breaks laid around it, and staggering that never drops coverage below your minimums. This is included at every location, and on the free trial too. Break, coverage and hour-cap problems are flagged as you draft, and printed schedules show where every break was placed. Always look over the week before you post it. Weeksolved is scheduling software, not legal advice — you stay in charge of your own compliance.

No. It only ever schedules shifts you've defined, from the pool you set. If your coverage can't be met, the slot stays open and it tells you the rule that stopped each person — then shows you the ways out, clearly labeled, least disruptive first.

Every flagged problem carries a Fix button — on Home, in the checks panel, on every coverage dip on the day sheet, and on the break sheet. It opens one short list: what fixes it this week (stretch a shift already on the day with the overtime priced, move a meal to a time the floor holds, waive a meal where your state allows, bring someone in, hand a shift to someone who is clear) and what stops it coming back (let a meal count as on duty for that rule, close the doors for lunch on solo days, take a day out of a rule, schedule one more person that weekday, change your hours). One option is marked Recommended. Nothing is invented — every option uses shifts, people and rules you already have — and the checks run again the moment you press one.

Holidays sit alongside the days of the week. Wherever you set Coverage needs — Sunday through Saturday — there is an eighth tab called Holidays, and whatever you put there is what a holiday gets, instead of the weekday it happens to land on. One pharmacist on Thanksgiving is one row: one pharmacist. Each holiday can also be closed outright, cut to reduced hours, or given its own opening hours, and there is a switch that stops anyone being added to a holiday just to reach their guaranteed hours — so a slow holiday stays a skeleton crew instead of quietly filling back up.

Yes. Coverage needs has a Peak hours setting for each day of the week — say 11am to 2pm on a Friday — and the drafter steers people towards shifts that cover them. It steers, it does not override: your coverage numbers, break rules, hour caps and everyone's availability still come first, and peak hours only break a tie between shifts that were equally good anyway. If a peak stretch ends up thin, you get told rather than quietly left short.

Next to almost every setting there is a small ? button. Press it and it says, in a sentence or two, what that setting does and what changes if you switch it — no leaving the page, no searching the Help centre for the right words. The Help & FAQ page inside the app is still there for the longer answers.

Both, and you choose which. Every fix list has two halves: what fixes it this week and what stops it coming back. When the same flag shows up in two or more weeks — a dip every Tuesday, one person over their cap week after week — Home lists it under This keeps happening with a Fix for good button that opens only the permanent changes: a rule lowered or narrowed, one more person on that weekday, the doors shut for lunch, a cap or contract updated. Nothing is ever changed on its own. A temporary patch each week is still a perfectly good choice; the point is that the pattern is pointed out so your schedule improves over time instead of being patched every Monday.

Where your state allows it, yes. Under Scheduling rules, meal waivers have three settings: not used; manager decides, where you waive a meal shift by shift from the day sheet or a Fix list; and automatic, where every meal your state lets you waive is left off as the shift is drafted, so a six-hour shift stays six hours. Each person can opt in or out on their Team profile — someone with a signed waiver on file can be set to always, someone who never waives to never — and the Team page shows who is which. When a shift runs a few minutes past a meal line (6:05 instead of 6:00), the shift editor says so and offers to end it on the line with one press.

Yes. A card called Worth a look on Home and at the top of Scheduling rules points out where the rules, the roster and the coverage do not add up — a turnaround no shift pair can meet, a role with nobody in it, a cap that makes someone unschedulable, a house rule stricter than it needs to be. Each line explains why in a sentence and offers the change. Nothing is applied on its own, any suggestion can be dismissed, and the card can be switched off in Settings.

Yes, and they are kept apart on purpose. Posting the week is one thing; the Day sheet has its own Hand out the day, where you pick which days (today, the next few, or any days of a posted week), whether each person gets only their own lines or the whole day, and how it goes — text, email, a copy to paste, or a printout. You can also have the day sheet go out by itself each morning, but only for days inside a week you have already posted, only if you switch it on and confirm, and it is off until you do. A posted week’s day sheet can be redone — breaks, posts and mentors re-laid for that one day — without touching the weekly schedule people already have.

No. Posting a week asks once, with the week and who will see it; sending from Weeksolved asks once, with how many people it is going to. Both can be set to Don’t ask in Settings if you would rather not be asked. Anything that sends by itself asks for a confirmation when you turn it on, and is off by default.

Please do. The same ⚑ button that reports a problem has an I have an idea switch; it goes straight to the people who build Weeksolved, with nothing but what you typed and the screen you were on. Problems and ideas both stay open for every account, testing or not, and good ideas end up in the app and on the What’s new page.

Almost nothing. Every rule, every check, the drafter, breaks, hand-outs and exports are on. Two things are sized for a trial: you can draft up to six weeks ahead, and sending from Weeksolved’s own server is capped at 200 messages a month — past that your own mail or messaging app opens with the message ready, so nobody is left without a schedule. A paid plan lifts both.

One place of business with its own hours, team and coverage needs — one shop, one clinic, one café. Pricing is per location. Running several? Add them under Settings → Business → Locations: each site keeps its own coverage needs and posts, people are marked with where they work, and the week is drafted as one roster across all of them, so a floater's hours are counted once and overtime is right. The Week view filters by location and the day sheet shows a lane per site.

No. Nothing that identifies one of your people — name, phone, email, hourly rate, accrued time off, license dates, your notes, or their schedule history — is sold, rented, published, or given to anyone for their own purposes. That is section 3.1 of the Terms, so it is a promise we owe you contractually, not a policy line we could quietly rewrite. There are three ways it can leave your account and none of them is us deciding to pass it on: you send it, our database provider stores it so the service can exist, or valid legal process compels it — and then we tell you first unless we are legally forbidden from doing so. Worth knowing too: none of it is required. Weeksolved drafts a full week from first names alone.

Your schedules live in your private account, encrypted in transit and at rest on Google Cloud infrastructure, and no one else's account can see them. There are no ads, no trackers, and your data is never sold. The security page spells it all out.

Checkout runs on Stripe and takes the usual cards and digital wallets. Prices are in US dollars and shown before tax. Weeksolved is the seller of record; we add sales tax only where we are registered to collect it, and California does not tax software subscriptions. We sell to businesses in the United States.

The Help & FAQ page inside the app answers most things in seconds, the ⚑ Report button files a problem in ten, and Contact us messages go straight to a person. A real human reads every message and replies to the email on your account.