1. Start from the workload, not from the machine
Write the requirement as a job to be done: what is cleaned, coated, bonded, assembled or tested; how many units per hour; on which shift pattern; by how many operators. For a cleaning application in the PowerDe cleaning equipment range, that sentence might be "wash and degrease the exterior of 20 light commercial vehicles per day in a covered bay with a single operator and a tap-water supply". Numbers like these make later arguments short. Adjectives like "efficient" or "heavy duty" make them long.
2. Turn each requirement into a measured test
Every requirement should have a matching test method, a pass value and a witness. A useful structure has four columns:
- Requirement — for example, steam temperature at the nozzle.
- Method — measured with a calibrated probe, at a stated position, after a stated warm-up.
- Pass value — a figure the supplier signs, not a range quoted from a brochure.
- Witness — who is present, what is recorded, and where the record is kept.
If a value cannot be measured, it does not belong in the criteria. Where the parties disagree on a figure, hold the acceptance to the measured value rather than negotiating the wording.
3. Separate prototype, pilot and production acceptance
For R&D-stage work, define what the prototype must prove and what it is allowed to fail at: a first unit may be accepted on function while its cycle time is still being optimized. For a pilot run, require continuous operation over a realistic period, at the target rate, using the buyer's own materials or soiling conditions. For series supply, add repeat runs across the number of units to be delivered. Splitting the stages prevents one dispute at the end of the project from blocking the value already delivered.
4. Put the interface requirements in the criteria, not in the notes
Most post-delivery friction comes from utilities and interfaces that nobody tested: available supply voltage and socket type, water source and inlet connection, drainage, floor space, door width, and the floor the machine must pass through. State the buyer's site conditions in the criteria and require the supplier to confirm compatibility in writing. PowerDe's mobile cleaning machines are built for indoor garages and narrow parking areas, which is exactly the kind of constraint that should be recorded as a site condition and then verified on delivery.
5. Define the documentation package as a deliverable
Acceptance should include paperwork: an as-built specification showing the values actually measured, an operation and maintenance manual in the language the operators read, a wiring and plumbing diagram, a spare-parts and consumables list with recommended intervals, and the test report from the acceptance run itself. Buyers who treat documentation as optional usually end up unable to hold the supplier to anything after the warranty period.
6. Agree the handling of exceptions and change
Two clauses save projects: what happens when a criterion cannot be met — retest, remedy, price reduction or rejection — and what happens when the buyer changes the requirement mid-project. Price the change process. R&D schedules slip when an undocumented change reaches the workshop floor, and an agreed change-control step is what keeps a team-based engineering engagement moving instead of renegotiating the whole scope.
