New York public procurement can put certification, product compliance, schedule, price, and documentation into the same conversation. They still need to be evaluated as distinct facts.
1. Define the procurement question
Start with the specific decision the project team needs to make. Is the request for budget pricing, a bid response, an approved-equal review, a material buyout, or a required-on-site delivery plan? State that purpose, the responsible contact, and the dates that control the response.
A supplier’s category capability can be clear while manufacturer authorization, stocking position, lead time, or project history remains unverified. Ask for the evidence relevant to the decision rather than treating broad capability as proof of every specific condition.
2. Build the governing document set
Include the current plans, specifications, schedules, quantities, addenda, alternates, approved-manufacturer language, and commercial instructions. Identify which files govern if versions conflict. A bill of materials is helpful, but it should not silently replace specification notes or schedule exceptions.
Practical rule The RFQ should make it possible to locate the requirement, understand the quantity, see the constraint, and identify the decision date.
3. Verify certification in the official record
The NYS OGS public directory lists Crestview Group, LLC under SDVOB control number 201029. Because directory status may change, procurement teams should use the official NYS OGS record at the time the information is relied upon.
Certification evidence does not by itself establish eligibility for a particular award, agency interpretation, goal-credit treatment, or solicitation. Those depend on the governing documents and the issuing entity’s rules.
4. Keep product compliance separate
Supplier-status review and material-compliance review answer different questions. The product side may involve basis-of-design language, listed manufacturers, ratings, finishes, test standards, submittals, or approved-equal procedures. Ask for product evidence that maps to those requirements.
5. Preserve the decision trail
Record the files reviewed, addenda incorporated, clarifications received, exceptions stated, and approval path used. If an alternate is proposed, keep the stated requirement and the comparison together. If a schedule is discussed, distinguish a requested date from a confirmed commitment.
Quote-ready RFQ checklist
- Project name, location, and issuing entity
- Solicitation or contract identifier
- Bid due date and response due date
- Required-on-site date or phase dates
- Plans, specifications, schedules, and addenda
- Bill of materials, quantities, and unit conventions
- Category scope and exclusions
- Approved manufacturers or substitution rules
- Technical ratings, finishes, and accessory requirements
- Commercial and compliance instructions