Operating Problem

Business Perspective

D2C runs campaigns, activations, merchandising jobs, sampling campaigns, and complex field-team work across Australia and New Zealand. The operational cost is not only the act of creating a roster. The real cost is uncertainty: on a busy day, operations needs to know which shifts are exposed, which invited staff have not responded, which confirmed staff are actually the best fit, and which gaps need action before they become field problems. After the work is done, the question changes again: which completed shifts have enough evidence to support client reporting?

Roster is the data capture point for many future systems: ERP, CRM, payroll, geolocation, briefing files, equipment, route planning, and client dashboards. If roster status and shift reports are not trustworthy, downstream dashboards and finance workflows inherit noise.

Workflow at a Glance

Product Perspective

Roster is a focused operational cockpit, not a broad module catalogue. It supports the workflow where an operations user moves from campaign intent to covered shifts, while field staff get a simple way to respond and supply ground-truth reports.

Admin need

Create shifts, invite staff, see coverage, and understand what to action next.

Field staff need

See invitations, accept or decline quickly, declare availability, and file post-shift reports.

Client need

Eventually receive clear reporting from completed shift activity, not just a roster export.

Product Boundary

The current product boundary covers the capabilities needed to run and inspect the core operational loop. It includes shift creation and editing, staff invitations and responses, coverage computation, the action queue, staff availability, candidate ranking by skill, state, availability, and distance, plus shift reports that roll into client dashboards. It deliberately defers the broader ERP/CRM module, payroll and award interpretation, full route optimisation, equipment lifecycle management, document management, a native mobile app, and a production analytics warehouse.

Problem-state screenshotShows an exposed shift, pending replies, and action queue context from the final admin UI.

Evidence-state screenshotShows a completed shift with report evidence and client rollup context.

This keeps the system focused while leaving clear extension points for future modules.