Skip to main content

Schedule staff for an event

Create the shift your team member needs, with clear times, location and the appropriate event access.

Written by Releventful Support

Create the shift your team member needs, with clear times, location and the appropriate event access.

Steps

  1. Open the event's Scheduling area, or select the event on the calendar and choose Schedule Employees.

  2. Review available employees and any time-off or conflict warnings.

  3. Select the employee and open Edit Request when you need to change the shift details.

  4. Check the shift dates/times, description, location and role. Do not assume the event times are the correct working hours.

  5. Review portal access, pay rate, clock-in settings and the confirmation window, then save.

Portal access is separate

Scheduling records the work request. Event Portal Access and employee visibility permissions control what the person can see. Check their access rather than assuming a scheduled employee sees all client information or every detail report.

Confirmation window

The confirmation window controls when responses open. A value is the number of days before the shift start when the position becomes open for responses. It is not simply a deadline by which the employee must reply. Review the description in the dialog before choosing a value.

Clock-in controls

For on-site clock-in, select the verified venue address so the event has the location information the feature needs. Review the on-site and early clock-in options. The early option permits clock-in up to 15 minutes before the scheduled start. Mobile/device permissions can also affect location features.

Pay and time records

A shift role can fill a default rate. An override on this shift is different from changing the saved role rate. Check clocked-in/out values before correcting them; a correction changes the work record.

Notifications

Scheduling can notify the employee and request a response. Team notices depend on permissions and notification preferences. Review the saved request state rather than treating an email alone as confirmation.

Related guidance

Did this answer your question?