Inspection reports and audits
Not shown in the Loom recording.
- Not shown in the Loom recording.
Not shown in the Loom recording.
How Well We Know This Block
A person sets it on a 5-step scale. Click a step to set it as Ivan (mock sign-in, top right).
1Earlier settings (1)Earlier settings (1)Earlier settingsEarlier settingsEarlier settingsEarlier settings (4)
Our CRM and the 4 Vendors
FieldRoutes calls it: Condition, Condition Type, Condition Template
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, inspection findings are called Conditions. A Condition is a finding at a customer site, such as accumulated debris, a leak, a pest-entry opening, an unsanitary area, a preparation obstacle or a damaged or missing device. It is broader than a pest sighting. Admin defines Condition Types (finding categories) and Condition Templates. A template bundles a type with a unit context, a severity, a responsible party and a recommendation. Each customer has a Conditions tab that reports findings. Two shared dictionaries, Target Areas (treatment places) and Target Issues (pests and problems), describe where work happens and what it treats. Diagram Markers are the symbols on property diagrams. The research has about 23 screenshots here, mostly Admin setup forms plus the empty customer Conditions report. No real finding was created, photographed, resolved or sent to a customer.
In short
- A Condition is a site or service finding, not only a pest sighting (Observed 130-settings-condition-types). Official FieldRoutes material agrees: technicians report pest-conducive conditions from Mobile and pass notes and recommendations to the office.
- A Condition Template combines a Condition Type, a unit type (Single Unit or Structure), a severity (Low/Medium/High), a Responsible Party (Customer or Company) and recommendation text (Observed 133-settings-condition-template-form).
- The customer Conditions tab filters findings by Found date, Status (Resolved / Not Resolved), Severity, Recommendations (service types) and Responsible party (Observed 012-customer-conditions, no results).
- Target Area means a treatment place. Target Issue means a pest or problem. Neither is a routing territory (false friend) (Observed 542-target-area-editor-clear, 544-target-issue-editor-clear).
- Target Issues carry educational content (image, Threat, Family, Fact, About text, Fun Facts) and drive the Target Issues By Service Type report (Observed 544-target-issue-editor-clear, 098-report-target-issues).
- Only the configuration was proven. How a technician records a real finding, attaches photos, places it on the site, communicates the recommendation and marks it resolved is untested.
Screens: 14 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 Conditions tab is a per-customer report of inspection findings. Filters: Found date range, Status (All/Resolved/Not Resolved), Severity (Low/Medium/High), Recommendations (service types) and Responsible (All/Customer/Company), with Refresh. It returned 'No results found' for this customer; no finding was created.
Full description
Counts the pests (target issues) recorded on appointments. Filters: start/end date, group by pest, city, zip code or appointment, service types and appointment status (all, completed, pending, cancelled, rescheduled, no show). It has a searchable table (description, count, issues), Refresh and Export to CSV; no rows are shown.
Full description
Catalog of inspection finding types used to record site conditions, e.g. accumulated debris, leaking air conditioning, pest-entry openings, unsanitary areas, preparation obstacles and damaged or missing devices. Filters by office scope and visibility, text search, per-row edit and + Condition Type. Shows that 'conditions' cover site and service findings, not only pest sightings.
Full description
Inline form for a new finding type: required name, office scope (this office or all offices) and visible/hidden, with save and cancel. Not saved. The form is small and hard to read here; capture 541 is the readable version.
Full description
List of reusable finding templates with office-scope, visibility and unit-type (Single Unit / Structures) filters and search; columns include severity and unit type. A template packages a finding with a default recommendation.
Full description
Form for a reusable finding: required name, office scope, visibility, unit type (Single Unit or Structure), severity (Low/Medium/High), Condition Type, responsible party (Customer or Company) and recommendation text. Not saved. Links a finding type to who must fix it and what is recommended.
Full description
Large catalog of treatment locations (rooms, exterior spots, device sites, property areas) with visibility, scope and System filters and search. A treatment-location list, not a routing territory.
Full description
Inline form with required name, office scope and visibility. Not saved; capture 542 is the readable version.
Full description
Catalog of pests and problems treated, with visibility, scope and System filters and search. This capture has a blank gap in the image; capture 543 is the continuous view.
Full description
Form for a pest or problem: name, scope, visibility, uploaded image and educational fields (Threat, Family, Fact, About text, Fun Facts). Not saved; capture 544 is the readable version.
Full description
Blank form to define an inspection finding category: required Condition Type, office scope and visibility, with save/cancel. The existing types behind the editor are configured categories, not new findings.
- 541-condition-type-editor-clear-detail.jpg: readable viewport view, avoids clipping
Full description
Blank form to define a treatment area (a room, exterior spot or device site): required Name, office scope and visibility, with save/cancel. The System filter on the list is not an editable field.
- 542-target-area-editor-clear-detail.jpg: readable viewport view of the form
Full description
Catalog of about 100 pests and problems that treatments address (for example ants, roaches, bed bugs, wildlife, lawn issues). Visibility, Global and System filters, Search and + Target Issue; each row shows scope, visibility and System. This recapture closes a white stitching gap in the earlier capture.
Full description
Blank form with required Name, scope and visibility, plus descriptive content: Uploaded Image / Choose File, Threat, Family, Fact, About 1, About 2, About Blurb, Fact Blurb and Fun Facts. Nothing was uploaded or saved.
- 544-target-issue-editor-clear-detail.jpg: readable viewport view of the form
Their words for this block 13
Where it lives in FieldRoutes
Menus, pages and settings where this block appears 10 menu paths
- Customers > Customer Card > Conditions, the Conditions Report (012-customer-conditions)
- Admin > Preferences > Service Related, the menu (129-preferences-service-menu)
- Admin > Preferences > Service Related > Condition Types (130-settings-condition-types); + Condition Type (131-settings-condition-type-form, readable recapture 541-condition-type-editor-clear)
- Admin > Preferences > Service Related > Condition Templates (132-settings-condition-templates); + Condition Template (133-settings-condition-template-form)
- Admin > Preferences > Service Related > Target Areas (177-settings-target-areas); + Target Area (178-settings-target-area-form, readable 542-target-area-editor-clear)
- Admin > Preferences > Service Related > Target Issues (179-settings-target-issues, continuous recapture 543-target-issues-clear); + Target Issue (180-settings-target-issue-form, readable 544-target-issue-editor-clear)
- Admin > Preferences > Mobile > Diagram Markers (187-mobile-diagram-markers); + Diagram Marker (188-mobile-diagram-marker-form); icon chooser (189-mobile-diagram-marker-icons)
- Reporting > Office > Target Issues By Service Type (098-report-target-issues)
- Customers > Customer Search > Service Appointment filters, which include Target Issues / Excl. Target Pests, Images Uploaded and Appt Checklist Data (420-service-appointment-filters-lower)
- Target Areas and Issues also appear on products (172-settings-product-form), on equipment types (168-settings-equipment-type-form) and on customer devices (013-customer-equipment). The Device Exceptions report tracks "days since last inspected" (483-device-exceptions-revisited).
Connections to other blocks
- Inspection records findings on Customer account through the Customer Card Conditions tab (Observed 012-customer-conditions).
- Inspection uses the unit context of Service location. Templates choose Single Unit or Structure (Observed 133-settings-condition-template-form).
- Inspection recommends services from Service agreements and renewals. The Recommendations filter lists service types (Observed 012-customer-conditions).
- Inspection shares the Target Area and Target Issue dictionaries with Chemical use and state reporting (products) and Devices and bait stations (equipment types and devices) (Observed 172-settings-product-form, 168-settings-equipment-type-form, 013-customer-equipment).
- Inspection tracks the state of Devices and bait stations. Damaged or missing devices is a Condition Type, and Device Exceptions tracks days since last inspected (Observed 130-settings-condition-types, 483-device-exceptions-revisited).
- Inspection happens in Mobile app and Work order. Findings are reported from Mobile (Documented, official commercial page), and diagram markers are a Mobile dictionary (Observed 188-mobile-diagram-marker-form).
- Inspection may show to Customer portal. The official page says status and pest activity can be surfaced to customers. Target Issue educational content is customer-style text, but its display was not verified (Documented / untested).
- Inspection feeds Reporting and analytics through Target Issues By Service Type (Observed 098-report-target-issues).
- Inspection segments Customer messages and marketing (marketing). The Marketing Pro guide uses unresolved Conditions as a customer attribute (Documented).
How FieldRoutes does it
Defining findings (observed forms, nothing saved).
- An admin keeps a catalog of Condition Types. Each type has a required name, an office scope and visibility.
- Condition Templates package a type with:
- a unit type (Single Unit or Structure)
- a severity (Low, Medium or High)
- a responsible party (Customer or Company)
- Recommendation Details text
The relationship is proven only at configuration level. (admin findings)
Recording and following up findings (documented in outline, untested). The official commercial product page says three things:
- technicians can report pest-conducive conditions from Mobile
- they pass notes and recommendations to the office (Operations Suite)
- status and pest activity can be shown to customers
The research did not test how a technician records a finding, attaches photos, assigns a site location, communicates the recommendation or marks it resolved. (official source checks)
Reviewing findings per customer (observed, empty). The Customer Card's Conditions tab is a Conditions Report. It filters by Found date range, Status (All / Resolved / Not Resolved), Severity (Low/Medium/High), Recommendations (service types) and Responsible (All / Customer / Company), with Refresh. For the inspected customer it said "No results found." The template configuration explains these filters.
Describing treatment places and pests (observed dictionaries). Target Areas and Target Issues are shared lists. The places that select from them:
- products
- equipment types
- customer devices
- Service Appointment search filters
- the Target Issues By Service Type report
Target Issues also hold an uploaded image and educational text: Threat, Family, Fact, About 1, About 2, About Blurb, Fact Blurb and Fun Facts. How these show in the field app or to customers, and how they are reported, is unverified.
Diagrams (configuration only). Diagram Markers define the symbols technicians place on property diagrams. A global setting always shows the name and license number of the FieldRoutes user viewing the diagram. The icon catalog covers pests, treatments, site findings and interface symbols. Icons named "Delete" or "Cancel" are only pictures. Drawing a diagram, placing markers and diagram output were not tested.
Reporting.
- Target Issues By Service Type counts target issues on appointments. It groups by pest, city, zip code or appointment and filters by service types and appointment status (all, completed, pending, cancelled, rescheduled, no show). It showed no rows.
- Customer Search's Service Appointment filters can include or exclude target issues. They also filter on whether images were uploaded and on checklist data. The research did not establish how treatment and inspection are counted.
Field context (documented, not executed). The assessment groups inspection with field execution. Appointment Checklists appear to technicians in the mobile app, with required items, acknowledgements and signatures. Device Exceptions tracks "days since last inspected" for site devices. See Work order and Devices and bait stations. (assessment)
Settings and controls
All settings and controls seen 32 rows
**Condition Types (130-settings-condition-types, 541-condition-type-editor-clear)**
| Control | Options and limits |
|---|---|
| Global filter | All / Specific to Office / Available to all Offices |
| Visibility filter | All / Visible / Hidden (hidden is not deleted) |
| Search | Text search; matching rules not tested |
| List columns | Condition Type / Global / Visible; row edit |
| + Condition Type | Inline form |
| Condition Type (required) | Finding category name |
| Office scope | Specific to this office / Available to all offices |
| Visibility | Hidden / Visible |
| save / cancel | Not saved |
**Condition Templates (132-settings-condition-templates, 133-settings-condition-template-form)**
| Control | Options and limits |
|---|---|
| Filters | Global; Visibility; Unit Type (All / Single Unit / Structures); Search |
| List columns | Condition Template / Global / Visible / Unit Type / Severity |
| Condition Template (required) | Template name |
| Office scope and visibility | Reuse and offered state |
| Unit Type | Single Unit / Structure |
| Severity | Low / Medium / High |
| Condition Type | Chosen from the configured catalog |
| Responsible Party | Customer / Company |
| Recommendation Details | Free text |
| save / cancel | Not saved |
**Customer Conditions tab (012-customer-conditions)**
- Filters: Found (date range); Status (All / Resolved / Not Resolved); Severity; Recommendations; Responsible (All / Customer / Company)
- Refresh
**Target Areas and Target Issues (177-settings-target-areas, 542-target-area-editor-clear, 543-target-issues-clear, 544-target-issue-editor-clear)**
- List: Global, Visibility, System (All/Yes/No) filters; Search; + Target Area / + Target Issue; row edit
- Editor: required Name, office scope, visibility, save / cancel
- Target Issue extras: Uploaded Image / Choose File; Threat; Family; Fact; About 1; About 2; About Blurb; Fact Blurb; Fun Facts. No upload or publication was done.
**Diagram Markers (187-mobile-diagram-markers, 188-mobile-diagram-marker-form, 189-mobile-diagram-marker-icons)**
- List: Global filter; Search; + Diagram Marker
- "Show tech name and license # on diagram": the tooltip says it always shows the viewing user's name and license
- Editor: Marker Code (required); Marker Description (required); Marker Notes; Most Used / Not Most Used; office scope; Icon Image from a preset catalog; save / cancel
**Target Issues By Service Type (098-report-target-issues)**
- Start Date / End Date; Group By; Service Types; Appt. Status
- Refresh; Export to CSV; searchable table with Description, Count and Issues
**Customer Search, Service Appointment (420-service-appointment-filters-lower)**
- Target Issues / Excl. Target Pests (include and exclude, including a "(hidden)" label)
- Images Uploaded (N/A / with or without / only without / only with)
- Appt Checklist Data fields
What the research did not prove
- No Condition Type, Condition Template, Target Area, Target Issue or Diagram Marker was saved.
- The customer Conditions tab returned "No results found". No real finding was created, photographed, located on the site, communicated or resolved.
- Whether a finding can override its template severity, and whether the responsible party is enforced, are unknown.
- The field-app and customer display of Target Issue images and educational text was not tested.
- Diagram drawing, marker placement and output were not tested. The icon pane scrolls internally and was only partly visible (189).
- The Target Issues By Service Type report showed no rows. How treatment and inspection are counted is not established.
- The Conditions Tab manual target was tested and was inaccessible. Conditions Overview is indexed only. So no procedural status or severity workflow is documented.
- Ivan specifically asked what "Conditions" means (channel context). This page answers that from configuration evidence only.
- No separate "audit" workflow for inspections (for example a commercial audit report) appears in the research for this block.
Ideas for Our CRM
- Proposal: model a finding as its own record tied to the customer and site or unit, with type, severity, responsible party, recommendation and resolved status, mirroring the FieldRoutes template fields.
- Proposal: keep "treatment place" and "pest or problem" as shared dictionaries used by findings, products and devices, and keep them separate from routing territories.
- Proposal: in acceptance tests, check that a technician can record findings with photos in the field, hand exceptions back to the office, and edit after completion (assessment acceptance questions).
- Proposal: name the concept "Findings" or "Site conditions" in our UI to avoid the contract-condition meaning.
Official FieldRoutes manuals
None of the 15 manuals read in the research covers this block in depth. These public official sources back the meaning:
- Commercial Pest Control product page, "Make Compliance A Snap": conditions reported from Mobile; recommendations passed to the office; status visible to customers
- FieldRoutes Marketing Pro starter guide: Conditions as unresolved findings tied to the card
- 2024 Pest Control Software Year in Review: Condition Codes label findings at customer sites
These knowledge base articles are indexed only (bodies not read):
- The Customer Card: Conditions Tab (tested; inaccessible)
- Conditions Overview
- Condition Types
- Condition Templates
- Target Areas
- Target Issues
- Target Issues by Service Type
- Diagram Markers (Flags)
- FieldRoutes Mobile: Conditions Tab
- FieldRoutes Mobile: Diagramming Tool
- API reference: Conditions
See also the archive's official source checks.
Screenshots kept in other blocks that also matter here 9
- 013-customer-equipment · Customer Card, Equipment tab, new equipment form (Devices and bait stations): The Equipment tab manages devices placed at the customer site (e.g.
- 129-preferences-service-menu · Service Related menu (Service agreements and renewals): Expanded list of the 21 service setup pages: add-ons, application methods, appointment cancel/no-show, reschedule and reservice reasons, appointment checklists, condition templates and types, custom schedules, custom appointment and unit details, discounts, equipment types, frequency options, products, service bundles, plans and types, skills, target areas and target issues.
- 168-settings-equipment-type-form · New Equipment Type form (Devices and bait stations): 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.
- 172-settings-product-form · New Product form (Chemical use and state reporting): Form for a product: name and label, EPA number, manufacturer, concentrated/diluted/inventory units, measurement type, default dilution and active percentage, SDS and label links, Sentricon bait flag, mix ratio, application method and rate, chemical or non-chemical, target areas and issues, 'available to WDO', California pest-control use code and active ingredients.
- 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.
- 188-mobile-diagram-marker-form · New Diagram Marker form (Mobile app): Form for a diagram symbol: code, description, notes, Most Used flag, scope and an icon from a preset library.
- 189-mobile-diagram-marker-icons · Diagram marker icon chooser (Mobile app): Expanded icon library for diagram markers (Angle Drill is preselected).
- 420-service-appointment-filters-lower · Customer Search, Service Appointment filters (bottom) (Customer account): Bottom of the Service Appointment filters: target issues/excluded pests, stand-alone services, appointment flags, appointment and unit custom fields, show tech notes, subscription appointment number, serviced interior, images uploaded and appointment checklist data (name, required, acknowledged and so on).
- 483-device-exceptions-revisited · Device Exceptions (Devices and bait stations): Shows devices (bait stations and similar) that were not handled normally on visits.
Research sections used for this page 24
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 › Condition Types and Templates: Condition Types and Condition Templates: finding categories, unit type, default severity, responsible party (customer/company) and reusable recommendation text.
- admin/controls.md › Application methods, reason dictionaries, and target dictionaries: Shared dictionaries: application methods (chemical), appointment cancel/no-show, reschedule and reservice reasons (scheduling), target areas and target issues with descriptive pest content (inspection).
- admin/controls.md › Products and dilution calculator: Products catalog editor (EPA number, units, dilution, active %, SDS/label links, mix ratio, application method/rate, target areas/issues, WDO availability, CA pest control code, ingredients) and the dilution calculator.
- admin/controls.md › Mobile Diagram Markers, Objections, Preset Notes, Spray Rigs: Mobile dictionaries: diagram markers and icons (tech name/license on diagram), sales objections, preset notes by property type and note type, and spray rigs with license numbers.
- admin/controls.md › Final clarity recaptures (539–547): Clear recaptures 539-547: service plans list, service type editor, condition type, target area, target issue, dilution calculator (result clipped), full AR trigger placeholder catalog of 24 tokens, department dialog.
- 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 › Conditions: configuration explains the previously empty customer report: Condition Types catalog and Condition Templates (unit type, severity, responsible party, recommendation) show conditions are site/service inspection findings; finding lifecycle untested.
- admin/findings.md › Products, skills, target areas, and target issues: Products catalog fields (EPA, units, dilution, SDS, WDO, CA use code), dilution calculator, Skills linked to services and scheduling, Target Areas and Target Issues taxonomies.
- admin/findings.md › Remaining Mobile dictionaries: diagrams, objections, preset notes, spray rigs: Diagram Markers and icon library, sales Objections, Preset Notes by property/note type, and Spray Rigs with license numbers.
- admin/findings.md › Final clarity recaptures and retained limits (539–547): Table of clear recaptures 539-547 (Service Plans, Service Type editor, Condition Type, Target Area, Target Issues, calculator, trigger placeholders, Department) and their remaining limits.
- admin/findings.md › Clear recaptures 539–547 and retained limits: Short restatement of the 539-547 recaptures and remaining limits (calculator clipped, Marketing Pro, Composite Stat, contract preview).
- 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.
- channel-context.md › FieldRoutes customer evidence and scope: FieldRoutes customer evidence scope: Ivan's customer-profile screenshot thread (asks what each button does, e.g. Conditions), 19 unimported screenshots, v1 navigation areas not verified.
- coverage-gaps.md › Screenshot and state corrections now closed: Screenshot corrections closed: report recaptures, payment/aging details, recaptures 539-547 (service plans, service type, condition type/target area/issue, trigger placeholders, department), edge states 556-558.
- customer-search.md › Service Appointment: Service Appointment filters: scheduled/created/skipped/due dates, skip and opt-out, staff attribution, auto-scheduled, paid, service balance, status, reminders, rating, target issues, stand-alone, flags, custom fields, notes, interior, images, checklist data.
- 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.
- domain-model.md › Dispatch and field service: Dispatch and field service: job pool, calendar, route templates/builder, visual grouping, intelligent routing, fill routes fee; conditions, target areas/issues, products, checklists.
- evidence-quality.md › Corrections verified: Corrections table: which later captures supersede loading/clipped ones (form selector 451, maps 522-526, billing/report reloads, aging 537-538, settings recaptures 540-547, communication details, customer filters, subscription billing, Job Pool 556, Recommended Routes 557, reinstatement 558, invoice 443).
- reporting/controls.md › 098-report-target-issues — Target Issues By Service Type: Observed controls for Target Issues By Service Type (098): Counts the pests (target issues) recorded on appointments.
- 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.
- 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.
How This Block Connects
Inbox: New Items for This Block
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.
Upload a screen or noteAsk the agent to research
Mock: no agent runs in this static page.
Where this block is stored: How it works, part 2.