An RFI, submittal and change order tracker

On most construction projects, money is lost in the space between a question and its answer. An RFI goes out by email, sits in an architect's inbox, and the crew works around the gap or waits. A submittal comes back with notes nobody reads before the material is ordered. A superintendent agrees to extra work in the field, and the change order is written three weeks later, if ever. By closeout, the contractor is arguing for money it earned but cannot prove.

An RFI, submittal and change order tracker puts all three logs in one place, numbers every item, shows who has the ball, and records the cost and schedule impact as you go. This guide covers what each log should contain, how the three connect, how to describe the tracker in plain words so an AI platform can build it, and how to roll it out.

What email threads and spreadsheet logs cost you

• Questions with no owner. An RFI sent by email has no due date anyone sees and no reminder. When it goes unanswered, the crew waits or guesses.
• The wrong version gets built. When submittal responses live in attachments, the field may install from a version that was rejected or approved with changes.
• Unbilled extra work. Field changes agreed to verbally often never become change orders. Without a log that starts the moment the change is discussed, the money is gone.
• No schedule story. When an owner disputes a delay, you need to show which RFIs were open, for how long, and what they held up. Scattered emails make that a week of digging.
• Spreadsheet logs drift. A shared spreadsheet log is only as current as the last person who remembered to update it, and it cannot remind anyone of anything.

How the three logs connect

The three logs are different, but they are one story. A question becomes an answer, the answer changes the work, and the change gets priced and approved.

What the tracker should contain

RFI log

• RFI number, assigned automatically in sequence per project.
• Subject and question, with references to drawing sheet and spec section.
• Suggested answer, if you have one. A good suggestion speeds the reply.
• Who asked, date sent, and the date a response is needed by.
• Ball in court: you, architect, engineer or owner.
• Response, who answered and when.
• Cost impact (yes, no, unknown) and schedule impact (yes, no, unknown).
• Attachments: marked-up drawings and photos.
• Status: draft, sent, answered, closed, or void.

Submittal log

• Submittal number and spec section.
• Description, such as storefront shop drawings or roofing product data.
• Subcontractor or supplier responsible.
• Required approval date, worked back from when the material must be ordered.
• Date sent, reviewer, and date returned.
• Result: approved, approved as noted, revise and resubmit, or rejected.
• Revision number, so each resubmittal keeps its history.
• Lead time after approval, so you can see when material will arrive.
• Attachments, including the returned marked-up copy.

Change order log

• Potential change number, created as soon as a change is discussed.
• Description and source: RFI, owner request, field condition, design change.
• Linked RFIs and daily reports.
• Your price, broken into labor, material, equipment, subcontractor and markup.
• Days of schedule impact requested.
• Status: potential, pricing, submitted to owner, approved, rejected, or void.
• Approved amount and approved days, which may differ from what you asked.
• Approval date and who approved it.

Roles

• Project manager creates and manages all three logs on their projects, sees costs, and submits to the owner.
• Superintendent creates RFIs and potential changes from the field and sees answers immediately.
• Project engineer or coordinator manages submittal packages and keeps the logs current.
• Subcontractor, if invited, submits RFIs and submittals for their scope and sees only their own items, never your pricing.
• Owner or executive sees all projects and change order totals.
• Accounting sees approved change orders so billing matches the contract.

Notifications

• When an RFI or submittal is sent, the reviewer is told and the due date is set.
• Two days before a due date, and on the day it passes, the project manager is reminded, so they can follow up.
• When an answer or review comes back, the superintendent and the relevant subcontractor are told right away.
• When an RFI is answered with cost or schedule impact marked yes, a potential change is suggested so it is not forgotten.
• When a change order is approved, accounting is told.

Reports

• Open RFIs by ball in court and days open.
• Average RFI response time by reviewer.
• Submittals behind their required approval date, which is your early warning on late material.
• Change orders by status, with totals for potential, submitted and approved.
• Approved versus requested amounts and days, per project.

Example request

Example request: "Build an RFI, submittal and change order tracker for our commercial contracting company. Each project has its own logs. RFIs get an automatic number per project and have subject, question, drawing sheet, spec section, suggested answer, who asked, date sent, response needed by, ball in court (us, architect, engineer, owner), response, answered by, answered date, cost impact and schedule impact (yes, no, unknown), attachments and a status of draft, sent, answered, closed or void. Submittals have number, spec section, description, responsible subcontractor, required approval date, date sent, reviewer, date returned, result (approved, approved as noted, revise and resubmit, rejected), revision number, lead time and attachments, and each resubmittal keeps the history. Change orders start as potential changes with description, source, linked RFIs, a price broken into labor, material, equipment, subcontractor and markup, requested days, status (potential, pricing, submitted, approved, rejected, void), approved amount, approved days and approval date. When an RFI is answered with cost or schedule impact marked yes, prompt the project manager to start a potential change. Remind the project manager two days before anything is due and when it is overdue. Tell the superintendent when an RFI is answered. Tell accounting when a change order is approved. Subcontractors can submit RFIs and submittals for their own scope and see only their own items, never pricing. Show open RFIs by ball in court, submittals behind schedule, and change order totals by status. Roles are owner, project manager, superintendent, project engineer, accounting and subcontractor. Only invited people can sign in."

How to roll it out

1. Pick one active project. Choose a project with a project manager who already keeps good logs. They will see the improvement fastest.
2. Load the current logs. Bring every open RFI, submittal and potential change into the tracker so the project manager is not running two systems.
3. Agree on numbering and statuses. Use the same numbering and status words on every project from now on. Consistency is what makes company-wide reports possible.
4. Make the field part of it. Show superintendents how to start an RFI or potential change from their phone with a photo. Field changes captured the same day are the biggest win.
5. Run for one month. At the end, compare RFI response times and the number of potential changes captured against a similar past project.
6. Invite subcontractors on the next project. Once your own team is comfortable, invite subcontractor project managers with their limited role.
7. Start every new project in the tracker. Make it part of project setup, alongside the budget and schedule.

Mistakes to avoid

• Waiting to log changes until they are priced. Log the potential change the day it is discussed. Pricing can come later, but the trail starts now.
• No required-by dates. An RFI or submittal without a needed-by date cannot be late, which means nobody follows up.
• Free-text statuses. Statuses that are typed instead of picked make reports impossible.
• Showing pricing to everyone. Your markup and cost breakdown are for your team. Use roles so subcontractors and outside reviewers never see them.
• Not linking items. An approved change order that cannot point back to the RFI and daily report that caused it is harder to defend.
• Closing items without the answer distributed. An answered RFI is only useful when the field has it. Make "answered" and "distributed to field" different moments.

How to measure that it works

• Average RFI response time, and the share answered by the needed-by date.
• Submittals approved by their required date.
• Number of potential changes logged per project, compared to similar past projects.
• Share of potential changes that become approved change orders.
• Time to assemble the change and RFI history for a dispute or closeout.

Capturing more potential changes is the clearest sign of value, because each one is money that would otherwise have been forgotten.

Launch checklist

1. Fields and statuses for all three logs are agreed by your project managers.
2. Numbering is automatic and consistent across projects.
3. Ball in court and needed-by dates are required on RFIs and submittals.
4. RFI answers with impact prompt a potential change.
5. Reminders and overdue alerts go to the project manager.
6. Roles keep pricing away from subcontractors and outside reviewers.
7. One project has run on the tracker for a month.
8. New projects start in the tracker as part of setup.

How FORGE handles it

On FORGE, a project manager or operations lead describes the tracker in plain words, like the example above, and FORGE builds it. A panel of top AI models plans it around your logs and roles, a dedicated AI crew builds it, and every piece is checked for quality and security before it is saved. Most teams have their first real tool the same day.

Your logs, pricing and approvals stay inside your company. People join only by invite, so a subcontractor sees only what their role allows, and there is a complete record of who did what, which matters when a change order is questioned at closeout. Subcontractors and field staff who only use the tracker are free; builders are $49 a seat a month with 3 builds included, and changes cost a small fraction of a build. We onboard every team ourselves, starting with a workflow workshop. Talk to us or read about security.

Questions people ask