A procurement-grade framework for moving from a workplace problem to a defensible exoskeleton shortlist — without letting a demo decide for you.
ExoSelect researchContinue reading
Editorial QA
Checked for sourced parameters, internal links and prohibited claims.
Quick answer. A procurement-grade framework for moving from a workplace problem to a defensible exoskeleton shortlist — without letting a demo decide for you.
Exoskeleton procurement fails in a predictable way: a team sees a device lift a heavy box, buys a pilot fleet, then discovers that the real task is a 40-second overhead reach performed 300 times a shift. The technology may be sound. The selection process was not.
This guide sets out a repeatable sequence for buyers: define the task, quantify the exposure, shortlist by architecture, verify the data, then design the pilot. It is written for operations, EHS and procurement teams who need a decision that survives an audit.
An exoskeleton is an intervention on a biomechanical exposure. Before looking at products, describe the work in measurable terms: joint angles, load weight, repetition rate, duration, reach height, terrain and clothing. A back-assist exosuit and a full-body powered frame solve different problems, and neither replaces task redesign.
Passive systems use springs, elastics or mechanical structures. They are lighter, need no charging and are easier to deploy at scale. Active systems add actuators and control software, which can deliver larger assistance but introduce battery, service and training overhead. Hybrid designs sit between the two.
For a first programme, the decisive question is not “which is strongest?” but “which architecture fits the task and the shift?”. A 1.2 kg passive back exosuit may outperform a powered system simply because workers keep it on.
Demand a parameter-level data sheet. Weight, assistance profile, runtime, user limits, certifications and warranty should be stated explicitly. Where a value is missing, record it as missing. Do not accept a similar model's number as a proxy. Our product index marks every parameter as known, not disclosed, unknown or not applicable for exactly this reason.
Check the certification claim against the intended use. A CE mark for machinery does not automatically cover a medical claim, and a medical certificate does not cover a workplace lifting claim. Ask for the declaration of conformity, the applicable standards and the notified body where relevant.
A useful pilot defines success before it starts: task completion, perceived exertion, wear time, discomfort, change in lifting technique and adverse events. Run it long enough to see novelty effects fade — typically four to six weeks. Include workers who are sceptical, not only volunteers.
Measure wear time honestly. If the device is left in a locker after two hours, the ergonomic case collapses regardless of the assistance rating. Fit, donning time, heat and freedom of movement are adoption variables, not soft factors.
Add training, fitting, replacement parts, cleaning, charging infrastructure, service contracts and the cost of managing a mixed fleet. For subscription models, model the exit cost. For capital purchases, ask about the expected service life and spare-parts availability.
A defensible decision records the assumptions. Use a side-by-side comparison for the shortlist, then ask each maker the same questions in writing. The fastest way to expose a weak dossier is to request the source behind each number.
Before a pilot, request: the technical file summary, the declaration of conformity, the user manual, the maintenance schedule and a named reference site. If any document cannot be produced, that is a finding. It belongs in the evaluation, not in a follow-up email.
When the shortlist is ready, send us the brief. We will map the requirement against the index and flag the gaps before you commit to a trial.
An exoskeleton analysis is only useful if it changes what a buyer does next. The purpose of a dossier is not to declare a winner in the abstract, but to make the next conversation more specific: which task, which users, which environment, which constraints and which evidence is still missing.
The first step is to translate the task into a written requirement. Describe the posture, load, repetition, duration, reach height, floor surface and clothing. Add the practical constraints that decide adoption: donning time, heat, tool clearance, cleaning and storage. A system that performs well in a demonstration but interferes with the actual workflow will not be worn after the pilot team leaves.
The second step is to separate the system from the deployment. A device can be well engineered and still fail because the service network is thin, the training is inadequate or the spare-parts lead time is measured in months. Ask for the service model in writing, including response time, replacement units and the cost of consumables.
Data quality should be scored explicitly. A dossier that publishes weight, runtime, user limits and certification scope is easier to pilot than one that leaves those values unknown. Missing values are not automatically disqualifying, but they are a cost: someone has to resolve them before a purchase order, and that work belongs in the project plan.
Use the product index to narrow the field by category, drive type, weight, runtime and region. Treat the filters as a way to structure the question, not as a substitute for reading the parameter states. A system that disappears from a weight band because its weight is not disclosed is telling you something about the dossier.
Place the shortlisted systems side by side in the comparison tool and focus on the rows where they diverge. Differences are useful; similarities are useful too. If two systems are identical on the parameters that matter, the decision may turn on service, fit or commercial terms rather than engineering.
Check the manufacturer profile for verification level, product line and company documentation. A maker with a clear primary source for each claim is easier to audit than one whose brochure is the only available reference. Where a claim matters to safety, ask for the declaration of conformity and the technical file summary.
Finally, write the brief. Include the task, environment, user profile, deployment volume, region and budget range. A good brief lets the research desk separate sourced values from open questions, so the next conversation starts with evidence rather than a demonstration.
Training is part of the system, not an afterthought. Ask who delivers the first session, how competency is assessed and what happens when a new operator joins the team. A device that requires a specialist to fit it every morning has a different operating cost from one that a trained supervisor can deploy independently.
Keep a decision log beside the shortlist. Record what was verified, what was assumed and who owns each open question. When the recommendation goes to a capital committee, the log is often more persuasive than another product demonstration because it shows exactly which risks have been retired.
Send the requirement when the shortlist is ready. The response should make the gaps visible, not hide them behind a polished recommendation. That is the standard this index is built to support.
Start with the intended use, the certification scope and the service model. Those three items decide whether a system can be deployed, not just demonstrated.
No. Published parameters support shortlisting, but fit, comfort, training quality and local service response require a structured evaluation with the intended users.
Missing values are recorded as Unknown or Not disclosed and are never inferred from a similar product. Each dossier shows the date of the last update and links to its primary sources.
Editorial note
This analysis is based on published specifications and named sources. No first-party physical evaluation was performed.
Reviewed by the ExoSelect editorial desk
