When an Undecided Material Specification Needs Project-Team Review
An unresolved material requirement does not always mean procurement must stop. It does mean the buyer needs to distinguish between information a supplier can provide and a decision the project team must make. A missing pack quantity and an undecided performance requirement may both look like blank fields, but they should not be handled in the same way.
The useful question is not simply whether a quotation can be obtained. It is whether sourcing can proceed without turning an assumption into an apparent requirement. On Matravo, a construction and landscape material RFQ-to-offer marketplace, a clear request starts with an honest description of what is known and what remains unresolved.
1. Separate missing information from missing decisions
A clarification asks someone to explain a fact: how many pieces a pack contains, which product a technical document covers, or what assumptions support a quoted unit. A project decision establishes what the material must do or which conditions it must satisfy. Suppliers can describe their products, but that does not settle what your project requires.
Consider an external paving request. Asking a supplier to confirm available dimensions is different from asking that supplier to choose an unspecified performance requirement. The first can inform sourcing. The second may depend on intended use, the design, and applicable requirements that belong with the qualified project team.
Write the uncertainty in plain language before deciding what to do next. “Supplier to confirm pack contents” identifies a factual question. “Required performance not yet confirmed by project team” identifies an unresolved decision. Neither should be silently replaced with a familiar value from an earlier project.
2. Keep a clarification open only when its boundary is clear
A question can remain open when the request still communicates a meaningful basis for discussion and the unanswered point is clearly labelled. State what is undecided, who needs to answer it, and what the answer could change. This helps prevent a provisional detail from being treated as an instruction.
For example, you might request a stated number of square meters while asking suppliers to explain their packaging quantities. The packaging question remains visible, while the requested quantity has a clear basis. Do not assume that every pallet contains the same amount or that an offer in pallets is directly comparable.
An unresolved finish preference may also remain a discussion point if the project team has confirmed that the options under consideration fit the project's requirements. Without that confirmation, do not label the difference as merely cosmetic. Similar appearance is not evidence that materials can serve the same intended use.
Use precise wording: “Alternatives may be proposed for review; acceptance is not confirmed.” That invites information without giving suppliers an implied authorization to redefine the specification.
3. Escalate when the answer defines suitability
Refer the issue to qualified project-team members when the missing decision determines whether a proposed material is suitable. This includes uncertainty about required performance, compatibility with another system, dimensions affecting interfaces, or which drawing revision governs the request. The buyer should not resolve these matters by choosing whichever value produces an easier quotation.
- Conflicting references: two documents describe different requirements, and it is unclear which one controls.
- Undefined performance: the request names a material but does not establish a requirement relevant to its intended use.
- Unclear substitution limits: a proposed alternative changes something the project team has not authorized suppliers to change.
- Uncertain evidence: a document is available, but its relevance to the proposed product or system is unresolved.
Ask the project team to resolve the specific decision, not simply to “approve the material.” Identify the conflicting information, explain the purchasing consequence, and ask for the governing requirement or an explicit boundary for alternatives. Where that decision determines the sourcing basis, resolve it before proceeding on that basis.
4. Do not let quotations become design decisions
A supplier response can reveal an ambiguity without resolving it. If offers use different thicknesses, units, or declared performance, the lowest total does not establish the correct specification. First determine whether the responses address the same requirement. A price comparison cannot substitute for that judgment.
Where units differ, ask the supplier for the conversion and its assumptions. State wastage or spare quantities explicitly rather than concealing them inside a total. Where documentation matters, name the document, test, or declared performance required and the product or system it must cover.
Separate commercial information from technical acceptance in your own review. You can record what a supplier proposes while leaving acceptance unresolved. Matravo's category guides help buyers prepare requests; they do not certify products or replace project specifications, design review, or locally applicable requirements.
5. Resume with the decision recorded, not remembered
Once the project team responds, carry its decision into the request wording. Identify the applicable specification or drawing revision, distinguish essential requirements from permitted alternatives, and remove provisional wording that is no longer accurate. If a question remains open, retain its label and explain what still requires confirmation.
The aim is not to eliminate every conversation before sourcing. It is to make sure supplier questions concern a shared, stated requirement rather than a guessed technical decision. When you are ready to begin your request, visit the Matravo website and choose Create account, or Sign in if you already have an account.
