"Significantly outstanding debtor?" is a yes/no field at the bottom of this call sheet. Most people scroll past it because debtor management feels like finance department territory. Those people are why accounts go 90 days overdue before anyone in the field flags them.
The field exists because the rep is the first person with eyes on the account every cycle. They know before head office does when a store owner is stalling, when the till is slow, when the order is smaller than usual and the payment is partial. The debtor flag field converts that field intelligence into a structured signal rather than a vague concern mentioned in a phone call that nobody wrote down.
The Data That Gets Lost Between the Car and the Office
A standard retail field call generates five or six distinct observations: the state of the customer relationship, what was actually done at the store, whether the competitor is undercutting on price, whether the store is holding up their end of the planogram agreement, which cycle presentations were completed. By the time the rep is driving to the next stop, some of that is already fragmenting.
Customer Status — Active, Inactive, Issues — is a triage field, not a description field. An account flagged as Issues should trigger a different response pattern from the account manager than Active. But only if the flag gets recorded at point of call, not reconstructed from memory at end of day. The rep who marks an account Issues at 10:40 AM in a convenience store in Penrith is giving the account manager actionable data. The rep who writes "had some problems at that store in the west" in an email on Thursday is not.
Customer Service Rating — Good, Bad, No Comment — works the same way. It is not about politeness. It is about pattern detection. An account that has been rated Bad on three consecutive calls is telling you something systemic about that relationship that is not visible if the ratings are buried in free-text comments.
The Call Record as a Cycle Compliance Layer
The Cycle Questions field is what separates a call sheet from a simple contact log. This cycle: presented Harvest Dark RYO and Reef 25's. Both checkboxes either get ticked or they do not. At cycle close, you can query every account record and see instantly which stores received which presentations. There is no ambiguity about whether the cycle objectives were executed.
Compliance to Agreement functions the same way. Planogram compliance, promotional compliance, whatever the store is contracted to — it is a binary state at time of call. The call record captures it. The Comments field is where nuance goes: "store compliant on planogram but Reef display moved to secondary position by store manager after my last visit."
Action in stores — Sale, Swap, Credit, Other — is the activity log. Not a narrative, a category. When you filter a hundred call records by Action = Credit, you see exactly which accounts received credits in that cycle. You do not have to read through comment text to reconstruct the distribution.
When You Have 80 Accounts in the Territory
The call record history per account is the rep's actual knowledge base.
Pull all records for a specific Account Number sorted by Call Date. You can see the last four visits: what was done, what the status was, what the rating was, whether the debtor flag was raised. That is a complete account context that takes fifteen seconds to retrieve and does not depend on the rep's memory, their notes, or the previous rep who covered the territory before them.
The Pricing Parity field — a simple yes/no on whether REX pricing matches competitors — generates intelligence at scale. Thirty accounts with "No" on pricing parity in the same metro cycle is a pricing action item for the product team. One account with "No" is an outlier that might have a local explanation. The difference between those two situations is only visible when the data is structured.
Account Number anchors everything. Not the store name — the account number. Store managers change. Store names change. The account number persists through all of it and ties back to the financial records, the delivery history, and the debtor ledger without ambiguity.
The test (linked library) field is the early iteration of what became the Field Rep Comments library in the later version of this template. The concept was right from the start: the longitudinal account narrative belongs in a linked structure, separate from the call record itself, queryable over time.