Why substitutions start early
A substitution can begin as a contractor suggestion, a supplier alternative, or an owner directive during the bid period. Each source carries a different level of authority, and the estimator needs to know which one applies before changing the basis. A request that is only an idea should not overwrite a specified product.
The log separates a question from an approved change. The bid documents usually require a formal substitution process with a deadline and a named reviewer. Even when the process is informal, the estimate needs a record of what was assumed.
A verbal alternative discussed on a call can disappear before the bid review. Write it down with the date, the source, and the person who raised it.
Record the request
Open one row for each proposed product or method and give it a stable request number. Record the specification section, the specified item, the proposed item, and the reason for the request. Add the request date and the bid deadline so the team can see the time available.
A short description is enough when it points to the supporting document. Attach the product data, the test report, and any manufacturer letter that supports the proposal. Note whether the request changes a dimension, a finish, a fire rating, or an installation method.
Those changes can affect other trades, so the reviewer needs the full effect rather than the product name alone. Keep the attachment list inside the row so the evidence travels with the decision.
Separate equal and alternative
An equal product is offered as a direct match to the specified item, while an alternative changes performance or method. The two need different review paths because an alternative can shift the design intent. Label the request type before anyone spends time on a comparison.
A mislabeled request can pass a review that was never designed for it. For an equal, compare the published characteristics line by line and record where the evidence is thin. For an alternative, ask the design team to confirm that the change is acceptable before the estimate relies on it.
Do not let the supplier's own comparison decide the question. The estimator records the evidence, and the authorized reviewer makes the call.
Tie the request to the specification
Use the specification section number as the primary key so the request sits beside the scope it affects. A request that crosses sections needs a primary section and a list of related sections. That structure helps the reviewer find every affected line during the bid review.
It also stops the same product from being requested twice under different names. Check the general requirements for submittal timing, sample requirements, and approval authority. A substitution that is acceptable in principle may still arrive too late for the bid.
Record the required lead time and the date the answer is needed. The estimate should carry a hold when the answer will not arrive before the deadline.
Review before release
Add the open substitution requests to the bid review agenda and show which ones carry a cost or schedule effect. A request with no cost effect can be closed with a note, while a request that changes a system needs a decision. Give the reviewer the specified basis and the proposed basis side by side.
That comparison is faster than reading the full product file in the meeting. Decide whether the estimate will use the specified item, the proposed item, or a stated allowance. Record the decision and the person who approved it.
If the decision is unresolved, state the assumption in the bid qualifications. A silent change is the risk that the log exists to prevent.
Close the log
At bid close, mark every row as approved, rejected, withdrawn, or carried as an assumption. Rows that remain open need an owner and a date after submission. A clean close means no request is left without a disposition.
That discipline makes the next bid faster because the history is already there. Save the closed log with the estimate file and reference it in the handoff note. The project team will need the same record when the substitution returns during construction.
A reviewer should be able to see the original request, the evidence, and the decision without asking around. That record is the real value of the log.
Coordinate with the design team
Send the proposed substitution to the design team with the specification reference and the evidence attached. Ask for a written response rather than a verbal opinion so the decision can travel with the estimate. Set a response date that leaves time for a second option if the answer is no.
The log should show when the request was sent and when the answer is due. When the design team asks for more information, record the request and the new due date in the same row. A request that bounces between offices without a date is effectively lost.
Copy the bid lead on any item that affects the base scope. That visibility keeps the substitution from becoming a last-minute surprise.
Keep the evidence current
Product data and test reports can change during a long bid cycle, so check the revision date on every attachment. A report that was current at the start of the bid may have been replaced by the time the estimate is released. Replace the file and note the change in the log.
A stale attachment can support a decision that no longer applies. Close the loop after award by sending the approved log to the project team. The team will use the same evidence when it prepares the submittal.
A short cover note should identify the approved items and the ones still open. That handoff prevents the field team from starting the submittal process from scratch.
Set the decision rights
Name the person who can approve an equal product and the person who can approve an alternative. The two decisions carry different risk and should not default to the same reviewer. Write the names and the limits in the log header.
A request that reaches the wrong reviewer loses time and credibility. Record the level of evidence each reviewer expects before the request is reviewed. A reviewer who wants a full test report should not receive a manufacturer flyer.
A reviewer who accepts a written statement should not be asked to wait for a lab. Matching the evidence to the decision keeps the process moving.
| Field | What to record | Why it matters |
|---|---|---|
| Request number | Stable identifier and date received | Prevents duplicate requests |
| Specification section | Primary section plus related sections | Links the request to scope |
| Basis | Specified item, proposed item, and type | Separates equal from alternative |
| Disposition | Approved, rejected, withdrawn, or carried | Shows what the bid assumes |