FieldRoutes calls it: Equipment, Equipment Type, ID Prefix
From a read-only look at the FieldRoutes account on 2026-11-02 and its official manuals. Each line ends with its evidence: Observed in the account, Documented in a manual, or not tested. Capture numbers link to the screen below. All of FieldRoutes across the 20 blocks
In FieldRoutes this block is called Equipment. It means service devices placed at a customer site, such as bait stations. It does not mean the company's vehicles or tools. Each customer has an Equipment tab of individual devices. Admin defines Equipment Types (device categories) with barcode and completion rules. Two Office reports watch device work: Device Exceptions and Equipment Appointments. The research has 9 screenshots for this block (6 placed here and 3 from other blocks): the customer Equipment tab and its new-device form, the Equipment Types setup pages, the two reports (with a later recapture of Device Exceptions), generic flags and the Diagram Markers list. The Job Pool is referenced below but its capture is placed on scheduling. No device was saved, scanned or inspected, and every report showed zero rows.
In short
- "Equipment" is the FieldRoutes word for customer-site service devices, such as a bait station. It is not a vehicle fleet or telematics (false friend) (Observed 013-customer-equipment; corroborated by the official commercial product page).
- Each device record holds a type, an assignee, flags, a device ID, an application method, a barcode, a target area, target issues and notes (Observed 013-customer-equipment).
- Equipment Types are categories with rules: ID prefix, Required to Complete, Active/Frozen status, Barcode Required, Default Sentricon Bait, code, application method, target issues and products (Observed 168-settings-equipment-type-form).
- Scanning matters. Device Exceptions reports devices that were not scanned, replaced, removed or skipped, against a "days since last inspected" threshold (Observed 483-device-exceptions-revisited).
- Two controls govern scanning: a mobile setting requires confirmation of the last four digits of a scanned device, and an access permission lets a user mark equipment as inspected without scanning (Observed 183-mobile-service-default-editor, 203-access-control-profile-editor).
- None of the scan, completion-gate or bait-consumption behavior was executed.
Screens: 6 captures
Upload a screenEach capture is a saved screen state from the FieldRoutes account on 2026-11-02. A screen shows what controls exist; it does not prove what happens when they are used.
Full description
The Equipment tab manages devices placed at the customer site (e.g. bait stations), with an Exceptions Report, Add New Equipment, filters and sort. The New Equipment form has Description, Type, Assigned To (Customer), Flags, Device ID, Application Method (about 60 methods such as bait station, backpack sprayer), Barcode, Target Area (about 140 places such as attic, back yard), Target Issues (about 100 pests/problems) and Notes. The form was not saved.
Full description
Meant to show bait stations and other devices that were not scanned, replaced, removed or skipped. This capture shows only the heading with a blank body (the page did not finish loading); capture 483 shows the loaded report.
Full description
Lists appointments that involve customer equipment (devices) in a date range, filtered by equipment flags. Columns: customer, company name, subscription, technician, equipment code, label, assignment start/end and notes, whether it has a control matrix, equipment flags and notes, activity, target issues and date. It has search, page size, Refresh and Export to CSV; the table shows zero entries.
Full description
Settings list for the equipment and device categories used on customer sites, with a 'required to complete' filter, Active/Frozen status, search and + Equipment Type. Under the default Active filter the list shows no rows, so the capture does not show which types exist in this account.
Full description
Form for a device category: ID prefix, description, required to complete a visit, Active/Frozen, default Sentricon bait, barcode required, code, application method, target issues and a products area. Not saved; no scan or completion check tested.
Full description
Shows devices (bait stations and similar) that were not handled normally on visits. Filters: date range, exception types (not scanned, replaced, removed, skipped), group by customer, structure or device, group by day, month or year, and days since last inspected (30). It shows a date chart and a table with total equipment, scanned and % scanned, not scanned, manually inspected, skipped, replaced barcode, replaced equipment, removed and activity. An Actions dropdown was not opened; the table shows zero entries.
Their words for this block 14
Where it lives in FieldRoutes
Menus, pages and settings where this block appears 9 menu paths
- Customers > Customer Card > Equipment tab: Exceptions Report, Add New Equipment, Filters, Sort (013-customer-equipment)
- Customers > Customer Card > Equipment > Add New Equipment, the New Equipment form (013-customer-equipment)
- Admin > Preferences > Service Related > Equipment Types (167-settings-equipment-types); + Equipment Type (168-settings-equipment-type-form)
- Admin > Preferences > Customer Preferences > Generic Flags, which includes the Equipment flag type (329-generic-flags, editor 330-generic-flag-editor)
- Admin > Preferences > Mobile > Diagram Markers, the symbols placed on property diagrams (187-mobile-diagram-markers; see Inspection reports and audits)
- Reporting > Office > Device Exceptions (483-device-exceptions-revisited; the earlier blank attempt is 077-report-device-exceptions)
- Reporting > Office > Equipment Appointments (081-report-equipment-appointments)
- Scheduling > Job Pool > Advanced Filters, which filters due work by customer and subscription flags, measurement and skills. It has no device-specific filter in the capture (032-job-pool-advanced)
- Related controls in other areas:
- Mobile Service defaults (183-mobile-service-default-editor)
- access control profile (203-access-control-profile-editor)
- Service Related menu (129-preferences-service-menu)
Connections to other blocks
- Devices belong to Customer account through the Customer Card Equipment tab (Observed 013-customer-equipment).
- Devices can sit under a Service location structure. Device Exceptions can group by Structure (Observed 483-device-exceptions-revisited).
- Devices use the Application Method, Target Area and Target Issue dictionaries from Chemical use and state reporting and Inspection reports and audits, and Equipment Types carry a Products area and a default Sentricon bait (Observed 168-settings-equipment-type-form).
- Devices can gate Work order completion through Required to Complete and the scan confirmation on Mobile app (configuration observed, enforcement untested).
- Devices are covered by a permission in Technicians and licenses: "Mark Equipment as Manually Inspected" (Observed 203-access-control-profile-editor).
- Devices appear in Scheduling and appointments through the Equipment Appointments report, which lists appointments that involve devices (Observed 081-report-equipment-appointments). The Job Pool's advanced filters (032-job-pool-advanced) show no device-specific filter.
- Devices feed Reporting and analytics through Device Exceptions and Equipment Appointments (Observed).
- Devices link to Inspection reports and audits: one finding type in the Condition Types catalog is damaged or missing devices (Observed 130-settings-condition-types).
How FieldRoutes does it
Defining device categories (observed form, nothing saved).
- An admin opens Equipment Types and adds a type.
- The admin sets the ID prefix and description.
- The admin sets Required to Complete, status, Barcode Required and Default Sentricon Bait.
- The admin sets the code, application method and target issues, and the Products area.
This is category-level validation and configuration. The editor does not show a scan, a completion check being enforced, or bait or product consumption. The Equipment Types list was empty under its default Active filter in the captured state. (admin findings)
Placing a device at a customer (observed form, not saved).
- On the Customer Card, open Equipment and choose Add New Equipment.
- Enter Description, Type, Assigned To (Customer), Flags and Device ID.
- Choose the Application Method (about 60 methods, such as bait station or backpack sprayer).
- Enter the Barcode and choose the Target Area (about 140 places, such as attic or back yard), Target Issues (about 100 pests or problems) and Notes.
- Save. Save was not pressed in the research.
The tab also offers an Exceptions Report, Filters and Sort.
Servicing devices on a visit (configuration observed, runtime untested).
- Mobile Service defaults can require confirmation of the last four digits of a scanned device.
- The access profile permission "Mark Equipment as Manually Inspected" lets a user mark a device as inspected on the scan page without scanning.
- Equipment Types can make devices required to complete a visit and can require a barcode.
- The research did not test native mobile scanning or completion. (assessment)
Watching exceptions (observed loaded report, zero rows). Device Exceptions:
- Filters on date range, exception type (Not Scanned / Replaced / Removed / Skipped) and Days Since Last Inspected (30 shown).
- Groups by Customer, Structure or Device, and by Day, Month or Year.
- Draws a date chart and a table with the columns below.
- Has an Actions dropdown that was not opened.
Table columns: Customer; # Total Equipment; # Scanned; % Scanned; # Not Scanned; # Manually Inspected; # Skipped; # Replaced Barcode; # Replaced Equipment; # Removed; Activity.
The first attempt (077) stayed blank and timed out. The later capture 483 replaced it. The cause of the blank state is unknown. (reporting findings)
Equipment Appointments (observed, zero rows). This report lists appointments that involve customer devices in a date range, filtered by Equipment Flags. Its columns are: customer, company name, subscription, technician, equipment code, label, assignment start and end and notes, whether the device has a control matrix, equipment flags and notes, activity, target issues and date.
Settings and controls
All settings and controls seen 20 rows
**Equipment Types list (167-settings-equipment-types)**
- Filters: Equipment Required (Any/Yes/No), Equipment Status (Any/Active/Frozen)
- Search; + Equipment Type
- Columns: ID Prefix, Description, Required to Complete, Status, Default Sentricon Bait
**Equipment Type editor (168-settings-equipment-type-form)**
| Control | Options and limits |
|---|---|
| ID Prefix / Description (required) | Category prefix and name |
| Required to Complete | Yes / No; visit validation not tested |
| Status | Active / Frozen; effect on existing devices unknown |
| Default Sentricon Bait | Only None exposed in the new form |
| Barcode Required | Yes / No; enforcement untested |
| Code / Application Method / Target Issues | Category identifier and treatment and problem links |
| Products area | Product association section; no editable product row shown |
| save / cancel | Not saved |
**Customer Equipment tab (013-customer-equipment)**
- Tab actions: Exceptions Report, Add New Equipment, Filters, Sort
- New Equipment form:
- Description, Type, Assigned To, Flags, Device ID (number)
- Application Method, Barcode, Target Area, Target Issues, Notes
- Save
Field and permission controls
| Control | Where | Effect (as labeled) |
|---|---|---|
| Require Scanned Equipment Last Four Digit Confirmation | Mobile Service defaults 183-mobile-service-default-editor | Adds a confirmation step to equipment scans |
| Mark Equipment as Manually Inspected | Access control profile 203-access-control-profile-editor | Lets a user mark a device inspected without scanning |
| Generic Flag type Equipment | Generic Flags 330-generic-flag-editor | Reusable equipment markers. List filters: Global, Type, Status (Any/Active/Inactive), Search. Editor: Code and Description (required), Type, office scope, Active/Inactive. The listed examples include equipment requirements, such as a ladder being needed. |
**Device Exceptions (483-device-exceptions-revisited)**
- Filters: Date Range; Exception Types (Not Scanned / Replaced / Removed / Skipped); Group By (Customer / Structure / Device); Group By Date (Month / Day / Year); Days Since Last Inspected
- Actions: Refresh; Actions dropdown
- Output: chart; Search; sortable columns
**Equipment Appointments (081-report-equipment-appointments)**
- Date; Equipment Flags; Refresh; Export to CSV; search; Show entries (page size)
What the research did not prove
- No device or Equipment Type was saved. No scan, barcode check, completion gate, bait or product consumption, or exception was executed.
- The Equipment Types list was empty in the captured Active-filter state, so no existing category was seen.
- Both reports showed zero entries. The Device Exceptions Actions menu, its alternate groupings, populated exceptions and exports were not tested.
- The cause of the earlier blank Device Exceptions state (077) is unknown.
- The effect of Frozen status on existing devices, and how Sentricon bait works, are unknown.
- The flag display, mobile alerts and workflow enforcement of Equipment flags were not tested.
- Nothing here shows vehicle telematics, vehicle hardware or driving scores.
- Mobile Equipment tab behavior, the scanner and diagram drawing were not tested.
- No official manual body about equipment could be read. The Equipment Tab manual target was tested and was inaccessible; the others are indexed only.
Ideas for Our CRM
- Proposal: name this concept "site devices", not "equipment", so it is not confused with company vehicles or tools.
- Proposal: keep device categories (rules: barcode required, required to complete) separate from device instances at a customer site.
- Proposal: track per-visit device outcomes (scanned, manually inspected, skipped, replaced, removed) so an exceptions view like Device Exceptions is possible.
- Proposal: put the manual-inspection override behind a permission and audit it, and decide how a legitimate exception is handled without losing service evidence (assessment acceptance question).
Official FieldRoutes manuals
None of the 15 manuals read in the research covers this block. The official source checks cite the public Commercial Pest Control page for the meaning "customer-site service devices, for example bait associated with a bait station". These knowledge base articles are indexed only (bodies not read):
Screenshots kept in other blocks that also matter here 3
- 187-mobile-diagram-markers · Diagram Markers list (Mobile app): Catalog of symbols technicians place on property diagrams, with scope filter, search and a 'show tech name and license # on diagram' option.
- 329-generic-flags · Generic Flags list (Customer account): Dictionary of markers that warn staff about a customer, appointment, equipment, subscription, region, affiliate network or local-SEO item.
- 330-generic-flag-editor · Generic Flag editor (new) (Customer account): Blank form with required Code and Description, Type (Customer, Appointment, Equipment, Subscription, Region, Affiliate Network), office scope and Active/Inactive, with save/cancel.
Research sections used for this page 17
The original research reports are kept unchanged in the archive. These are the sections that speak about this block:
- admin/controls.md › Service Related menu: Index of the Service Related menu with a one-line purpose for each entry (add-ons, application methods, appointment reason lists, checklists, conditions, custom schedules/fields, discounts, equipment types, frequencies, products, bundles, plans, types, skills, target areas/issues).
- admin/controls.md › Equipment Types and Frequency Options: Equipment Types (ID prefix, required to complete, active/frozen, bait default, barcode required, linked methods/issues/products) and Frequency Options typed by auto-schedule, Fill Routes buffer, follow-up, billing, subscription, renewal and convenience payments.
- admin/controls.md › Mobile Default Settings: Mobile Default Settings for Sales and Service: scheduling prerequisites, default service types and source, look-ahead days, completion gates (balance, products, interior, equipment scan), payment collection rules, push notifications, rescheduling.
- admin/controls.md › Generic Flags: Generic Flags for customers, appointments, equipment, subscriptions, regions and affiliates, with code, description and status.
- admin/findings.md › Customer Preferences and Service Related menus: Inventory of the 22 Customer Preferences and 21 Service Related menu entries; navigation only.
- admin/findings.md › Discounts, equipment types, and frequency options: Discount definitions, Equipment Types (required to complete, barcode, bait, products) and typed Frequency Options covering several timing policies.
- admin/findings.md › Flags, note types and note categories express different concepts: Generic Flags by target entity, Note Types and Note Categories as different concepts.
- assessment.md › 6. Field execution, inspections and inventory: Field execution: condition templates (severity, responsible party, recommendation), equipment/barcodes/target areas, inventory and State Chemical formats, appointment checklists for mobile, mobile completion/scan gates, spray rigs, device exceptions.
- domain-model.md › Customers, properties and people: Core concepts: Customer Card and checkout, service vs billing address, Default Bill To payer, linked properties, merge, unit/structure modes, additional vs business contacts, staff roles; plus the purpose of each of the 12 Customer Card tabs.
- reporting/controls.md › 077-report-device-exceptions — Device Exceptions: Observed controls for Device Exceptions (077): Meant to show bait stations and other devices that were not scanned, replaced, removed or skipped.
- reporting/controls.md › 081-report-equipment-appointments — Equipment Appointments: Observed controls for Equipment Appointments (081): Lists appointments that involve customer equipment (devices) in a date range, filtered by equipment flags.
- reporting/controls.md › 483-device-exceptions-revisited — Device Exceptions loaded state: Observed controls for Device Exceptions (483): Shows devices (bait stations and similar) that were not handled normally on visits.
- reporting/findings.md › What is directly observed: Per-capture table of every Reporting page (six categories, 44 Office reports, Inventory, Locations, Technician/Office Stats, Form Lookup) with visible controls and what is unverified; notes which blanks were later resolved.
- reporting/findings.md › Device Exceptions and Monthly Services: recaptures 483–485: Device Exceptions 483 (exception types, groupings, scan columns) and Monthly Services 484-485 (summary cards and separate date windows per category) now render.
- reporting/findings.md › Facts that change interpretation: Interpretation facts: how Average Contract Rates, Time On Site, Audit, AR Oversight, Billing/Line Items, Retention, Commission, Sales Tax, Inventory, State Chemical, Technician Stats, Locations and Form Lookup define their numbers.
- sources/official-source-checks.md › Corroborated business meaning: Public-source corroboration table: customer card, Conditions, Equipment as site devices, Properties, Service Type vs Plan, prospect/lead/customer, grouping/optimise/assign, Fill Routes, Job Pool map, AutoPay, Convenience Payments, Forecast and cancellation reports, payments, disbursements, AR Oversight, prepayments/bundles, condition codes and appointment notes.
- sources/official-source-checks.md › Direct manuals for the observed account surfaces: Indexed manual links per account surface (customer card tabs, subscriptions, billing, notes/communication, documents, appointments, invoices, properties, conditions, equipment, admin tab, Job Pool, routes, plans, AutoPay, credits/collections, batches, convenience payments, stored cards, disbursements); indexed only, not read.