Fieldworker Job Decline Reason Form (Decline Booking Request Form)

Schedule a call

Schedule a call

Fieldworker Job Decline Reason Form (Decline Booking Request Form)

When a fieldworker declines a job request, you need to know why—fast. OctopusPro’s Job Decline Reason Form (also called the Decline Booking Request Form) lets you capture a clear, structured reason at the exact moment a job is refused, so your dispatch team can quickly reassign work, reduce back-and-forth, and spot patterns like coverage gaps, scheduling issues, or training needs.

Fieldworker job decline reason form overview

On this page

What this is for

This feature is designed for any business that sends job requests to fieldworkers and allows them to accept or decline work (common for subcontractor teams, flexible rosters, multi-branch operations, after-hours coverage, and peak-season overflow).

With the decline reason form, you can:

  • Capture structured decline reasons (not vague “can’t do it” replies)
  • Reduce dispatch time by knowing what to fix (timing, distance, skill mismatch, safety, access, etc.)
  • Improve future assignment by identifying recurring issues (coverage gaps, service-area limits, licensing/tools, workload balance)
  • Create better policies (lead time, travel radius, minimum notice windows, safety rules, escalation paths)
  • Support fixed-site and remote services (e.g., clinics, offices, workshops, online sessions) with reasons beyond travel (equipment/roster capacity, time zones, availability)

How it works

  1. A job request is sent to one or more fieldworkers (manual or automatic dispatch).
  2. The fieldworker opens the request and chooses Accept or Decline.
  3. If they choose Decline, OctopusPro can prompt them to complete your Decline Reason Form (your custom questions).
  4. The decline reason is logged against the booking for auditing and reporting.
  5. Your admin/dispatch team uses the reason to reassign faster and improve how future jobs are routed.

Fieldworker accept or decline job request prompt in the app

When declining, the fieldworker can be prompted to provide the reason immediately:

Fieldworker decline booking request form in the app

Admins can also receive an alert when a job is declined (depending on your notification settings):

Admin notification when a job is declined

Before you start (required settings)

1) Allow fieldworkers to decline job requests

The decline reason form only applies if your team is allowed to accept/decline job requests. If declines are disabled, assignments are automatically accepted and the fieldworker won’t see the decline flow.

Guide: Fieldworker Permissions & Access Control (look for the setting: Allow fieldworkers to accept and decline booking requests).

2) Use job requests (dispatch workflow)

This feature is used when you dispatch work using job requests (manual or automatic). If you need a refresher on dispatch modes and how job requests work:

Service Request & Resource Allocation Workflow (Manual vs Automated Dispatch)

Accept and Decline Job Requests

Set up the decline reason form

The decline reason form is configured using Forms & Checklists. You’ll create (or edit) a form and set its visibility so it appears when a fieldworker declines a booking request.

Step 1: Open Forms & Checklists

Go to Settings > General Settings (or Company Settings) > Forms & Checklists.

Forms and checklists list in OctopusPro settings

Step 2: Create a new form (or edit an existing one)

You can either:

  • Create a dedicated form for decline reasons (recommended), or
  • Edit an existing form and add decline-specific questions.

When editing/creating the form, confirm it’s visible to the right users and set to display when declining:

Edit form visibility and display settings for decline booking/appointment

Step 3: Add your decline questions (fields)

Add the fields you want the fieldworker to complete when declining. Common field types include:

  • Multi-select or single-select reason: “Why are you declining this job request?”
  • Optional notes (long text): “Add details (optional)”
  • Photo upload (optional/required): “Upload a photo (if relevant)”

Example of configuring options and field rules:

Configuring decline form field options and rules

Step 4: Save & test

Save the form, then send a test job request and decline it in the fieldworker app to confirm the form appears as expected.

Once configured, the decline form responses will be linked to the relevant booking record:

Decline reason form responses linked to the booking record

Need help with forms? These guides cover setup, options, and field types:

What fieldworkers see in the app

When a job request is sent, fieldworkers can review it in the app (commonly under Bookings > New Requests / Notifications). They can then:

  • Tap the request to view details
  • Choose Accept to confirm
  • Choose Decline and complete the decline reason form (if enabled)

Accept/Decline prompt:

Accept/decline job request prompt on mobile

Decline reason form:

Decline booking request form on mobile

Where results appear (admins)

Once submitted, decline reasons become part of your operational history. Common places you’ll use them:

  • Booking record: view the form response linked to the booking (useful for quick reassignment and auditing)
  • Notifications & alerts: optionally notify admins/dispatch when a decline occurs
  • Reporting: review decline trends over time to improve service coverage and scheduling rules

Example of an admin alert for a declined job request:

Admin decline notification alert

Tip: If you want to reduce “unacknowledged” job requests, consider enabling the Accept/Decline reminder/alarm so fieldworkers must respond promptly.

Overview of OctopusPro Fieldworker App alarms, alerts and reminders

Examples & practical use cases

Scenario Common decline reasons to capture What you can improve
Mobile/on-site services Too far, traffic/ETA, no parking/access, unsafe location, missing tools/parts Service areas, travel radius rules, lead times, job notes, prep requirements
Fixed-site operations (clinic, office, workshop) Roster conflict, wrong skill set, equipment unavailable, site not ready, capacity full Shift planning, skill-based routing, asset availability, capacity controls
Virtual/online services (telehealth, coaching, remote consults) Time zone mismatch, calendar conflict, tech issue, not qualified for topic, missing prerequisites Availability rules, time zone settings, prerequisites, routing by specialty
Subcontractor networks Rate too low, schedule clash, outside service area, licensing requirement, job scope unclear Pricing/rates, clearer scopes, compliance filters, smarter dispatch targeting

If you also want fieldworkers to suggest alternative times when declining, combine this with:

Best practices

  • Keep the reason list short (6–12 options is usually enough). Add Other + notes for edge cases.
  • Make the main reason required so every decline is actionable.
  • Use consistent language (e.g., “Out of service area”, “Schedule conflict”, “Not qualified/licensed”).
  • Add a safety option and consider requiring notes/photos for safety-related declines.
  • Review trends monthly and adjust dispatch rules, service areas, lead times, or training accordingly.

Troubleshooting

Fieldworkers don’t see “Decline”
  • Confirm the permission is enabled: Fieldworker Permissions → Allow fieldworkers to accept and decline booking requests.
  • Confirm you are sending job requests (not auto-assigning without accept/decline).
The decline form doesn’t appear
  • Check the form’s visibility/display rules are set to show when a booking request is declined.
  • Make sure the form is visible to the correct user type (fieldworker/sub-worker as needed).
  • Confirm the form is active and assigned to the relevant service/status conditions (if you filtered it).
Admins aren’t being notified
  • Review your notifications/alerts configuration and ensure declines trigger an admin notification for the relevant roles/branches.
  • If you rely on SMS/email notifications, confirm those channels are enabled and configured.

To stay updated, please subscribe to our YouTube channel.

Scroll to top