CRD TRANSPORTATION SERVICE REQUISITION TRIGGERS Policy
CRD policy outlining the financial triggers and maximum requisition amounts for different phases of the transportation service.
CAPITAL REGIONAL DISTRICT CORPORATE POLICY AND PROCEDURES
| Section | Regional and Strategic Planning | |
|---|---|---|
| Subsection | Policies, Procedures, Manuals | (policy #) |
| Title | TRANSPORTATION SERVICE REQUISITION TRIGGERS |

POLICY:
The CRD has authority under Service Establishment Bylaw 4093 to requisition funding for transportation services. This policy outlines the triggers and process to be satisfied prior to the CRD Board requisitioning above the base level, yet within the maximum requisition level, to fund priority transportation projects. This policy should be used to identify the circumstances under which funding above the requisition base level may be considered and to clarify the possible maximum requisition levels for the various phases of service development.
PURPOSE:
The purpose of this policy is to describe the requisitioning process, including the identification of triggers for requisitioning above the amount needed to fund existing CRD transportation functions, also referred to as the base level of the transportation service. The policy places parameters around funding requests for new and expanded transportation functions.
RESPONSIBILITIES:
This policy will be administered by the Regional and Strategic Planning Division.
SCOPE:
The policy applies to funding associated with expansion of the transportation service as outlined in Service Establishment Bylaw No. 4093. The policy will be used by staff to inform future planning and recommendations to the CRD Board and by CRD Board members to inform future decision making related to transportation funding.
PROCEDURE:
The transportation service is reflected in three phases of service development:
- Existing functions 2a. New non-infrastructure functions 2b. New and/or expanded infrastructure functions and
- Regional transit governance and administration
The following table identifies triggers for transportation service requisition increases along with the maximum requisitions for each of the service development phases.

| Phase | Trigger(s) | Maximum Requisition |
|---|---|---|
| Phase 1 Existing Functions |
Service Bylaw Adoption | As per existing service budgets |
| i. Transportation, policy, plans, surveys and studies | “ | “ |
| ii. Regional trails planning, operations and maintenance, capital planning and tenure | “ | “ |
| iii. Transportation data collection, monitoring, analysis and reporting | “ | “ |
| iv. Transportation modelling | “ | “ |
| Phase 2a.* Additional functions – non infrastructure |
New function identified in Board-adopted Service Plan, post Service Bylaw Adoption | A property value tax rate of $0.036 per one thousand ($1,000) dollars applied to the net taxable value of land and improvements in the Service Area. (approximately 3 million in 2016 dollars) |
| i. Transportation web based and multi-media platforms | “ | “ |
| ii. Active transportation programming, planning and promotion | “ | “ |
| iii. Transit partnerships, data gathering, analysis and policy | “ | “ |
| Phase 2b.* i. Additional functions - transportation infrastructure, funding applications and partnerships ii. Regional Trails Expansion |
New function identified in Board-adopted Service Plan, post Service Bylaw Adoption At minimum matching funds from other levels of government and/or agencies or Board motion to fund |
A property value tax rate of $0.119 per one thousand ($1,000) dollars applied to the net taxable value of land and improvements in the Service Area. ($10 million in 2016 dollars) |
| Phase 3** Regional Transit Governance and Administration |
i. Provincial legislation change – BC Transit Act ii. Amendment to Service Establishment Bylaw No. 4093 iii. Provincial funding assurances |
* The sequencing and timing of phases 2a. and 2b are at the will of the CRD Board. ** Dependent on provincial legislation, the sequencing and timing of Phase 3 is at the will of the CRD Board.
| Approval Date: | Approved By: |