The short version
Start with your subcontract’s notice requirements. Record the direction and its source promptly, describe the difference from the current scope, separate known cost and schedule effects from estimates, and keep proof of what you sent.
1. Check the subcontract before choosing a notice process
Before drafting, find the subcontract sections that cover changes, extra work, notice, claims, time extensions, and required project communications. Confirm who may direct changed work, who must receive notice, how it must be sent, what backup is required, and any stated response or submission window. Also check whether the prime contract requirements were flowed down to your subcontract.
There is no single notice deadline or process that automatically applies to every U.S. subcontract. Federal clauses are useful examples of how particular contracts can set detailed notice steps, but they do not replace the language in your own agreement. For example, FAR 52.243-7 calls for prompt written notice and has a blank negotiated number of calendar days; FAR 52.243-4 describes a different clause-specific process and timing.[2][3]
2. Record the direction while the details are fresh
A potential change can arrive as a revised drawing, an email, a meeting direction, a field conversation, an access restriction, or a sequence change. Record the event without deciding for the other party whether it is contractually compensable. A federal notification clause illustrates useful factual fields: date and circumstances, the people involved, the documents or oral communication, and the work elements that may be affected.[2]
- Project name, number, subcontract or purchase-order reference, location, and affected area or drawing detail.
- Date and approximate time you received the direction, who gave it, their role, and who else heard or received it.
- What the current documents or agreed scope showed, what new direction or condition you observed, and when the difference became clear.
- The work already completed, material ordered or fabricated, and work that may need to be revised, removed, repeated, or resequenced.
- The immediate clarification or written direction you need to avoid guessing about the next step.
Use neutral, specific wording. “On Tuesday the superintendent asked us to move the west wall embeds after fabrication; the current issued detail shows the earlier locations” is more useful than “the GC caused a major delay.” If direction was verbal, make a dated written record of what you understood and send it through the required channel so the recipient can confirm or correct it.
3. Separate the changed scope from its possible impacts
Describe the added, deleted, revised, or disrupted work first. Then show the labor, equipment, material, and schedule effects in separate, traceable parts. Identify what is measured, what is estimated, and what still needs confirmation. The FAR notification clause is one example of contract language that asks for affected work elements, labor or materials added or wasted, possible delay or disruption, and estimated price or schedule adjustments.[2]
- Labor: trade or crew, headcount, hours, shift, and whether hours are actual or forecast. Keep time records tied to the affected activity.
- Materials: quantity, unit, source or quote, freight, restocking, and any material made unusable. Separate a quote from an incurred cost.
- Equipment and subcontractors: equipment type and time, delivery or remobilization charges, and any lower-tier work affected.
- Schedule: the planned activity and dates, what changed, dependencies, the period potentially affected, and whether the impact is confirmed or still being evaluated.
- Credits and avoided work: identify deleted scope or costs that may be avoided so the record does not hide offsets.
4. Attach records that let someone check the facts
Keep the original records and organize them by date and affected activity. Useful backup may include the current and revised drawing sheets, marked-up details, emails or meeting minutes, dated site photos, daily reports, labor and equipment time records, delivery tickets, supplier quotes, invoices, and a schedule excerpt showing the planned sequence. Do not alter source files; label your copies and explain what each attachment shows.
A short index can make a package easier to review: “Attachment 1 — revised west wall detail received [date]; Attachment 2 — field photo of fabricated embeds [date]; Attachment 3 — supplier quote for replacement material.” Keep the notice itself readable and put detail in the backup rather than burying the request in a pile of unexplained documents.
5. Send it to the right person and track the response
Use the notice method and recipient named in your subcontract or project procedures—such as the designated email address, project-management system, or written notice address. Save the sent copy, attachments, timestamp, delivery or submission confirmation, and any response. A federal contract rule likewise describes prompt written notification so the government can evaluate the reported conduct; that rule is specific to its setting, but illustrates why identifying the right recipient and preserving the transmittal matter.[1]
Ask for the decision or information you actually need: confirm the revised scope or detail, identify the authorization path, clarify whether additional backup is required, or request a response by a date tied to a project need. Do not state that silence equals approval unless your contract and qualified advisor support that position. Follow the applicable written direction and escalation process; do not rely on this guide to decide whether to proceed, stop, or incur disputed cost.[2]
6. Update the record as actual costs and schedule effects emerge
A first notice may need a later update. Link each update to the original notice, distinguish actual labor and material from earlier estimates, add new records, and explain any change in the schedule analysis. Keep the same project reference and a clear version date so the team can tell which information was current when it made a decision.
For some federal contracts, FAR 52.243-4 describes a clause-specific written statement of the general nature and amount of a proposal within the stated period, unless extended. That is not a universal subcontract deadline; confirm the notice and proposal requirements that govern your project.[3]
A concise example and a send-ready checklist
- I checked the applicable subcontract notice clause, recipient, delivery method, and deadline.
- I stated the date, source, direction, and difference from the current scope or documents.
- I separated scope, labor, materials, equipment, and schedule effects, and labeled unknowns and estimates.
- I attached and indexed the records that support the facts and preliminary calculations.
- I made a clear request, sent the package through the required channel, and saved proof of delivery.
- I scheduled a follow-up to update actual cost, schedule, and response records.
Sources and scope
These primary sources describe federal acquisition rules and clauses. They are cited as examples of contract-specific language, not as rules that automatically govern private construction subcontracts.
- [1] FAR 43.104 — Notification of contract changes
Federal acquisition guidance describing prompt written notice in the context of government contracts.
- [2] FAR 52.243-7 — Notification of Changes
An example federal clause covering notice content, affected work elements, continued performance, and response steps when included in a contract.
- [3] FAR 52.243-4 — Changes
An example federal clause with its own written notice and proposal provisions; it is not a universal subcontract rule.
Have project details ready? Start an editable change-notice draft for review.
Draft a change notice