Heavy Machinery RFQ Clarification and Milestone Alignment Framework
Construct a systematic follow-up cadence for specialized equipment OEMs to resolve technical scope gaps and protect production launch dates.
Use this template during capital equipment procurement when custom machinery vendors have outstanding technical clarifications during the bidding process. It builds a disciplined follow-up framework to eliminate ambiguity without inflating costs.
Role: Head of Capital Projects and Industrial Automation Procurement with expertise in bespoke manufacturing lines.
Context
- Equipment category: {{equipment_type}}
- Procurement reference: {{rfq_reference_id}}
- OEM machinery vendor: {{vendor_name}}
- Unresolved specification: {{unresolved_technical_clause}}
- Target commissioning date: {{production_target_go_live}}
- Allocated budget limit: {{budget_envelope}}
Task
Construct an industrial procurement follow-up framework and structured email playbook to resolve {{unresolved_technical_clause}} with {{vendor_name}} while safeguarding the target commissioning date of {{production_target_go_live}}.
Method
- Analyze {{unresolved_technical_clause}} for downstream impacts on cycle time, throughput, and factory acceptance testing (FAT).
- Establish an RFQ clarification milestone schedule anchored backwards from {{production_target_go_live}}.
- Create an Engineering Clarification Email specifying exact mechanical and electrical interfaces required from {{vendor_name}}.
- Create a Commercial Risk Email addressing the impact of scope creep on {{budget_envelope}} and overall bid competitiveness.
- Create a Bid Finalization Email setting a binding deadline for proposal revisions under {{rfq_reference_id}}.
- Draft a Technical Exception Log template for cross-functional review between plant engineering and procurement.
- Detail a decision framework for evaluating vendor responses against competing equipment alternatives.
Constraints
- MUST keep technical clarifications strictly aligned with the {{budget_envelope}} boundaries.
- MUST NOT reveal competitive pricing intelligence from other bidding OEMs.
- All follow-up communications MUST mandate written confirmation of FAT and SAT obligations.
- Email bodies MUST NOT exceed 200 words each to keep OEM sales engineers focused on technical parameters.
Output format
- Section 1: Milestone & Decision Gateway Timeline (table with Phase, Due Date, and Pass/Fail Gate)
- Section 2: RFQ Follow-Up Communication Sequence (3 targeted emails: Technical Interrogatory, Commercial Boundaries, Final Gateway)
- Section 3: Vendor Response Evaluation Rubric (scoring criteria for compliance, timeline, and risk)
Self-review
- Is every technical requirement tied directly to the {{production_target_go_live}} schedule?
- Does the framework prevent vendor-driven cost increases beyond {{budget_envelope}}?
- Are the engineering parameters in {{unresolved_technical_clause}} addressed without ambiguity?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.