Book demoSign up

Platform

PlatformApp builderForm builderWorkflowDashboardIntegration

Solutions

Order & inventoryProduction orderLean managementMaintenanceAfter-sales work orderCRMProject managementTask managementConstruction

AI Templates

AI Templates

Resources

Help docsQuickstart guidePartnersCommunityTemplatesBlogAbout usSecurity

Pricing

Pricing
Book demoSign up
AI Templates
Guides
Construction Operations Guides
RFI, Submittal, and Change Order Workflow Guide
Guide

RFI, Submittal, and Change Order Workflow Guide

Plan construction RFI, submittal, and change order fields, review ownership, evidence, due dates, and field handoffs before choosing templates.

RFIs, submittals, and change orders are separate records, but they often move through the same review reality: someone asks, someone reviews, a decision affects field work. This guide helps construction teams define the fields and handoffs that keep review work visible.

Review construction review fieldsOpen RFI template
Construction Request For Information FormStart from: Construction Request For Information Form
01

Use the right record for the review question

RFIs, submittals, and change orders should not be collapsed into one generic form. Each has a different purpose, but they should share clear reviewer and status fields.

  • Use RFI fields for field questions, drawing references, impact, and response needed.
  • Use submittal fields for package, specification section, reviewer, and approval status.
  • Use change order fields for scope, cost, schedule impact, approval, and revised terms.
  • Keep project, location, related document, and due date consistent across all three.
02

Reviewer ownership prevents hidden delays

Construction review work stalls when ownership is unclear. Each record should show who owes the next decision and what is blocking that decision.

  • Reviewer, reviewer role, assigned date, due date, and escalation owner.
  • Pending information, returned reason, clarification request, and response status.
  • Decision status such as open, under review, approved, rejected, revised, or closed.
  • Overdue status and impact on field work or schedule.
03

Decision history should stay attached

The final answer is not enough. Teams need to know what changed, who approved it, and whether the decision affects cost, schedule, drawings, materials, or punch work.

  • Question, response, revision, decision date, and approver notes.
  • Cost impact, schedule impact, field impact, and contract impact.
  • Linked daily report, drawing, submittal package, or change record.
  • Notification status for site teams and affected subcontractors.
04

Handoff decisions back to the field

A reviewed record should change field execution. The workflow should show whether the answer has been communicated, implemented, or moved into change or closeout work.

  • Field owner, implementation status, effective date, and communication notes.
  • Change order required, punch item created, or submittal revision needed.
  • Updated drawings, specifications, material status, or schedule notes.
  • Closeout evidence after the decision is applied.
Review workflow

RFI, submittal, and change order handoffs

Use these fields to keep construction review work visible from intake through field implementation.

RecordCore fieldsDecision fieldField handoff
RFIQuestion, drawing, location, impact, due date.Response, reviewer, decision date.Answer communicated to field owner.
SubmittalPackage, spec section, revision, reviewer.Approved, rejected, revise and resubmit.Approved package released for work.
Change orderScope, cost, schedule, contract impact.Approval status and revised terms.Change implemented or tracked.
Daily report linkDate, site note, blocker, related work.Whether review is blocking progress.Progress or delay updated.
Punch list linkOpen item, owner, due date, evidence.Closeout accepted or reopened.Completion verified.
Templates

Connect review records to field execution

Use the guide to define review fields, then connect RFIs, submittals, change orders, daily reports, and punch list follow-up.

Best template to start withBest starting point: Construction Request for Information Form

Start here when field questions need scope, drawing references, reviewer ownership, response dates, decision history, and field impact in one workflow.

Construction Request For Information FormConstruction Request For Information FormCapture construction RFI details, route each request to the right owner, and keep status visible through follow-up in one structured workflow.Construction Submittal LogConstruction Submittal LogTrack construction submittals, reviewer handoffs, due dates, and revision history in one customizable Jodoo template.Change Order FormChange Order FormCollect change order details, supporting files, and review notes in one structured form.Change Control SoftwareChange Control SoftwareTrack change control requests with impact assessment, approvals, implementation tasks, validation evidence, and closeout status.Construction Daily Report FormConstruction Daily Report FormCollect construction daily report details, supporting files, and review notes in one structured form. Lead.Punch List FormPunch List FormCapture punch list items, assign responsible trades, and track closeout progress in one customizable Jodoo template.Subcontractor Prequalification FormSubcontractor Prequalification FormCollect subcontractor credentials, licenses, insurance certificates, safety history, trade scope, risk notes, and approval decisions.Roofing Scheduling SoftwareRoofing Scheduling SoftwareSchedule roofing inspections, estimates, repairs, crews, job stages, weather notes, materials, and customer follow-up in one workspace.
FAQ

Questions about construction review workflows

Should RFIs, submittals, and change orders be in one workflow?

They should stay distinct records, but they can share reviewer fields, due dates, decision history, and project handoffs so teams can see related work.

What fields should every construction review record include?

Include project, location, owner, reviewer, due date, status, decision, impact, supporting documents, and field implementation status.

When does an RFI become a change order?

When the response affects scope, cost, schedule, contract terms, or required work, it should trigger a change order or change-control record.

Next Step

Open the RFI template

Preview the Jodoo template, then adapt question fields, reviewer queues, due dates, and decision handoffs around your construction review process.

Preview this template