Small wind / Buyer questions
Purchasing and delivery
How can a buyer measure whether supplier engineering questions are being resolved?
The short answer
Measure whether technical queries reach supported, accepted closure, not merely whether the supplier replies quickly. Track acknowledgement, substantive response, buyer review and final resolution separately. A fast answer that repeats the question or introduces an unverified assumption may leave the engineering dependency unchanged even though an email response has been logged.
Define useful response stages
Give each query an identifier, affected document and required decision. Record when it was sent, acknowledged, answered substantively, reviewed and closed. Mark whether the answer supplied the requested evidence or instead proposed a change. Distinguish time spent awaiting the supplier from time awaiting buyer review or another interface party. These stages help explain the real workflow without using a single average response time to label every delay as the supplier's responsibility.
Assess closure quality
A closed query should have an accepted answer and a clear effect on the affected work. Ask whether the revised drawing was issued, the interface value confirmed or the proposed alternative formally approved. If the answer contains a condition, identify who verifies it. Where the reply creates another technical question, preserve the relationship rather than delete the first issue from the record. A query can be answered but still open for engineering review; that distinction prevents false confidence about production readiness.
Use trends to improve coordination
Review recurring query types, repeated incomplete answers and avoidable document inconsistencies. Assign a coordination action where multiple suppliers depend on the same missing information. Report a small set of meaningful counts: critical open items, overdue decisions and accepted closures, with explanations for their project impact. This is a management tool rather than a contractual service guarantee. Agree any promised response levels separately, and avoid turning this register into unsupported claims about product reliability or engineering competence.
Sources
Examples are illustrative. Confirm product-specific performance, compatibility and supply scope in the applicable documents.