Deputy Virtual Assistant: rosters built, timesheets chased

Nobody searches “deputy virtual assistant” for fun. You search it on a Sunday night, with next week’s roster half-built, three people who haven’t confirmed, a timesheet queue you haven’t touched since Wednesday, and payroll due Tuesday. The venue runs on Deputy. The person running Deputy is you, between the lunch rush and the close.

Deputy is genuinely good at the hard part. It interprets awards as you build, warns you about breaks and overtime before you publish, pushes the roster to everyone’s phone, and lets staff swap shifts and request leave without a single text to you. The platform is not the problem. The problem is that every one of those features still needs a person to drive it, and that person keeps being the owner.

The weekly rhythm a VA runs in your Deputy

Roster first. Your VA opens the Schedule, copies forward the stable week, then adjusts for what’s different: the function on Friday, the staff member on leave, the area you’re short. They build against the template and the demand you’ve set, create open shifts where there’s a gap, and read every award warning Deputy raises along the way rather than clicking through them. Then they hold it for you. You glance at the draft, approve, and it publishes to the team’s phones. A roster that used to eat your Sunday night becomes a five-minute review.

Then timesheets. This is the one that quietly costs you money. Deputy logs the clocked times, but somebody has to work the queue: check each shift against what was rostered, query the missing clock-out from Saturday, and get everything to approved before payroll closes. Your VA does that as a daily pass, so on pay day the export into Xero or MYOB is a clean two minutes, not an hour of detective work against the rostered shifts.

Through the week, the moving parts. A swap request lands: reviewed and actioned. Someone calls in sick at 6am: the shift goes out as an open shift, or the VA messages down the list until it’s covered. A leave request appears: triaged against the published roster, conflicts flagged, and queued for your approve-or-decline with the context attached. The roster stays true to who is actually working, which is the entire point of having one.

If you run more than one site

Multi-venue is where a Deputy VA earns the most, because the admin scales with locations but your hours don’t. Your VA builds each location’s roster against its own template and demand, keeps the areas straight (kitchen versus floor, AM crew versus close), and runs one consolidated timesheet pass across every site before payroll. They can be scoped to a single location on Location Manager if you’d rather keep the sites walled, or sit at account level on Advisor to cover all of them from one seat. Either way you stop being the only person who can see across the whole roster, which is usually the thing that’s been keeping you tied to it.

The same goes for casual-heavy teams. When half your roster is casuals picking up open shifts and swapping between themselves, the swap and open-shift queue never sleeps, and that’s exactly the kind of constant low-stakes triage that should never have been the owner’s job in the first place.

The honest bit

Two lines we keep bright, because they protect you.

Deputy automates award interpretation, and that is exactly why a VA must not touch the configuration. Your pay rates, your award rules, your penalty and overtime setup are a payroll and compliance decision that stays with you or your bookkeeper. The VA works inside what’s already configured. When Deputy throws a break or minimum-engagement warning, they read it, fix a genuine roster error, and escalate anything that smells like a real award question to you. They never guess at compliance, and they never set a rate.

And the final sign-off stays where you want it. The VA chases, checks and readies the timesheets, but most owners keep the last approval click and the actual pay run for themselves. That’s not a limitation, it’s the right division: the VA removes the hour of legwork so your decision takes two minutes.

What stays with you

Pay rates and award setup, the final timesheet approval, the pay run, and any genuine employee-relations call. Deputy’s access model makes this easy to hold rather than hope for. Put the VA on the Advisor access level and they can set up and run your schedule, add people and manage integrations, but they cannot clock on, be rostered, or be paid through your account, which keeps a virtual assistant cleanly outside your payroll. If you’d rather they publish rosters and approve timesheets for one venue, Location Manager scoped to that single location does it without reaching your other sites. We default to the least access that lets the work happen, and you decide.

One practical detail: Deputy charges per active user. The right access level, set up properly, means the VA’s seat adds little or nothing to your subscription rather than another full per-head charge.

What it costs and where to start

Deputy admin sits on the admin tier, $12-17 AUD an hour excl GST, typically 10-15 hours a week for a single-venue or small-multi-site operator, covering roster builds, the timesheet queue, swaps, open shifts and leave triage. If the VA also fields front-of-house enquiries or keeps your booking and staff calendars straight, fold that into the same hours. Placement takes 7-10 business days, with 5-7 days supervised inside your Deputy before solo work, a 30-day recalibrate-or-replace guarantee, and no lock-in beyond 14 days notice.

If you want the industry view, the hospitality page goes deeper on venue admin, and the VA cost guide lays out the full pricing picture. Otherwise book a discovery call with Jenn, who has placed 48+ VAs into Australian businesses since 2024 and will tell you straight if your venue isn’t ready for one. Bring last week’s roster and your current timesheet queue. We’ll find the hours.