Conceptual Trail Design
Scope Tip
Clearly define the level of detail and intended use of the conceptual trail design. Conceptual plans should communicate the proposed trail concept, character, and key design elements without creating an expectation that the trail is fully designed or ready for construction.
Scope Item Definition
Develop a conceptual plan that establishes the proposed trail or trail system at a planning level, integrating project goals, stakeholder input, trail corridors, intended users and experiences, trail specifications, site conditions, management requirements, and other project considerations.
A conceptual trail plan communicates what is proposed and generally where it will occur, but does not establish the specific field-designed trail alignment or provide construction-ready design.
When / Where It Applies
A conceptual trail plan is typically developed as part of a trail planning project and may incorporate work completed through feasibility, stakeholder engagement, and trail corridor planning.
It provides a documented trail system or project concept that can be used to support decision-making, stakeholder and land manager review, cost estimating, permitting and environmental review, and subsequent field design.
Scope Considerations
Depending on the project, the scope should consider and clearly define:
Project purpose and goals: Incorporate the established project purpose, need, goals, management objectives, and desired outcomes.
Trail system and corridors: Document the proposed trail system, trail corridors, connections, access points, destinations, and other key features.
Trail users and experience: Define intended trail users, uses, difficulty, desired experience, and other user-related considerations.
Trail specifications: Establish planning-level trail specifications and design criteria, including trail type, width, grade, surface, difficulty, accessibility, and other applicable characteristics.
Control points: Document significant positive and negative control points that influence the proposed trail system and corridors.
Existing conditions and management requirements: Incorporate relevant site conditions, land management direction, natural and cultural resource considerations, property boundaries, existing infrastructure, and other known requirements or constraints.
Field investigation / ground-truthing: Clearly define whether the conceptual trail plan may be developed from desktop/GIS analysis and available information or whether proposed trail corridors and key plan elements are expected to be ground-truthed or field-verified.
Stakeholder input: Incorporate relevant findings from stakeholder engagement and document how they informed the proposed plan, when applicable.
Mapping and spatial data: Define the required level of mapping, GIS/spatial data, and other graphical representation of the proposed trail system.
Alternatives: Identify and evaluate alternative concepts, corridors, connections, or system configurations when required.
Cost and implementation considerations: Identify planning-level project costs, priorities, phasing, or implementation considerations when included in the scope.
Permitting and approvals: Identify how the conceptual plan will support environmental review, permitting, land manager approval, or other required processes.
Next steps: Identify additional studies, field design, permitting, approvals, or other work required to advance the project.
Owner-Provided Information
The owner should provide the following, if available and applicable:
Project purpose, need, goals, and desired outcomes.
Defined project or planning area.
Previous feasibility, corridor planning, or stakeholder engagement findings.
Intended trail users and desired trail experience.
Applicable land and resource management plans, policies, and requirements.
Available GIS/spatial data, mapping, and aerial imagery.
Property, jurisdictional, and management boundaries.
Existing trail system information.
Known access points, destinations, connections, and control points.
Existing natural and cultural resource information.
Known permitting, environmental review, or approval requirements.
Available budget, schedule, or implementation parameters.
Deliverables
Depending on the scope, deliverables may include:
Conceptual trail plan and supporting narrative.
Maps showing proposed trail corridors, connections, access points, destinations, and other key features.
Planning-level trail specifications or design criteria.
Identification of intended trail users, uses, difficulty, and desired trail experience.
GIS/spatial data for proposed trails and associated features.
Documentation of the level of field investigation completed and identification of proposed corridors or plan elements that have not been field-verified.
Summary of significant control points and site considerations.
Alternatives considered and recommendations, when applicable.
Planning-level cost estimate.
Project priorities or phasing recommendations.
Permitting, environmental review, or approval considerations.
Recommended next steps for field design and project implementation.
Pricing & Payment Considerations
The solicitation should clearly define the anticipated level of effort and pricing considerations, including:
Size and complexity of the project area.
Approximate trail mileage or extent of the proposed trail system.
Planning and analysis included in development of the conceptual plan versus work already completed.
Number of concepts or alternatives to be developed and evaluated.
Information and GIS/spatial data provided by the owner versus information the contractor is expected to obtain or develop.
Expected GIS/spatial analysis, mapping, and plan development.
Number of site visits or anticipated field days.
Mobilization and travel requirements, including whether travel time and expenses should be included in the proposed price or reimbursed separately.
Stakeholder engagement, meetings, presentations, and coordination requirements.
Level of cost estimating and implementation planning required.
Number and format of draft and final deliverables and anticipated review/revision cycles.
Whether specialized resource or technical studies are included or will be provided separately.
Pricing may be structured as a lump sum or time and materials with a not-to-exceed amount, depending on how clearly the required level of effort can be defined.
Common Scope & Contracting Issues
Not clearly defining what is meant by a conceptual trail plan or the expected level of planning and design.
Expecting a conceptual plan to provide a specific field-designed or construction-ready trail alignment.
Not clearly identifying which planning activities—such as feasibility, stakeholder engagement, corridor planning, or trail specifications—are included in development of the conceptual plan versus already completed.
Not defining the approximate trail mileage, number of alternatives, or level of field investigation expected.
Assuming that corridors shown on a conceptual plan have been ground-truthed or field-verified when field investigation was not explicitly included in the scope.
Not clearly identifying which corridors or other plan elements have and have not been field-verified, particularly when the plan will inform subsequent permitting, design, or decision-making.
Not defining the required mapping, GIS/spatial data, or level of detail for plan deliverables.
Not establishing intended trail users, desired trail experience, or trail specifications needed to guide the plan.
Not defining the level of cost estimating, phasing, or implementation planning expected.
Not defining draft review, stakeholder or land manager review, and revision expectations.
Assuming the conceptual plan is sufficient for permitting, approval, bidding, or construction without identifying what additional design, technical studies, or documentation will be required.