How requests are structured
Read the structured request: typed lines, normalised units and a citation behind every value.
Updated 23 September 2026
On this page
- Why
- A figure you cannot trace back to the customer's words has to be checked by hand, which is the work this removes.
- What
- Each request becomes a Structured request card: one row per thing asked for, every attribute cited.
- How
- Tap or click any value on the card to see the original text it was read from.
A tooling request read into a structured table: 4 lines, each with its quantity, and 15 attributes, each cited to the customer's own words.
What a line carries
| Part | What it is |
|---|---|
| Description | What the customer asked for, in their words. |
| Quantity and unit | As stated. One nobody gave is assumed as one off and marked assumed, or shown as not stated when you ask for it instead. |
| Attributes | Material, diameter, coating, tolerance and the rest, each in its own typed field. |
| Citation | The span of the request each value came from. |
| Not stated | The parameters that specify this kind of product, or the inputs a matched service needs, that the request left open. |
Normalised, with the original kept
The same size arrives as 12mm, 12 dia, Ø12 or 1/2in. The typed field holds one value in one unit so lines compare and formulas can read them, and the customer's own wording is kept one tap away.
Missing means a question
A value the request does not state stays empty. Where your order history, the customer's details or an engineering norm settles it, Kabaido fills it and marks it assumed with its basis; a specification, tolerance, price or part number is never assumed. See Clarifications.
The whole specification
Under each line, Not stated lists the parameters its kind of product is specified by that the request left open, as far as your catalogue schema scores them. You can tell a complete line from a thin one before the quote goes out.
The structured card needs no catalogue: it is what you get on day one. See Schemas and fields for the parameters it reads against once you have one.
Related
- ClarificationsAnswer what a request left out, see what was assumed, and have the line resolved again.
- Working with matchesRead how a line is matched to your catalogue, and overrule the match when you disagree.
- Application Engineering IntelligenceUnderstand the knowledge behind every AI answer: seven categories over fifteen knowledge packs, selected per request.