Draft vs Published Shifts: Visibility, Behavior, and Worker Applications

🧾 Draft vs Published Shifts: Visibility, Behavior, and Worker Applications
 

📘 Article Purpose

This article explains the difference between draft and published shifts in the Field Schedule, including how visibility works, what actions are allowed, and how workers can apply to draft shifts.

🔍 What Is a Draft Shift?

A draft shift is a shift that:

• Has been created but not yet published
• Is used for planning, reviewing, or collecting applications
• Appears as a transparent color block in the schedule

✅ What Is a Published Shift?

A published shift is:

• Fully visible to assigned users
• Considered official and ready to execute
• Displays as a solid color block

🎨 Visual Differences

👁️ Who Can See Draft Shifts?

This depends on permissions:

In Roles & Permissions > Schedule:

• View Draft Shifts by Role/Label
  • Users only see draft shifts that match their role or skill label
• View All Draft Shifts
  • Users can see every draft shift, regardless of role or label

🔐 Users with no draft visibility permissions will not see any unassigned drafts.

🙋 Worker Applications to Draft Shifts

Draft shifts with Expected User Groups allow workers to apply for shifts from their mobile app.

How It Works:

1. Dispatcher creates a draft shift with required labels (e.g., 2 electricians)
2. Draft appears to users who match the required role or label
3. Worker taps Apply in their app
4. Their name appears in the shift as a Pending User

✅ Confirming or Denying Applicants

In the Shift Slider, under Pending Users:

• Click Confirm to assign them to the shift
• Click Deny to reject their application

Once confirmed, the user is moved to the Assigned Users section.

🔁 Publishing the Shift

Once all planning is complete:

• Open the shift
• Click Submit

🧠 Published shifts notify assigned users (if notifications are enabled).

🧠 Use Cases for Draft Shifts