The visit is on plan
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
Plan, visit and outcome in one system.
Plan routes and visit tasks. Review photos, orders and exception reasons to decide the next action.
Discuss field-team operations- PLANDaily plan
- PROOFVisit evidence
- ACTIONNext action
Field-day pulse
Field-day status
See what is on plan, what needs review and what is blocking a visit. Select a status to see the manager's next action.A deviation needs review
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?
Work is blocked
The outlet is inaccessible, synchronization is in conflict, required data is unavailable or another department 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 visit plan to review
Each stage stays linked to the outlet and employee. Visit results help supervisors adjust the next route and its tasks.- 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 assigned steps and saves visit data.
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
Team tasks at the outlet
Each role has its own tasks. Visit steps are configured by channel, segment and outlet type, so managers can compare like-for-like results.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 · availability · 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 situations that need a decision
- Decision
- Whom to assist, what to change and when to recheck
Visit data
The facts behind each visit
Outlet, time, supporting material and outcome stay together. Managers review these facts and see what needs clarification.- 01
Outlet
Customer, address, channel, segment and applicable commercial agreement.
- 02
Time and geofence
Start, finish and location recorded under the agreed rules.
- 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
Situations that need review
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
From review to the next visit
After the review, the manager assigns an action. The next visit shows whether it helped resolve the problem.- 01
Signal
The system shows a deviation from the agreed visit rules.
- 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
Boundaries of execution control
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
Preparing for a pilot
Agree the territory, workflows, data and acceptance criteria before launch. The pilot shows how the selected process works.- 01
Territory and roles
Select the team, channels, outlet types and a period with a typical workload.
- 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
SFA and related workflows
Resources explain field-work terms and metrics. Product pages cover tools for collecting and analysing visit data.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
Discuss field-team operationsA review of your team's workflow
Discuss one territory: employee tasks, visit data and supervisor actions. Define what to test in a pilot.