June 12, 2026·7 min read

Landscape Architecture Submittal Log: A Practical Guide

A landscape architecture submittal log done right keeps projects moving. Here's how experienced PMs structure, track, and close out submittals without the chaos.

Submittal management is where a lot of otherwise well-run landscape architecture projects quietly fall apart. The design is solid, the contractor is capable, and then three weeks of back-and-forth over a decomposed granite spec sheet eats your construction schedule. A well-structured landscape architecture submittal log doesn't prevent all of that friction, but it does make sure you're not the reason the project stalls.

What a Submittal Log Actually Does

A submittal log is a living document that tracks every material sample, shop drawing, product data sheet, and mock-up that needs to flow between the contractor, your office, and sometimes the owner or other consultants. It records what was requested, when it was received, who reviewed it, what the disposition was, and whether a resubmittal is required. That sounds simple. In practice, on a project with 60+ line items across planting, hardscape, site furnishings, irrigation, and lighting, it becomes genuinely complex to manage without a system.

The log is also your liability record. If a contractor installs the wrong paver because they claim you never responded to their submittal, your log either proves you did or proves you didn't. That distinction has real consequences — I've seen disputes where the absence of a timestamped review record cost a firm a portion of their fee in settlement negotiations.

What Belongs in Every Log Entry

Each line item in your submittal log should capture the submittal number, the spec section it references, a description of the item, the date received, the date your review is due, the date you returned it, the disposition code, and any resubmittal tracking. Most firms use some version of the standard disposition codes: Approved, Approved as Noted, Revise and Resubmit, Rejected, and For Record Only.

The spec section reference matters more than people realize. When a contractor sends you a generic product data sheet for a concrete unit paver without referencing Section 32 14 00, it's easy for that item to float in your inbox without being tied to a spec requirement. Anchoring every submittal to a spec section forces clarity on both sides. It also makes your close-out documentation coherent when you're assembling the project record at the end of construction.

Setting Up the Log Before Construction Starts

The submittal log should exist before the contractor submits anything. During the construction documents phase, someone on your team should be building the preliminary submittal schedule — essentially a list of every item you expect to receive based on your spec sections. When the contractor submits their own submittal schedule early in the project (which most contracts require), you reconcile their list against yours.

This reconciliation step catches gaps. A contractor might not include a submittal for their proposed irrigation controller because they assume it's a standard item not requiring review. Your spec says otherwise. Catching that before construction starts is a five-minute conversation. Catching it after the system is roughed in is a change order negotiation. The preliminary log is also where you establish your review period — typically 10 to 14 business days is standard for landscape architecture submittals, though some owners push for less. Whatever you agree to, document it in the log header and reference it in your CA procedures.

Review Periods and Turnaround Commitments

Fourteen business days sounds like a lot until you're managing five active projects in CA simultaneously. The trap most project managers fall into is treating the review period as a target rather than a commitment. Submittals pile up, a priority project pulls your attention, and suddenly you have four items sitting at day 11 with no review started.

The log should flag items approaching their due date automatically, or at minimum be reviewed in a weekly CA meeting. Some firms assign a dedicated CA coordinator to manage the log across all active projects. That role pays for itself quickly on larger projects — a missed review deadline that causes a contractor to order the wrong material can generate a change order that dwarfs the coordinator's hourly cost. If you're a smaller firm without that capacity, the log review has to be a standing agenda item, not something you get to when you have time.

Handling Resubmittals Without Losing the Thread

Resubmittals are where logs get messy. A contractor submits Item 14 — decomposed granite, 3/8" minus, Class II. You return it as Revise and Resubmit because they didn't include the gradation test results. They resubmit. Now you have Item 14A. If your log isn't set up to link 14A back to 14, you end up with orphaned line items and no clear picture of whether the original issue was resolved.

The cleanest approach is a parent-child structure: the original submittal number stays the parent, and each resubmittal gets a suffix. Your disposition column for the parent item stays open until the resubmittal is approved. This sounds obvious, but plenty of firms just add a new row and lose the connection. On a project with 20 resubmittals across 60 items, that fragmentation makes it nearly impossible to answer a simple question: how many items are still open?

Coordinating Submittals Across Consultants

On most projects, you're not the only design professional reviewing submittals. Civil, structural, MEP, and lighting consultants may all have items in the queue. The general contractor typically routes submittals through a single log, but each design professional maintains their own review record. The coordination problem is that a site furnishing might require review by both your office and the structural engineer if it involves a footing design.

Establish clear routing protocols at the pre-construction meeting. Document which items require multi-discipline review, who gets the submittal first, and what the combined review period is. If the structural engineer needs five days to review a footing detail before you can complete your review of the furnishing package, your 14-day clock needs to account for that. Contractors will not give you the benefit of the doubt on this — they'll submit everything on day one and expect everything back on day 14, regardless of routing complexity.

Common Mistakes Firms Make

Using a spreadsheet with no version control. A shared Google Sheet or Excel file is better than nothing, but when two people edit it simultaneously and one overwrites the other's disposition entry, you have a problem. Firms that use spreadsheets should at minimum have a single owner for log edits, with others submitting updates by email or comment.

Not logging verbal approvals. A contractor calls, you tell them the sample looks fine, they proceed. No log entry, no email confirmation, no record. Three months later there's a dispute about whether you approved that specific product. Log every disposition, even informal ones, with a note about how the communication happened.

Setting unrealistic review periods under owner pressure. Agreeing to a five-day review turnaround to satisfy a fast-track schedule sounds cooperative. When you can't consistently hit it, you're in breach of your CA procedures and the contractor has grounds to claim your delays impacted their schedule. Negotiate realistic periods upfront.

Closing out the log before all resubmittals are resolved. It's tempting to declare the submittal process complete when construction is winding down. But if Item 31B is still technically open because the contractor never sent the revised product data, that's an unresolved item in your project record. Chase it down before substantial completion.

Treating the submittal log as separate from the project schedule. Submittal review periods are construction schedule activities. If the log isn't integrated with the master schedule, nobody sees the downstream impact of a delayed review. A two-week slip on an irrigation controller submittal can push the irrigation rough-in and cascade through the planting schedule.

Failing to track "For Record Only" items. Items submitted for record only don't require your approval, but they do need to be logged and filed. These become part of the project close-out record and are often requested during warranty claims or future renovations.

How Phasewise Handles This

Phasewise includes a submittal log module built specifically for landscape architecture CA workflows, with spec section tagging, disposition tracking, and resubmittal linking built into the structure. Review deadlines surface in your project dashboard so items don't age past their due date without someone noticing. The log ties directly to your project's phase and task structure, so a pending submittal review shows up as an active task rather than a line item buried in a spreadsheet tab. It won't replace your judgment on what to approve — but it does make sure nothing falls through the cracks while you're focused on the work itself.