An RFI asks a question. A submittal shows what you propose to use.
A construction request for information, or RFI, asks for clarification about the project documents or an unresolved condition. A submittal provides something for review, such as shop drawings, product data, samples, or equipment details. The two can involve the same scope of work while serving different purposes.
Use the project’s document procedures to confirm who can submit a question, who reviews each record, and how responses are distributed. Neither an RFI response nor a submittal review should be treated as automatic authorization for a change in scope, price, or time.
When to write a construction RFI
Write an RFI when a specific question needs a formal answer. For example, an architectural drawing and a mechanical drawing may show conflicting locations for the same opening. Identify the affected room or grid line, cite the drawing numbers and revisions, and ask a question the reviewer can answer directly.
Include a clear markup if it helps, and explain the date by which the field team needs a response. If you suspect a cost or schedule impact, flag it and follow the project’s separate process for documenting that impact. Keep the original question and the response together so the team can trace the decision later.
What belongs in a construction submittal?
A submittal shows how a proposed item or fabricated assembly relates to the project requirements. A useful package identifies the specification section, the actual model or configuration, and the locations where it will be used. Highlight the proposed selection if the manufacturer’s literature covers several options.
Review the package for completeness before routing it. Identify deviations and follow the project’s procedure for substitutions. A reviewer needs to know exactly what the contractor proposes; a catalog covering every available model rarely answers that question by itself.
Example: one door package, two different records
Suppose the floor plan shows a door swinging into a corridor, but the door schedule shows the opposite swing. A project engineer can submit an RFI that references both documents and asks the design team which direction governs. The project engineer records the answer and shares it with the affected team members.
Once the direction is clear, the door supplier can prepare a submittal with the proposed door, frame, and hardware information for review. The submittal should reflect the clarification. Track the two records separately and cross-reference them so the team can see why the package changed.
How project engineers keep RFIs and submittals moving
A log is most useful when it shows the next action. Record the item, current owner, status, due date, and affected activity or purchase. Review older items before coordination meetings and flag decisions that could hold up fabrication, procurement, or installation.
- Check the latest drawing and specification revisions before routing a question.
- Confirm that the right reviewer has the information needed to respond.
- Record comments and resubmissions without losing the earlier versions.
- Tell the field and procurement teams when an answer affects their work.
How to explain this experience in an interview
Describe a real example where you identified a conflict or reviewed a package for completeness. Explain the documents you checked, what you personally did, who made the decision, and how the answer reached the people doing the work. If you maintained a log without approving the record, say so. That distinction shows you understand the process and your role in it.
If you enjoy organizing technical information and coordinating next steps, compare project engineer, project coordinator, and assistant project manager roles. Read the duties closely: some positions focus on document control, while others also include field coordination, procurement, or cost tracking.