Six pricing cycles. Ten metro zones. Two markup percentages that have to be captured on-site before the store manager changes his mind about what he told you last week.
That is the working reality of a Richland Express field rep, and it is why a generic CRM dies on contact with this territory. The data you need to capture at every retail call is not a "contact" with a few notes attached — it is a structured audit with compliance flags, cycle-specific questions, and a direct communication channel back to head office that gets cleared weekly. The moment you start recording that in plain text notes, you lose the ability to filter, sort, or escalate anything at speed.
What Breaks When the Rep Leaves the Office
The disconnect between field activity and head office visibility is almost always a data-capture problem dressed up as a communication problem. A rep visits 12 stores in a metro cycle, logs observations in a notebook or a generic notes app, and by Thursday afternoon the account manager at HQ is working with whatever made it into the email summary — which is whatever the rep remembered to include.
The Cycle # field in this template is the first signal that the person who designed it understood field ops. Locking each call record to a specific cycle — METRO 2, METRO & COUNTRY 3, and so on — means that when you pull reports at cycle close, you are comparing apples to apples. You are not trying to figure out whether that store visit from three weeks ago was Metro 4 or Metro 5 because the rep just wrote "visited Parramatta."
The Account Number and Store Number fields look trivial until a credit is disputed. At that point the difference between a 6-digit account number and a store name is the difference between a 10-minute resolution and a half-day reconciliation exercise.
The Pricing Intelligence Layer
REX markup percentage versus competitor markup percentage — captured at point of contact, in the store, while the pricing ticket is still on the shelf. Not reconstructed later. Not estimated.
This is the part of the template that earns its keep. Pricing parity intelligence gathered in the field has a shelf life measured in days, sometimes hours in promotional cycles. The double-field format forces an exact percentage rather than a vague "they're a bit cheaper." After three cycles of data, you have a pricing trend per account that the rep can reference before they walk in the door on the next visit. Before they're standing at the counter with the store manager saying "yeah I think we might be a bit high on that."
The Compliance to Agreement field sits alongside this. Planogram compliance is either yes or no — it does not benefit from nuanced annotation at the time of capture. Get the binary state recorded, flag it, and let the comments field handle the context. The structured choice field prevents the kind of creative compliance language that makes reports unfilter-able.
When Head Office Needs to Act
The two-field communication architecture — Comments to action at Head Office and Office Action Requests — is the part of this template that most field systems get wrong by having one direction of flow.
The rep writes what HO needs to action. HO writes back into Office Action Requests with whatever they need the rep to do on the next visit. The hint text on the comments field makes it explicit: "this is cleared weekly." That cadence discipline is what makes the field-to-office loop function instead of turning into a comment graveyard that nobody audits.
Customer Status — Active, Inactive, Issues, New Customer — is the triage layer. An "Issues" flag on an account should trigger a different response pattern than "Inactive." When you have 200 accounts across metro and country zones, you need that status field to be machine-readable, not buried in a note.
The Metro/Country channel flag and Priority fields exist for routing and sequencing. Priority 1 in Metro is not the same workload commitment as Priority 3 in Country. Reps who have worked both know why that distinction matters when you are planning a run that starts at 6 AM and has to cover 14 stops before close of business.
The Field Rep Comments linked library is where the longitudinal account narrative lives — separate from the call record itself, queryable across time, and not overwritten on each visit. After 18 months of data, that library is the most valuable asset the rep owns.