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 set against 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 is prime on a public park, greenway, or sports complex, the financial exposure is fundamentally different. The LA firm is now responsible for managing civil engineers, structural engineers, electrical engineers, and irrigation consultants, carrying their liability, coordinating their deliverables, and billing their fees to the public agency client.

That is a project management and financial management challenge of a completely different order than a subconsultant role on a private development project. When the LA firm holds the prime contract, it carries the full subconsultant liability burden across civil, structural, electrical, and irrigation engineers simultaneously — each one creating a committed financial obligation the moment the client is invoiced, not the moment the consultant asks for 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

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 is real design and coordination time. When the proposal doesn't define a specific number of included cycles — and doesn't establish that additional cycles are a billable additional service — every cycle beyond the first is absorbed. The path to billing additional review time is there in principle. In practice, the landscape architect is in a client relationship with a public agency that expects review cycles to be included and will push back on 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 doing their job—keeping the planting plan up to date. From the firm's perspective, the landscape architect is doing work that was not in the original scope because another discipline's decisions changed the design conditions.

Without a scope of services that specifically defines what triggers a planting plan revision as an additional service — and without a project management system that makes hours logged to revision activities visible 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 is real from the moment the agency is invoiced — it does not begin 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 billing in specific formats — certified payroll documentation, DBE reporting, progress billing certifications, Schedule of Values updates, and formal change order processing for any scope additions. That administrative work is real-time. It is almost never included in the fee because it is not design work, and because the full administrative burden of public agency billing is not visible at proposal time.

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 that was 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 is managing financial complexity closer to that of a general contractor than to that of a typical design subconsultant. The proposal needs to feed the phase budgets. Phase budgets need to reflect time as it's logged. Logged hours need to flow into billing. Billing needs to surface the obligations it creates for subconsultants. And all of it needs to be visible in real time — not reconstructed at month's end from separate systems that don't share data.

When that chain is intact, project management stops being reactive and starts being predictive. When it isn't, the prime LA firm is making financial decisions — about cash, about staffing, about whether to pursue the next phase — from a picture that is always at least one billing cycle behind reality.

For a landscape architecture firm specifically, that means:

• Tracking time against phases separately — so agency review time, planting plan revision time, and CA time are all visible against their own fee allocations rather than pooled in a single project total.
• Making it immediately visible when review or revision hours are consuming the fee allocated for a different phase, so the project manager can have the additional services conversation while the work is still in progress.
• Tracking subconsultant liability from the moment of client invoicing — not from the moment a pay request arrives — so the prime LA firm always knows how much of its billed revenue is already committed to engineering subconsultants.
• Supporting public agency billing formats and the administrative overhead they require — without creating a separate administrative process disconnected from the project 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 cost.

Most general project management tools check none of these boxes for landscape architecture work. Most accounting tools check one or two. The gap between what those tools provide and what a prime landscape architect managing a multi-discipline public agency project actually needs is where margin disappears — not dramatically, but consistently, across every agency review cycle that wasn't tracked, every planting revision that wasn't billed, and every engineering pay request that arrived before the liability was visible.

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

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

→ Read: BaseBuilders vs BQE Core

→ Read: BaseBuilders vs Monograph