- AV rostering is event-driven: early starts, late finishes, overnight changeovers and casual crews. Office-hours tools don't fit.
- Positions, shift templates, each person's normal-week pattern and recurring series build a week in minutes; drafts publish when it's set.
- Open shifts are claimed from a phone, with manager approval if the site wants it; leave uses an Australian taxonomy with approvals and clash detection.
- Rostering inside the AV platform means the rostered technician is the one the tickets, tasks and maintenance are assigned to.
Why AV rostering is different
Retail and hospitality rostering tools assume shifts that repeat and locations that don't move. AV crews work a calendar of events: a 5am wakeup-check shift before the conference, a 14-hour day for the gala, an overnight changeover between two exhibitions, a Sunday for the wedding, and a quiet Tuesday. Positions matter: an event lead isn't interchangeable with a day tech. Casuals work across venues. Leave has to be approved against what's already rostered, and when a technician drops a shift, someone has to pick it up by tonight.
The spreadsheet handles none of that well, and it has a deeper flaw: it doesn't know who's on shift when a ticket comes in. AVDesk's rostering module was built for AV crews and lives in the same platform as the tickets, tasks and maintenance, so it does.
Building the week
- Positions, colour-coded roles such as day tech, evening tech, event lead and casual, so the grid reads at a glance.
- Shift templates for the standard calls: start, end, break and position prefilled with one click.
- Each person's normal week as a pattern that generates their shifts for the period, skipping days already rostered or on approved leave, and every generated shift stays editable for the exceptions.
- Recurring series for the regular shifts and one-off shifts for events, with overnight shifts that end after midnight handled properly.
- Draft and publish. Build the week as a draft, then publish; assignees are emailed and notified in-app when it goes live, and staff see published shifts only.
Open shifts and claims
Not every shift has a name on it when the week is built. Open shifts sit on their own row of the grid and staff claim them from their phones, immediately or subject to manager approval depending on how the site is configured. When a technician needs to drop a shift, they request it, a manager approves, and the shift goes back to open for someone else to claim. The manager's Approvals tab shows every pending claim, drop and leave request across every site they manage.
Leave and unavailability
Leave in AVDesk uses an Australian taxonomy: annual, sick, compassionate and long service leave need a roster manager's approval; RDOs, off-site days and plain unavailability are self-service; public holidays are applied by a manager to everyone at once. Each leave request shows the manager how many days it covers and how many rostered shifts it clashes with, and approving it can release those shifts back to open in one step. The applicant gets an email and an in-app notification either way.
The week grid
The week view is a staff-by-day grid: a sticky column of people, a row for open shifts, each person's weekly hours totalled, and hover controls to add a shift or apply a pattern. Month and my-shifts views exist for planning and for the individual technician. A branded print view produces the roster for the crew room wall, for one person or the whole site.
Roster managers and notifications
A user can be nominated as a roster manager for the sites they can see. That nomination grants roster management and routes the leave, claim and drop notifications to them, by email and in-app. Everyone else sees the published roster, submits their own availability and claims open shifts.
Why roster inside the AV platform
This is the part a standalone rostering app can't do. In AVDesk the technician on the 6am shift is the same user the wakeup-check ticket is assigned to, the same person on the pre-event checklist task, and the same one closing the maintenance job with photos. Managers assign work to the people who are actually there. Rostering is a per-site module, switched on by an administrator or the site's integrator for the sites that need it, with its own permissions: view for staff, manage for the people building the week.
Spreadsheet, generic rostering app, or AVDesk
| Spreadsheet | Generic rostering app | AVDesk rostering | |
|---|---|---|---|
| Event shifts, overnights, casuals | Manually | Varies | Built for it |
| Open shifts claimed from a phone | No | Usually | Yes, with optional approval |
| Leave with AU leave types and approvals | No | Usually | Yes, with clash detection and release |
| Knows who's assigned the tickets | No | No | Same platform, same people |
| Print for the crew room | Yes | Sometimes | Branded print view |
| Extra subscription | No | Yes | A module of the platform you already run |
The roster isn't a separate document about the team. It's the answer to "who's on, and what are they doing", and it should live where the work does.
Rostering is one module of one platform for AV support teams; see it in a working day in a day in the life of an AV support team. Book a demo and bring next month's events calendar.
