The visit follows the applicable playbook
The outlet, time and required steps are confirmed; a commercial outcome or a valid reason is retained.
- Signal
- Continue the field day
- Manager's question
- Are any planned outlets or required steps still open?
Skip to main contentField day · illustrative scenarioTerritory 04 On plan Needs attention Blocked 01 02 03 Missed outlet Evidence gap No outcome Synchronization 01 02 03
Smartup · Field Team Management
Field Team Management
Every visit becomes a verified outcome, an exception or the next action.
Smartup connects territory plans, routes, outlet visits, evidence and commercial outcomes. Field employees know what applies at each outlet; supervisors see where to investigate, assist or recheck.
Book a process review- PLANA clear plan before the team enters the fieldOutlets · priorities · tasks · applicable visit playbook
- PROOFAn outcome linked to visit evidenceOutlet · time · steps · image · order · reason
- ACTIONAn exception with an accountable ownerInvestigate · assist · assign · recheck
Field-day pulse
Manage the team by execution state - not a trail of location dots.
Three states separate normal execution from the situations that genuinely need a manager. These illustrative cards contain no customer performance figures.A deviation can be investigated while it is actionable
The sequence is broken, a required step is missing or visits repeat without an outcome.
- Signal
- Open the evidence and reason
- Manager's question
- Does the employee need help, a task or a revised day plan?
Execution has stopped because of an external condition
The outlet is inaccessible, synchronization is in conflict, required data is unavailable or another function must decide.
- Signal
- Separate the process from the data issue
- Manager's question
- Who is accountable for removing the constraint?
Illustrative operating model · no customer data
One working day · one chain of facts
From plan to review - without a break between field and manager.
Every stage uses the same outlet and employee context. Motion shows how the cycle advances; the content and controls remain usable without animation.- 01
Plan
Territory, outlets, tasks and priorities define a clear workload for the day.
Role · route · objective - 02
Route
Visit order reflects outlet schedules and the agreed territory constraints.
Outlets · sequence · status - 03
Visit
The employee completes applicable steps and records facts in the outlet context.
Check-in · steps · images - 04
Outcome
An order, audit, task or reason updates the operating view and its defined KPI.
Outcome · reason · source data - 05
Review
The supervisor acts on the exception and checks the effect in the next cycle.
Owner · action · repeat
Role playbooks
One management standard - different work at the outlet.
Visit steps are selected by role, channel, segment and outlet type. Each employee sees only applicable work, while managers compare like-for-like outcomes.Sales representative
What should be sold and agreed at this outlet?
- Working scenario
- Customer history · assortment · order · receivables · reason
- Verifiable outcome
- An order or a verified reason for no order
- Decision
- Which commercial action should follow
Merchandiser
Does in-store execution match the outlet standard?
- Working scenario
- Assortment · OSA/OOS · price · display · promotion · image
- Verifiable outcome
- Execution evidence and a specific deviation
- Decision
- What to correct now or route to the supervisor
Supervisor
Where did execution diverge - and why?
- Working scenario
- Plan versus actual · evidence · reasons · recurrence · tasks
- Verifiable outcome
- A prioritized list of management exceptions
- Decision
- Whom to assist, what to change and when to recheck
Visit evidence passport
The visit outcome can be verified and interpreted in context.
A single check-in explains little. The evidence passport preserves what a supervisor needs to investigate without asking the employee to reconstruct the visit later.- 01
Outlet
Customer, address, channel, segment and applicable commercial agreement.
- 02
Time and geofence
Start, finish and the agreed geographic context of the business visit.
- 03
Playbook version
Role, visit type and the steps required on that date.
- 04
Outcome and materials
Order, answers, images, comments and primary facts from the visit.
- 05
Reason and follow-up
Reason code, owner, action, due time and recheck status.
Exception centre
Managers see four decision types - not another stream of noise.
Choose a situation. The panel connects the signal, investigation and next action without automatically judging the employee.A planned outlet has no verified visit
- Signal
- No check-in, or the visit was moved without an applicable reason
- What to inspect
- Outlet schedule, route, previous status and employee comment
- Action
- Revise the day, move the task or correct the territory plan
- Recheck
- Outlet status before the working day closes
The visit record does not support the stated outcome
- Signal
- A step is missing, an image is unrelated or the geofence needs review
- What to inspect
- Playbook version, source materials and outlet conditions
- Action
- Request clarification or assign a repeat check
- Recheck
- Corrected evidence or the next comparable visit
Visits repeat without a commercial outcome
- Signal
- The same no-order reason recurs by outlet, SKU or employee
- What to inspect
- Order history, assortment, price, receivables and reason codes
- Action
- Investigate the cause and change the applicable action or priority
- Recheck
- The next visit outcome for the same reason
A field fact was saved but needs reconciliation after exchange
- Signal
- Price, stock, credit limit or document status changed after offline work
- What to inspect
- Event times, data versions and the conflict-resolution rule
- Action
- Separate a technical conflict from an execution error and follow the agreed protocol
- Recheck
- Final document status and the linked visit
Supervisor operating loop
A review changes the next visit - or it is not a closed loop.
Smartup preserves the link between an exception, the manager's action and the later outcome, so a follow-up task does not become an isolated record.- 01
Signal
The system separates an applicable deviation from the visit stream.
- 02
Context
The manager sees the outlet, employee, playbook and primary facts.
- 03
Cause
An operating cause is separated from a data issue or accepted exception.
- 04
Action
Assign assistance, a joint visit, a task or a rule change.
- 05
Recheck
The next comparable visit shows whether execution changed.
Solution boundaries
Execution control does not become an assessment without context.
Data-use rules, access roles and permitted actions are agreed in the project and made clear to the field team.GPS supports a business visit
Location is used within an agreed visit scenario. It does not replace the visit outcome and is not a standalone employee assessment.
HR records and payroll remain separate
Smartup manages field execution and tasks. Employment records and payroll calculations remain in their specialist systems.
Offline work needs synchronization rules
Locally available data, version priority and conflict handling are defined for the specific process and integrations.
Pilot readiness
Start with a management scenario - not an app installation.
Four agreements make process quality measurable without an unsupported promise of sales uplift.- 01
Territory and roles
Select the team, channels, outlet types and a representative period.
- 02
Visit playbooks
Define required steps and accepted omission reasons for each role.
- 03
Evidence and exceptions
Agree the data, review rules, owners and response times.
- 04
Acceptance criteria
Measure process completeness, reason quality, review time and action closure.
Method and product
Check the SFA mechanics and related operating scenarios.
The resources define field KPIs and process boundaries; product pages show where visit evidence is captured and how it returns to management action.FAQ
Frequently asked questions
01Is this employee surveillance?
No. GPS, time and steps are business evidence for a visit and exception workflow. The purpose is execution management and coaching, not location collection without a business case.
02Can agents and merchandisers have different visit flows?
Yes. Steps are configured by role, channel, outlet segment and visit type, so order, shelf audit or receivables tasks appear only when relevant.
03What happens with unstable connectivity?
Behavior depends on the configured SFA flow and synchronization policy. Data status remains visible and exceptions can be reviewed after exchange.
04What is Voice AI used for?
Voice AI can structure agreed voice input and visit context. Supported languages, fields and scenarios are confirmed for the project.
05What does a supervisor see?
Planned and actual visits, evidence, recurring causes, problem outlets and assigned actions within the supervisor’s permitted territory.
06How can a pilot be assessed without an uplift promise?
Agree process criteria such as visit and step completeness, exception quality, review time and follow-up closure for a controlled group.
Field process review
Book a process reviewMap the path from visit plan to supervisor action.
Select one territory and role, then review the current playbook, data sources, exceptions and pilot acceptance criteria.