Skip to main content
GullySystem
Automotive

Job Cards for Small engine and generator repair shops

Connect the received engine or equipment, accepted repair, parts history and actual test evidence before collection.

Field Service

Does this function belong in your operation?

Use for workshop-received portable generators, small engines and supported engine-powered equipment. Installed-system work and on-site electrical service are separate scopes; an accepted bench job does not authorise them.

The workshop accepts an identified or identity-pending asset for assessment within its declared repair scope.

Join the received equipment, separate engine identifiers, customer complaint and supplied accessories in one repair record. Track assessment, accepted work, actual parts and the tests performed. A component sent outside stays linked to its asset and custodian. Collection without repair, limited testing and a repeated complaint need explicit outcomes. A completed bill cannot establish technical readiness or prove all supplied items were returned.

Bring the records the workflow depends on.

  • Workshop asset label, equipment identity and separate engine identifiers where applicable
  • Customer symptom, visible condition and supplied accessories
  • Owner, commissioning customer, payer and authorised collector
  • Assessment scope, accepted repair revision and technical references
  • Parts issues, outside component handoffs and test evidence

Outputs to check

  • Asset-specific assessment and repair history
  • Accepted work, parts use and outside-handoff record
  • Test evidence with limits and reviewer decision
  • Collection and actual-work billing statement

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.

  1. 1. Receive and identify

    Record the actual machine and accessories presented. Keep equipment and engine identity distinct; flag unreadable details before selecting a technical reference or parts list.

  2. 2. Record assessment findings

    Separate customer-reported symptoms from the technician’s observations. Keep the initial assessment charge and any later repair proposal identifiable.

  3. 3. Confirm the accepted work

    Retain the customer buyer’s accepted revision or refusal. Technician allocation and technical suitability decisions remain separate from commercial consent.

  4. 4. Record work and components

    Link actual labour and parts used to the asset. A component sent to another specialist retains its identity, purpose and custody history while the remaining workshop job stays open.

  5. 5. Review actual tests

    Record tests performed, conditions, observations and limitations under the responsible technician’s method. Unavailable or unperformed checks must not become a generic passed result.

  6. 6. Hand back with the recorded outcome

    Confirm the authorised collector and returned items, including the agreed disposition of removed parts. Send actual accepted charges to accounts and retain unresolved findings beside the collection record.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Intake adviser

Maintains the asset label, supplied items and commissioning authority.

Repair technician

Owns findings, technical references and actual work entries within verified competence.

Parts and component custodian

Tracks issued parts and components sent outside, keeping customer property separate from workshop stock.

Technical completion reviewer

Records test conclusions and remaining limitations without treating an invoice or collection request as technical release.

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.

Equipment and engine references disagree

Retain both observed identifiers and obtain qualified clarification. Do not copy parts from a visually similar machine.

Customer declines the repair

Record the completed assessment, declined work and authorised collection outcome. Apply agreed charges separately; do not mark a repair complete.

Outside component has not returned

Keep its custody and technical dependency open. Return of another part does not complete the missing specialist work.

Required check cannot be performed

Record the unavailable facility, information or other limitation and the responsible next decision. Do not imply readiness for the customer’s installation.

Can this work independently?

The job can start from entered asset and customer records. Estimates retain accepted scope; stock records supply parts movements; invoices retain charges. Manufacturer documents and external specialist evidence need verified references. The system does not perform diagnosis or tests.

Systems and records it connects with

  • Estimate revisions: assessment and accepted repair lines.
  • Parts ledger: receipts, reservations, issues and returns.
  • External specialist record: component identity and custody.
  • Invoice and collection: actual charges, authorised recipient and returned items.

Configure, test and introduce the workflow.

  • Trace a portable generator and an engine-powered tool with separate equipment and engine identifiers.
  • Test missing identity, declined repair and a component sent outside.
  • Compare actual work, limited testing and collection records against the bill before adopting closure.

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.

  • Each asset keeps its own parts, approvals and test record.
  • Assessment, accepted repair and collection without repair are different outcomes.
  • Unperformed tests retain explicit reasons.
  • Technical review, collection and payment cannot be inferred from one completion flag.
Small engine and generator repair shops

How the business operates.

Two similar generators arrive at the counter, but one has a different engine and the other is missing a supplied lead. A workshop needs an identified asset and custody record before ordering parts or promising a repair. This scope covers workshop-received small engines, portable generators and supported engine-powered equipment such as pumps or garden tools. It follows assessment, accepted work, actual parts and recorded tests through collection. Large installed power systems, building connections and on-site work need separately confirmed capability and arrangements. The software records decisions; qualified people determine diagnosis, test methods and technical release.

Counter and asset intake

Identify the equipment and engine separately where required, with the customer’s symptom, supplied items and visible condition. Record the owner, person delivering the asset and payer. A missing nameplate requires an identity-review action rather than a guessed parts match.

Assessment and estimating

The technician records findings and proposed work within declared capability. Separate the initial assessment charge from further repair and replacement options. Any additional work discovered later needs a retained revision and the customer buyer’s decision.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Workshop asset identifier and customer ownership or custody reference
  • Equipment model and serial with separate engine model, type or code where applicable
  • Supplied accessories, condition and reported symptom
  • Assessment findings and accepted estimate revisions

Operational bottlenecks to check

A part fits the description but not the variant

Equipment and engine references can point to different parts lists. A supplier description or similar-looking component needs qualified fitment review before it becomes an accepted substitution.

The repair exceeds the telephone estimate

Preserve the original assessment basis and the later findings. Staff need to see what the customer accepted, declined or has not answered before continuing chargeable work.

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. 1. Identify and receive the asset

    Create a workshop reference and record equipment identity, supplied items and condition. Keep several machines from one account separate so parts and approvals cannot move between them unnoticed.

  2. 2. Assess within the accepted scope

    Record the technician’s findings and proposed work. Obtain missing identity or specialist information before selecting parts. Keep customer-reported symptoms distinct from faults actually established.

  3. 3. Agree the repair version

    Price labour, parts and any outside work with clear boundaries. Preserve partial acceptance or a decision to collect without repair; internal job allocation does not replace customer commercial consent.

  4. 4. Record parts and work

    Link issued and actually used parts to the asset, including a reviewed substitution. Track a component sent to another specialist with its identity and return evidence, without closing the whole repair.

  5. 5. Review test evidence

    Retain the tests performed and the responsible person’s conclusions. Mark unperformed or limited checks clearly. A new fault or unavailable test facility requires a recorded next decision, not a generic passed status.

  6. 6. Hand back and reconcile

    Confirm the authorised collector and supplied items returned. Explain unresolved findings through the technical handoff, bill the accepted work and keep any disputed line or pending payment traceable.

Industry reports to connect with

  • Assets awaiting identity clarification or customer decisions
  • Jobs blocked by specific parts or outside specialist work
  • Issued parts without matching use or return records
  • Tests outstanding and limited-test outcomes by asset

Questions before implementation.

When should small engine and generator repair shops consider job cards?

Use for workshop-received portable generators, small engines and supported engine-powered equipment. Installed-system work and on-site electrical service are separate scopes; an accepted bench job does not authorise them. The workshop accepts an identified or identity-pending asset for assessment within its declared repair scope.

What should we bring to the requirements discussion?

Bring anonymised examples of Workshop asset label, equipment identity and separate engine identifiers where applicable; Customer symptom, visible condition and supplied accessories; Owner, commissioning customer, payer and authorised collector; Assessment scope, accepted repair revision and technical references; Parts issues, outside component handoffs and test 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. Connect the received engine or equipment, accepted repair, parts history and actual test evidence before collection. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

This module does not give repair or electrical procedures, approve a replacement-engine conversion, certify output or establish safe site installation.

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. Each asset keeps its own parts, approvals and test record. Use this check when reviewing the first working version.

Talk to us

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

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. 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