Contracts

What is a request for change in construction?

A request for change (RFC) is a formal written request, from the owner or the contractor, to alter the scope, cost, or schedule of a construction contract before anyone commits to a change order.

Two construction professionals review paper plans beside a tablet at a jobsite workbench.
Plan reviews connect field conditions, drawings, and the next decisions on a job. AI-generated illustration.

A request for change, usually shortened to RFC, is the paperwork that starts a change conversation. One side puts in writing what it wants different (more scope, less scope, a substitute product, a new sequence, a later date) and asks the other side to respond. Nothing is binding yet. The RFC becomes money and time only when both sides sign a change order, or when the owner forces the issue with a change directive.

Who sends it depends on the contract. On many owner forms, the RFC goes from the owner or architect to the contractor and says, in effect, "price this." On other jobs the contractor uses the same name for its own request, which works much like a change order request. Read the contract's changes clause to see which meaning applies on your job, because the response deadlines follow the definition.

How a request for change moves through a job

  1. Issue: the requester describes the change, references drawings or spec sections, and says whether work should stop, continue, or wait.
  2. Price: the contractor collects sub and supplier quotes, adds labor, equipment, markup, and any schedule impact.
  3. Review: the owner, architect, or construction manager checks the numbers and may negotiate or ask for backup.
  4. Decide: approved RFCs become change orders; rejected ones are closed in the log with a reason; disputed ones may turn into a directive or a claim.

A worked example

Say an owner on a $480,000 dental office build-out issues RFC 07: add two sinks in the sterilization room. The general contractor sends it to the plumbing and casework subs. Plumbing comes back at $6,200 with three extra days of rough-in; casework adds $3,900 and a two-week lead time on the countertop. The GC adds its own supervision and markup and returns a priced response of $11,450 and five working days.

The owner balks at the time, not the money. After a call, the GC resequences so the casework lead time overlaps other work, and the revised response drops to two days. The owner signs, RFC 07 becomes Change Order 4, and the schedule of values gets a new line for the next pay application.

Where RFCs go wrong

  • Working before the paper is signed. An RFC is a question, not an approval. Crews that build from an RFC alone risk doing free work.
  • Leaving out time. Price gets all the attention. If the response does not ask for days, many contracts treat the silence as zero schedule impact.
  • Missing the response window. Some contracts give the contractor a set number of days to answer. Late answers weaken the position.
  • Mixing RFCs with RFIs. A request for information asks what the documents mean. An RFC asks to change them. When an RFI answer adds scope, open an RFC right away.
  • No log. Open RFCs are exposure. Without a running list, nobody can say how much pending change is sitting on the job.

Related terms

Requests for change sit in the same family as scope creep, field orders, and the change log. For a step-by-step on pricing the response, see how to price a change order.

Smart Business Automator keeps requests, pricing, and approvals for change orders in one place per job, so pending exposure shows up next to the budget. See change order approval automation.

Frequently asked questions

Is a request for change the same as a change order?

No. A request for change asks for a change and usually asks for a price. A change order is the signed agreement that actually modifies the contract sum or time.

Who issues a request for change?

Either party, depending on the contract. Owners and architects often issue them to get pricing; contractors use them to propose changes or to flag extra work. The contract's changes clause defines the term for that job.

Should work start when an RFC is issued?

Usually not. Unless the owner issues a written directive to proceed, work on the change should wait for a signed change order, or you risk not getting paid for it.

What should an RFC response include?

A clear scope description, a cost breakdown with sub and supplier quotes, markup as allowed by the contract, schedule impact in days, any exclusions, and how long the price is good for.

Written and edited by

Maurice Francois writes and edits construction operations guides for Smart Business Automator. More from Maurice on the Scaling Legends podcast.

Get a free assessment