September 25, 2026·7 min read

Plant Substitution Request Form Template for LA Firms

A practical plant substitution request form template for landscape architecture firms—what to include, how to track approvals, and where the process breaks down.

Plant substitutions are one of the most common sources of uncompensated time during construction administration. A contractor calls, says the specified Quercus agrifolia is unavailable, and suddenly you're spending 45 minutes evaluating a proposed replacement with no paper trail, no approval record, and no fee attached. A proper plant substitution request form template fixes most of that.

Why the Verbal Approval Habit Costs You Money

Most firms handle substitutions informally for years before a bad outcome forces a change. The contractor texts a photo of a proposed plant, the project manager says "fine, go ahead," and the substitution gets planted. Nobody logged it. Nobody checked the caliper, the water use zone, or whether the replacement species is on the invasive list for that county.

The liability exposure is real. If a substituted plant fails at year two and the client asks why Platanus × acerifolia ended up in a water-sensitive zone instead of the specified Platanus racemosa, "I approved it verbally" is not a defensible answer. Beyond liability, untracked substitutions create punch list headaches when the installed plant schedule doesn't match the record drawings.

The fix is procedural, not technical. A form forces the contractor to do the research, documents the basis for approval, and creates a timestamped record tied to the submittal log.

What a Plant Substitution Request Form Template Needs to Include

A workable form has three sections: the request, the evaluation, and the disposition. Here's what belongs in each.

Section 1: The Request (Contractor Fills This Out)

The contractor should provide the specified plant—genus, species, cultivar, container size or caliper, and the spec section number (typically Section 32 93 00 for exterior plants under MasterFormat). They document why the substitution is needed: unavailability, lead time, cost differential. If it's a cost substitution, require them to state the price difference in writing. They propose the replacement with the same level of botanical specificity, and they certify that the proposed plant meets the same mature size, water use zone, and hardiness zone requirements.

Requiring this from the contractor is intentional. You are not doing their sourcing research for them.

Section 2: The Evaluation (Your Firm Fills This Out)

Your reviewer checks the proposed plant against four criteria: mature form and size, WUCOLS water use category or equivalent, USDA hardiness zone, and any project-specific requirements (LEED credits, MWELO compliance, invasive species restrictions). For LEED v4 projects pursuing SSc Rainwater Management or BD+C credits, a substitution to a higher water-use species can affect compliance—that needs to be caught here, not during a certification audit.

Add a field for aesthetic judgment. "Meets design intent" is subjective but it belongs in the record. Note whether the substitution was reviewed against the planting plan context, not just the plant schedule in isolation.

Section 3: Disposition

Approved / Approved as Noted / Rejected. If approved as noted, specify the conditions—caliper minimum, container size, source nursery restrictions, or a requirement to resubmit a revised plant schedule. Include a signature line, date, and a reference number that ties back to your submittal log.

A Comparison: Minimal vs. Complete Form

Field	Minimal Form	Complete Form
Specified plant (botanical name + cultivar)	✓	✓
Spec section reference	—	✓
Reason for substitution	✓	✓
Proposed plant (botanical name + cultivar)	✓	✓
Mature size comparison	—	✓
Water use category	—	✓
Hardiness zone confirmation	—	✓
Price differential	—	✓
LEED / MWELO impact noted	—	✓
Reviewer signature + date	✓	✓
Submittal log reference number	—	✓

Minimal forms get used. Complete forms get defended in disputes.

How to Set Your Review Fee Policy

Most firms don't charge for substitution reviews. That's a mistake, especially on large projects where a single planting plan might generate 15 to 20 substitution requests across a 14-month construction schedule.

A reasonable structure: the first two substitution reviews per project are included in the CA fee. Each subsequent review is billed at your standard hourly rate with a 1-hour minimum. At a billing rate of $145/hour for a project manager, that's $145 per substitution after the first two. On a project with 18 substitution requests, that's potentially $2,320 in recoverable CA time that most firms leave on the table.

Document this policy in your CA scope of services before construction starts. Reference it in your contract exhibit. When the contractor submits substitution number three, send the form with a note that review time will be billed per the contract. You will get pushback exactly once.

Connecting the Form to Your Submittal Log

Every plant substitution request should generate a submittal log entry. This is not optional on a well-run project. The substitution gets a submittal number (many firms use a sub-numbering system: if the original plant schedule submittal is 32-001, the first substitution request is 32-001-SR-01), a received date, a required response date, and a disposition date.

Without this connection, substitutions fall into a documentation gap. They're not quite RFIs, they're not quite standard submittals, and they end up in a folder of PDFs that nobody can reconstruct at project closeout. Tying them to the submittal log means they appear in your project record, they show up in status reports, and they have a clear owner responsible for response.

Response time matters too. A 10-business-day review window is standard. If the contractor needs a faster turnaround because of a planting window, that's an expedited review and it should be flagged—and potentially billed—accordingly.

Common Mistakes Firms Make with Plant Substitutions

Accepting substitutions without a form. Verbal approvals and email chains are not documentation. When a contractor's super says "your PM said it was fine," you need something more than a text message from eight months ago.

Letting the contractor define the evaluation criteria. If the contractor's substitution request says "similar plant, same size," that's not an evaluation—it's an assertion. Your form should require botanical specificity and force comparison against the actual spec criteria.

Failing to check invasive species lists. A proposed substitution that looks innocuous—say, Ligustrum lucidum instead of a specified Olea europaea 'Wilsonii'—may be on the county invasive list. This check takes two minutes and should be a required field on the form.

Not updating the record drawings. Approved substitutions need to make it into the as-built plant schedule. Firms that track substitutions informally often end up with record drawings that don't reflect what was actually installed.

Treating all substitutions as equal. A substitution from one Cercis canadensis cultivar to another is not the same risk as substituting a Betula nigra for a specified Quercus lobata in a drought-tolerant scheme. Your form should prompt the reviewer to assess the magnitude of the change, not just check boxes.

Missing the MWELO or LEED impact. On regulated projects in California, substituting a plant with a higher ETAF value can push the project out of MWELO compliance. This is a project-level risk, not just a plant selection preference.

How Phasewise Handles This

Phasewise includes a submittal log built specifically for landscape architecture CA workflows, which means plant substitution requests can be logged, numbered, and tracked alongside standard submittals without creating a separate spreadsheet that goes stale. The response-due-date tracking surfaces overdue reviews before they become contractor complaints. If your firm uses Phasewise for project management, substitution requests live in the same project record as your RFIs and meeting notes—not in a separate email thread.