Landscape Architecture Has a Project Management Problem — And It Gets Worse When You're Prime

Ask a principal at a landscape architecture firm why a project underperformed, and the answers are consistent: the agency required three more review cycles than anticipated, the civil grading changed after the planting plan was complete, the owner added sports lighting and irrigation systems after the fee was set, and the contractor substituted plant material that required redesign.

All of those things happened. None of them is the root cause.

The root cause is that landscape architecture fees are based on a scope that assumes a linear design process, a predictable agency review timeline, and, when the LA firm is a subconsultant, a manageable coordination role. When the firm serves as prime on a public park, greenway, or sports complex, the financial exposure is fundamentally different. The LA firm becomes responsible for managing civil, structural, electrical, and irrigation consultants; coordinating their deliverables; carrying the associated liability; and billing their fees to the public agency client.

That presents project management and financial challenges on a completely different scale from those of a subconsultant role on a private development project. When the LA firm holds the prime contract, it carries the full liability for civil, structural, electrical, and irrigation consultants simultaneously. Each consultant creates a committed financial obligation when the client is invoiced, not when the consultant requests payment. Most project management tools were never built to surface that liability in real time. The firms that run profitable landscape architecture projects have systems that do.

→ Read: Project Management for A/E Firms: How to Control Scope, Fees, and Profit

Why Landscape Architecture Projects Are Financially Harder to Manage Than They Look

Landscape architecture carries a specific set of financial risks that generic project management tools, and even many A/E-specific tools, consistently fail to surface.

Public agency review cycles are unpredictable and often multiply without triggering fee adjustments. City parks, greenways, recreation areas, and sports complexes are frequently reviewed by multiple agencies, including parks departments, planning commissions, public works departments, stormwater authorities, and sometimes federal agencies when wetlands or federal funding are involved. Each agency has its own review schedule, comment patterns, and required response format. A single agency resubmittal cycle can consume weeks of design time. Three resubmittals across two agencies are not unusual, yet they are almost never included in the original fee.

Planting plan revisions are often driven by decisions in other disciplines. Civil engineering changes can shift drainage patterns, alter slope conditions, and affect planting zones. Hardscape revisions requested by the architect or owner can change planting areas and bed configurations. Irrigation system changes can affect plant selection and grouping. Each revision requires the landscape architect to revisit plant schedules, spacing, and specifications. The work originates with another discipline's decisions but consumes the LA firm's hours. Without a clear process for additional services, those hours are absorbed.

When the LA firm is prime, subconsultant liability often remains invisible until pay requests arrive. On public agency projects where the landscape architect holds the prime contract, the firm is responsible for contracting with civil, structural, electrical, and irrigation engineers. Each consultant relationship creates an obligation to pay for work performed. That obligation exists when the client is invoiced for the phase, not when the consultant submits a pay request.

A public agency project with $400,000 in engineering subconsultant fees flowing through the prime LA firm creates $400,000 in committed obligations. Most project management systems will not show those obligations until pay requests arrive. When civil, structural, and electrical engineers all submit pay requests at the same phase milestone, as they routinely do, the firm suddenly finds itself managing obligations it should have tracked for months.

Plant material availability creates surprises in construction administration. Specified plant material is frequently unavailable at the time of installation due to nursery supply constraints, seasonal availability, or regional shortages. Contractor substitution requests require the landscape architect to evaluate whether proposed substitutes are equivalent in species, size, form, and design intent. On a large public park or sports complex project, substitution review volume can be substantial. It is almost never scoped as a standalone CA service.

Seasonal installation windows create schedule-driven CA demands. Planting work tied to spring or fall installation windows, which maximize establishment rates, concentrates construction administration demands in specific periods. When a project's construction schedule shifts and the planting window compresses, demands on the landscape architect intensify during a period that may already be busy with other projects. Fees that do not account for concentrated CA activity consistently underperform.

Phased project delivery creates scope gray areas between contracts. Large greenways, park systems, and recreation complexes are frequently delivered in phases under separate contracts. Each phase builds on earlier work, so the landscape architect is regularly asked to review, coordinate, and update prior-phase documents while delivering the current phase. That work does not fall cleanly inside or outside the current contract scope. Without a scope of services that explicitly defines the boundary and a project management system that tracks prior-phase coordination hours against the current phase budget, the effort is quietly and consistently absorbed on every phased project the firm undertakes.

→ Read: Scope Creep in Architecture Projects

The Five Places Landscape Architecture Project Management Actually Breaks Down

Profitability problems on landscape architecture projects almost always trace back to one of five structural failures.

1. Agency review cycles beyond the first are not scoped as additional services.

Most landscape architecture proposals include one or two agency review and resubmittal cycles in the base fee. Public agency projects routinely require more. Planning commission reviews generate comments that require design revisions before public works will accept the civil package. Parks department reviews generate comments that require revisions to the planting plan before the irrigation engineer can finalize the system design.

Each additional review cycle requires real design and coordination time. When the proposal does not define the number of included cycles or establish additional cycles as billable services, every extra cycle is absorbed. The firm may have a basis for billing additional review time, but public agency clients often expect review cycles to be included and may resist additional service claims unless the scope language clearly supports them.

2. Cross-discipline revision hours are never captured as additional services.

Grading changes, hardscape revisions, and utility conflicts that require planting plan updates originate in another discipline's work. From the client's perspective, the landscape architect is simply keeping the planting plan current. From the firm's perspective, the landscape architect is performing work outside the original scope because another discipline's decisions changed the design conditions.

Without a scope of services that defines what triggers a planting plan revision as an additional service, and without a project management system that tracks revision hours against the phase budget, this work disappears into the base fee on every project.

3. Prime-contract subconsultant liability is not tracked in real time.

When the landscape architect holds the prime contract on a public agency project, the firm assumes full liability for engineering subconsultant fees. That liability begins when the agency is invoiced, not when the subconsultant submits a pay request.

A landscape architecture firm managing a public park project with civil, structural, irrigation, and electrical engineers has multiple consultant liability streams running simultaneously. If those liabilities are only visible when pay requests arrive, the firm's apparent cash position is consistently more optimistic than the real position. A billing cycle that looks strong can become a cash flow problem when three engineering pay requests arrive in the same week at phase closeout.

4. Public agency billing formats create administrative overhead not priced in the fee.

Public agency projects frequently require specific billing formats and documentation, including certified payroll records, DBE reporting, progress billing certifications, Schedule of Values updates, and formal change-order processing for scope additions. That administrative work takes time. It is rarely included in the fee because it is not design work and because the full burden of public agency billing is difficult to see at the proposal stage.

A landscape architecture firm that has billed private development clients for years will systematically underprice the administrative component of its first major public agency project. The administrative hours accumulate quietly against a fee that was never structured to cover them.

5. Maintenance specification additions are treated as design continuation rather than new scope.

Owners frequently add maintenance specifications, long-term care plans, and plant establishment monitoring requirements after the design fee is set. On public agency projects, these additions may be driven by grant requirements, agency standards, or post-design policy decisions that the landscape architect could not have anticipated at proposal time.

Adding a three-year establishment monitoring program to a planting specification priced as a static document is a meaningful scope addition. Because it is delivered as a document revision rather than a new design phase, it is routinely absorbed into the base scope, even when the monitoring requirement adds weeks of specification writing, field observation, and reporting.

→ Read: How to Track Project Progress Without Breaking Billing

What Good Project Management Software Actually Does for Landscape Architecture Firms

A landscape architecture firm holding a prime contract on a public agency project manages financial complexity closer to that of a general contractor than a typical design subconsultant. The proposal must feed the phase budgets. Those budgets must reflect time as it is logged, and logged hours must flow into billing. Billing must then surface the obligations it creates for subconsultants. The entire chain must be visible in real time, not reconstructed at month's end from disconnected systems.

When that chain is intact, project management shifts from reactive to predictive. When it is not, the prime LA firm makes decisions about cash, staffing, and whether to pursue the next phase using a financial picture that is always at least one billing cycle behind reality.

For a landscape architecture firm specifically, that means:

• Tracking time separately by phase so agency review, planting plan revision, and CA hours remain visible against their own fee allocations rather than being pooled in a single project total.
• Showing immediately when review or revision hours consume fees allocated to another phase, allowing the project manager to discuss additional services while the work is still in progress.
• Tracking subconsultant liability from the moment the client is invoiced, rather than when a pay request arrives, so the prime LA firm always knows how much billed revenue is already committed to engineering subconsultants.
• Supporting public agency billing formats and their administrative requirements without creating a separate process disconnected from the project's financial picture.
• Making additional services easy to identify and bill so planting plan revisions driven by civil grading changes, extra agency review cycles, and maintenance specification additions become revenue rather than absorbed costs.

Most general project management tools meet none of these needs for landscape architecture work. Most accounting tools meet only one or two. The gap between what those tools provide and what a prime landscape architect managing a multidisciplinary public agency project needs is where margin disappears. It happens gradually but consistently through every untracked agency review cycle, unbilled planting revision, and engineering pay request that arrives before the liability is visible.

The firms that run profitable landscape architecture projects for public agencies are not the ones that scope every detail perfectly at the proposal stage. They are the ones with systems that reveal the financial consequences of every scope change, agency review cycle, and subconsultant obligation while there is still time to act.

→ Read: Subconsultant Liability: The Cash Flow Risk Most A/E Firms Don't See Coming

→ Read: BaseBuilders vs BQE Core

→ Read: BaseBuilders vs Monograph