Datasheet software for hardware startups: keep every product consistent
Private beta. Access is by waitlist, and paid plans open when the beta ends. Join the waitlist.
A hardware startup often ships its second product with a datasheet copied from the first. By the fourth product the tables use different units, the sections come in a different order and nobody is sure which revision a customer holds. Datasheet software prevents that drift by fixing the sections, the table columns and the notation, and by recording every revision.
What a datasheet needs
- Description and key features: two or three lines on what the product does, and up to five features a buyer can check.
- Electrical characteristics: a table with Parameter, Min, Typ, Max, Unit and Test conditions columns. The worked example below uses exactly these columns.
- Environmental limits: operating and storage temperature, humidity range and ingress protection, each with a note on how it was measured.
- Mechanical details: dimensions with a drawing reference, weight, connector and mounting details.
- Radio details, where the product has a radio: frequency range, output power and range under stated conditions.
- Ordering information: the rules that map a part number to a variant.
- Document ID and revision on every page, so a reader knows which version they hold.
Where drift starts
Drift comes from copying an old file and editing it. A column is added to one table but not another, "mA" becomes "milliamps", a section moves. Each change is small, and together they make a product line look improvised.
The clearest case is one parameter written differently across a product line. Here are three datasheets for a fictional sensor family, TH-210, TH-215 and TH-230, all describing the same low-power state between measurements:
| Datasheet | Name as written | Value as written | Standardized name | Standardized value |
|---|---|---|---|---|
| TH-210 | Sleep current | 0.4 uA typ | Supply current, sleep mode | 0.4 µA typ |
| TH-215 | Standby supply current | 400 nA typ | Supply current, sleep mode | 0.4 µA typ |
| TH-230 | Idd (idle) | 0.0004 mA typ | Supply current, sleep mode | 0.4 µA typ |
The same value appears three ways. The rule that fixes it has three parts:
- Name: always "Supply current, sleep mode". Never "sleep current", "standby" or "Idd".
- Unit: µA for any current below 1 mA, written as a plain number with no power-of-ten prefix.
- Conditions: supply voltage, temperature and how the measurement was made, always in the Test conditions column.
A worked electrical characteristics table
The table below is for TH-210, a fictional temperature and humidity sensor. Every value is invented for this example, and the values are internally consistent: in each row the minimum, typical and maximum are in order.
| Parameter | Min | Typ | Max | Unit | Test conditions |
|---|---|---|---|---|---|
| Supply voltage, VDD | 1.62 | 3.3 | 3.6 | V | Operating range |
| Supply current, measurement | - | 120 | 180 | µA | VDD = 3.3 V, TA = 25 °C, one measurement per second, average |
| Supply current, sleep mode | - | 0.4 | 1.2 | µA | VDD = 3.3 V, TA = 25 °C, between measurements |
| Relative humidity measurement range | 0 | - | 100 | %RH | Full range, VDD = 3.3 V |
| Temperature measurement error | -0.5 | 0.1 | 0.5 | °C | 15 to 40 °C ambient, VDD = 3.3 V |
| Measurement time | - | 8 | 12 | ms | One temperature and one humidity reading, VDD = 3.3 V |
Notation rules that keep a table like this readable:
- Units: one symbol per unit, with a space before it (3.3 V, 120 µA, 12 ms). Pick µA and use it in every table, never uA in one and µA in another.
- Symbols: define each symbol at first use. VDD is supply voltage, TA is ambient temperature, RH is relative humidity.
- Not specified: write a dash and add the note "- means not specified" under the table. Never leave a cell empty, because a reader cannot tell missing data from zero.
- Conditions: write supply voltage, ambient temperature and any mode or timing in the same order every time, for example "VDD = 3.3 V, TA = 25 °C, between measurements".
- Errors: write the sign explicitly. A minimum of -0.5 °C means the reading can be 0.5 °C low.
- Precision: use the same number of decimal places within a column, matching the precision of the test data.
Revision history and naming
Each revision of TH-210 records the date, the change and why it matters to someone holding that revision.
| Revision | Date | What changed | Why it matters to a reader |
|---|---|---|---|
| Rev A | 2026-02-10 | First release. Sleep current typical 0.6 µA, maximum 1.5 µA. | Baseline. Designs built on it carry the higher sleep figure. |
| Rev B | 2026-05-12 | Supply current, sleep mode: typical 0.6 µA to 0.4 µA, maximum 1.5 µA to 1.2 µA, after a firmware change. | Battery-life estimates made from Rev A are pessimistic. Recalculate them with Rev B values. |
| Rev C | 2026-09-30 | Measurement time maximum 10 ms to 12 ms. Test conditions added to temperature measurement error. | Timing budgets based on 10 ms need the new maximum. The added conditions show where the error figure applies. |
Name the revision so a customer can tell which one they hold. Put the document ID and the letter together, for example TH-210-DS Rev C, on the cover and in the footer of every page. The footer matters because a single page can be printed or emailed on its own. Increase the letter for any change to a value, a condition, an ordering code or a requirement, including small corrections, so two different documents never share a letter. Keep the date in the history table rather than the name, because a date can mean a release date or a print date. The revision letter is not part of the part number: units sold in Rev A and Rev C have the same order code.
Ordering information
A TH-210 part number is built from codes read left to right: series, output, cable, then packaging. For example, TH-210-D-2-B is the TH-210 with I2C digital output, a 300 mm cable and bulk packaging.
| Segment | Code | Meaning |
|---|---|---|
| Series | TH-210 | Temperature and humidity module, documented in TH-210-DS |
| Output | D | Digital output, I2C |
| Output | U | Digital output, UART |
| Cable | 1 | Bare module, no cable |
| Cable | 2 | 300 mm cable |
| Cable | 3 | 1 m cable |
| Packaging | B | Bulk bag, 100 pcs |
| Packaging | T | Tape and reel, 1000 pcs |
Not every combination is stocked, so check the stocked list before quoting a customer. The revision letter never appears in the part number.
Pre-release checklist
- The document ID and revision letter appear on the cover and in every page footer.
- Every electrical row has a value or a dash. No cell is empty.
- Minimum, typical and maximum are in order in every row, and each value traces to a test report whose number is recorded in your internal file.
- Each row states its test conditions, including supply voltage and ambient temperature.
- Parameter names, units and symbols match the notation rules and the previous revision.
- Environmental and mechanical figures match the current drawing and the test records.
- Every ordering code decodes with the part-number table, and every stocked variant appears in it.
- Every changed value has a row in the revision history with the reason for the change.
- Section order and table columns match the template, not the previous document.
- Check the rules that apply to your product and market, and confirm the document contains whatever statements they require.
- Export the PDF and check the page numbers, the revision in the footer and the links.
Wordspecs for datasheets
Wordspecs includes a hardware datasheet template with electrical, environmental, mechanical and ordering fields. The TH-210 sample sheet (a fictional sensor) shows the layout. Saved templates let you keep your own table columns and wording for every product, and the Team plan adds shared templates and version history.
Related: which template fits which document.