Job Cards for Electric vehicle service centres
Keep an EV concern, qualified assessment, permitted work and actual outcome on a traceable vehicle job.
Does this function belong in your operation?
For fixed-site EV centres recording routine and permitted specialist work, including jobs ending in referral or unresolved assessment.
The centre accepts a vehicle for an assessment within its declared model and task scope.
An EV job needs a clear boundary between the customer’s symptom and the qualified technical finding. Record the model, accepted assessment scope and access dependencies before work allocation. Keep customer commercial consent separate from task authorisation, vehicle-readiness decisions and manufacturer responses. A charging complaint can end in a referral or unresolved finding. Preserve those outcomes alongside any component movement so closing a job cannot manufacture a completed repair.
Bring the records the workflow depends on.
- Vehicle and model identity, reported behaviour and relevant declared accessory history
- Centre capability, diagnostic-access reference and responsible technical owner
- Customer commercial acceptance, task-authorisation reference and actual work evidence
Outputs to check
- Vehicle assessment and work history
- Customer consent and separate technical-decision references
- Unit-change, unresolved-work and handback record
Follow the job cards workflow.
Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.
Who uses the module, and who approves?
Keep responsibilities distinct even when one person holds more than one role.
Decide how exceptions are handled.
These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.
Can this work independently?
Cards can use entered vehicle and assessment records. Qualified owners supply technical and readiness decisions; the customer accepts commercial scope. Manufacturer diagnostics, software access and claim systems require their own supported permissions. Training evidence and stock movements provide context, not automatic authority.
Systems and records it connects with
- Accepted estimate and revised customer scope.
- Training and task-authorisation references controlled by the qualified owner.
- Physical component handoffs, customer bill and separate manufacturer correspondence.
Configure, test and introduce the workflow.
- Trace a charging complaint and routine-work request through different capability reviews.
- Test missing access, an absent specialist and a referral outcome.
- Check that the handback record preserves technical findings without treating payment as readiness.
Check the result before rollout.
Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.
- Reported charging symptoms remain separate from assessed cause.
- Customer price approval cannot grant restricted-task permission.
- A referral or unresolved finding remains identifiable after an activity closes.
How the business operates.
An EV arrives with a charging complaint, but reception cannot decide whether the issue belongs to the vehicle, an accessory or another service provider. EV workshop software needs to preserve the reported concern, the qualified assessment and the centre’s actual scope before promising work. This profile covers fixed-site electric-vehicle service centres within their declared model and task capabilities. It separates routine work from restricted specialist tasks and tracks physical component identity where units are received or replaced. The proposed records support professional decisions; they do not make them.
The records that hold the operation together.
- Vehicle and model identity, customer concern and declared accessory history
- Centre capability check and diagnostic access reference
- Assessment findings with source, date and qualified decision owner
- Customer estimate acceptance distinct from technical work authority
Operational bottlenecks to check
A charging complaint is assigned to the wrong scope
An owner describes failure at a particular charger. Capture that context and the qualified finding without assuming the workshop must replace the vehicle battery or install building equipment.
The trained person is unavailable
A course entry remains on file but the authorised specialist is absent. Keep task permissions and actual allocation visible instead of treating another technician’s experience as equivalent.
How work flows across this business
This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.
1. Check the service boundary
Identify the vehicle and requested help before accepting an investigation. Record work outside the centre’s capability and the proposed referral.
2. Arrange qualified assessment
Assign the appropriately authorised person and record required external access. Missing diagnostic access is a dependency, not a reason to invent a diagnosis.
3. Separate technical and commercial decisions
Retain the qualified work decision and customer acceptance of the relevant charge. A warranty request is another decision and must not silently replace either.
4. Track work and component movement
Preserve actual work and identifiable unit changes. Refer newly discovered scope and any interrupted job to the authorised reviewer before continuing the applicable work.
5. Review release and unresolved questions
Record the responsible technical conclusion and the handback decision. A diagnostic report, course certificate or cleared bill is not independent proof of vehicle readiness.
6. Reconcile customer and external records
Bill accepted work and retain separate manufacturer or specialist outcomes. Keep the earlier complaint and component history available when the concern returns.
Industry reports to connect with
- Jobs awaiting qualified assessment, access or customer consent
- Restricted tasks awaiting the responsible authorisation decision
- Identifiable components with incomplete outside handoffs
- Customer-paid and manufacturer-pending work by job
Questions before implementation.
When should electric vehicle service centres consider job cards?
For fixed-site EV centres recording routine and permitted specialist work, including jobs ending in referral or unresolved assessment. The centre accepts a vehicle for an assessment within its declared model and task scope.
What should we bring to the requirements discussion?
Bring anonymised examples of Vehicle and model identity, reported behaviour and relevant declared accessory history; Centre capability, diagnostic-access reference and responsible technical owner; Customer commercial acceptance, task-authorisation reference and actual work evidence. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.
Does this replace our existing business software?
The starting point is your current system and the gap you need to close. Keep an EV concern, qualified assessment, permitted work and actual outcome on a traceable vehicle job. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.
What is outside this module?
No high-voltage, isolation, repair or safety procedure is prescribed. The record cannot certify competence, vehicle readiness or manufacturer approval.
How are scope, price and rollout decided?
The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Reported charging symptoms remain separate from assessed cause. Use this check when reviewing the first working version.
Related functions for electric vehicle service centres.
Discuss job cards for your business.
Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.
What happens after you share your requirements
- We review your brief and the systems you already use.
- We clarify the workflow, missing information and the work to consider first.
- The proposed scope sets out the deliverables, responsibilities and dependencies.
- Review the scope and commercial terms before deciding whether to proceed.
Start with your requirements
Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.
Share your requirements