Blog · · 6 min read

Hardware product requirements: the one-page spec that keeps a machine project on track

Before you build a machine, write one page: who uses it, what it must do in numbers, what it must never do, and how you will test it. A practical template with examples.

Most hardware projects do not fail because a part breaks. They fail because nobody wrote down what the thing was supposed to do. Three weeks in, the housing is too small for the battery, the motor is strong enough for a flat floor but not for a ramp, and everyone has a different picture of "portable".

A requirements list fixes this. It does not need to be a long document. For a first prototype, one page is enough, if the page contains the right things. This article shows what belongs on it, with examples you can copy.

Why one page, and why numbers

A requirement is a sentence that you can check. "The device should be light" cannot be checked. "The device weighs less than 1.5 kg including the battery" can. You put it on a scale, and you know.

This matters even more when an AI system helps with the design. A person may guess what you mean by "light" from the context. A design system will pick some value and continue. If the value is on the page, the 3D model, the electronics and the parts list all work towards the same target. If it is not, each step makes its own guess.

One page is a good limit because it forces you to choose. If everything is important, nothing is.

Part 1: who, where, and what for

Start with three short answers:

  • Who uses it? A hobby cook, a nurse, a maintenance worker with gloves. This decides button size, display, language and how much setup is acceptable.
  • Where does it live? Kitchen shelf, garden, workshop, vehicle. This decides temperature range, water, dust, vibration and sunlight.
  • What is the one job? One sentence. "Hold the temperature inside a charcoal grill at a set value for eight hours without attention."

That last sentence is the most valuable line on the page. When a design question comes up later, you hold it against this sentence.

Part 2: what it must do, in numbers

Now list the functions, each with a number and a unit. Five to ten lines are typical. Some examples:

  • Holds the set temperature within plus or minus 5 °C once it is stable.
  • Runs 12 hours on one battery charge.
  • Moves a 20 kg load up a 10 degree slope at walking speed.
  • Is ready to use 30 seconds after switching on.
  • Can be opened for cleaning without tools.

If you do not know a number yet, write your best estimate and mark it with a question mark. An estimate that can be corrected is far better than an empty line. Often the estimate is the first thing a feasibility check will test, and it is good to learn early that "12 hours" needs a battery twice as big as you imagined.

Part 3: limits

Limits are the frame around the design. They are often forgotten because they feel obvious to the person with the idea.

  • Size and weight. Largest outer dimensions, or the space it must fit into. "Fits through a 70 cm door." "Fits in a backpack."
  • Power. Mains, battery, USB, solar. Which voltage, which plug, which country.
  • Cost. A target for the parts of one unit, and how many units you expect: one, ten, or a thousand. The same product is designed very differently for each of these.
  • How it is made. If you only have a 3D printer and standard parts, say so. If sheet metal or machining is possible, say that.
  • Rules. Food contact, toys for children, mains voltage, radio. You do not need the full legal text, but naming the area early avoids expensive surprises.

Part 4: what it must never do

This part is short, and it is the one people skip. Ask: what is the worst thing this device could do, and what should happen when something fails?

  • A heater must switch off when the sensor is unplugged, not heat at full power.
  • A watering system must stop the pump when the tank sensor fails, not flood the room.
  • A moving machine must stop when the cover is open.
  • A battery device must not be chargeable below freezing, if the cell type does not allow it.

Each of these lines later turns into a real part or a real rule in the control logic: a second sensor, a mechanical switch, a time limit. If the line is missing on the page, the part is usually missing in the product.

Part 5: must, should, and not now

Mark each line with one of three words.

  • Must: without this, the product has no purpose.
  • Should: wanted, but can be dropped if it costs too much time, money or space.
  • Not now: good ideas for a later version. Writing them down keeps them out of the first version without losing them.

The third group is the most useful. An app, a second colour, a solar panel, a voice interface: put them under "not now". The first prototype has only one job, which is to show that the main function works.

Part 6: how you will test it

For every "must" line, write one sentence about the test. It can be simple.

  • Weight: kitchen scale.
  • Battery life: charge fully, run until it stops, note the time.
  • Temperature stability: log the temperature every minute for two hours, look at the highest and lowest value.
  • Slope: a board, a stack of books, a protractor app.

If you cannot think of a test, the requirement is not clear enough yet. Rewrite it until you can.

A filled-in example

Here is a short version for a temperature controller on a charcoal grill:

  • Job: hold the grill temperature at a set value for eight hours without attention.
  • User and place: hobby cook, outdoors, light rain possible, 0 to 40 °C around the device.
  • Must: set range 90 to 180 °C; stable within plus or minus 5 °C; two probes (grill and meat); runs from a common USB power bank for 10 hours; fan and electronics survive next to a hot grill wall.
  • Should: small display readable in sunlight; fits several grill sizes with one adapter.
  • Not now: phone app, cloud logging.
  • Never: blow at full power when the probe is missing or broken; hot parts within reach of the cables.
  • Tests: eight-hour cook with a temperature log; pull the probe plug during operation and watch the fan stop.

That is less than a page. And it already answers most of the questions that a designer, or a design system, would otherwise have to guess.

Keep the page alive

A requirements page is not a contract that is signed once. You will learn things. The feasibility check shows that the battery target is too high. The first print shows that the housing needs to be 10 mm taller. Change the page, with the date, and keep the old value visible. Then everyone, human or machine, works from the same current version, and you can see later why a decision was made.

On our platform, this page is the first result of every project: the concept step turns an idea in plain words into checked requirements, and every later step, from the 3D model to the parts list, is measured against it. You can see the result in the public project DIY BBQ Temperature Controller, where the requirements above became a real design.

Watch hardware get built by AI. Follow public projects on makemachine.ai, read every result in full and get an email when there is something new.

Get started See the live projects

More from the blog

Open-hardware projects built with AI