Field note ·
What a specification-support service should actually deliver
Buying machinery from a distance is not a purchasing problem, it is a translation problem. A specification-support service is worth paying for only if it produces documents you can hold a supplier to - not reassurance.

The gap between a requirement and a specification
A buyer knows what the plant needs: throughput, product range, floor space, labour available, budget. A supplier sells a machine defined by its own standard. Between those two descriptions there is a gap, and every unclosed part of it becomes a variation or a concession later.
Specification support exists to close that gap in writing before money moves. The deliverable is not advice; it is a document set - a functional specification with measurable values, a supplier questionnaire, a comparison matrix, an acceptance plan and a handover checklist. If a service produces a pleasant conversation and a recommendation, it has produced nothing that can survive a dispute.
The test is simple: could a third party, reading only the documents, hold the supplier to the result? If not, the documents are marketing.
A functional specification with numbers in it
The specification should describe what the machine must do in the plant's terms: rate with the real product mix, accuracy measured on a sample, changeover time for a defined change, availability over a defined period, noise at the operator position, and the services it may draw.
Each requirement needs a value, a tolerance, a measurement method and a moment of verification. 'High throughput' is not a requirement; '1,200 items per hour at a stated mix, measured over a 30-minute run at acceptance' is one. The measurement method matters as much as the number, because it decides who wins the argument at FAT.
The specification should also state what is excluded. Site preparation, utilities, foundations, local labour, downstream handling - each exclusion is a cost that will otherwise appear later wearing a different name.
Supplier qualification that goes beyond the certificate
A quality certificate proves a system exists. It does not prove the supplier can build your machine. The useful qualification asks for: a comparable project reference with a contact, the last acceptance report from that project, the engineering team's size and structure, the standard they design to, and the sub-suppliers they intend to use for controls, drives and safety components.
A site visit on a running job is worth more than an audit on a quiet Friday. Look at the machine, the documentation posted on it, the state of the assembly area, and the answers the operators give when asked how often it stops.
The output of qualification is a shortlist with reasons, not a ranking with scores. Scores hide judgement; reasons can be argued with, which is what a buyer needs.
FAT, SAT and the documents that travel
Factory acceptance is run against the specification, on the buyer's parts if possible, with the measurement methods agreed in advance. The output is a report with measured values, signed by both parties, plus a punch list classified by severity.
Site acceptance proves the machine in the plant: with the plant's services, the plant's operators, the plant's product and the plant's interfaces. It is the moment when the installation quality, the foundations, the power quality and the network all get tested together, and it is usually where the surprises are.
The document pack at handover is the asset that keeps paying: as-built drawings, IO schedule, risk assessment, FAT and SAT reports, spare parts BOM with manufacturer numbers, commissioning parameters, training records and the warranty terms with their start date.
The commercial structure that protects both sides
Payment milestones tied to documents rather than dates. A deposit at order, a payment at drawing approval, a payment at FAT, a payment at installation complete, and a balance at handover with retention released after a defined re-test period. That structure makes each stage meaningful.
Variations should be priced before they are executed, in writing. A supplier who starts work on a verbal change is a supplier who will invoice at the end, at the point of maximum leverage.
Warranty terms should define what is covered, what is excluded, the response time, the remedy (repair, replace or credit) and the start date. The most common dispute is not about coverage but about the start date and the response time.
Where the service stops
A specification service should not take responsibility for the supplier's design, the plant's structural capacity or the buyer's production plan. It should make those decisions visible and put them in front of the person who owns them.
The line we hold is that we specify, we compare, we witness and we record. We do not replace the buyer's engineer of record, and we do not sign for the supplier. A service that blurs that line is a service that will be blamed for something it did not control.
The scope we actually deliver across specification, supplier qualification, build supervision, acceptance and after-sales is described on our services page, stage by stage.
How to judge a specification service in one meeting
Ask for a sample specification from a previous project with the commercial details removed, and read the acceptance section first. If it has numbers, methods and a verification moment, the service is real. If it has adjectives, it is not.
Ask what happens when the FAT fails. A service with a defined remedy, a re-test procedure and a cost allocation has done this before. A service that says it will be resolved between the parties has not.
Three examples of the gap, and what each costs
Example one: a conveyor specified without a gap requirement. The line runs, the sorter diverts miss, and the supplier says the gap was never specified. The cost is a rework of the induction and a period of reduced rate.
Example two: a machine specified without a changeover time. The machine meets its rate in a single product and loses an hour per changeover in a high-mix plant. The cost is either a second machine or a permanent overtime line.
Example three: an acceptance specified without a measurement method. The machine passes on the supplier's method and fails on the buyer's, and the argument is about the method rather than the result. The cost is a delay, a re-test and a relationship.
All three gaps are closed by one paragraph each in the specification. That is the entire commercial case for specification support, and it is why the service should be judged by the documents it produces rather than by the meetings it attends.
What the buyer must still own
The buyer owns the production plan, the site, the utilities, the structural capacity of the building and the decision about risk. A specification service can make each of those visible and can put a number against them, but it cannot take the decision.
The buyer also owns the acceptance signature. A consultant who signs for the buyer has taken responsibility without authority, and the resulting document is worth less than one signed by the person who will live with the machine.
Being explicit about that boundary at the start is what keeps a specification engagement useful. A service that drifts into signing for everything becomes a scapegoat, and a service that drifts into advising on production strategy becomes expensive entertainment.
How the documents travel through a project
The functional specification is written first and becomes the enquiry document. The supplier questionnaire is issued with it and returns as part of the quotation. The comparison matrix is built from the returns, and the acceptance plan is written from the specification once the supplier is selected.
Each document is reused rather than rewritten: the acceptance plan is the specification turned into tests, and the handover checklist is the acceptance plan turned into a closing list. A project that writes four different descriptions of the same machine has four chances to be inconsistent.
The practical benefit is speed. A buyer with a specification, a questionnaire and a matrix can evaluate four suppliers in two days rather than two weeks, because every return is answering the same questions in the same order.
The one page that should sit on top
Every specification pack should open with a single page: the decision, the rate, the mix, the environment, the budget, the acceptance date and the owner. That page is what a director reads, and it is what keeps the project honest when the details get interesting.
If the one page cannot be written, the project is not ready to go to market. That is a useful gate, and it is cheaper than discovering the same thing after three quotations have been prepared against three different interpretations.
What to check
- Every requirement needs a value, a tolerance, a measurement method and a verification moment.
- State exclusions explicitly: site prep, utilities, foundations, local labour.
- Qualify on a running job, with the last acceptance report, not on a certificate.
- Tie payments to documents, not to calendar dates.
- Handover pack: drawings, IO schedule, risk assessment, FAT/SAT, BOM, parameters, training.