Technician reviewing Minuteman floor scrubber documentation
One record from identification to follow-up

Minuteman support starts with the machine, the route, and the evidence

Use this roadmap to identify equipment, locate current documentation, prepare a reproducible issue record, coordinate service, and confirm the machine has returned to its defined operating condition.

Follow the Support Roadmap
Six-stage route

Keep each support step attached to a verifiable record

A support conversation moves faster when machine identity, operating conditions, observations, and prior actions are stated separately.

  1. 01

    Identify

    Record model designation, serial identifier, installed options, battery or power configuration, attachments, and the current brush, pad, squeegee, filter, or broom setup.

  2. 02

    Locate

    Retrieve the model-specific operating manual, current data sheet, safety information, parts reference, warranty terms, and applicable technical bulletins. Avoid substituting a similar model's document.

  3. 03

    Observe

    State when the symptom occurs, which route segment exposes it, what the operator sees or hears, and whether the condition changes with turns, pressure, speed, load, temperature, or component condition.

  4. 04

    Isolate

    Follow only authorized checks from current documentation. Record each changed variable and result. Do not bypass guards, interlocks, site procedures, or qualified-service requirements.

  5. 05

    Coordinate

    Send the identity record, issue description, environment, maintenance history, observations, permitted checks, photos where appropriate, and the operational consequence to the support contact.

  6. 06

    Confirm

    Document the completed action, replacement parts, configuration, test boundary, return-to-service result, operator notice, and any revised inspection or maintenance interval.

Evidence tools

Four compact records cover most support handoffs

1 record

Machine identity card

Model, serial, configuration, options, power system, consumables, attachments, and document revision references. This prevents advice for the wrong configuration.

1 route

Operating context sheet

Floor, soil, debris, slope, turns, access, operating window, water, power, storage, and operator. The symptom is tied to the conditions under which it appears.

3 times

Condition timeline

Note the last known normal operation, first observed change, and current state. Add maintenance, component replacements, impacts, and changes in chemistry or method.

2 states

Before-and-after check

Use the same test boundary and method before and after authorized action. Compare observation, not memory, and retain the result with the machine record.

Safety and evidence boundary

Support information on this page is organizational guidance, not a repair instruction. Stop operation when site procedure, the operating manual, a warning indicator, damaged electrical components, loss of control, abnormal heat, fluid leakage, or another unsafe condition requires it. Troubleshooting, adjustment, disassembly, electrical work, and return-to-service decisions must follow current product documentation and qualified-service requirements.

Shared responsibility

Route the right evidence to the right role

OP

Operator

Records pre-use condition, controls, route symptoms, warnings, cleanup, and shutdown. The operator does not replace authorized diagnosis with an improvised workaround.

SV

Supervisor

Confirms the route, operating method, training, site procedure, downtime consequence, and whether conditions changed. The supervisor preserves comparable test conditions.

MT

Maintenance

Checks permitted service items, maintenance history, component condition, and completed actions using model-specific documentation. Work and parts are recorded against machine identity.

SP

Support contact

Receives the structured brief, identifies missing evidence, routes the request, and clarifies which next step requires product documentation, parts support, or qualified service.

6roadmap stages
4responsible roles
1machine identity record
1repeatable return check

These counts describe the support method, not product performance. Actual service availability, documentation, warranty coverage, parts, and response paths depend on model, serial, region, and current terms.

Attach the facts before the question

Open a structured Minuteman support brief

Include machine identity, route context, first observed change, current condition, maintenance history, authorized checks already completed, and the operational consequence.