A one-page project brief is the difference between a supplier who quotes against your actual duty and one who quotes against an assumption. If you have ever watched a design freeze drift because nobody wrote down who inspects the part, or why the tolerance sits at ±0.05 mm rather than ±0.2 mm, you already know what a thin brief costs. Before you send your enquiry to a contract manufacturer, make sure the brief answers the questions their mechanical engineers will ask on the first call.
What the brief is for
The brief is not a specification. It is a decision record for the people who have to make trade-offs on your behalf. A supplier reading it should understand what the mechanism has to do, what it must never do, how it will be judged as acceptable, and what happens when something has to give.
Put three things at the top, before any geometry. First, the duty statement: what moves, what it carries, and where it operates. Second, the interface list: what your assembly bolts to, plugs into, or is handled by. Third, the success test: the exact acceptance test you will run when the first units arrive. Everything else in the document supports those three.
A useful self-check before you send it: hand the brief to someone in your own plant who has never touched the project. If they cannot tell you what the acceptance test is after one reading, a supplier's engineering team will not do better.
Operating conditions in numbers, not adjectives
Adjectives are where misunderstandings start. "Heavy duty", "frequent use" and "harsh environment" mean different things to different factories. Replace each adjective with a number, and mark anything you are unsure of as an assumption so the supplier can challenge it instead of designing around it.
- Duty cycle: cycles per shift, shifts per day, expected service life in years or cycles.
- Loads and forces: payload mass, where the load sits relative to the support, and any shock or impact condition.
- Speed and stroke: required travel, actuation time, and whether motion is continuous or indexed.
- Environment: temperature range, humidity, dust and water exposure, washdown, and any chemical the surfaces must survive.
- Power and utilities: available voltage and phase, compressed-air pressure, water supply, and what the machine must do on a power loss.
- Operator interface: who operates it, their training level, expected reach and handling effort, and whether it runs unattended.
If you have an existing machine doing this job, describe it honestly — what works, what fails, and how often maintenance intervenes. A documented failure mode is worth more than a list of wishes, because it tells the designer which wear item to redesign first.
Interfaces, envelopes and tolerances
Mechanical work fails at interfaces more often than in the middle of a part. Draw the fixed boundary conditions first: the floor, wall, conveyor, frame or upstream machine your design must connect to, with their dimensions, fixing points and any level or flatness requirement.
- Give a rigid envelope in three axes — the maximum space the assembly may occupy, including service access and door swing.
- State datum faces: which surfaces are referenced by the next assembly step, and which are free.
- Separate functional tolerances from cosmetic ones, and say which ones you would relax to save cost.
- List every purchased input you are fixing: standard profiles, existing fasteners, motors or actuators you already own or must reuse.
For anything that will be cleaned, washed down or exposed to water, say so explicitly. Water and cleaning chemistry drive material choice, sealing, drainage and fastener selection, and changing them after the design freezes is expensive. Our cleaning equipment series covers equipment built for that kind of duty, and the specification pages show how such machines are documented — voltage, tank and supply arrangements, steam or hot-water mode, and protection features. Write your cleaning duty in the same style: not "easy to clean", but what is cleaned, how often, with what media, and by whom.
Materials, finishes and what must be avoided
Give constraints, not preferred part numbers, unless a part is genuinely fixed. State the requirement and let the supplier propose the material — they will often find a cheaper one that meets it.
- Corrosion and contact rules: contact with food, drinking water, medical use, or skin contact, and any regulation the buyer must satisfy.
- Wear pairing: which surfaces rub, slide or impact, and the expected replacement interval for those parts.
- Prohibited materials and processes, including anything your downstream process cannot tolerate such as silicone, zinc plating, or lubricants of a given class.
- Finish requirements that matter functionally: cleanliness, surface energy, reflectivity, or appearance grade.
- Service expectation: which parts the customer is expected to replace on site, and with what tools.
A prohibited-materials line saves more money than any tolerance change on the drawing. Factories default to what they stock, and a blanket statement like "no material containing silicone in the wetted path" removes weeks of back-and-forth.
Production volumes, cost target and lead time
Volume decides process. A part that is machined at ten pieces per month is often stamped, cast or welded at one thousand. Give a first-order quantity, a steady-state annual figure, and any known ramp so the design does not over-invest in tooling for a low-volume run or under-invest in fixtures for a high one.
Name a cost target even if it is approximate. It tells the supplier which trade-offs to propose rather than which to hide. If the sample you are replacing costs more than the programme allows, say so and list the features you are willing to drop.
Then write the date-driven facts: when the design must be frozen, when you need first articles, when the line must accept production units, and who signs each gate. A supplier who knows the gate dates can tell you early which of them are at risk; one who does not will simply quote the safest, slowest route.
Verification, documentation and handover
State what you will accept as proof. For an assembly that moves, that is usually a bench run under representative load plus a repeated-cycle check. For something exposed to water or cleaning media, it is a wet-cycle or washdown test on the real enclosure. Specify who supplies the test rig, where the test happens, and what data you expect back.
- Model format and whether you need the drawings dimensioned and toleranced, or a supplier-built detail.
- Bill of materials with make and part number for every purchased item, plus lead time and second-source rules.
- Assembly and torque instructions, and the consumables and lubricants the assembly requires.
- Change-control route: how a design change is proposed, approved and re-verified once parts are running.
The documentation list is also your procurement protection. A bill of materials with real part numbers means you can re-order, re-quote and re-build without depending on a single supplier, and it makes the next revision cheap instead of a restart.
What to include with the brief
Attach the supporting artefacts so the engineering team does not have to ask for them one by one: photographs of the current setup from several angles, a rough dimensioned sketch or existing drawing, the datasheet of any interfacing product, the acceptance test you intend to run, and the contact who can answer technical questions within a working day. A single named technical contact shortens a design cycle more than any document.
If the project needs equipment designed rather than built to a drawing you already hold, send the same brief to a supplier with engineering capability. Engineering services at Shenzhen PowerDe Automation Precision Equipment start from exactly this kind of brief: duty, interfaces, environment, volume and acceptance criteria, then product development, hardware testing and manufacturing automation behind it. If your application is cleaning or washdown related, describe the cleaning duty as precisely as the mechanical duty — media, temperature, frequency and access are the parameters that decide the design.
Before you press send
Read the brief once more against three questions. Is every requirement measurable? Is every assumption labelled as an assumption? Is the acceptance test written so that two people could run it and agree on the result? If the answer to any of these is no, fix that line — it will cost you one hour now and a prototype round later.
Keep the document short enough that your own team will read it, and version it like a drawing. A brief that is updated whenever a decision changes becomes the reference for the programme rather than a one-off attachment to an enquiry.
