编写施工图纸疑问澄清单
针对图纸或现场冲突起草单一问题的工程澄清文件,列明引用依据、建议方案、回复期限及发送检查项。
完整提示词
<context>
You write requests for information (RFIs) for contractors and trades. An RFI asks the designer or contract administrator to clarify or resolve a conflict in the contract documents. Designers answer good RFIs fast: one question per RFI, exact references with revisions, a description of the conflict that quotes what each document says, a question phrased so the answer can be decisive, a proposed solution they can simply approve, and a clear date tied to the work it holds up. Bad RFIs bundle several issues, ask vague questions ("please advise"), or try to obtain a change in scope without going through the change process.
<issue>
{{issue}}
</issue>
<references>
{{references}}
</references>
Answer needed by: {{needed_by}}
{{#proposed_solution}}
<proposed_solution>
{{proposed_solution}}
</proposed_solution>
{{/proposed_solution}}
</context>
<task>
1. If the issue does not say what conflicts with what, or where on the project, ask for that and stop.
2. If the issue contains more than one separate question, write one RFI for the most urgent and list the others as separate RFIs to raise.
3. Write a subject line of a few words that names the element and the location.
4. Describe the issue factually: what each referenced document says (quote the note or dimension where given), what was found on site, and why work cannot proceed as drawn.
5. Ask one precise question that can be answered decisively, for example "Confirm whether the beam bearing at gridline C/4 should be 150 mm as on S-201 rev B or 100 mm as on A-305 rev D."
6. Give the proposed solution, if supplied, or suggest one labelled as for the contractor to confirm, so the designer can reply "approved".
7. State the impact of a late answer in neutral terms: the activity held up and from when. If the answer may change cost or time, say the contractor will notify under the contract's change procedure, without making a claim in the RFI.
8. State the date needed and the reason.
9. List attachments (photos, markups) and the distribution.
10. Before writing the final version, check that the RFI has exactly one question, every reference has a revision where one was supplied, and the date is stated.
</task>
<constraints>
- Neutral, professional tone; no blame for the design team.
- Never invent drawing numbers, revisions, dimensions or specification clauses. Use `[ADD]` for missing references.
- If the issue is really a request to change the scope or specification rather than a clarification, say so in the checks and recommend the change process instead.
- Keep it short enough to read in a minute.
</constraints>
<output_format>
## RFI
A form: RFI number `[ADD]`, Project `[ADD]`, Date, To, From, Subject, References, Issue, Question, Proposed solution, Impact if not answered by the date, Answer needed by, Attachments, Distribution.
## Checks before sending
Bullets, including any further RFIs to raise separately.
</output_format>可替换内容
- {{issue}}
- {{references}}
- {{needed_by}}
- {{#proposed_solution}}
- {{proposed_solution}}
- {{/proposed_solution}}
- [ADD]
分类与标签
办公效率、工程澄清单、施工图纸、项目沟通、文书起草、发送前检查