Orders, routes and driver work in one system

When an order is amended by email, the route stays in a spreadsheet and the driver receives the change over the phone, it soon becomes unclear which information is current. Rita Grid keeps one up-to-date record for each order. Authorised users can see its status, assigned route and execution notes in the same place.

The dispatcher plans or updates the task, while the driver receives the information needed for the job. Completion data comes back to the same order, so the office does not have to reconcile several sources manually. Statuses, fields and modules are configured during implementation to reflect the team's operation.

The aim is not to collect the largest possible set of fields. It is to shorten the path from a received order to a confirmed delivery. Before configuration, we agree which information is mandatory, who may alter a task and what evidence is sufficient to close it.

• Order entry, status and responsible user.
• Routes, stop sequence and subsequent changes.
• A dispatch workspace for the day's operation.
• A driver PWA for tasks and delivery confirmation.
• Fleet and warehouse data linked to orders.
• Tracking, reporting and agreed data exports.

We begin with a typical order and follow it from receipt to completion. This reveals the user roles, decision points and information that has to be retained. The first release is limited to what that workflow genuinely needs. Rare exceptions and convenience features can wait until the core work has become familiar.

User permissions, statuses and starting data are then prepared. A pilot checks more than whether the controls work. We watch whether a dispatcher can find the next action without an extra explanation, whether the driver receives enough detail and whether delivery information returns to the place where the office expects it.

The go-live date is agreed with the people responsible and set against the real operating calendar. The team knows where to record an incident and who decides on a requested change. Integrations and historical migration are assessed separately because their effort depends on third-party interfaces and the quality of the source data.

We design reports from operational questions. Which deliveries are still open? On which route does the same delay keep appearing? Who owns the next action? If a field answers no decision question and is not required for a record, it is worth asking whether the team should capture it at all.

Management needs an overall view, dispatch needs the position now, and a driver needs the current task. Access and screens are therefore set by role. Convenience for one group should not create more administration for another. Rita Grid is useful when its information prompts a timely action, not simply when it has been stored.