SECTOR 03 / PLACES, MARINAS & DESTINATIONS
A successful waterfront has to work from both directions: for the people arriving from the land and the vessels arriving from the water.
THE SHORT ANSWER
Waterfront development brings land uses, water access, infrastructure, public space, and ongoing operations into one project. A useful plan explains not only what will be built, but who can use it, how it connects to the water, and who will operate and maintain it. Start with the site, its users, and the responsibilities at the land–water edge.
A waterfront is more than a real estate project. Its operating plan matters as much as the place itself.
A practical framework for concession roles, guest experience, shared facilities, deliveries, utilities, and operating responsibilities.
Waterfront development can combine public space, marine access, commercial uses, utilities, and active operations. A site can look coherent in a concept plan while leaving unresolved how service vehicles enter, where passengers queue, or who maintains shared facilities.
Distinguish the developer, planner, engineer, construction team, and eventual operator. An adviser who creates an operating plan is not necessarily the company acquiring land or constructing the pier. Ask providers to name their role and their interfaces.
| Brief | Questions it answers | Common mismatch |
|---|---|---|
| Place and access | Who visits and how do they move? | Visitor routes cross deliveries or boarding queues |
| Marine and infrastructure | Which vessels, berths, utilities, and assets? | A destination concept assumes unverified water access |
| Operating and commercial | Who opens, staffs, maintains, and earns? | Shared areas have no funded maintenance owner |
Walk through one busy arrival, a waste collection, a routine repair, a concession delivery, and a service interruption. Record the places where two users need the same space or two contractors assume the other is responsible. That list is an agenda for the project team.
Moffatt & Nichol publishes urban waterfront planning and coastal engineering capabilities; Land & Sea describes destination and operating-plan work. Those are different entry points into a project team. Our company index separates the published scope from the questions an owner still needs to resolve.
These are editorial decision gates, not a jurisdiction-specific approval sequence. The project team needs to establish applicable permissions, studies, and professional responsibilities for the actual site. Use the gates to expose decisions; do not substitute them for the local project process.
| Stage | Decision to make | Evidence before moving on |
|---|---|---|
| 1. Define the place | Which needs and uses should this site support? | Users, current activity, site context, and project purpose |
| 2. Test the constraints | Which assumptions need specialist investigation? | Known access, assets, conditions, and an investigation plan |
| 3. Compare concepts | Which combination of uses is worth developing? | Operating scenarios and a consistent alternatives comparison |
| 4. Develop the interfaces | How will land, water, utilities, and people connect? | Roles, requirements, circulation, and unresolved dependencies |
| 5. Prepare for delivery | What must be designed, procured, and handed over? | Packages, decision owners, acceptance evidence, and sequence |
| 6. Open and operate | Who runs, maintains, and improves the place? | Usable records, trained owners, reporting, and a funded operating plan |
Start by separating land development from marine infrastructure and ongoing operation. A development manager may coordinate property, capital, and delivery. Planners and designers shape uses and public space. Engineers assess and design the physical interfaces. The future operator tests how staffing, servicing, maintenance, and customer activity fit together.
Ask prospective firms which role they will actually perform and which work they assume is provided by others. A broad “waterfront development” claim can describe very different services. An adviser developing a concession offer is not the same appointment as a marine structural engineer assessing a pier.
Moffatt & Nichol publishes waterfront planning and marine structural capabilities; Land & Sea describes destination and operational planning. Those published scopes provide different research starting points. Compare the proposed individuals and assignment, then identify who will coordinate the boundaries between them.
Waterfront Alliance’s voluntary WEDG framework organizes waterfront design around resilience, ecology, and access. It is a useful primary reference for widening a project conversation beyond buildings and berths. Using it as a discussion resource does not mean a project has been verified or that the framework replaces applicable requirements.
For the owner’s brief, ask who needs access to the place, what activities and natural features already exist, and which changing conditions the design team needs to examine. Record the source of each assumption. Community access, vessel activity, maintenance access, and visitor programming can place different demands on the same edge.
EPA’s Community-Port Collaboration Toolkit provides resources for understanding stakeholder priorities and working through port-related issues. The practical lesson for a project team is to maintain a visible record of who has been engaged, what they have said, and which decisions remain open. This is more useful than labeling a concept “community-led” without documenting the process.
There is no credible universal cost per waterfront project without a site, scope, and price basis. Compare capital assumptions and the operating plan together. A concept may be affordable to construct while leaving the owner with an unfunded maintenance or staffing obligation. Ask the cost team to distinguish confirmed information, estimates, allowances, and exclusions.
| Cost area | Questions for the project team | Often missed in a concept budget |
|---|---|---|
| Existing assets and conditions | What is known and what requires investigation? | Work assumed unnecessary before evidence is available |
| Water access and infrastructure | Which vessels, berths, utilities, and interfaces? | Changes to one interface causing work in another package |
| Public and visitor space | Who uses it, at what times, and how? | Cleaning, storage, lighting, and service access |
| Concessions and facilities | Which operator provides and maintains each item? | Shared responsibilities without a paying owner |
| Opening and ongoing care | Who staffs, supports, replaces, and reports? | Mobilization, lifecycle upkeep, and usable asset records |
Illustrative concept: a pier will serve a passenger ferry, a food concession, occasional events, and a public promenade. The attractive rendering shows all four uses. The useful next question is what happens when a ferry arrival, a food delivery, and an event queue occur at the same time.
Walk each activity through the site. Mark passenger holding space, visitor circulation, service access, waste storage, staff facilities, and maintenance routes. Record who can change an arrangement and who must be informed. If a concession delivery depends on access through the boarding area, the design and operating teams have a specific interface to resolve.
The output is not simply a revised picture. It is a circulation sketch, a shared-space schedule, and a responsibility list. Some conflicts may be addressed through design, others through service timing or operating agreements. The appropriate solution needs project-specific assessment; the value of the example is making the conflict visible before opening.
A concession should fit the destination’s users and the rhythm of the operation. Define the offer, the hours, the arrival peaks, and the owner’s expectations for the shared environment. Then examine the less visible work: deliveries, utility connections, storage, cleaning, waste, and the process for resolving an exception.
Destination programming changes the use of space over time. A normal weekday, a busy weekend, and an event can have different service patterns. Give the operating team those scenarios while decisions about access and shared facilities are still adjustable. Do not assume that an event operator, concessionaire, and property owner use the same definition of responsibility.
Keep commercial questions alongside operating questions, with the relevant advisers reviewing project-specific terms. Our concession guide provides an interface schedule for discussions about services and space. It does not prescribe a lease or a particular procurement model.
List the information the operating team will need to maintain and use the site: asset identification, relevant design and equipment records, supplier arrangements, planned care, responsible contacts, and unresolved work. Agree what a usable record looks like. A large collection of files is not necessarily a usable maintenance handover.
Walk the first ordinary operating day and a busy-day scenario with the people who will own the work. Assign responsibility for shared paths, furniture, utilities, visitor facilities, and interfaces with vessel activity. Confirm how the operator will raise a defect or request an owner decision after opening.
The development process should leave the owner with more than a completed place. It should leave a clear account of who operates it, who pays for its shared services, what evidence is available, and which commitments need ongoing review.
TAKE IT INTO YOUR NEXT MEETING
Use these prompts to turn the research into a specific assignment. Capture what is known, what still needs evidence, and who owns the next decision.
Plain text. No signup. Save, edit, or share it with your project team.
The scope may involve land-use planning, operating requirements, concessions, infrastructure coordination, or project advisory. Clarify whether the provider advises, designs, builds, owns, or operates.
Early enough to test access, staffing, deliveries, maintenance, and revenue assumptions while the design and operating model can still change.
A useful decision sequence is to define purpose and users, test constraints, compare concepts, develop land–water interfaces, prepare delivery packages, and hand over to an operating team. The actual planning and approval process depends on the site and jurisdiction.
A meaningful estimate needs site evidence and a defined scope. Existing conditions, marine infrastructure, utilities, public space, concessions, and ongoing operations all affect the cost. Ask for the price basis, exclusions, and assumptions instead of relying on a universal per-project figure.
A developer may coordinate the property, capital, and delivery. A consultant may provide defined planning, engineering, operational, or commercial advice. Some organizations take several roles, so identify the actual responsibility in the proposed appointment.
WEDG is Waterfront Alliance’s voluntary rating system and guidance for waterfront resilience, ecology, and access. It can inform a project conversation; verification is a separate process, and the guidance does not replace applicable requirements.
Map both activities in the same operating scenarios. Include busy arrivals, deliveries, waste, maintenance, and events, then assign owners to unresolved overlaps. The team can assess design, scheduling, and operating options against the actual site.
The sources below document published capabilities, programs, or frameworks. Decision tools, scenarios, calculations, and procurement prompts are our editorial analysis. Illustrative examples are not completed client projects.