Transmittal form: proving what was sent, to whom, and when
A transmittal form records exactly which documents were issued, at which revision, for what purpose. What to include, how to number transmittals, and why they settle disputes.
A construction RFI resolves a gap or conflict in the design documents. What a good RFI form contains, how to log and track responses, and how to keep RFIs from delaying work.
A construction RFI — request for information — is a formal question from the contractor to the design team when drawings or specifications are unclear, incomplete or in conflict. It creates a written record of the question, the answer and its date, which matters when the answer changes cost or programme. Projects routinely raise hundreds of RFIs; the difference between a manageable process and a source of delay is how well each RFI is written and tracked.
An RFI answer that changes scope, cost or time is a change, not information. Flag it as such when it comes back, or the cost impact disappears into the RFI log.
The form captures the question; the log tracks every RFI's status. Ettex Forms is a practical way to raise the RFI with required fields and attachments, and each submission lands in Ettex Records as a row in the RFI log with status, responder and dates. That makes the questions that matter in a project meeting — what is overdue, what is waiting on which consultant, which answers created changes — a filter rather than a spreadsheet exercise.
The contract usually sets it — often five to ten working days. Where it does not, agree a standard at the start of the project and record it in the RFI procedure.
In construction, an RFI asks for clarification of design information. An RFP requests proposals and an RFQ requests prices — both are procurement documents, not project queries.
Only if the contract says so. Many contracts require a separate instruction or variation for any change, even when the RFI answer describes it.
A transmittal form records exactly which documents were issued, at which revision, for what purpose. What to include, how to number transmittals, and why they settle disputes.
A quality control checklist turns a specification into repeatable inspection steps. What to include, how to make it usable on the floor, and variants for incoming, in-process and final inspection.
A customer complaint form is the start of a record, not an inbox. The fields that make complaints actionable, how to keep a complaint log, and what to do in the first 48 hours.