Identify the product

A product family name is rarely a complete specification. Two devices with similar names can differ in processor, memory, storage, connectivity, keyboard layout and regional support.

If you already know what you need, include the manufacturer name and exact part number. If the purchase is for a new use case, describe the applications, working environment and equipment it must connect to.

Define acceptable alternatives

Mark the features that cannot change. For example, an existing docking setup may require a particular interface, or a replacement memory module may need a specific platform reference.

Then list the details that can vary. An approved alternative is easier to review when the supplier knows which requirements are fixed and which are preferences.

A useful distinction: “must have” describes a requirement. “Preferred” leaves room for a proposal. Keep both visible in your brief.

Add quantity and delivery

Give a quantity for every line item, a delivery destination and the date you are working towards. For a phased rollout, separate the quantities and destinations by phase.

Include any documents needed by your purchasing team, as well as requirements concerning product condition, warranty coverage or packaging. Those details can affect which supply options are suitable.

Use a simple checklist

FIELDWHAT TO INCLUDE
Product referenceManufacturer, full model, part number and description
ConfigurationProcessor, memory, storage, interfaces and regional variant
QuantityUnits per item, with delivery phases if relevant
AlternativesMandatory features and acceptable substitutions
DeliveryDestination and required delivery window
Commercial detailsRequired documents, product condition and support expectations

Keep the first version simple. A clean spreadsheet with one item per row is usually easier to clarify than a long email with several overlapping product descriptions.

Back to the journal