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.
Each 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.
013Customer Card, Equipment tab, new equipment form
The Equipment tab manages devices placed at the customer site (e.g.
Full description
Where: Customers > Customer Card > Equipment > Add New Equipment Captured: 2026-11-02 15:34 UTC · Quality: clear
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.
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.
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.
Settings list for the equipment and device categories used on customer sites, with a 'required to complete' filter, Active/Frozen status, search and…
Full description
Where: Admin > Preferences > Service Related > Equipment Types Captured: 2026-11-02 16:05 UTC · Quality: partial
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.
Form for a device category: ID prefix, description, required to complete a visit, Active/Frozen, default Sentricon bait, barcode required, code,…
Full description
Where: Admin > Preferences > Service Related > Equipment Types > + Equipment Type Captured: 2026-11-02 16:05 UTC · Quality: clear
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.
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.
Equipment: A service device at a customer site (for example a bait station), recorded on the customer's Equipment tab. Not vehicles or the fleet (false friend) Observed013-customer-equipment; official commercial page (bait associated with a bait station)
Equipment Type: A device category with rules and defaults. It is separate from the customer's individual Equipment records Observed168-settings-equipment-type-form
ID Prefix: A prefix defined on the Equipment Type, shown in the list next to Description Observed167-settings-equipment-types
Device ID: The numeric identifier of one device on the customer Observed013-customer-equipment
Required to Complete: An Equipment Type rule linked to visit completion. Enforcement was not tested Observed168-settings-equipment-type-form
Active / Frozen: The lifecycle status of an Equipment Type. Its effect on existing devices is unknown Observed168-settings-equipment-type-form
Default Sentricon Bait: The default bait for a device type. Only "None" was offered in the new form Observed168-settings-equipment-type-form
Assigned To: Who the device is assigned to on the customer form ("Customer" shown) Observed013-customer-equipment
Exceptions Report / Device Exceptions: Devices not handled normally on visits: Not Scanned, Replaced, Removed or Skipped Observed483-device-exceptions-revisited
Control matrix: A column in Equipment Appointments that shows whether a device has a control matrix. The research does not define it further Observed081-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)
Devices can gateWork order completion through Required to Complete and the scan confirmation on Mobile app (configuration observed, enforcement untested).
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.
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.
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.
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
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
Agent proposals, not decisions
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.
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/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 › 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.
2
Step 2
How This Block Connects
Click a block for its vendor terms.
Solid arrow: a source shows this linkDashed arrow: our hypothesis, no source yetThe word on an arrow says what one block does to the next.
3
Step 3
Inbox: New Items for This Block
Items from Slack, uploads and agent research wait here. Accept moves an item to its place.
Add from here
Planned: post in Slack and mention the agent, and it files the post here. Today the copy of Slack keeps the text and file names only.