April 24, 2026·7 min read

Landscape Architecture Submittal Log: Best Practices for 2026

How to run a submittal log for landscape architecture projects. Covers required fields, numbering systems, tracking workflows, response-time targets, ball-in-court protocols, and the mistakes that turn a submittal log into a liability instead of a tool.

A submittal log is the single most-used document during the Construction Administration phase of a landscape architecture project. Done well, it prevents missed deadlines, catches substitution attempts, and protects the firm during disputes. Done poorly, it becomes a source of confusion — or worse, legal exposure. This article walks through the best practices firms actually use.

What a submittal log does

A submittal log tracks every material, product, and shop drawing the contractor proposes to install on the project. The LA reviews each submittal against the CDs and specifications, then approves, rejects, or requires revision.

For landscape architecture projects, typical submittals include:

Plant material (every species, size, quantity, source)
Irrigation equipment (controllers, valves, heads, pipe, drip components)
Hardscape products (pavers, natural stone, concrete mixes, bases, joint materials)
Site furnishings (benches, bike racks, trash receptacles)
Lighting fixtures and controls
Soil amendments and mulch
Seed mixes
Tree protection materials
Structural components (walls, steps, railings, pergolas)
Drainage components
Wayfinding and signage

On a medium-sized commercial project, expect 30–80 submittals. On a large resort or public park, 150+.

Required fields for every submittal

Minimum data points you need to track:

Field	Why it matters
Submittal #	Reference point for all future correspondence
Date received	Starting point for the response-time clock
Date due	Contract-specified response window (typically 10 business days)
Specification section	Links submittal to the relevant spec (e.g., 32 93 00 for plants)
Item description	Short human-readable description
Contractor / subcontractor	Who submitted and who's installing
Status	Pending / In Review / Approved / Approved as Noted / Revise & Resubmit / Rejected
Ball in court	Whose action is next (LA, contractor, owner)
Date returned	When the LA sent the response
Resolution	Link to the stamped submittal + review comments

A log missing any of these fields is incomplete. You'll regret it during a dispute.

Submittal numbering

Use a consistent numbering system so the log is scannable. Two common approaches:

Method A: Sequential

SUB-001, SUB-002, SUB-003, ...

Simple, works fine for small projects.

Method B: Spec-section-prefixed

32-93-00-01 (first plant submittal)
32-93-00-02 (second plant submittal)
32-91-00-01 (first soil preparation submittal)

Scales better on large projects. Makes it easy to find all submittals for a specific spec section.

Pick one and stick to it for the whole project. Don't mix.

Response time targets

The contract typically specifies 10 business days for submittal response. Target faster:

Routine submittals: 5 business days (nothing blocking construction)
Critical-path submittals: 3 business days (plant material for a phase about to be installed)
Resubmittals: 3 business days (you already reviewed once)

If the LA is the bottleneck, the GC will weaponize it during delay claims. Fast responses are cheap insurance.

Ball-in-court protocol

"Ball in court" is who has the next action. Only one party can hold the ball at any time. Clear handoffs prevent items from sitting in limbo.

Standard workflow:

GC sends submittal → Ball in court: LA
LA reviews → if questions, sends to owner or consultant → Ball in court: Owner/Consultant
Owner responds → Ball in court: LA
LA stamps and returns → Ball in court: GC
GC resubmits (if required) → Ball in court: LA

Every transition gets a timestamp in the log. If an item sits with one party for 10+ days, escalate.

Submittal response actions — what each means

Different firms stamp different things, but the general convention:

Approved — Proceed with installation as submitted. No changes required.
Approved as Noted — Proceed with the minor changes marked in red. Contractor does NOT need to resubmit.
Revise and Resubmit — Submittal has substantive problems. Contractor must correct and resubmit. Installation cannot proceed based on this submittal.
Rejected — Submittal is fundamentally wrong or unresponsive to the CDs. Contractor must start over.
Reviewed — (Sometimes used for informational submittals that don't require approval.)

Be explicit in your stamp wording. Ambiguity creates disputes.

Substitutions — the highest-risk category

The single most common submittal problem is contractors proposing substitutions. The CDs spec "Quercus agrifolia 24"box", the contractor submits "Quercus douglasii 15-gallon" from their preferred nursery, hoping nobody notices.

Protocol:

Every substitution requires a separate substitution request form with justification
Review against the original spec, not just the submitted product
Flag any difference in species, cultivar, size, container, source, or growing conditions
Reject silent substitutions — require the contractor to submit the correct spec first, THEN submit a substitution if needed
Copy the owner on substitution reviews — they're approving a change to what was specified

Failing to catch substitutions is how you end up with a punch list full of issues that the contractor claims were "approved."

Common submittal log mistakes

Tracking in email instead of a log

Email threads are linear, searchable only by keyword, and get lost. Any CA dispute will require you to prove what was submitted, when, and what you said. Email is a bad record.

No due dates

Without due dates, submittals drift. 30 days later, you're being blamed for schedule delays you didn't cause.

No ball-in-court discipline

Without explicit ball-in-court tracking, two parties both think the other is handling it. 2 weeks later, nobody has moved.

Stamping without reading the specs

Every submittal must be reviewed against the spec section, not just the attached cut sheet. The cut sheet shows what the contractor claims to be submitting. The spec is what was actually required.

Not archiving stamped submittals

At closeout, you need to hand the owner a complete set of approved submittals as part of the as-built package. If they're scattered across email, reconstructing the set takes days.

Verbal approvals at site meetings

If you said "yeah, that paver looks fine" at a site meeting, and the contractor installs 10,000 sq ft of it, and the owner hates it — good luck. Written approvals only.

Keeping the log current during CA

Plan the submittal workflow into the CA schedule:

Weekly review meeting (internal): 30 minutes to scan the log. Flag overdue items, assign action to specific staff.
Weekly update to owner: Short email with submittal status (count approved, count pending, count overdue). Keeps owner informed without requiring them to chase.
Monthly CA hours review: Compare submittal log turnaround to CA hours used. If submittals are slow AND hours are burning fast, something is wrong with the review workflow.

What a well-run submittal log looks like at closeout

When the project closes, hand the owner a single package containing:

Complete submittal log (PDF or spreadsheet)
All stamped submittals in one PDF or organized folder
Substitution requests with approvals
Any RFIs referencing submittals

This is part of the as-built deliverable. A clean package makes the closeout walk easier and reduces the chance of post-occupancy disputes.

Tools for running a submittal log

Options range from simple to sophisticated:

Shared spreadsheet (Google Sheets / Excel) — works for small projects, doesn't scale
Procore / PlanGrid — robust but expensive and architect-oriented
Firm-built Airtable or Notion — flexible but requires ongoing maintenance
Phasewise Submittal & RFI module — purpose-built for LA firms, includes auto-reminders for overdue items, full audit history, filterable by status/project/responsible party

The right tool is the one your team will actually update. The most sophisticated tool is worthless if staff bypass it.

How Phasewise handles submittal logs

The Phasewise Submittal & RFI module ships with:

CRUD log with all required fields pre-built
Status tracking (Pending → Under Review → Approved / Rejected / etc.)
Ball-in-court tracking with timestamps
Automatic overdue reminders emailed daily (via Vercel Cron)
Filtering by project, status, responsible party, or overdue flag
Full history so you can see every change for each item
Tied to the project so you can see CA workload across active jobs

That removes the manual tracking overhead so your CA hours go to actual review work, not spreadsheet maintenance.