AREKTON / PRACTICAL WORKFLOW GUIDE
How to Track Construction RFIs and Submittals in Excel
For commercial contractors and construction project managers, a useful log answers three questions: what needs a response, who owns the next action, and when is it due? Keep RFIs and submittals in separate logs, using consistent identifiers and a repeatable review routine.
This guide provides general workflow advice, not a contract interpretation or a description of every AREKTON field. Your contract documents, specifications and agreed project procedures govern review periods, routing, responsibilities and required notices.
RFI or submittal: which record do you need?
An RFI (request for information) asks for clarification about an ambiguity, omission or conflict in project information—for example, two drawings showing different dimensions. A submittal presents specified information for review, such as product data, shop drawings or samples. A submittal review is not a substitute for resolving a design question through the required RFI process. Neither log, by itself, authorizes changes to cost, scope or time; follow the project’s change procedures.
Start with consistent log fields
Use a unique number, a concise subject, a responsible party, date sent, due date, status, and response or disposition in each log. Clarify whether “responsible party” means the person preparing the item or the person who owes the next action. Add a reference to the relevant drawing or specification and a link to the supporting files. Record the actual response date separately from the planned due date.
Use agreed status labels. For example, an RFI might move from Draft to Sent to Response received to Closed. A submittal might move from Preparing to Submitted to Returned, with the reviewer’s actual disposition recorded separately. Do not replace the reviewer’s wording with a more favorable status.
Set review dates from project requirements
Confirm the required review period, who receives the item, and what counts as receipt before calculating a due date. Check whether the period uses calendar days or workdays, how holidays are handled, and whether a submission cutoff applies. Do not assume every item gets the same review period. Coordinate planned submission dates with procurement and installation needs, allowing time for routing and resubmittals.
Keep the original sent date and due date. If an agreed date changes, record the revised date and reason without erasing the original record. A spreadsheet formula can help calculate dates, but a person still needs to confirm the inputs and the applicable contract requirements.
Fictional RFI log example
Illustrative only: the people, project issue and dates below are fictional. The seven-day period shown is an example, not a recommended or contractual review period.
Fictional RFI log — one example entry
Number: RFI-014
Subject: Conflicting door opening dimensions at Room 102
Responsible party: Morgan Lee, design-team coordinator (next response)
Date sent: April 5, 2027
Due date: April 12, 2027 — fictional agreed date
Status: Closed after response distribution
Response: Response received April 9, 2027: use the opening dimension on revised detail A-502, revision 2. Response PDF retained with the entry.
Fictional submittal log example
Illustrative only: this example is not an AREKTON screenshot or a required disposition vocabulary. Use the reviewer’s actual designation and follow the project’s approval and release procedures.
Fictional submittal log — one example entry
Number: SUB-023, revision 1
Subject: Interior door hardware product data
Responsible party: Casey Rivera, architect’s review coordinator (next response)
Date sent: April 6, 2027
Due date: April 20, 2027 — fictional agreed date
Status: Returned; resubmittal pending
Disposition: Returned April 16, 2027: Revise and resubmit. Provide the missing hardware-set schedule. Retain marked-up return; open revision 2 as the next review cycle.
Review overdue items and record the response
At a regular project review, filter for open items with due dates before today. Check whether a response was received outside the log before sending a follow-up. Confirm the next responsible person, record the follow-up date, and follow the required escalation or notice process. An overdue flag is a prompt for review, not proof of contractual responsibility or an entitlement.
When a response arrives, record its date and a concise factual summary, then retain the complete response or marked-up submittal. Distribute it through the required channel. Close the item only when the response has been reviewed and the next actions are understood. Track a resubmittal as a new revision with its own sent date, due date and disposition.
Organize supporting documents and preserve closed records
Use a consistent project folder structure and filenames containing the log number and revision, such as RFI-014_Response_2027-04-09.pdf. Keep the original submission, transmittal, supporting drawings and returned response together. Link the log to the correct folder or file and check that other authorized team members can access it.
Do not overwrite returned documents or delete closed rows to tidy the workbook. Preserve prior revisions, keep backups, and retain dated read-only snapshots or PDFs at agreed milestones. Follow your company’s access, confidentiality and retention requirements; a log is an index to the project record, not a replacement for that record.
Where AREKTON fits — verified workbook features
The workflow advice above can be applied to an Excel-based project process. AREKTON’s verified RFI features include tracking questions, responses and due dates, with printable RFI forms and logs. Its submittal features include workday or calendar-day review settings, holidays, an after-2-PM review start, and printable submittal forms and logs. Configure and check those settings against your project requirements; they do not determine your contractual obligations.
AREKTON requires Windows desktop Microsoft Excel with VBA macros enabled. Excel is not included. Excel for the web, mobile Excel and Google Sheets are unsupported; Mac compatibility is unverified. AREKTON forms are not official AIA documents.
Explore the connected workbook
See the full workbook workflows, screenshots, compatibility requirements and purchase terms, or evaluate one project with the free 40-day trial. The trial does not automatically charge you or convert to a paid purchase.
