Allow Fieldworkers to Create New Bookings
In many field-service businesses, technicians need to create bookings on the go—while they’re onsite, between jobs, or when an urgent request comes in. OctopusPro lets you control this with a simple permission: Allow fieldworkers to create new bookings.

When enabled, fieldworkers can create bookings from the Fieldworker App (and any enabled fieldworker portal access), and those bookings immediately appear in your admin dashboard—so office staff can review, adjust, dispatch, and follow up without delays.
Table of contents
- What this permission does
- Benefits and best-fit use cases
- How to enable the permission
- Fieldworker workflow (create a booking)
- Recommended related permissions (control & security)
- Notifications (stay in the loop)
- What office/admin staff should review
- Best practices
- Troubleshooting
- Related guides
What this permission does
The Allow fieldworkers to create new bookings permission determines whether a fieldworker can create a brand-new booking record (job/work order) directly from the Fieldworker App.
When enabled:
- Fieldworkers can create bookings while in the field, without needing the office to do it for them.
- New bookings instantly appear in your admin dashboard for visibility and follow-up.
- You can still control what fieldworkers can see and change (pricing, customer list access, approvals, custom services, etc.).
When disabled:
- Fieldworkers can still view and manage assigned bookings (based on your permissions), but they can’t create new ones.
- New bookings must be created by office/admin users (or via other flows like online booking / inquiry conversion, depending on your setup).
Benefits and best-fit use cases
Enabling fieldworker booking creation is ideal when speed matters—but you still want structure and control.
- Faster response times: technicians can log urgent jobs immediately (e.g., emergency callouts).
- Better customer experience: the customer gets booked right away instead of “we’ll call you back.”
- Fewer admin bottlenecks: office staff don’t need to manually create every job.
- Cleaner job tracking: each visit is recorded as a proper booking, improving reporting and accountability.
Common examples:
- Technician finishes a job and sells an add-on service for the same week
- Onsite assessment turns into an immediate service booking
- Emergency/after-hours callout needs to be logged instantly
- Property/strata work: technician creates bookings while moving between sites
How to enable the permission (admin setup)
To allow fieldworkers to create new bookings:
- Go to Settings → General Settings → Fieldworkers Permissions.
- Enable Allow fieldworkers to create new bookings.
- (Recommended) Configure the related controls and notifications (see sections below).
- Click Save.

Fieldworker workflow (create a booking)
Once enabled, fieldworkers can create a booking in a few steps (exact labels may vary slightly by app version):
- Open the Fieldworker App.
- Go to Bookings.
- Tap Create a New Booking (or the + button).
- Select the Customer (from your database) or create a new customer (only if you allow it).
- Add Service(s), Date/Time, and any required fields (notes, custom fields, checklists, etc.).
- Review the booking details and tap Confirm / Save.

Tip: If your fieldworkers can’t find a customer, it’s usually because customer database access is restricted. See the “Recommended related permissions” section below.
Recommended related permissions (control & security)
Letting fieldworkers create bookings works best when you pair it with the right supporting permissions—so you get speed and control.
- Customer database access (search first): If you want technicians to select existing customers (instead of creating duplicates), enable customer database access.
Allow fieldworkers to view your entire customer database (when creating bookings)

- Allow creating new customers: Enable this only if you trust fieldworkers to add customers correctly (recommended for emergency jobs or onsite sales).
Allow fieldworkers to add new customers

- Approval for booking edits (protect pricing & scope): Decide whether fieldworker booking edits require office approval before changes are applied.
Fieldworker requests permission to edit booking (office approval needed)

- Control pricing visibility: If you don’t want fieldworkers to see totals/charges, disable billing visibility (useful for subcontractors).
Show booking charges to fieldworkers (billing amount)

- Restrict adding custom services: Prevent fieldworkers from adding non-catalog items if you want strict service standardization.
Allow fieldworkers to add custom services to quotes, bookings & invoices

- Full permissions overview: Review all fieldworker permissions in one place.
Fieldworker permissions & access control

Notifications (stay in the loop)
To ensure nothing slips through the cracks, enable notifications when a fieldworker creates a booking. This keeps office staff aware of newly created jobs for review, dispatch, and customer follow-up.
Common notification options:
- Email notification: receive an email when a booking is created by a fieldworker.
- Admin portal notification: receive an in-app/admin notification when a booking is created by a fieldworker.

What office/admin staff should review
Bookings created by fieldworkers should still follow your internal quality checks—especially for pricing, service scope, and scheduling accuracy.
Recommended checks:
- Customer record: confirm customer details are correct (and merge duplicates if needed).
- Service selection: confirm the correct service(s) were chosen and any required custom fields/checklists are completed.
- Date/time: confirm booking date/time and duration are accurate and don’t conflict with availability.
- Pricing & charges: review totals, discounts, surcharges, travel fees, and add-ons (based on what fieldworkers are allowed to edit).
- Assignment: confirm the correct fieldworker (or crew) is assigned, if your workflow requires dispatch review.

Best practices
- Train fieldworkers on data quality: especially customer names, addresses, and required booking notes.
- Reduce duplicate customers: enable customer database search first, and encourage “search before create.”
- Standardize services: use a clean service catalogue and restrict custom services if you want consistency.
- Protect margins: require office approval for edits if fieldworkers shouldn’t change pricing/scope.
- Use photo requirements for quality control (optional): require “before/after” photos for certain services:
Troubleshooting
- Fieldworker can’t see “Create new booking”: confirm Allow fieldworkers to create new bookings is enabled and the user is logging in as a fieldworker (not a different role).
- Fieldworker can’t find existing customers: enable customer database access: Allow fieldworkers to view your entire customer database.
- Fieldworker can’t add a new customer: enable: Allow fieldworkers to add new customers.
- Prices/total aren’t visible in the app: that’s controlled by billing visibility: Show booking charges to fieldworkers.
- Edits are “pending approval”: booking edits may require office approval: Fieldworker booking edit approval.
- Duplicate customers are being created: encourage “search first,” enable customer database access, and standardize naming rules (e.g., use customer phone + suburb checks).
Related guides
- Fieldworker permissions & access control
- Getting started as a fieldworker (Fieldworker App guide)
- Create a new booking (admin guide)
- Fieldworker booking edit approval (office approval workflow)
- Show booking charges to fieldworkers (billing visibility)
- Allow fieldworkers to add custom services
To stay updated, please subscribe to our YouTube channel.
