Skip to main content

Activity Feed - Master Sequence

Use the Master Sequence Activity Feed to confirm who made a sequencing change, when they made it, and whether it was a master-level change (affects the route pattern going forward) or a daily-level change (only affects a specific date).

Updated over a week ago

Accessing the Master Route / Master Sequence

You can open the Master Route / Master Sequence in two different ways:

Option 1: From the Main Header

  1. Click Master Route / Master Sequence from the top navigation bar.

  2. Select the route you want to view or edit.

Option 2: From the Route’s Action Menu

  1. Open any specific route in your system.

  2. Open the Action menu.

  3. Select Master Route / Master Sequence.

Tip: When you open it from a route’s Action menu, the route context is automatically pre-filled.


Finding Master Sequence Change History (Who + When + What Changed)

The Activity view shows a detailed history of updates. Use it to answer:

  • Who made the change (user)

  • When it occurred (date/time)

  • What was changed (the action recorded in the entry)

  • Whether the change was master-level or daily-level

Where to look first

Use this quick rule:

  • If the sequence issue affects the route pattern going forward → start with Master-Level Changes

  • If the sequence issue happened on one specific service date → start with Daily-Level Changes


Types of Activity Entries

There are two kinds of entries:

1) Master-Level Changes

These show updates made to the overall route pattern (Master Sequence). Example: “moved stop in master sequence.”

Common reasons you’ll see these:

  • A stop was moved earlier/later in the master order

  • A stop was added/removed from the master pattern

  • A long-term route optimization was made

2) Daily-Level Changes

These show route adjustments made on a specific date.

Common reasons you’ll see these:

  • A one-time reorder due to a missed stop or same-day constraint

  • A driver adjustment made for that day only

  • A date-specific exception (weather, access issue, special request)

Did this answer your question?