Move Gigs Board
Log In
Mover Help Center

Early departure, no-show, and removal

When you need to leave early, can't make it, or are removed from a crew — how it works and what it costs.

Overview

Sometimes things go wrong: you get sick, the customer asks a mover to leave, a teammate no-shows. Move Gigs Board handles these as per-mover exceptions so the rest of the crew keeps working. This article covers the Leave Early flow, No-Show handling, Removal, and Replacement Requests.

Why this feature exists

Independent movers work in loose crews. Making the whole move fail because one person had an emergency would punish everyone. Per-mover exceptions keep the customer moved and pay honest movers for time worked.

Before You Begin

  • Actively assigned to a move
  • Reason ready (documented emergencies help avoid Quality Score penalties)

Step-by-step instructions

1. Leaving early (yours)

On /mover/timeclock, tap "Leave Early". Choose a reason: emergency, illness, injury, other.

What happens next: a dialog appears. Your crew_status flips to left_early, your timer stops, and hours-to-that-point snapshot. Your row moves out of the active crew count.

2. Confirm hours worked

The dialog confirms your final worked minutes and calculates pay pro-rated.

What happens next: the customer is notified, the crew count updates, and the move continues.

3. If admin flags it

Repeated Leave Early without documented reason lowers your Reliability metric.

What happens next: admin may reach out for context. Documented emergencies are excluded from penalty.

4. No-show handling

If you never mark En Route by 30 minutes past the move start time, the customer's /customer/moves/<id> shows a No-Show banner and offers a Replacement Request.

What happens next: your crew_status flips to no_show. Cancellation Rate is affected.

5. Customer-initiated removal

If a customer removes you mid-move (via /customer/moves/<id>), your crew_status flips to removed, timer stops, and you are paid for hours worked minus any deducted portion admin approves.

What happens next: you get an in-app notification with the reason. You can appeal within 7 days.

6. Replacement Request

If a mover leaves or no-shows, the customer opens a Replacement Request. The remaining crew keeps working. Available movers on the Board get an immediate alert.

What happens next: the first qualified mover to accept fills the slot. Your replacement_requests row is fulfilled.

Helpful Tips

  • Call the customer through messaging before you leave — humans forgive when they are told.
  • If you are sick, mark leave early first, then explain. Do not disappear.
  • Keep documentation (doctor note, accident report) for admin review.

Common Mistakes

  • Ghosting. Silence is the worst outcome. Even a one-line message helps.
  • Filing a Leave Early to skip the last hour. Reviewed by admin; kills your Quality Score.
  • Declining a replacement job then complaining about slow work. The system is trying to help you.

Troubleshooting

  • Timer did not stop after Leave Early. Refresh once. If it persists, contact support with the move ID.
  • Removal reason unclear. Message the customer or contact support. Every removal has a documented reason in move_crew.
  • Replacement request never filled. No available mover in the area at that moment. Customer keeps the current crew.

Frequently Asked Questions

Do I get paid if I leave early? Yes, for time worked, pro-rated to the minute.

Does an emergency Leave Early hurt my Quality Score? Not if documented. The Reliability metric excludes admin-approved emergencies.

Can I refuse to be replaced? No. Removal is at the customer's discretion.

Related Articles