FieldRoutes calls it: Service address, Residential Property, Single Unit
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 the service location is not a separate record. It is the service address and property description stored on the Customer Card (Info tab, and the New Customer form at intake), plus a classification of the property (Residential or Commercial; Single Unit, Multi Unit or Structures; Sub-Property Type). Extra sites are separate Customer Cards joined through the Properties tab ("Linked Properties"). Around this sit admin dictionaries (Structure Templates, Sub-Property Types, Property Estimation Units), office geography (physical location, territory, ZIP claims, route regions) and data-quality checks (bad geocode, differing addresses). The research has 29 screenshots that touch this block (9 placed here and 20 from other blocks): intake and Info forms, the Properties tab, structure and sub-property editors, office territory and ZIP settings, location search filters and map, and two Audit checks. No address was saved, geocoded, linked or merged.
In short
- One Customer Card holds one service address. A second site is another Customer Card linked on the Properties tab. Documented: each linked site keeps its own billing, invoices, subscriptions, documents and balance, and a payment to one site does not pay the others. Linked sites are not automatically pooled into one ledger (documented, not tested; a consolidated statement or master-portal payment does not prove a pooled balance).
- Linking and merging are different. Documented: Merge permanently absorbs one card and its history into a master and cannot be undone.
- The service address, the billing correspondence address and the payer (Default Bill To / billing account) are three separate things. Changing the billing address does not assign another payer.
- Property classification (Residential/Commercial) and unit mode (Single Unit/Multi Unit/Structures) are two independent choices. Observed: choosing Multi Unit or Structures at intake shows no unit table or structure tree before saving, so how units and structures attach to a site is not shown.
- Structure Templates is a reusable tree editor of structure nodes. It was seen only as an empty list and an empty draft (node names and levels are not shown); how a template is applied to a customer is not shown.
- Office geography appears as four separate settings (observed; how each is enforced was not tested): office Physical Location (route start/end), Territories (map boundary of the area served; Not set here), Office Zip Codes (which ZIPs an office claims for creating accounts) and Route Regions (name-only labels). Office Info also keeps two other addresses: the Invoice Address and the legal Business Address.
- Observed: the Audit report flags customers whose address could not be placed on the map (4 rows) and customers with differing addresses (0 rows).
Screens: 9 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 Properties tab links this customer account to other property accounts (Linked Properties). It shows only a 'Link a Property' search box; no properties are linked and no link was made.
Full description
Library of reusable structure trees for multi-structure properties. Global and Visibility filters, Search, + Structure Template and Structure Template/Global/Visible columns; the list is empty.
Full description
Blank structure template with office scope, Hidden/Visible, save/cancel and a tree with one root node named 'New Structure'. There is no separate name field. Nothing was saved.
Full description
The draft template with the root 'New Structure' node selected and its name text box active for renaming. Nothing was saved.
Full description
The draft hierarchy after the plus icon added one child under the root; both nodes are named 'New Structure', and the child has a trash icon. Maximum depth and reparenting were not checked; the draft was cancelled.
Full description
Dictionary of sub-property classifications, separate from the structure tree. Visibility, Global and System filters, Search, + Sub-Property Type and Description/Global/Visibility/System columns; the list is empty.
Full description
Blank form with required Sub-Property Type, office scope and Hidden/Visible, with save/cancel. No property assignment or pricing effect is shown; nothing was saved.
Full description
One of the 19 Audit data-quality checks: customers whose address could not be placed correctly on the map. It shows 4 potential errors in a searchable, sortable table with customer ID, customer, address, city, state, zip and account status. Help text suggests checking the office's map coordinates if many rows appear. Nothing was corrected.
Full description
One of the 19 data-quality checks in the Audit report, selected on its own: Customers with differing addresses. The screen gives only the check's name; which addresses it compares (for example service versus billing) is not stated. The panel shows 0 customers for customers entered on the captured day, so no result table or columns appear. It shares the Audit date range, Refresh and Export to CSV; nothing was corrected or exported.
Their words for this block 16
Where it lives in FieldRoutes
Menus, pages and settings where this block appears 11 menu paths
- Customers > Customer Card > Info: service address with state and county pickers, property classification, unit mode, Sub-Property Type. 004-customer-info
- New Customer (top bar) > Create a New Customer > Basic Information: the same fields at intake, plus map code, square feet, country and an embedded map. Variants: residential single unit 370-new-customer-form, commercial 371-new-commercial-customer-form, commercial multi unit 372-new-multiunit-customer-form, commercial structures 373-new-structures-customer-form.
- Customers > Customer Card > Properties: Linked Properties with a "Link a Property" search box. 011-customer-properties
- Admin > Preferences > Customer Preferences (menu 128-preferences-customer-menu):
- Structure Templates: list 348-structure-templates, editor 349-structure-template-editor, root node 350-structure-template-node, child node 351-structure-template-child.
- Sub-Property Types: list 352-subproperty-types, editor 353-subproperty-type-editor.
- Property Estimation Units: list 340-property-estimation-units, editor 341-property-estimation-unit-editor.
- Route Regions: list 344-route-regions, editor 345-route-region-editor.
- Admin > Preferences > Office Settings > Office Info: physical location, invoice address, territories and office map position. 196-office-info, address editor 200-office-invoice-address-editor, territory editor 201-office-territory-editor.
- Admin > Preferences > Office Settings > Office Zip Codes: list 260-office-zip-codes, editor 261-office-zip-code-editor.
- Customers > Customer Reports (Customer Search) > Customer Location filters 414-customer-location-filters and Toggle Map 433-customer-report-map.
- Reporting > Office > Audit > Customers with bad geocode 471-audit-bad-geocodes and Customers with differing addresses 473-audit-differing-addresses.
- Related map surfaces owned by other blocks: Scheduling > Visual Grouping > Assign Regions 524-visual-grouping-regions; Sales > Area Management 054-sales-area-management.
- Unit-level settings owned by other blocks: Condition Templates unit type 133-settings-condition-template-form; Custom Appointment Unit Details 163-settings-custom-unit-details, 164-settings-custom-unit-group; Preset Notes by property context 193-mobile-preset-note-form.
- Dashboard measured-area cards: Subscribed Meas. SF 408-dashboard-metric-help-20 and Subscribed Meas. LF 410-dashboard-metric-help-22.
Connections to other blocks
- Location is stored on Customer account: the Customer Card Info tab holds the service address, and each linked site is its own Customer Card (observed 004-customer-info, 011-customer-properties).
- Location classification feeds Commercial accounts: Residential/Commercial and unit mode are the only commercial distinctions seen at intake (observed 371-new-commercial-customer-form).
- Location is billed through Invoicing and billing terms: service address, billing address and payer are separate; Default Bill To and billing account decide who pays (observed, plus Billing manual).
- Linked locations keep separate balances in Payments and collections: a payment to one property does not settle the others (documented, Properties manual).
- Linked locations shape access in Customer portal: master account sees and pays children; children cannot see each other (documented).
- Location geocodes feed Routing: the Intelligent Routing and Fill Routes manuals say missing or invalid geocodes can exclude work; the Audit flags bad geocodes (documented and observed 471-audit-bad-geocodes).
- Location data drives Scheduling and appointments: the Job Pool filters by property type, map pages, ZIP codes and cities, and its multi-row selection excludes multi-unit properties (observed).
- Location size is reused by Service agreements and renewals and Lead, sales and estimate: estimation units and measured square/linear feet on subscriptions and dashboard cards (observed 340-property-estimation-units, 408-dashboard-metric-help-20).
- Unit or structure context is used by Inspection reports and audits (condition templates) and Work order (unit details, preset notes) (observed).
- Office ZIP claims limit where Lead, sales and estimate and Customer account can create accounts (observed settings, enforcement untested 261-office-zip-code-editor).
- Location quality is reported in Reporting and analytics: Audit checks for bad geocode and differing addresses (observed).
How FieldRoutes does it
Record a service location at intake (observed screens, save not tested). The office opens New Customer from the top bar. The Basic Information tab is the only tab. It takes the address, ZIP, city, state (defaults to the account's state), county and country (defaults to United States), the map field, square feet, tax rate, division and an embedded map (Map/Satellite, fullscreen, camera, Street View, link to Google Maps). The same form takes Residential/Commercial, Single Unit/Multi Unit/Structures and Sub-Property Type. Switching between the four captured combinations did not change any field. Save was never pressed, so required fields, duplicate detection, geocoding and the tabs that appear after creation are unknown. 370-new-customer-form, 371-new-commercial-customer-form, 372-new-multiunit-customer-form, 373-new-structures-customer-form
Edit it on the card (observed). The Info tab shows the same service address with state and county pickers and the classification fields. Nothing was edited. 004-customer-info
Add another site (documented, not tested). The Properties tab has only a "Link a Property" search box in this account; no property is linked. The Properties manual says each linked site needs its own Customer Card and keeps separate billing, invoices, subscriptions and documents. The master portal account can navigate and pay child properties; child accounts cannot navigate the other linked accounts. A payment stays on the property it was made for. The FieldRoutes commercial product page also claims linking can support consolidated invoices, separate charges to service addresses and unit quotas per appointment (public claim, not tested). 011-customer-properties
Merge two cards (documented, not tested). Merge permanently absorbs a card's records and history into a master and cannot be reversed. The customer Admin tab is the indexed entry point for Merge, Move and Remove; no merge was run.
Who pays for a site (observed controls, documented rules). The Billing tab has a separate billing address, Default Bill To (applies to new invoices and subscriptions) and Assign New Billing Account. The Billing manual says responsibility can be set per customer, subscription or invoice; Assign New Billing Account changes the responsible customer; Copy Billing Info copies correspondence details between linked accounts. The Billing tab supports US billing addresses only. An AR Freeze Customers trigger action freezes the responsible customer and the service subscriptions of other accounts whose balances that customer is responsible for. See Invoicing and billing terms and Payments and collections.
Define structures (observed draft only). + Structure Template opens a tree with one root node named "New Structure". The root name is edited in place (there is no separate name field). A plus icon adds a child; children have a trash icon; nodes expand and collapse. The draft was cancelled. Maximum depth, reparenting, inheritance and use on a customer were not checked. 349-structure-template-editor, 350-structure-template-node, 351-structure-template-child
Find customers by location (observed). Customer Search has a Customer Location filter group (map code, address, city, ZIP, country, state, county including "[County Not Set]", latitude/longitude with a distance, square-feet range). Its Customer Account group also filters Has Linked Properties, Has Child Billing, Account Type and Unit Type. Toggle Map draws the result set as markers; marker details, clustering and omitted addresses were not tested. 414-customer-location-filters, 433-customer-report-map
Check location data quality (observed). The Audit report has 19 checks; it says it shows problems for customers entered in the selected dates (both dates showed the capture day; this date logic was not verified). "Customers with bad geocode" showed 4 potential errors with Customer ID, customer, address, city, state, ZIP and account status columns, a search box and sortable headers. Its help suggests checking the office's map coordinates when many rows appear; that is guidance, not proof of the cause. "Customers with differing addresses" showed 0 customers and no table. Nothing was corrected or exported. 471-audit-bad-geocodes, 473-audit-differing-addresses
Office geography (observed settings, enforcement untested). Office Info keeps the legal Business Address (part of Business Info, next to legal name, entity type and EIN; distinct from the correspondence and routing addresses), the Invoice Address (printed on invoices, statements, service notices and emails; P.O. box allowed), the Physical Location (route start/end; per-technician overrides on the User Card Location tab), Territories and a separately saved office map position (GeoCoordinates, Save Map Position). The territory editor offers hand, draw-shape and delete tools, Map/Satellite, Save and Close; status is Not set and nothing was drawn. Office Zip Codes lets an office claim ZIPs per category and decide whether accounts can be created in unclaimed areas; sharing works only when both offices set Share Zip Codes to Yes. Whether ZIP claims actually block or allow account creation was not tested. 196-office-info, 201-office-territory-editor, 260-office-zip-codes, 261-office-zip-code-editor
Settings and controls
All settings and controls seen 41 rows
Service address and property fields (intake form and Info tab) 370-new-customer-form, 004-customer-info
| Control | What it does / limit |
|---|---|
| Address / Zip Code / City / State / County / Country | Service-location inputs. State defaults to the account's state; Country to United States. County and supported-country options are visible; they are UI choices, not a promise of tax or regulatory support. |
| Map field | Unlabeled input beside the Map label; likely a map code (inference). |
| Sq. Ft. | Property area. No calculation or pricing effect tested. |
| Residential Property / Commercial Property | Classification. Selecting Commercial adds no fields and keeps person-name fields. |
| Single Unit / Multi Unit / Structures | Unit mode. No deeper controls before save. |
| Select Sub-Property Type | Only a placeholder; no definitions exist. |
| Embedded map: Map / Satellite, fullscreen, camera, Street View, keyboard shortcuts, open in Google Maps, terms, report a map error | Map navigation only. No address was geocoded. |
Linked properties 011-customer-properties
| Control | What it does / limit |
|---|---|
| Link a Property (search) | Find another customer/property account to link. No link made. |
| Linked Properties list | Empty in this account. |
Structure Templates 348-structure-templates, 349-structure-template-editor
| Control | What it does / limit |
|---|---|
| Global / Visibility filters, Search, + Structure Template | Find and create templates. List empty. Columns: Structure Template, Global, Visible. |
| Office scope; Hidden/Visible; save/cancel | Availability; saves or abandons the whole tree. |
| "New Structure" root link and text box | Select and rename the root. No separate Name field. |
| Plus icon on root/child | Add a nested node. |
| Expand/collapse; trash icon on child | Navigate and remove draft nodes. Depth and reparenting not checked. |
Sub-Property Types 352-subproperty-types, 353-subproperty-type-editor
| Control | What it does / limit |
|---|---|
| Visibility / Global / System filters, Search, + Sub-Property Type | Find and create labels. Columns: Description, Global, Visibility, System. List empty. |
| Sub-Property Type (required); office scope; Hidden/Visible; save/cancel | Define a label. No property assignment, inherited attributes or pricing effect shown. |
Property Estimation Units 340-property-estimation-units, 341-property-estimation-unit-editor (owned by Lead, sales and estimate)
| Control | What it does / limit |
|---|---|
| Global / Visibility / System filters, Search, + Unit of Measure | System units Square Feet (SF), Linear Feet (LF), Count (CNT) have no edit link. |
| Description (required); Abbreviation (required, max three characters); office scope; Hidden/Visible; System = No | Define a custom unit. No conversion, takeoff or automatic pricing shown. |
Office geography 196-office-info, 200-office-invoice-address-editor, 201-office-territory-editor, 260-office-zip-codes, 261-office-zip-code-editor, 345-route-region-editor
| Control | What it does / limit |
|---|---|
| Physical Location Address / City / State / Zip / Country | Office base and default route start/end. |
| Business Address / City / State / Zip (Business Info) | Legal business address, distinct from the Invoice Address and the Physical Location. Values omitted. |
| Invoice Address / City / State / Zip | Return address on invoices, statements, notices and emails. |
| Territories edit / status | Service-area boundary; Not set. Editor: stop drawing, draw a shape, delete, Map/Satellite, Save, Close. |
| Office Location Map / GeoCoordinates / Save Map Position | Office map position saved separately from the address text. |
| Office Zip Codes: ZIP search, Office, row edit; columns Office, Category, Zip Codes, Can Create in Unclaimed Areas, Share Zip Codes | One office row: Allow / No. |
| ZIP editor: Category multi-select (a service category and SYSTEM offered), "Paste zip codes here", Can Create in Unclaimed Areas (Do Not Allow / Allow), Share Zip Codes (No / Yes), save/cancel | SYSTEM meaning, ZIP validation and conflict handling untested. Access profiles include an "Assign Office Zip Codes" permission. |
| Route Regions: Visibility, Search, + Region; Region (required), Hidden/Visible | Label only; list empty. |
Customer Search location filters 414-customer-location-filters
| Filter | Options / limit |
|---|---|
| Map Code / Address / City / Zip Code | Text filters on the service location, not the bill-to address. Match rules unknown. |
| Country | Any Country, Brazil, Canada, Germany, Guam, United Kingdom, United States, Virgin Islands. Filter options only. |
| State | Multi-select labeled with country. |
| County | Multi-select, including [County Not Set]. |
| Lat / Lng / Distance | Proximity search. Distance unit and radius rules not given. |
| Square Feet Between | Area range, distinct from subscription measurement units. |
| Account group: Has Linked Properties (N/A/No/Yes), Has Child Billing (N/A/Yes/No), Account Type, Unit Type (N/A / Single Unit / Multi Unit / Multi Structure) | Relationship and classification filters; joins untested. |
| Toggle Map | Result markers on a map. |
Audit checks 471-audit-bad-geocodes, 473-audit-differing-addresses
| Control | What it does / limit |
|---|---|
| Start Date / End Date / Refresh / Export to CSV | Shared by all 19 checks. Export not run. |
| Customers with bad geocode | 4 potential errors; columns Customer ID, customer, address, city, state, zip, Account Status; search and sort. |
| Customers with differing addresses | 0 customers; no table or columns exposed. |
Unit and structure context used by other blocks
- Condition Templates have a unit type (Single Unit or Structure). 133-settings-condition-template-form (Inspection reports and audits)
- Custom Appointment Unit Details holds unit-level custom fields for visits at multi-unit properties; only a name-only group dialog was reachable. 163-settings-custom-unit-details, 164-settings-custom-unit-group (Work order)
- Preset Notes have 12 checkboxes making a note available as Service, Invoice or Office note for Residential, Commercial, Multi-Unit and Structure properties. 193-mobile-preset-note-form (Work order)
- Billing Preferences have separate Residential and Commercial portal payment caps. (Customer portal)
What the research did not prove
- No existing linked-property, multi-unit or structure hierarchy was found or opened. How units and structures are entered after saving a Multi Unit or Structures customer is not shown.
- No Structure Template was saved or applied; maximum depth, reparenting and inheritance are unknown.
- No link, merge, master/child portal session or property-specific payment was tested. The master/child and merge rules come from the manual only.
- Whether a billing relationship can change without moving service history or rewriting earlier invoices is not tested. Cross-account invoice consolidation output was not seen.
- No address was geocoded. The meaning of the Map field / Map Code is not verified. The cause of the 4 bad geocodes is not established.
- The Audit date filter ("customers entered during the dates selected") was not verified, and the differing-addresses check had no rows, so its columns are unknown.
- Office territory is Not set; ZIP claim enforcement, sharing approval and overlap ownership were not tested.
- Sub-Property Types and Structure Templates are empty in this account, so no real example exists.
- The Customer Card Info tab manual was not reachable; Properties and Customer Portal manuals were read.
- Open commercial questions: many sites under one bill-to party, parent/child accounts, per-unit service, inspections and conditions, structure reuse, commercial agreements and unit-level reporting.
- The fit conclusion lists separate linked-property payments and the US-only billing address as acceptance conditions.
- Acceptance tests suggested by the research: one recurring residential account and one multi-site commercial agreement, where each site has its own instructions, access contact, PO, service scope and billing treatment; a realistic example separating service customer, service location, contract holder and payer; consolidated output, property-specific payment steps and separate-site charges; customer creation in claimed, shared and unclaimed ZIP areas.
Ideas for Our CRM
- Proposal: keep the service location, the billing correspondence address and the payer as three separate fields or records, as FieldRoutes does.
- Proposal: decide early whether a second site is its own account (FieldRoutes linking, separate balances) or a child location of one account; in FieldRoutes linked sites are not automatically pooled (documented per site; the master portal account can pay child properties, and consolidated invoices are a vendor claim; none of this was tested).
- Proposal: keep property classification (residential/commercial) separate from unit mode (single/multi-unit/structures).
- Proposal: if we support structures, show the unit or structure editor at intake, which FieldRoutes did not show before save.
- Proposal: keep office territory, ZIP claims and route regions as distinct concepts with clear names, to avoid the "region" confusion seen here.
- Proposal: offer a geocode-quality check on service addresses, since routing depends on valid geocodes.
- Proposal: make merge reversible or at least preview its effect; FieldRoutes documents merge as permanent.
Official FieldRoutes manuals
- The Customer Card: Properties Tab (Merge and Link) (read; updated 2025-12-16)
- Customer Portal: Overview (read; updated 2026-10-09; master/child property access)
- The Customer Card: Billing Tab (read; US billing addresses only, payer levels)
- The Customer Card: Info Tab (indexed; not reachable by the research tool)
- The Customer Card: Admin Tab (indexed only; Merge, Move, Remove)
- Public product page: Commercial Pest Control (linking, consolidated invoices, unit quotas; vendor claim)
- Research reports: customer intake, assessment, official manual findings, customer search
Screenshots kept in other blocks that also matter here 20
- 004-customer-info · Customer Card, Info tab (Customer account): The Info tab holds the customer's core record: name, two phones, email, company name, Source and Sub-Source, Residential/Commercial, Single Unit/Multi Unit/Structures, Sub-Property Type, Special Scheduling text and SMS/Email/Voice preference checkboxes.
- 054-sales-area-management · Area Management (sales territories) (Lead, sales and estimate): A map for managing door-to-door sales territories.
- 128-preferences-customer-menu · Customer Preferences menu (Customer account): Expanded list of the 22 customer-related setup pages: contact types, cancellation/hold reasons, contract templates and terms, customer communication, sources, divisions, email categories and templates, form templates, flags, note categories and types, prepayment discounts and letters, property estimation units, renewal notices, route regions, skip reasons, structure templates, sub-property types and voice messages.
- 133-settings-condition-template-form · New Condition Template form (Inspection reports and audits): 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.
- 163-settings-custom-unit-details · Custom Appointment Unit Details list (Work order): Same structure as Custom Appointment Details but for unit-level data on a visit (multi-unit properties): filters, search, empty table and + New Group of Custom Fields.
- 164-settings-custom-unit-group · New unit custom-field group (Work order): Name-only dialog (Group Name, cancel, save) for a unit-level custom-field group.
- 201-office-territory-editor · Office territory map editor (Routing): Full-screen map for drawing the office's service territory boundary, with hand, draw-shape and delete tools, a 'select or create a new boundary' prompt, Map/Satellite toggle, Close and Save.
- 260-office-zip-codes · Office Zip Codes list (Customer account): Configures which postal ZIP codes an office claims, which controls where accounts can be created.
- 261-office-zip-code-editor · Office Zip Code editor (Customer account): Edit form for an office's ZIP claim: a Category multi-select (a service category and SYSTEM are offered), a 'Paste zip codes here' box, Can Create in Unclaimed Areas (Do Not Allow / Allow) and Share Zip Codes (No / Yes), with save/cancel.
- 340-property-estimation-units · Property Estimation Units list (Lead, sales and estimate): Units of measure for sizing a property when estimating or pricing service.
- 341-property-estimation-unit-editor · Property Estimation Unit editor (new) (Lead, sales and estimate): Blank form with required Description and Abbreviation (max three characters per tooltip), office scope and Hidden/Visible; System shows No.
- 370-new-customer-form · New customer form, residential single unit (Customer account): The Create a New Customer form (Basic Information tab) is the intake screen for a new account.
- 371-new-commercial-customer-form · New customer form, commercial property (Commercial accounts): The same intake form with Commercial Property selected (still Single Unit).
- 372-new-multiunit-customer-form · New customer form, commercial multi unit (Commercial accounts): The intake form with Commercial Property and Multi Unit selected.
- 373-new-structures-customer-form · New customer form, commercial structures (Commercial accounts): The intake form with Commercial Property and Structures selected.
- 408-dashboard-metric-help-20 · Dashboard help: Subscribed Meas. SF (Reporting and analytics): The help dialog for the dashboard's Subscribed Meas.
- 410-dashboard-metric-help-22 · Dashboard help: Subscribed Meas. LF (Reporting and analytics): The help dialog for the dashboard's Subscribed Meas.
- 414-customer-location-filters · Customer Search, Customer Location filters (Customer account): The Customer Location group filters by service address: map code, address, city, zip, country, state, county (including 'County Not Set'), latitude/longitude with a distance radius, and a square-footage range.
- 433-customer-report-map · Customer Search, map view (Customer account): Toggle Map shows the search result on a map with customer markers and map navigation controls.
- 524-visual-grouping-regions · Visual Grouping, by region (Routing): The region mode groups subscriptions by geographic region instead of technician: 34 subscriptions are Unassigned/Any Region, with the map, list and drawing tools.
Research sections used for this page 37
The original research reports are kept unchanged in the archive. These are the sections that speak about this block:
- admin/controls.md › Customer Preferences menu: Index of the Customer Preferences menu with a one-line purpose for each entry (contact types, cancel reasons, contracts, communication, sources, divisions, email/form templates, flags, notes, prepayment, estimation units, renewals, regions, skip reasons, structures, sub-property types, voice messages).
- admin/controls.md › Composite Stat and Office Zip Codes: Composite Stat for the Sales Leaderboard (Add Metric did not work in capture) and Office Zip Codes claims with create-in-unclaimed-areas and sharing settings.
- admin/controls.md › Property Estimation Units: Property Estimation Units (system SF, LF, CNT; custom units with 3-letter abbreviation).
- admin/controls.md › Structure Templates and Sub-Property Types: Structure Templates (draft tree of nested structure nodes) and Sub-Property Types.
- 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 › Custom schedules and custom appointment detail groups: Custom Schedules (month-by-month date or weekday rules for subscriptions and billing) and name-only custom appointment/unit detail groups.
- admin/findings.md › Office identity, correspondence address, routing origin, and service territory are separate: Office Info keeps contact, legal identity, authorized contacts (for the FieldRoutes account), invoice address, physical route origin and territory separate; territory editor.
- admin/findings.md › Property classification, route labels and structure hierarchy: Property Estimation Units, Route Regions, Skip Reasons, Structure Templates hierarchy and Sub-Property Types.
- assessment.md › 2. Residential and commercial operations: Residential vs commercial: Residential/Commercial and Single/Multi Unit/Structures classification, New Customer variants, Business Contacts are not customers, preset notes per property class, PO-expiry freeze and portal payment caps.
- assessment.md › 3. Multiple properties and billing relationships: Multiple properties and payer: linked properties stay separate accounts with own balances, Default Bill To / billing account, Structure Templates, merge is irreversible; AR Freeze action reaches subscriptions of accounts the payer is responsible for.
- assessment.md › 5. Scheduling, dispatch and routing: Scheduling and routing: Calendar, Job Pool, Dispatch Map, Route Builder/Templates, Fill Routes (chargeable on entry, 2,000 limit, time zones), Visual Grouping, Intelligent Routing (Equal Stop vs Auto Optimize), assignment; office endpoints/territory/ZIP policy; populated day and maps.
- assessment.md › 17. Workforce, office boundaries and operating policy: Workforce and offices: time-clock categories, transition rules, weekly limits, Time Clock report with ADP export, office legal/address/routing origin/territory and ZIP sharing; Vendors and Social Network are only dictionaries.
- coverage-gaps.md › Acceptance checklist and available follow-up states: Acceptance/follow-up checklist of unverified items: report filters, linked properties, mobile and portal runtime, roles/2FA, scheduling enforcement, financial and automation outcomes, integrations/migration, business requirements.
- customer-intake.md › What the property choices establish: Property classification (Residential/Commercial) is separate from unit mode (Single/Multi Unit/Structures); choosing Multi Unit or Structures shows no unit or structure editor before save; Sub-Property Type is empty.
- customer-intake.md › Observed fields and controls: Field-by-field table of the intake form: names, phones, email, source/sub-source, property and unit mode, special scheduling, SMS/Email/Voice preferences, flags and status checkboxes, address/county/map/sq ft, tax rate, division, embedded map, Save/Close.
- customer-intake.md › Software-fit questions still open: Open questions for commercial use: multiple sites under one payer, parent/child accounts, per-unit service and inspections, structure reuse, commercial agreements and unit-level reporting are not yet shown.
- customer-populated-findings.md › Billing contact, default payer and invoice consolidation are distinct: Billing contact, Default Bill To payer and invoice consolidation are distinct; manual says responsibility can be set per customer/subscription/invoice and subscription AutoPay overrides default; additional contact editor.
- customer-populated-findings.md › Fit implications and remaining evidence: Fit summary: evidence supports multiple subscriptions, separate billing/service cadence and payer; still missing linked properties/multi-unit, cross-customer responsibility, completion, payments allocation, signatures, permissions.
- customer-search.md › Shared report controls: Shared controls: submenu, filter groups, Clear Filters, Run Report, table search, Actions, Toggle Map, sortable headers, 134 entries, saved reports/columns.
- customer-search.md › Customer Account: Customer Account filters: account status, cancel date, subscriptions/appointments/linked properties/child billing, names, account and unit type, email, division, source, flags, payment and consent flags, tax; flags need List By Customer.
- customer-search.md › Customer Location: Customer Location filters: map code, address, country/state/county, lat/lng distance, square feet.
- customer-search.md › Map and result-table search: Toggle Map shows result markers on a map; table search narrows visible rows to one customer while footer still says 134.
- 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.
- final-evidence-review.md › Business-fit conclusion: Business-fit conclusion: conditional fit; acceptance conditions are non-US billing, separate linked-property payments, payment-plan compatibility, Fill Routes cost/time zones, shared access profiles, automation scope.
- report.md › Start with the conclusions: Headline distinctions: customer/subscription/appointment/invoice/payment are separate records; service vs invoice frequency; Service Type vs Plan vs Bundle, skip vs opt-out; linked properties keep own balances; revenue vs production vs contract value; checkout and Transfer; configuration is not outcome.
- reporting/controls.md › 065-report-audit — Audit: Audit report controls: date range, Refresh, CSV and the 19 data-quality check tabs with their counts, plus the stated purpose (common data-entry mistakes).
- reporting/controls.md › 471-audit-bad-geocodes — Audit: Customers with bad geocode: Observed controls for Audit check: Customers with bad geocode (471): One of the 19 Audit data-quality checks: customers whose address could not be placed correctly on the map.
- reporting/controls.md › 473-audit-differing-addresses — Audit: Customers with differing addresses: Observed controls for Audit check: Customers with differing addresses (473): One of the 19 data-quality checks in the Audit report, selected on its own: it lists customers whose addresses do not match each other (for example service versus billing address).
- reporting/findings.md › Audit panel review: captures 065 and 461–478: All 19 Audit data-quality panels with counts and columns (42 subscriptions without initial, 4 bad geocodes, 8 multiple subscriptions); counts are potential errors, date filter semantics unverified.
- routing/controls.md › Visual Grouping (036, 522–524): Visual Grouping controls: technician vs region mode, scheduled-customer inclusion, group lists, drawing tools, Revert/Save, Hard Reset.
- sales/controls.md › 054: Area Management: Area Management map filters and layers.
- sales/findings.md › Area Management: Area Management territory map and filters; no territory shown.
- sources/official-manual-findings.md › The Customer Card: Properties Tab (Merge and Link): Properties tab manual: each linked site keeps its own card, billing and documents; master portal account can pay children; payments stay per property; merge is permanent.
- sources/official-manual-findings.md › Customer Portal: Overview: Customer Portal manual: auto-sign-in email links expire in two weeks, fixed usernames, self-service contact/payments, master/child property access, review prompt.
- 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.