Conceptual Trail Design
Scope Tip
Clearly define the level of detail and intended use of the conceptual trail plan. A conceptual plan should establish the proposed trail concept, character, and general location without creating an expectation that specific trail alignments have been field designed or that the project is 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:
Planning area and purpose of the conceptual trail plan.
Proposed trail system, connections, destinations, or other elements to be developed conceptually.
Intended trail users, experiences, trail types, and applicable design criteria.
Required level of detail for proposed trail locations, recognizing that conceptual trail locations do not establish final field alignments.
Required alternatives or concepts to be developed and evaluated.
Known or anticipated control points, opportunities, constraints, connections, and areas to avoid.
Required desktop analysis, GIS analysis, mapping, field investigation, or ground-truthing.
How existing trails, roads, facilities, infrastructure, or other site elements should be incorporated or addressed.
Required coordination with landowners, agencies, stakeholders, or other project partners.
Required level of cost estimating, permitting, constructability, or implementation analysis.
How the conceptual plan will be used to support subsequent decisions, approvals, permitting, budgeting, field design, or other project development.
Required maps, GIS data, graphics, recommendations, and other deliverables.
Owner-Provided Information
The owner should provide the following, if available and applicable:
Existing plans, studies, reports, assessments, or previous trail concepts.
Available mapping, GIS data, surveys, aerial imagery, topographic data, or property information.
Information on existing trails, roads, facilities, infrastructure, access points, destinations, and land uses.
Known control points, opportunities, constraints, connections, or areas to avoid.
Known land ownership, easements, agreements, or jurisdictional boundaries.
Known environmental, cultural, regulatory, permitting, or resource constraints.
Applicable agency or land-manager plans, policies, standards, or design criteria.
Previous stakeholder, agency, landowner, or public engagement and relevant findings.
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.