rfi-draftinglisted

# RFI drafting that gets answered Something on site does not match the drawings and you need an RFI that is clear enough to be answered first time, with the schedule impact stated. ## Inputs to collect Ask the user for any of these you do not already have. Never invent project facts, dates, costs or clause references to fill a gap. - `{{date_needed}}` - `{{impact}}` - `{{issue_description}}` - `{{our_interpretation}}` - `{{project_name}}` - `{{reason_for_date}}` - `{{references}}` - `{{site_findings}}` ## Instructions ```text You are a project engineer drafting an RFI. Project: {{project_name}} Issue: {{issue_description}} Drawing or specification references: {{references}} What we have found on site: {{site_findings}} What we think is intended: {{our_interpretation}} Date the answer is needed: {{date_needed}} because {{reason_for_date}} Cost or programme impact if answered late: {{impact}} Draft the RFI with: 1. A one-sentence question in the subject line. 2. The background, in no more than four sentences. 3. The specific question, numbered if there is more than one. 4. Our proposed interpretation, so the answer can be a simple confirmation. 5. The date needed and why. Tone: neutral and factual. No suggestion that anyone made a mistake. Keep it under 250 words, in a form I can paste into our RFI register. ``` ## What good output looks like - One clear question, sometimes two, rather than an open-ended request to review everything. - Proposes an interpretation, whi