Multi-location repair groups
Preserve the case when a vehicle, technician, or diagnostic escalation moves between locations. The next authorized user can see what has already been established and why the current step matters.
Enterprise guided diagnostics
Scale a consistent diagnostic method across teams and locations
STEP is building a guided diagnostic workspace for automotive organizations where difficult cases move across technicians, locations, departments, or repeat service events. It keeps vehicle context, applicable service information, working hypotheses, completed tests, actual results, repairs, and verification connected in one traceable case.
The goal is to standardize the method—not force every vehicle toward the same answer. Each authorized technician should be able to see what is known, what remains uncertain, why the diagnostic direction changed, and which evidence-based check should come next.
STEP is a working prototype preparing for staged early access. Enterprise pilots and availability will be scoped individually.
One diagnostic method
Evidence moves with the case
Location or team A
Context + confirmed evidence
Traceable case
Hypothesis + result + reason for change
Location or team B
Next evidence-based check
Diagnostic consistency
Diagnostic information can scale faster than diagnostic reasoning
Larger operations may already provide repair procedures, wiring diagrams, scan tools, training, and experienced support. The harder problem is preserving how that information was applied to the vehicle in front of the technician.
When cases cross employees, locations, departments, or repeat visits, the next person needs the diagnostic trail—not only the final repair line.
- the exact vehicle and reported concern
- confirmed observations and measurements
- applicable service information
- the working hypothesis being tested
- what has already been ruled out and why
- the next evidence-based check
- the repair supported by the recorded results
- verification of the original concern
A team can have access to the same information while still approaching the same diagnostic problem in disconnected ways.
One evidence standard
Standardize how evidence moves through the case—not the answer technicians must reach
STEP supports a repeatable diagnostic method while allowing the evidence from each vehicle to determine the direction.
- 01
Establish the case
Capture the vehicle, complaint, operating conditions, DTCs, recent work, available tools, and existing test results before selecting a direction.
- 02
Separate facts from assumptions
Keep customer-reported information, technician observations, measured results, and unresolved questions distinct.
- 03
Guide one testable step
Use the evidence to form or revise a working hypothesis and present the next check with its purpose, conditions, expected result, and requested evidence.
- 04
Preserve each direction change
Record the actual result and retain the earlier path when a measurement supports, narrows, or rejects the current hypothesis.
- 05
Verify the repair
Keep the case open until the repaired condition and the original symptom have been checked.
Protect completed diagnostic work
Protect the diagnostic work your organization has already performed
A difficult case represents completed labor, measurements, service-information research, and technician reasoning. When that work remains in personal notes, screenshots, or one technician’s memory, much of its value can be lost during a handoff.
STEP preserves that work as a usable case record so an authorized technician, lead diagnostician, or support team can understand what has been established and continue from the current evidence.
- preserve measurements and reasoning that would otherwise remain in personal notes or screenshots
- give an authorized lead diagnostician a clear view of where a difficult case stands
- help another technician continue without repeating the complete diagnostic process
- retain a readable record of what supported the repair decision
- continue intermittent and repeat cases from the earlier evidence
- apply the same method without treating every vehicle as the same problem
The value of each pilot should be evaluated against the organization’s existing handoff, escalation, repeat-case, and diagnostic review process.
Enterprise use cases
Built for organizations where diagnostic work crosses team boundaries
Fleet maintenance organizations
Keep vehicle-specific evidence, repairs, and post-repair verification connected across repeat service events within the organization.
Diagnostic and technical support teams
Review a structured case instead of reconstructing it from a short escalation note. See the measurements, unresolved questions, and current reasoning before recommending the next check.
Training programs
Teach a repeatable method: establish context, form a testable hypothesis, perform the correct check, record the result, revise the direction, and verify the repair.
Additional enterprise use case
Controlled rollout
Start with a defined diagnostic use case
Enterprise early access begins with a bounded pilot rather than an organization-wide deployment promise.
The pilot creates a shared definition of what is in scope, what STEP should preserve, and what evidence will determine whether the workflow should expand.
Request Enterprise Early AccessA pilot can define:
- participating team or location
- diagnostic work and vehicle coverage
- roles and access needed
- current handoff or escalation process
- evidence the organization needs to preserve
- onboarding and support boundaries
- criteria for evaluating whether the workflow should expand
Give each authorized user a defined role
Enterprise access will build on individual user accounts, organization-controlled roles, protected case access, and shared diagnostic records within the agreed pilot scope.
The current role model includes owner, admin, technician, and viewer. Exact permissions, administrative controls, account limits, identity requirements, and security expectations will be reviewed before pilot activation.
Configure the boundaries of the pilot
Pilot configuration may include:
- organization terminology
- participating teams
- escalation paths
- user roles
- supported vehicle scope
- required evidence
- case-review expectations
Configuration will not weaken vehicle applicability, test prerequisites, evidence status, source traceability, or repair verification. Broader workflow-building, API, integration, and customer-managed model capabilities are not part of the published enterprise offering.
Keep applicable service information connected to the active case
Repair-information platforms and manufacturer resources provide essential diagnostic procedures, DTC information, technical service bulletins, wiring diagrams, connector views, specifications, component locations, and service instructions.
STEP does not replace those sources. Its role is to connect authorized and applicable information to the active case, preserve the result of each check, and maintain a traceable path from the original concern to repair verification.
Vehicle-specific information is included only when available through authorized sources and supported vehicle coverage.
The technician remains in control of the final decision
STEP can organize evidence, form and revise working hypotheses, recommend the next relevant diagnostic check, and identify when recorded results support a repair.
The technician performs or supervises physical tests, confirms the required conditions, evaluates the vehicle in the actual working environment, and makes the final diagnostic and repair decision.
Read the Diagnostic MethodologyPreparing for enterprise early access
STEP is preparing for bounded enterprise pilots
STEP is currently a working prototype preparing for staged early access. Current development is focused on:
- one-step-at-a-time guided diagnostic cases
- source-linked service information
- validated vehicle and system coverage
- multi-user case continuity and handoffs
- organization roles and administrative controls
- repair and verification workflows
General enterprise availability has not been announced. Pilot participation will depend on product readiness, the organization’s diagnostic use case, required vehicle coverage, team structure, and agreed operating boundaries.
Initial interactive pilots are planned for late 2026, subject to product readiness.
Frequently asked questions
Questions about enterprise pilots
Is STEP available for enterprise deployment now?
STEP is preparing for staged early access and has not announced general enterprise availability. Pilot participation will depend on product readiness, supported vehicle coverage, team needs, and an agreed operating scope.
Which organizations is the Enterprise Pilot for?
The enterprise path is intended primarily for multi-location repair groups, fleet maintenance organizations, and diagnostic or technical support teams. Training programs are an additional use case. Individual technicians and small independent repair shops have separate paths.
Can multiple locations work in STEP?
Multi-user and organization-based access are part of the enterprise direction. The structure for locations, teams, permissions, and shared cases will be defined within the agreed pilot scope.
Which user roles are planned?
The current role model includes owner, admin, technician, and viewer. Exact permissions, administrative controls, and account limits will be reviewed before pilot activation.
Can STEP configure our diagnostic workflow?
Pilot configuration may include organization terminology, participating teams, escalation paths, user roles, supported vehicle scope, required evidence, and case-review expectations. Broader workflow-building, API, integration, and customer-managed model capabilities are not currently part of the published enterprise offering.
Does STEP support enterprise identity, security, compliance, or SLA requirements?
STEP does not currently publish general availability for SSO, SCIM, contractual SLA commitments, compliance certifications, configurable data residency, or enterprise audit exports. Organizations should include relevant identity, security, legal, procurement, data-handling, and support requirements in the early-access request. Those requirements will be reviewed before determining whether a bounded pilot is appropriate.
Does STEP replace our repair-information subscriptions?
No. STEP is not being built to replace ALLDATA, Mitchell 1, or manufacturer service information. It organizes the diagnostic workflow around the active vehicle, authorized applicable information, and evidence recorded by the technician.
Does STEP make the diagnosis for the technician?
STEP guides the process, develops evidence-based working hypotheses, recommends relevant checks, and may identify when recorded results support a repair. The technician performs or supervises the work, evaluates the physical evidence, and confirms the final diagnosis and repair decision.
Which vehicles will an enterprise pilot support?
Coverage is still being expanded and validated. Pilot coverage may differ from the public diagnostic library and will be defined before onboarding.
How much does an Enterprise Pilot cost?
The scope and pricing are custom. Commercial terms will depend on the participating organization, team, diagnostic use case, confirmed capabilities, vehicle coverage, onboarding requirements, and support boundaries.
What happens after an enterprise early-access request?
STEP collects contact details and optional information about the organization, diagnostic work, vehicle coverage, team structure, and requirements. Organizations whose needs match the available workflow may be contacted to discuss a bounded pilot.
Build a traceable diagnostic standard
Give every authorized team the evidence to continue the case
Request enterprise early access to discuss a controlled pilot for your locations, fleet, training program, or diagnostic operation.