Field Staff Workflow

Brand ambassadors and field staff use the staff view to manage their own shift actions. The staff workflow should stay short enough to complete on a phone between real shifts: see the invitation, respond clearly, get to the store, check in on arrival, update availability, and report what happened after the shift.

Staff Flow

Review invitations

See the shifts assigned or offered to you.

Accept or decline

Give operations a clear response so coverage can update.

Set availability

Add unavailable or preferred windows so future suggestions are more accurate.

Submit a report

After the shift, record samples, conversations, notes, and optional photo evidence.

Responding to an Invitation

Each invitation should answer the questions a field staff member naturally has before committing: where the shift is, when it happens, what format the work takes, and what operations needs from them. If the staff member can work the shift, they accept. If they cannot, they decline. The important part is that the answer is recorded in the system so operations does not have to infer status from chat history.

The staff view now separates work that needs a reply from work the staffer is already rostered on. Pending invitations show the store, client, timing, format, address, directions, and any briefing links. Confirmed upcoming shifts show directions again and add a check-in button. The directions link prefers store coordinates, then falls back to the address or store name, which keeps the flow useful even while location data is still being cleaned.

Invitation response screenshotShows the pending invitation card with store, timing, format, directions, and accept/decline actions.

Confirmed shift screenshotShows directions, briefing links, and the check-in action on a mobile viewport.

Check-in is a one-time arrival action, not continuous tracking. The browser asks for location permission, captures a single GPS fix, and records that point against the assignment. Operations can then see that the staffer is on-site and, when the store has coordinates too, how far the check-in was from the store.

Availability

Availability is intentionally simple. An unavailable window tells operations that the staff member cannot work during that time. A preferred window gives the ranker a positive signal when a person likes that kind of slot. A recurring pattern repeats weekly, such as every Saturday, so staff do not need to re-enter the same constraint every week.

The product assumes a staff member is generally available unless they add an unavailable window. That default keeps the workflow light for casual field staff while still giving operations useful signals.

Reports After a Shift

After completing a shift, staff submit a short report. The report captures the operational facts that matter most: samples handed out, shopper conversations, notes from the field, and optional photo evidence when Vercel Blob is configured. This should feel like a quick closeout, not admin paperwork. The value is that the field observation becomes the evidence base for client dashboards and campaign performance follow-up.

Availability screenshotShows unavailable and preferred windows once recurring availability UI copy is final.

Post-shift report screenshotShows samples, conversations, notes, and optional photo evidence fields on mobile.

Good Staff Experience Principles

The staff side should remain short enough to use on a phone, clear enough to use without training, and focused on the next action. It should also be careful with personal data. Availability and location signals are useful for operations, but they should stay proportionate to the work being rostered and avoid exposing staff details more broadly than needed.