Skip to main content
Scootee

Implementation

Plan a Scootee field-team pilot

A Scootee implementation starts with a pilot: a small team, its manager and office reviewers use the field app and portal on normal working days. The pilot tests work sessions, visits, expenses, attendance, permissions and exports on real phones, and the rollout expands only after agreed checks pass.

Four pilot steps

Set up, test, review, then expand.

  1. 01

    Choose the team and workday

    Select a small employee group, the manager and office reviewers, and a normal day to test. Include a customer visit, a receipt or advance request, and an attendance exception where relevant.

  2. 02

    Set up people and permissions

    Prepare employees, branches, departments, shifts, customer assignments, expense categories, and reviewer access. An employee’s job title should not automatically grant portal authority.

  3. 03

    Test the employee app

    Run the supported work session, visit, expense, request, and attendance steps on representative devices. Check start and stop actions, connectivity loss, receipt uploads, and recovery for the selected platform and release.

  4. 04

    Check review and exports

    Confirm who can see each record, who cannot, how missing information is handled, and what reaches accounts or HR. Inspect distance methods and compare exported records with the reviewed source.

What does a Scootee pilot include?

A pilot puts a small field team, its manager and the office reviewers on Scootee for normal working days. Staff use the field app for work sessions, customer visits, expenses and, on the Workforce plan, attendance; reviewers use the portal to check routes, approve or return claims and export the results. The Field, Workforce and Operations plans include a 14-day trial and Enterprise evaluations run for up to 30 days, with the trial scope confirmed before activation.

What data should you prepare before the pilot?

Setup moves faster when these are ready before the first call:

  • An employee list with name, email, phone, branch and department, plus each person’s reporting manager — employees can be imported in bulk from a spreadsheet.
  • Branches, departments and, for attendance, shifts and rosters.
  • The customers each salesman or technician is assigned to.
  • Expense categories and the per-km conveyance rate for each employee’s two-wheeler or car.
  • Who reviews what: which managers, HR and accounts users need access, and to which branches.

How should you introduce GPS tracking to field staff?

Explain the purpose before the app is installed: location is recorded only during a work session the employee starts and ends, the record supports attendance and travel claims, and named roles can see it. Show the start and stop on a real phone, explain the Android location disclosure and permission prompts, and give a simple way to raise a disputed journey. The employee location privacy checklist lists what to cover, including notice under the DPDP Act, 2023.

Which phones and conditions should the pilot test?

Test the phones your staff actually carry, including low-cost Android models, plus iPhones if any staff use them. Turn on battery saver, lock the screen during a session, drive through a low-network stretch and restart the phone mid-session, then check the route, km and queued records in the portal. Background restrictions and battery settings differ by phone manufacturer, so note the settings each model needs.

How do you know the pilot has worked?

Agree the acceptance checks before the pilot starts and review them with the manager and accounts at the end. Typical questions are: did every session start and stop as expected, did offline records sync, can each reviewer see their own team and not others, do conveyance claims match the recorded km and rates, and does the export match what payroll or accounts needs. The checklist below is a starting point.

What happens after a successful pilot?

Most teams expand branch by branch, then add the next workflow — for example attendance and leave after the employee tracking app, or conveyance reimbursement once km records are trusted. The commercial proposal confirms the plan, user count, GST, billing term and support scope; compare plans on the pricing page.

Before adding more employees

Agree what a successful pilot must prove.

Current conveyance exports use kilometres and INR. For a US rollout, also confirm miles and currency requirements, company-policy rates, and the receiving payroll or accounting format. Payroll preparation does not imply US tax filing or bank payments.

Attendance and payroll review checklist
  • Representative employee and manager accounts tested
  • Expected and denied data scopes verified
  • Offline queue and reconnect behavior exercised
  • Distance method visible for the tested route
  • Expense, request, or attendance correction reaches the right reviewer
  • Required report or downstream export inspected

Pilot questions

Timing, scope, and acceptance checks.

How long does a Scootee implementation take?

Timing depends on the team structure, data preparation, devices, review process, and required exports or integrations. Agree a pilot scope and acceptance checks before confirming a schedule; there is no fixed rollout timeline for every customer.

Should every module go live at once?

Not necessarily. A safer evaluation starts with one bounded workflow and adds workforce, finance, or automation depth only after the first release criteria are met.

What should a pilot prove?

At minimum: employee access, explicit session behavior, supported offline recovery, manager visibility, role scope, exception handling, office decisions, exports, and mobile behavior on representative devices.

Can we import our employee list from Excel?

Yes. Employees can be imported in bulk from a spreadsheet in the portal, and the import produces a results file showing which rows were created and which need attention. Branches, departments and reviewer access are set up alongside.

Discuss your first team

Bring the process you want to pilot.

Share your team size, devices, customer-visit process, expenses, and office reviewers. Use the demo to agree what needs configuration and what the pilot should test.

Book a pilot planning demo