Visit Duration: Interpret Unusually Short or Long Sales Visits

Duration anomalies are review triggers, not verdicts. Check start and end events, separate waiting from service and complex orders, and use a consistent exception worksheet before acting.

Field sales supervisor checks shelf execution with a sales representative.

A short sales visit is not automatically poor, and a long one is not automatically good. Treat duration as an exception signal: verify that start and end events were recorded correctly, compare the visit with others of the same type and objective, then review the cause with the salesperson and store context. Duration alone should not trigger a universal minimum, a performance ranking or automatic discipline.

For FMCG field sales teams, the useful question is not what number of minutes is right. It is what happened during the call and whether the record explains the time. This guide gives a review process, a worksheet and a labeled hypothetical example.

Check the time record before interpreting visit duration

Start with data quality. A record can look extreme because a checkout was missed, a duplicate check-in was created, a device clock was wrong, a record was edited, or the wrong visit type was selected. These are time-entry mistakes, not evidence about selling behavior.

Define the business events that start and end a visit. A start event might be arrival confirmed against the store record; an end event might be checkout after required tasks are complete or the call is closed as incomplete. Exact events depend on your process and system configuration. Ask which user actions write each timestamp, whether edits are logged, and whether waiting time can be recorded separately. If those questions cannot be answered, treat duration as low-confidence data.

Prepare store ID, staff ID, territory, visit type, objective, start and end timestamps, task status, order lines and reason codes. Confirm required fields for your implementation rather than assuming a standard set. For a broader view of visit evidence, see Visit Quality: How to Measure Store Visit Quality in FMCG Field Sales.

Separate the common causes of duration anomalies

Once timestamps are credible, classify the anomaly before judging it. The labels below are review categories, not misconduct findings.

Duration anomaly review categories
Cause What it can look like Evidence to check Review action
Time-entry mistake Extreme duration, duplicate check-in or missing checkout Raw events, edit history, device clock, staff and store IDs Correct the record; fix form rules; exclude until validated
Waiting or access delay Long record with little task activity Arrival note, reason code, store contact, task timestamps Record waiting; reschedule; review route and call window
Service task Long record dominated by an audit, promotion setup or collection Completed tasks, time-stamped evidence, service or order status Compare with the same task type; check required evidence
Complex order Long record with many lines, stock checks, returns or approvals Order lines, edits, stock checks, approval status Separate complexity from delay; review order readiness
Incomplete record Short record with missing fields or no clear outcome Task completion, reason code, follow-up status Complete follow-up or close with reason; do not count as productive
Genuine short productive call Short record with all required tasks and a clear outcome Completed tasks, order or follow-up, review status No exception if evidence is complete; test assumptions

No pattern proves cause on its own. A short call with complete tasks may be efficient, while a long call may reflect waiting time or a genuinely complex order.

Compare like with like by visit type

Duration comparisons are meaningful only within similar visit types. A routine order call, a store audit, a promotion setup, a collection call and a new outlet opening have different tasks and time profiles. Compare within the same visit type, customer format and territory, and where possible under similar trading conditions.

Define each visit type in writing: objective, required tasks, start event, end event, required evidence and reason codes. Use a peer range or median for that type rather than one global average. Review the lower and upper tails separately. Do not set a universal minimum visit duration; a local threshold can be a review trigger, not proof of quality.

Airpalm’s public site describes mobile visits, route planning, store audits, sales orders, inventory and promotion management (checked 9 October 2026). If your team uses Airpalm or another SFA (sales force automation) tool, confirm how your implementation records call start and end, and whether waiting or service tasks are captured separately. A call record does not by itself prove that a task was performed correctly.

Use an exception review worksheet

Use a repeatable worksheet for every flagged record. Record:

  • Call, store, staff, territory and date.
  • Call type, objective and peer range.
  • Raw start and end events, timestamp source and edits.
  • Data-quality status: credible, corrected or unresolved.
  • Cause category from the table.
  • Evidence reviewed: tasks, orders, reason code and follow-up.
  • Salesperson and store context.
  • Action, owner, status and closure date.

Sales operations can own definitions and extracts; the line manager can review context and decide the action; the salesperson supplies field context. Track whether repeated anomalies come from form design, route timing, access problems or task templates. Reason Codes for Failed Store Visits: Reschedule FMCG Follow-Ups offers a related method for capturing causes.

Labeled hypothetical example

Hypothetical example only. A distributor’s field team flags a call far shorter than its own range for routine order visits. The raw record shows a valid check-in, a checkout, no order lines and an incomplete task list. The salesperson reports that the store owner was unavailable and the call was closed for follow-up. The reviewer classifies it as an access issue plus an incomplete call, not a low-quality sales call. The action is to keep the reason code, schedule a follow-up and check whether the visit type and start and end rules were applied correctly. No disciplinary action follows from duration alone.

Turn anomalies into process improvements

Use findings to improve call definitions, form design, route timing and follow-up. Review trends, not isolated records. Short-record patterns may point to incomplete checkout habits; long-record patterns may point to waiting or task scope. Neither proves performance.

For a related outcome measure, see Visit Rate: Calculate Productive Sales Outcomes, Not Presence. Judge whether the call achieved its objective, not whether it filled an expected number of minutes. Next step: agree start and end definitions, run a small exception review on one call type, then decide whether a local threshold is useful.

Frequently asked questions (FAQ)

Should we set a minimum visit duration?

A universal minimum is not a reliable quality test. Define required tasks and evidence for each call type, then review the lower tail of your own distribution as a local trigger. Validate the cause before acting; a short call with complete tasks and a clear outcome may be efficient.

How can we distinguish a long complex order from waiting time?

Compare task and order activity. A complex order usually shows many order lines, stock checks, returns or approval questions; waiting usually shows little task activity before service begins. If sub-task timestamps are unavailable, use reason codes and manager context, and treat the result as a hypothesis rather than proof.

What if a salesperson forgets to check out?

Treat it as a time-entry exception. Correct or flag the record, check whether missing checkout is a repeated form-design issue, and avoid comparing the duration until the event is resolved.

Can duration be used in performance reviews?

Only as supporting context after the time record is validated and alongside other measures such as required-task completion, follow-up completion and order outcomes. Do not use duration alone for automatic disciplinary decisions; apply a consistent policy and allow manager review.

Put this guide into practice

This general-purpose worksheet is a starting point. Adapt its fields, responsibilities and rules to your business process.