Connect Deputy. Turn your rota into a clear owner action.
Moonmoot reads your Deputy rosters and timesheets, read-only, and turns rostered and recorded hours, open shifts and unapproved timesheets into a plain action for your board. Aggregate only, no staff identities, and quiet when the evidence is thin.
Read-only in practice. Moonmoot never writes to Deputy and never reads the staff record.
Your rota, working for the board
Moonmoot is built on evidence before intelligence. Your rota is workforce evidence: it helps the board see the week clearly and prompt one useful action, without grading your staff or inventing numbers.
Your rota joins the one business picture
Rostered and recorded hours sit alongside your books, till and bank, so your board reasons about the week from the same single picture, not a separate spreadsheet.
Open shifts and loose ends, surfaced
Unfilled shifts in the days ahead, and completed workdays whose timesheets are still unapproved or in progress, become a plain action while you can still deal with them.
Planned against recorded, in plain hours
The board can compare the hours you rostered with the hours actually recorded on comparable completed days, as context, without pretending to judge whether that was right or wrong.
Honest about what it can prove
Labour is treated as an auxiliary source. Connected does not mean complete: the board says what it can see and stays quiet where the evidence is thin.
Aggregate only, never personal files
Moonmoot reads shifts and areas, never the staff record. No names, no contact details, no pay or tax profiles ever reach the board.
Backed by real people
Behind the automated board is a real team. The workforce signals it reads are there to prompt a useful action, not to grade your staff.
Connect, set your timezone, then the board reads your rota
We set up the Deputy connection with you
During onboarding we connect Deputy together. You approve access on Deputy’s own screen; nothing is read until you do.
You set your business timezone
So the board can group shifts by your local day, you confirm the business timezone in settings. Until it is set, labour days stay in UTC and the board is deliberately cautious about them.
The board reads your rota as workforce evidence
Moonmoot reads your rosters, timesheets and areas, aggregates them with no staff identities, and keeps a summary the board can lean on when the evidence is strong enough.
From rota data to one clear action
Not a workforce dashboard. Concrete, evidence-gated prompts for your operations seat, each one something you can actually do. The kind of thing your rota unlocks:
Open shifts still to fill
When shifts in the schedule ahead have nobody assigned, the board can raise a single operations action to fill them, counted as shifts.
Timesheets waiting on approval
When completed workdays still carry unapproved timesheets, the board can prompt you to approve them, so recorded hours are final rather than provisional.
Timesheets left in progress
When completed workdays still have a timesheet marked in progress, the board can flag them to close out, so the record is clean.
Rostered but nothing recorded
When a completed workday was rostered but has no timesheet, the board can ask you to check it, so worked hours are not quietly missing.
Recorded but never rostered
When a completed workday has recorded hours but no roster, the board can flag the mismatch between the plan and the record.
Quiet when the evidence is weak
If Deputy is not connected, the summary is empty or stale, or the timezone is unresolved, the board raises no labour action at all rather than guessing.
Illustrative of the capability, not a promise of specific actions: what surfaces depends on your rota, your timezone and how fresh the data is.
Three things, stated plainly
Moonmoot reads only your rosters, timesheets and areas. It never opens the staff record, and the hours it works out are honest about what they are.
Rosters (planned shifts)
The shifts you have scheduled: when they start and end, which area they belong to, and whether a shift is open or assigned. Used to see planned hours and unfilled shifts.
Timesheets (recorded shifts)
The shifts actually recorded: start and end times, the area, and whether the timesheet is approved, unapproved or still in progress. Used to see recorded hours and what is not yet final.
Operational units (your areas)
The area or operational unit a shift belongs to, used purely as a label to group hours by area or operational unit. An area name is not personal data.
Hours from start and end times
Hours are measured as the span between a shift’s start and end. Moonmoot does not claim paid hours or break-adjusted hours, because those depend on rules it does not independently confirm.
Approval and progress state
Whether a timesheet is approved, still unapproved, or in progress, so the board can tell final hours from provisional ones.
A count of distinct people, then discarded
Employee identifiers on a shift are used only to count how many different people worked in a group, and are then discarded. No staff identity is kept.
To be precise: Moonmoot reads rosters, timesheets and operational units only. It aggregates them into a summary with no staff identities and no raw rows kept, and it never calls any write endpoint in Deputy.
Local days, so a comparison means something
A shift belongs to a day, and which day depends on your timezone. So that planned and recorded hours line up on the correct local day, Moonmoot asks you to set an explicit business timezone. It never guesses your timezone from your address, your country or the shifts themselves.
Until you set it, labour days stay in UTC and the board treats any planned-versus-recorded comparison as approximate, so it stays cautious rather than drawing a firm conclusion. Once the timezone is set, comparisons are grouped by your local day and the board can trust them.
Weak, stale or unresolved evidence stays silent
Moonmoot does not raise an action it cannot stand behind. Labour is an auxiliary source: connecting Deputy does not on its own put a workforce action in front of you. A labour action appears only when the evidence is strong, when Deputy is connected, the summary is present and reasonably fresh, your timezone is set, and there is something concrete to do.
If any of that is missing, if the connection is off, the summary is empty or several hours stale, or the timezone is unresolved, the board stays quiet on labour rather than guessing. And it never asks you to fix its own refresh timing; keeping the summary current is Moonmoot’s job, not yours.
Read-only, aggregate, and never the staff record
It never writes to Deputy. It does not create, edit, move, approve or delete shifts, timesheets or anything else. Moonmoot only reads.
It never opens the staff record. It does not read employee names, addresses, contact details, pay rates, tax details, emergency contacts or employment profiles.
It does not keep raw shift rows. Only an aggregate summary without staff identities is cached; the individual rows are not stored.
It does not present labour cost in money. Deputy does not confirm a currency to Moonmoot, so no monetary labour-cost figure is shown.
It makes no productivity, utilisation, efficiency, overstaffing or understaffing judgement, and sets no benchmark or ideal staffing level.
It never logs in as you and never takes an outward action in Deputy without your approval.
Your rota data, on your terms
Disconnect anytime. Remove the Deputy connection in your settings. This deletes Moonmoot’s stored Deputy connection, clears the cached labour summary and stops future reads. Moonmoot’s current disconnect does not revoke the authorisation inside Deputy.
Disconnect Deputy before deleting your business. This removes Moonmoot’s stored Deputy connection and cached labour summary. Your remaining Moonmoot data can then follow the normal 30-day deletion process: a short grace period, then permanent removal (GDPR right to erasure).
Aggregate, and used only for you. Access tokens are encrypted at rest, and only an aggregate summary of hours and counts, without staff identities, is cached. To produce your board’s analysis, relevant business context (which can include that aggregate) may be sent to our AI provider; under its commercial terms it is not used to train the provider’s models, and Moonmoot never uses your data for advertising. See our privacy notice for the detail.
See our privacy notice for the full detail. Questions about access or your data? Ask us and a real person replies.
Owner-operated businesses that run on shifts
It is built for owners who roster a team in Deputy: cafes, restaurants, bars, retail, salons, clinics, gyms and other local services where the schedule is a real part of running the week. If you plan shifts and record hours in Deputy, connecting it gives the board an honest read on the rota alongside your books and till. See the cafe and restaurant playbooks for how this fits a shift-run business.
When it may not be useful yet
- You do not use Deputy, or you do not roster in it, so there is little for the board to read.
- You have not set your business timezone yet, so planned-versus-recorded comparisons stay approximate.
- Your team is tiny and informal, where a rota tool adds little over a quick word.
- It is an auxiliary source: it supports the board on operations, it does not replace your accounting, till or bank connections.
For the wider picture on getting labour cost under control, see our guide to staff scheduling that stops losing money, and on tidying the paperwork behind a small food business, digitising bakery and cafe paperwork.
Honest limits: Moonmoot is guidance from the evidence it can see, not employment, legal, payroll or tax advice. It does not guarantee an outcome, and it works best alongside your own judgement about your team.
Deputy, answered plainly
What does Moonmoot read from Deputy?
Only three things: your rosters (planned shifts), your timesheets (recorded shifts), and your operational units (the areas shifts belong to). From those it works out planned and recorded hours, open shifts, and which timesheets are approved, unapproved or in progress. It reads nothing else.
Is the Deputy connection read-only?
Yes, in practice. Deputy does not offer a granular read-only permission (its only OAuth scope is a long-life refresh token), so Moonmoot enforces read-only itself: the connector can only call Deputy’s roster, timesheet and area reads, and it refuses every write. It never creates, edits, approves or deletes anything.
Does Moonmoot see my staff’s personal details?
No. It never opens the Deputy employee record. It reads shifts and areas only. Where a shift carries an employee identifier, that identifier is used only to count how many different people worked, then discarded. No names, addresses, contact details, pay, tax or emergency details are read or stored.
Do you show labour cost in pounds?
No. Deputy does not confirm a currency to Moonmoot, so it does not present any monetary labour-cost figure. The workforce signals are about hours, open shifts and approvals, not money.
Why do you keep asking me to set a business timezone?
Because a shift’s local day depends on your timezone. Without an explicit business timezone, Moonmoot groups shifts in UTC and treats any planned-versus-recorded comparison as approximate, so it stays cautious. Set the timezone in settings and local-day comparisons become trustworthy.
Will connecting Deputy add noise to my board?
No. Labour is an auxiliary source and quiet by default. If Deputy is not connected, the summary is empty or several hours stale, or the timezone is unresolved, the board raises no labour action. A labour action appears only when the evidence is strong and there is something concrete to do, like an open shift or an unapproved timesheet.
Does Moonmoot judge whether I am over or understaffed?
No. It can show rostered hours next to recorded hours on comparable completed days as context, but it makes no productivity, utilisation, efficiency or staffing-quality claim, sets no benchmark, and never says you are over or understaffed. Those are your calls to make.
How fresh is the labour information?
The summary is cached and refreshed periodically, so it may be several hours old. Moonmoot does not promise a live, to-the-minute view of your rota, and it never asks you to fix its own refresh timing.
How do I disconnect Deputy?
Remove the connection in your Moonmoot settings at any time. This deletes Moonmoot’s stored Deputy connection, clears the cached labour summary and stops future reads. Moonmoot’s current disconnect does not revoke the authorisation inside Deputy.
What happens to my Deputy data if I delete my business?
Disconnect Deputy before deleting your business. Disconnecting removes Moonmoot’s stored Deputy connection and cached labour summary. Your remaining Moonmoot data can then follow the normal 30-day deletion process: a short grace period, then permanent removal.
Are you a Deputy partner or listed on the Deputy marketplace?
No. Moonmoot is an independent product and is not affiliated with, endorsed by, or certified by Deputy, and it does not claim any marketplace listing. It simply reads the rota data you authorise.
See what your board reads from your rota
A free, honest read on your own business. No card, no signup for the read.
Not ready for either? Just ask us a question. No card, no signup, ever for the read.
Moonmoot gives business guidance based on the data it can see. It is not financial, legal, tax, or investment advice.
Deputy is a trademark of Deputechnologies Pty Ltd. Moonmoot is independent and is not affiliated with, endorsed by, or certified by Deputy.