Skip to content
Guides

Practical guides, kept clear

Understand what makes a useful brief, how to check compatibility and what to do when your documents arrive. Clear guidance, ready when you need it.

Fast to scan
Clear next steps
Built around real journeys
Featured guides

Start with the guide that fits

Read the guidance below to prepare your requirements and understand the scope of your document service.

Quick routes

Need an answer or document right now?

Jump straight to the FAQs, existing document retrieval or the help centre when you need a specific answer.

FAQs

Browse clear answers on scope, compatibility, delivery and revisions.

Existing documents

Use the existing customer retrieval journey to access previously issued documents.

Help & Support

Go straight to support if you are stuck or need guidance.

Helpful routes built around real journeys
Read the document and its limitations carefully
Confirm what is included before ordering
READ / 01

A clear brief helps establish whether the service matches your task.

Before you request a document

Start with the purpose: what do you need to understand, configure or record? Describe the intended outcome and any information you already have. An example document can help explain the format you want, but should not be assumed to apply to a different vehicle.

Record the relevant vehicle specification, installed equipment and software version where known. If something is uncertain, say so rather than guessing. Agree the deliverables, prerequisites, format, delivery timing and included revisions before placing an order.

READ / 02

Similar vehicles can have different configurations. Check the scope of the document itself.

Reading compatibility information

Look for the vehicle variant, equipment identifiers and software version to which the information applies. Compare them with the details supplied for your enquiry. A matching model name alone is not enough to establish suitability.

Pay attention to prerequisites, limitations and version notes. If the information does not match your setup, pause and ask for clarification. Do not treat general reference information as confirmation that a change is appropriate for your vehicle.

READ / 03

Keep the delivery message, the document and its reference together.

Receiving and keeping digital documents

Provide a valid, accessible email address or another agreed digital destination. Delivery can be an attachment, PDF, secure download link, customer-specific document link or another agreed electronic method. The order determines which method is used.

Check your inbox and junk folder, then confirm you can open the file. Retain the document name, version and order reference. If access fails, describe the error to support; do not post customer-specific links publicly.

READ / 04

Make the requested change easy to identify.

Requesting a correction or revision

Include the order reference, document name and version, the relevant section and a description of what appears incorrect. Provide the correct detail if known. For a delivery issue, say whether the message, link or file is the problem.

A correction and a new requirement are not always the same thing. A different vehicle, software version or task may change the scope. Ask which revisions or updates are included in your order and whether new work needs to be agreed.

READ / 05

The collection operator determines what it will accept.

Preparing documents for vehicle collection

Request the current requirements directly from the pound or collection operator before making arrangements. Keep the request and any reference numbers together, and establish who may collect the vehicle and which original records are required.

Coverza can discuss supporting documents and explanatory notes within an agreed scope. These do not replace official records, establish ownership, provide motor insurance or guarantee release. Confirm acceptance with the operator rather than assuming a document will be sufficient.