Reports & planning

Using the roadmap and requesting improvements

The Roadmap is a private place for planned work, ideas and dealership requests. It helps keep feature discussions separate from operational job notes.

In this guide Follow the steps below in order. You can return to this page at any time.
The Roadmap is a private place for planned work, ideas and dealership requests. It helps keep feature discussions separate from operational job notes.

Before adding a request


Describe the problem the user is trying to solve, not only the button they want. Include who needs it, how often the problem occurs and what the current workaround is.

Write a useful request


A strong request might say: “Service advisers need to record a courtesy-car number on Workshop bookings because it is currently written on paper and is often missed.” This is clearer than “add another box”.

Status and priority


Roadmap statuses show whether an idea is being reviewed, planned, in progress, testing or completed. Priority should reflect business impact, safety, repeated manual work and the number of dealerships affected.

Comments and evidence


Add examples, screenshots or anonymised details where they help explain the request. Do not include real customer personal information.

Feature availability


A roadmap item is not a promise of a delivery date. New features need scope, security checks, testing and compatibility with hosted and self-hosted installations.
Open the demo Browse all guides