Skip to main content

Mobile Settings

A guide to configuring Mobile Settings in BuildOps - control required Visit Report fields, customer signature details, field purchasing rules, technician self-scheduling, and general mobile app behavior.

Written by Angelene Rosario

Mobile Settings

Mobile Settings is where administrators configure how the BuildOps mobile app works for their technicians. From one screen, you can decide which fields technicians must complete before finishing a Visit, what customers see on the signature page, how field purchasing works, whether technicians can manage their own schedules, and a handful of other mobile behaviors.

Before You Begin

  • Mobile Settings permission: Your role must include Mobile Settings access. If you don't see this page in your Settings menu, ask your admin to enable it for your role.

  • Edit permissions: Some tabs may be view-only depending on your role. If you can't make changes on a tab, check with your administrator about your permission level.

Note: Mobile Settings works alongside Roles & Permissions. For example, turning on Display Unassigned Jobs won't show technicians open work unless their role also has the Create Visit permission. Both need to be aligned for a setting to take effect.


Accessing Mobile Settings

  1. Hover over your company name in the top-left corner of BuildOps to open the main menu.

  2. Click Mobile Settings.

You'll land on the Mobile Settings page, which is organized into five tabs: Gated Workflows, Visit Report, Procurement, Self-Service Scheduling, and General Settings.

Note: After making changes on any tab, click SAVE in the top-right corner to apply them.


Gated Workflows

The Gated Workflows tab controls which sections of the mobile Technician Report must be completed before a technician can mark a Visit as finished, and whether they're allowed to skip a required section when necessary.

The Gated Workflows tab, showing Required and Allow Bypass toggles for each Visit Report field.

The Gated Workflows tab, showing Required and Allow Bypass toggles for each Visit Report field.

Each row represents a section of the mobile Visit Report. Two toggles control how strictly that section is enforced:

  • Required — When ON, technicians must complete this section before they can finish the Visit. When OFF, the section is optional and any saved data is still kept.

  • Allow Bypass — When ON, technicians can skip a required section (usually with a warning) if it's genuinely not possible to complete. When OFF, the section can't be skipped when finishing on the Yes path (see the note below for the No path).

How this shows up for technicians: on the mobile Technician Report, required sections are labeled "Required." A green checkmark appears once a section is complete. When a technician finishes a Visit, they're asked Were you able to complete the work assigned on this visit? If they answer Yes with an incomplete required section, they can't proceed and must return to that section first.

Note: Required sections are only enforced on the Yes path. If the technician answers No to "Were you able to complete the work assigned on this visit?", they pick a reason, leave a note for the dispatcher, and tap Finish Visit & Submit Flag. This closes the Visit even when required sections such as Visit Summary are empty, and adds a Visit flag the office can use to find these Visits.

Note: If your team uses Auto Time Tracking (in Labor Settings), avoid setting Timesheets to Required here. Requiring a timesheet submission before the system finishes calculating automatic time can result in missed hours.


Visit Report

The Visit Report tab controls which details are shown to the customer on the signature page at the end of a Visit.

The Visit Report tab, where each detail can be shown or hidden on the customer signature page.

The Visit Report tab, where each detail can be shown or hidden on the customer signature page.

Toggle any of the following on or off to control what your customer sees when they review and sign the Visit Report:

  • Show Job Description

  • Show Visit Description

  • Show Visit Summary

  • Show Assets Worked On

  • Show Inventory Items Used

  • Show Purchase Orders (with the option to also show or hide the Vendor Name)

  • Show Before & After Photos

  • Forms

  • Show Submitted Hours — when ON, the technician's hours appear on the customer report. Two sub-toggles sit under it:

    • Require timesheets submission before collecting customer signature — when ON, the technician must submit their timesheet before the Collect Signature button on the customer report will proceed.

    • Require hours in timesheets before collecting customer signature — when ON, the technician's timesheet must have hours before they can collect the customer signature.

This is a good place to tailor the customer-facing experience — for example, some companies prefer to hide internal cost-related details like Purchase Orders or Vendor Name from the customer signature screen.

Note: The Timesheets row on the Gated Workflows tab only controls finishing a Visit. It does not affect the signature step. Whether a technician is asked for a timesheet before collecting the customer signature is controlled only by the two sub-toggles above. Show Submitted Hours can stay ON — turning off only the two sub-toggles removes the timesheet requirement at signature while still showing hours on the customer report.


Procurement

The Procurement tab governs what technicians are required to provide when creating Purchase Orders or submitting receipts from the mobile app.

The Procurement tab, covering field purchasing requirements for Visits, Projects, and Field Orders.

The Procurement tab, covering field purchasing requirements for Visits, Projects, and Field Orders.

Specify fields required for technicians to submit on jobs or projects

  • Packing Slip Images — Visits & Projects: When ON, technicians must attach a photo of the packing slip or receipt when submitting items on a Visit or Project.

  • Require Receipt Line Items — Field Orders: When ON, technicians must itemize what they purchased on a Field Order rather than submitting a single lump total.

Specify fields that will be shown to technicians on future Visits

  • Allow for Field Orders to be created for future Visits: When ON, technicians can create a Field Order ahead of an upcoming Visit rather than only during the Visit itself.

Note: If you're unsure which of these should be turned on, check with your accounting or procurement team so these settings match your purchasing and AP-matching policies.

No Mobile Settings or role setting lets technicians use Field Orders while stopping them from receiving those Field Orders. Add Receipt appears on every Field Order shown on a Visit. Every Purchase Order created from the mobile app is a Field Order, so removing Field Order access from a role stops technicians from creating Purchase Orders in the field entirely.

To keep receiving in the office, create a regular Purchase Order instead of a Field Order. Technicians can only view a regular Purchase Order in the mobile app; Add Receipt does not appear on it.


Self-Service Scheduling

The Self-Service Scheduling tab controls how much control technicians have over their own schedules from the mobile app.

The Self-Service Scheduling tab, controlling technician self-scheduling, self-assignment, and visibility of unassigned work.

The Self-Service Scheduling tab, controlling technician self-scheduling, self-assignment, and visibility of unassigned work.

  • Enable Technicians to self-schedule assigned visits allows technicians to choose or change the date and time of visits already assigned to them from the BuildOps Mobile App. This gives technicians more control over their schedules while still limiting them to work they are authorized to access.

    The technician must be designated as the job’s Preferred Technician or Primary Technician. They cannot use this setting to schedule visits assigned to another technician or reassign work to themselves.

    How it works

    When enabled, an eligible technician can:

    • View assigned visits in the mobile app.

    • Open an unscheduled or incomplete visit.

    • Select Start Visit Now to schedule the visit for the current date and time.

    • Select Schedule Visit Later to choose a date, start time, duration, department, and optional visit description.

    • View the scheduled visit under Today or Future in the Scheduled Visits section.

  • Enable Technicians to self-assign unassigned Visits and Jobs in their department — Lets technicians claim open work in their department directly from the mobile app, without waiting for a dispatcher.

  • Display Unassigned Jobs — Controls whether technicians can see open work in their department that hasn't yet been assigned to anyone.

Note: Display Unassigned Jobs only controls visibility. For a technician to actually claim that work, their role also needs the Create Visit permission under Roles & Permissions.


General Settings

The General Settings tab contains a handful of global behaviors that affect how Visits work on mobile.

The General Settings tab, covering overdue Visits, current-Visit editing, asset selection, and geofence retries.

The General Settings tab, covering overdue Visits, current-Visit editing, asset selection, and geofence retries.

  • Allow technicians to update overdue events

    • When OFF, technicians can't take action (Travel, Work, etc.) on Visits scheduled in the past that were never started; those Visits must be rescheduled first.

    • When ON, technicians can still start and complete overdue Visits directly from the app.

  • Technicians can only edit current visit

    • When ON, a technician can only work on one Visit at a time. Once they have a Visit in progress, other Visits scheduled for that day are locked until the current one is completed.

    • When OFF, technicians can work on multiple Visits at once, as long as other settings and permissions allow it.

  • Allow technicians to Select All assets when identifying which assets they worked on

    • When ON, technicians see a "Select All" option for assets worked on.

    • When OFF, they must select each asset individually, which can encourage more deliberate, accurate reporting.

  • Number of retry attempts permitted for a technician when taking an action subject to geofence validation — Sets how many times a technician can retry an action (such as clocking in) that requires them to be within a defined distance of the property.


Frequently Asked Questions

Why can't my technicians finish a Visit even though it looks complete?

Check the Gated Workflows tab. If a field is set to Required with Allow Bypass off, and that field is empty or incomplete, the technician can't finish the Visit on the Yes path. Common culprits include Forms (when no form is assigned) or Assets Worked On (when the job has no assets, but the field is still required). Note that required sections are not enforced if the technician answers No to "Were you able to complete the work assigned on this visit?" and uses Finish Visit & Submit Flag — that path closes the Visit and adds a Visit flag.

I turned off the Timesheets requirement on Gated Workflows, but technicians are still asked for a timesheet. Why?

The timesheet prompt at the customer signature step is controlled on the Visit Report tab, not Gated Workflows. Under Show Submitted Hours, turn off Require timesheets submission before collecting customer signature and Require hours in timesheets before collecting customer signature, then click SAVE. You can leave Show Submitted Hours ON if you still want hours on the customer report. Have technicians tap Clear Cache & Restart in the app menu so the new settings take effect.

Can I require different fields for different job types?

Not directly through Gated Workflows — those settings apply to all Visit types. However, you can use Forms and Custom Fields to capture different information for different job types.

Why can't a technician start an old Visit they missed last week?

Check General Settings for Allow technicians to update overdue events. If it's OFF, technicians can't take action on overdue Visits; the office needs to reschedule the Visit to a current date first.

Can technicians work on multiple visits or jobs at the same time?

By default, BuildOps allows technicians to edit multiple visits unless restricted by settings. To limit them to one job at a time, toggle the relevant settings in Mobile Settings.

What happens if a technician is logged into two jobs simultaneously?

Technicians are not automatically prevented from being logged into multiple jobs. However, the correct procedure is to finish the first visit before starting the next.

Can I let technicians create Field Orders but not receive them?

No. Add Receipt appears on every Field Order on a Visit, and there is no Mobile Settings or role setting that separates creating a Field Order from receiving it. Every Purchase Order created from the mobile app is a Field Order. If you want receiving to happen in the office, create a regular Purchase Order; technicians can only view it in the app.

Did this answer your question?