Import an external job

Follow this guide to create one internal job from a normalised provider record. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

What you’ll accomplish

Create one internal job from a normalised provider record. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.

Follow these steps

1. Check the external record and provider.
2. Verify no internal job already has the provider/external ID.
3. Select Import.
4. Go to the new internal job.
5. Check source, external reference, addresses, receiver, commercial fields and payload hash.
6. Complete missing required data before dispatch.

Fields and options to review

This action uses the values already stored on the selected source record. Review that record before continuing.

Rules the system enforces

• Duplicate provider/external ID combinations are protected.
• The saved payload hash supports change/evidence comparison.
• Imported data must still satisfy local dispatch rules.

How to confirm it worked

• The source record, status/history and any downstream notification, provider, POD or finance record should agree after the action.

Security, audit and operational checks

• Use the exact record and least-privilege role before changing any state.
• Verify the saved record after every action; a browser message alone is not evidence that every downstream step completed.
• Use protected document and image routes rather than exposing server filesystem paths.
• Keep customer, driver, provider, financial and credential data within the authorised workflow.
• For provider, finance, employment, transport and compliance decisions, follow the organisation’s authorised professional process.

Continue with related guidance