Submitted edits will appear in the Overrides List, which can be opened via the toolbar at the top of the MapExact screen.

For every corporate account, edits from each user’s Group will be visible. Company Admins will be able to see all edits across the account by default. Approver and User roles will only be able to see the Group(s) to which they are assigned. When querying the edits, each edit will be searchable through a number of parameters. These parameters are:

  • - Username
  • - Status
  • - Country
  • - Date Range

The edits can be grouped by the following criteria:

  • - Status
  • - Country
  • - Submitted By
  • - Group
  • - Approver

There is the capability of declining an edit, if it was created in error or no longer valid. Only edits with the status of Submitted and Accepted can be integrated with CoPilot or PC*MILER Web and Web Services. 

All edits have the status of For Review once created through MapExact. Approvers and Company Admins can then verify the edits and change the status to one of the following categories:

  • Accepted - Edits that have been accepted as an override
  • Declined - Edits that have been rejected

Edit Verification

When an edit has been submitted, it should be reviewed before it is approved and pushed out to devices with CoPilot. Depending on the distribution and structure of Approvers, this is usually done in one of two ways: 

  1. A central approval team, where all requests are verified by one Approver or Department.
  2. Local area approval, where many different Approvers can approve edits based on local knowledge and direct interaction with drivers.

Through the use of Groups, an Approvers structure can be set up in such a way that either of these methods can be managed.

There are a number of resources available to verify if a submitted edit is correct. Within MapExact, you are able to toggle between the road map view and satellite view. A good source of address validation is usually local postal services, for instance: 

  1. Royal Mail, British Postal Service (
  2. Deutsche Post, German Postal Service, (
  3. USPS, United States Postal Service, (
  4. La Poste, French postal service, (

Once an edit has been verified, the Approver or Company Admin should then approve or decline the edit. The User that made the last modification and a timestamp will be logged.

To ensure edits are verified correctly and independently, the user that submits the edit should always be different from the user that approves the edit.

Example Edit Process 

The diagram above shows a process for the reporting of edits before they are pushed out to devices. It is likely that Drivers and users of CoPilot in the field will suggest edits to the map data. For the purposes of this example, the roles have been split into three—the driver (end user of CoPilot); the MapExact User; and MapExact Approver.

In some instances, however, the roles may be the same person. When this is the case, the steps to submit and verify the edits should remain unchanged..

Once an edit has been identified, the first step should be to check the current data for that road segment in MapExact. In some cases, verifying the actual road address may highlight how information should be passed to CoPilot, and an edit may not always be required.

If an edit is required, it should then be submitted for verification. The verification of an edit is a key stage within this process. Once committed and pushed out to devices, the edits will take effect. Only edits that can be verified should be approved.