Taxi Status for Employees & Trips

Created by Moveinsync Help, Modified on Thu, 19 Mar at 6:34 AM by Moveinsync Help

Overview

The Taxi Status feature allows Transport Managers and Site Admins to mark employees as “Taxi” when they choose to commute independently instead of waiting for the assigned vehicle.

This ensures:

  • Accurate trip tracking

  • Proper handling of operational exceptions

  • Correct application of penalties and billing rules

This feature is controlled via the configuration:

  • Property: ENABLE_EMPLOYEE_AND_TRIP_TO_BE_TAXI

  • Default Value: false


Problem Statement

In real-world scenarios, employees may not always be able to wait for their assigned cab and may choose alternative transportation such as a taxi.

Previously, there was no structured way to capture this behavior in the system.
The introduction of the Taxi status enables proper tracking, reporting, and billing control for such cases.


Key Features & Functional Behavior

1. Employee Status – Taxi

A new employee status “Taxi” has been introduced.


2. Allowed Status Transitions

Employees can be marked as Taxi from the following states:

  • Sign-In → Taxi

  • No-Show → Taxi


3. When Can an Employee Be Marked as Taxi?

Employees can be marked as Taxi at any stage:

  • Before trip start

  • During the trip

  • After trip completion


4. Final Status Restriction

Once an employee is marked as Taxi:

  • The status cannot be reverted from:

    • Trip-sheet

    • Trip view


5. Adhoc Employee Restriction

  • Employees in Adhoc trips cannot be marked as Taxi


6. Driver App Behavior

  • If an employee is marked as Taxi during an ongoing trip:

    • The employee is removed from the Driver App trip roster


7. Trip Status Behavior

If all employees in a trip are marked as Taxi:

  • Trip Status → “Trip Marked as Taxi”

  • Trip is treated as an Incomplete Trip

  • Trip will not be considered for billing


8. Escort Scenario

Taxi logic behaves similar to No-Show, with a key exception:

  • If an escort:

    • Signs in

    • Signs out

→ The trip can still be completed, even if all employees are Taxi

However:

  • Such trips will not be billed


Tripsheet Controls

Taxi Status Option

On the Tripsheet, users can mark employees as:

  • Taxi

  • (Alongside existing statuses like No-Show and Cancelled)


Access Control

Only the following roles can mark Taxi status:

  • Site Admin

  • Transport Manager


Data Synchronization

  • Any Taxi status updates on the Tripsheet are automatically reflected in Trip details.


Billing Behavior

Employee Status Handling

  • Users can:

    • Mark / Unmark employees as Taxi (Billing side)

  • Adhoc employees cannot be marked as Taxi


Trip Completion Restriction

If enabled via configuration:

  • “Do not allow taxi trip to be completed”

Then:

  • Trips where all employees are Taxi cannot be manually completed


Billing Logic

If all employees are marked as Taxi:

  • The trip will not be billed, even if completed

Applicable for:

  • Trip-based packages

  • Zone-based billing

  • KM slab-based billing


Reporting Changes

BA Raw Report

  • Employee Status field now includes:

    • Taxi


RBD Reports

  • Trip Status “Marked as Taxi” is visible when:

    • “Include Incomplete Trips” filter is selected


UI Availability

Taxi status marking is supported in:

  • Modern Trip View

  • Tripsheet Edit (RMD Landing Page)

  • ODC Map Page


Summary

The Taxi Status feature provides:

  • Better operational visibility

  • Accurate exception handling

  • Controlled billing behavior

It ensures that trips where employees opt for alternative transport are properly tracked, managed, and excluded from billing where required.

Taxi Status for Employees & Trips

Overview

The Taxi Status feature allows Transport Managers and Site Admins to mark employees as “Taxi” when they choose to commute independently instead of waiting for the assigned vehicle.

This ensures:

  • Accurate trip tracking

  • Proper handling of operational exceptions

  • Correct application of penalties and billing rules

This feature is controlled via the configuration:

  • Property: ENABLE_EMPLOYEE_AND_TRIP_TO_BE_TAXI

  • Default Value: false


Problem Statement

In real-world scenarios, employees may not always be able to wait for their assigned cab and may choose alternative transportation such as a taxi.

Previously, there was no structured way to capture this behavior in the system.
The introduction of the Taxi status enables proper tracking, reporting, and billing control for such cases.


Key Features & Functional Behavior

1. Employee Status – Taxi

A new employee status “Taxi” has been introduced.


2. Allowed Status Transitions

Employees can be marked as Taxi from the following states:

  • Sign-In → Taxi

  • No-Show → Taxi


3. When Can an Employee Be Marked as Taxi?

Employees can be marked as Taxi at any stage:

  • Before trip start

  • During the trip

  • After trip completion


4. Final Status Restriction

Once an employee is marked as Taxi:

  • The status cannot be reverted from:

    • Tripsheet

    • Trip view


5. Adhoc Employee Restriction

  • Employees in Adhoc trips cannot be marked as Taxi


6. Driver App Behavior

  • If an employee is marked as Taxi during an ongoing trip:

    • The employee is removed from the Driver App trip roster


7. Trip Status Behavior

If all employees in a trip are marked as Taxi:

  • Trip Status → “Trip Marked as Taxi”

  • Trip is treated as an Incomplete Trip

  • Trip will not be considered for billing


8. Escort Scenario

Taxi logic behaves similar to No-Show, with a key exception:

  • If an escort:

    • Signs in

    • Signs out

→ The trip can still be completed, even if all employees are Taxi

However:

  • Such trips will not be billed


Tripsheet Controls

Taxi Status Option

On the Tripsheet, users can mark employees as:

  • Taxi

  • (Alongside existing statuses like No-Show and Cancelled)


Access Control

Only the following roles can mark Taxi status:

  • Site Admin

  • Transport Manager


Data Synchronization

  • Any Taxi status updates on the Tripsheet are automatically reflected in Trip details.


Billing Behavior

Employee Status Handling

  • Users can:

    • Mark / Unmark employees as Taxi (Billing side)

  • Adhoc employees cannot be marked as Taxi


Trip Completion Restriction

If enabled via configuration:

  • “Do not allow taxi trip to be completed”

Then:

  • Trips where all employees are Taxi cannot be manually completed


Billing Logic

If all employees are marked as Taxi:

  • The trip will not be billed, even if completed

Applicable for:

  • Trip-based packages

  • Zone-based billing

  • KM slab-based billing


Reporting Changes

BA Raw Report

  • Employee Status field now includes:

    • Taxi


RBD Reports

  • Trip Status “Marked as Taxi” is visible when:

    • “Include Incomplete Trips” filter is selected


UI Availability

Taxi status marking is supported in:

  • Modern Trip View

  • Tripsheet Edit (RMD Landing Page)

  • ODC Map Page


Summary

The Taxi Status feature provides:

  • Better operational visibility

  • Accurate exception handling

  • Controlled billing behavior

It ensures that trips where employees opt for alternative transport are properly tracked, managed, and excluded from billing where required.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article