The Routing screen (window title “Routing Catchment From: n”) sets, for one catchment, where its water goes and which of its BMPs treats it in the routing. Use it to build treatment trains: send an upstream catchment to the catchment downstream of it, and its treated outflow becomes an input to the downstream catchment’s BMP.
The Routing is accessed through the Configuration Screen by clicking Edit on a specific Catchment.

Inputs
| Input | Units | What it means / how it is used |
|---|---|---|
| Select Catchment to Route to: | list | Outlet or any other catchment (the catchment itself is not offered). The outlet is catchment 0. A disabled catchment is listed with “(Disabled)” after it so you can find it, but it cannot be chosen: BMPFast says so and keeps the previous choice. To route to it, enable it first. This catchment’s outflow, after its BMP, is added to the input of the chosen catchment’s BMP. |
| Select BMP to use in routing: | list | The BMPs defined for this catchment on Select Treatment Options. The one chosen is the catchment’s default BMP: it is the one shown under BMP Used on the configuration screen and the one the routing calculation uses. Other defined BMPs are kept but not used in routing. |
| Delay Time (hr): | hr | Tooltip: “Commingling Delay time only used if routing to Retention System.” Stored on the selected BMP. |
Buttons
| Button | What it does |
|---|---|
| Edit Catchment n | Opens the Watershed Characteristics Worksheet for this catchment. |
| Edit BMP | Stores your choices and opens the input screen of the BMP selected for routing. |
| Disable Catchment / Enable Catchment | This removes a catchment from the routing, but leaves all catchment routing (from and to) as their initial values. The label beside it reads “Catchment Active” or “Catchment Disabled”; press again to enable it. A disabled catchment is grey on the configuration screen and is left out of the routing calculation. |
| Remove Catchment | This disables a catchment and routes any catchment that is directed to the catchment removed to the catchment the removed catchment was flowing to. BMPFast asks you to confirm first. The screen then closes. To undo, enable the catchment again and re-route the upstream catchments by hand. |
| Back | Stores the destination, the BMP used and the delay time, and closes. |
Close the screen with Back, the window’s X or Esc: each one stores the destination, BMP and delay time. Help opens this page.
How routing is calculated
BMPFast works through the network from the most upstream catchments to the outlet. Each catchment is a node:
- Inputs. A node receives its own catchment’s runoff volume (Q, ac-ft/yr) and N and P loads (kg/yr), plus the outflow of every catchment routed to it. At a junction (two or more catchments flowing into one) the upstream outflows are added together.
- Treatment. The node’s BMP is applied to the total input (unless the catchment bypasses upstream runoff, below). Volume-sensitive BMPs are recalculated with the routed inflow: for a wet detention the residence time comes from the total routed volume; for a retention-type BMP (Retention, Exfiltration, Tree Well, Swale, and the Vegetated Natural Buffer or Filter Strip set to Retention) its Treatment Volume is spread over the whole upstream watershed, Treatment Depth (in) = 12 × Treatment Volume (ac-ft) / total area draining to it, with the area-weighted curve number and DCIA (see Retention BMPs). Other BMPs use the efficiency they have on their own catchment.
- Output. What the BMP does not remove flows on to the next catchment, or to the outlet.
Applicant’s Handbook reference
Section 9.5.1 Treatment Train Nutrient Reduction (Equation 9-5): BMPs in series combine as 1 − [(1 − Eff1) × (1 − Eff2) × …], each acting on what the one above leaves; BMPFast does this with loads in kg/yr, which is Equation 9-5 in mass form and also handles junctions. Where a BMP’s removal depends on the water it receives (wet detention, retention), BMPFast recalculates it with the routed volume.
Source reference
BMPFast method (ComplexRouting.CalculateWithStrands, DomainCode/ComplexRouting.cs): the network is worked from the most upstream catchments to the outlet, adding flows and loads at junctions; spreading a routed retention BMP’s Treatment Volume over all the area draining to it, with the area-weighted curve number and DCIA, is BMPFast’s own method.
Strands. A run of catchments in series in which none receives water from more than one catchment is a strand. A strand is calculated as one system when every BMP in it is retention-type (Retention in Series), every BMP is a wet detention (Detention in Series), or untreated catchments flow into a wet detention or a retention BMP (No Treatment to Detention / No Treatment to Retention). In a Detention in Series strand each pond is calculated with all the runoff reaching it (its own catchment’s and the ponds’ above it), so its residence time is the routed one; the strand report and the outlet use the same removals. In a Retention in Series strand the Treatment Depths of its BMPs are added, and the capture at that sum is the removal of all the load entering the strand. Any other strand is calculated node by node.
Applicant’s Handbook reference
Section 9.5.1 Treatment Train Nutrient Reduction: Equation 9-5 assumes each BMP acts independently; where there is “an identifiable causal relationship” between an upstream and a downstream BMP, “the designer should consider the use of another methodology”. Calculating a retention or detention strand as one system is BMPFast’s other methodology for those cases (Appendix O, Treatment Train repeats this text).
Source reference
BMPFast method (ComplexRouting.CalculateWithStrands and StrandCalculations; ponds in a chain calculated with all the runoff reaching each pond, Ron, 2026-10-15): catchments are worked from upstream to the outlet with loads in kg/yr; strands of retention BMPs, of wet ponds, and of untreated catchments into a pond or retention BMP are calculated as single systems, and every other node on its own.
FDEP and the water management districts (2010). Stormwater Quality Applicant’s Handbook: Design Requirements for Stormwater Treatment Systems in Florida, March 2010 draft (not adopted), Section 22.3 Dry Retention In Series, Table 22.3-2, notes 2 and 3 (the draft, not adopted: PDF, 16 MB): in its worked example the downstream basin’s efficiency is read from the dry retention tables at the sum of the two basins’ retention depths (2 in = 1.00 + 1.00 in; 1.89 in = 1.00 + 0.89 in), and the downstream basin is credited with the difference from the upstream basin’s efficiency; BMPFast’s Equivalent Treatment Depth adds the depths in the same way.
FDEP and the water management districts (2010). Stormwater Quality Applicant’s Handbook: Design Requirements for Stormwater Treatment Systems in Florida, March 2010 draft (not adopted), Section 25.3 Wet Detention In Series (pages 190 to 196) (the draft, not adopted: PDF, 16 MB): works a chain of five ponds in Zone 4 in which each pond receives its own basin’s runoff and the discharge of the pond above it; the draft says its method is for ponds with annual detention times under 100 days.
How each kind of strand is calculated, the other methods and how far apart they are: Routing Detention Systems in Series, Routing Retention Systems in Series, Routing No Treatment to Detention and Routing No Treatment to Retention. Filters in catchments routed one into another are calculated node by node (each filter removes its share of what reaches it); for how that compares with adding equivalent Treatment Depths, see Comparison of Methods for Calculating Filters in Series, and for two filters with different media, with a third method that BMPFast does not calculate (Specific Yield / Specific Retention), Comparison of Methods for Filter Media in Series. In BMPFast 2 a routing can calculate a run of filters as one system instead (Surface discharge filters in series, on the routing’s Entry tab); in BMPFast (v1) the same choice is on the Catchment Configuration window, under the diagram.
Bypass upstream runoff. A catchment’s BMP treats its own runoff and the runoff routed to it from upstream catchments. Tick Bypass upstream runoff on a catchment’s Routing screen and the upstream runoff goes past that BMP, untreated, to the catchment it routes to (or the outlet); the BMP then treats only its own catchment’s runoff. The routing report notes every bypass and why.
- Rainwater harvesting and green roofs always bypass upstream runoff: they should not be used to treat runoff from upstream catchments and must be considered separately in routing. The box is ticked and cannot be changed, and routing another catchment into one of them shows a warning.
- Stormwater harvesting, rain gardens, tree wells, vegetated natural buffers and vegetated filter strips would not normally treat runoff from upstream catchments, so they bypass it unless you confirm otherwise. When a catchment is first routed into one of them, BMPFast asks whether it treats that runoff; the answer is kept, and the box changes it later.
- Every other BMP treats the upstream runoff unless you tick the box.
A catchment that bypasses upstream runoff also stops a strand from being calculated as one system.
Source reference
BMPFast method (bypass of upstream runoff, BMP.TreatsOwnCatchmentOnly; Ron, 2026-10-05): harvesting, green roofs, rain gardens, tree wells, buffers and filter strips treat only their own catchment’s runoff unless the user confirms otherwise; this is BMPFast’s rule, not a handbook one.
The node-by-node results (inputs from upstream and from the catchment, removal, and output for each node) are in the routing table at the start of the Complete Report (button 5 on the main screen). The Flow Balance Report, the Full Routing Diagram and the Diagram window on the configuration screen show the same routing.
Other methods: each strand page compares the method BMPFast uses with the others over a range of sizes: Strand Based Routing for Retention in Series, Strand Based Routing for Wet Detention in Series, Strand Based Routing for No Treatment to Retention, Strand Based Routing for No Treatment to Detention.
Warnings
Routing warnings are printed in red under the routing table in the Complete Report:
- “Node a routes to missing or disabled node b; routed to the Outlet instead.” – a catchment sends its water to a catchment that is disabled or does not exist. Its water is counted at the outlet.
- “Circular routing detected; nodes in the cycle were not calculated.” – catchments route to each other in a loop. Change one of their destinations.
- The own-catchment-only warning described above.
In BMPFast 2
Retention basins in series. A run of retention catchments is calculated by Treatment Depth Allocation (the default; Ron Eaglin, October 19, 2026), by efficiencies in series (Equation 9-5), or by v1’s Treatment Depths added: the choice Retention basins in series on the routing’s Entry tab. Strand Based Routing for Retention in Series works an example by hand.
Runoff from upstream into a swale or a buffer. A swale is recalculated with the upstream flow added; a Vegetated Natural Buffer or Filter Strip always lets it go by (Retention BMPs).
Comparison of methods
Several kinds of strand in a routing can be calculated more than one way. The first four are the strand pages linked under How routing is calculated; the others compare methods for BMPs that are also routed. Each page below works one problem by each method and shows how far apart they are; each says which method BMPFast uses. Every number on them is from BMPFast or its retention curves.
- Strand Based Routing for Retention in Series — retention catchments routed one into another: Treatment Depth Allocation (BMPFast 2’s default), Equation 9-5 or the Treatment Depths added, over a range.
- Strand Based Routing for Wet Detention in Series — wet detention catchments routed one into another: the methods compared over a range.
- Strand Based Routing for No Treatment to Retention — an untreated catchment draining to a retention basin: the methods compared over a range.
- Strand Based Routing for No Treatment to Detention — an untreated catchment draining to a wet detention pond: the methods compared over a range.
- Comparison of Methods for Calculating Filters in Series — Surface Discharge Filters one after another, worked on two equal filters: the Handbook equation (Equation 9-5) or the Equivalent Treatment Depth (one system).
- Comparison of Methods for Filter Media in Series — two filters with different media, one after another: the Handbook equation and the Equivalent Treatment Depth, which BMPFast calculates, beside a third, Specific Yield / Specific Retention, which it does not (worked on the page from BMPFast’s retention curve, for a range of Specific Yield to Specific Retention ratios).
- Comparison of Methods for Calculating Wet Detention Ponds in Series — two wet detention ponds one after the other: the two ways BMPFast can model them, on one example.
- Comparison of Methods for Calculating Retention BMPs in Series — two or more retention BMPs one after the other in one catchment (BMPs in Series): their Treatment Depths added (one storage) or Equation 9-5, over a range of sizes.
- Comparison of Methods for Calculating Retention Followed by Wet Detention — a retention basin followed by a wet detention pond: BMPFast’s method, the routing and Equation 9-5, over a range of basin sizes.
- Comparison of Methods for Calculating Retention Followed by a Surface Discharge Filter — a retention basin followed by a filter: Equation 9-5 (what BMPFast uses) or the two as one storage, over a range of filter sizes.
Sample problems
Worked problems solved in BMPFast, each with every input, the steps with screen captures, the program’s results, a hand check and the project file to download. Captures are for demonstration only. All of them: BMPFast sample problems.