# Fleet Depot Charging 2026: Build Only if Peak Queue Tops 15 Minutes

Marcus Hale · November 17, 2026

> Fleet depots should build charging only if the peak shift-overlap queue exceeds 15 minutes. Use 30 days of session-and-port logs to compute the peak window average.

Because the ChargePoint figure lacks a denominator, it cannot reveal whether a depot’s shift-overlap queue will exceed the 15-minute method threshold. The queue that matters at a depot forms in the sharp overlap of shifts: arrivals per 30-minute window divided by usable ports, not annual sessions divided by 365. A fleet manager must therefore pull its own session-and-port log for at least 30 days, compute the peak window average, and only then compare it to the threshold.

Only when that shift-level peak queue exceeds 15 minutes AND the utility confirms no transformer upgrade should a 2026 fleet build owned depot charging. If either check fails, the comparison table in the fleet section shows that renting or subletting capacity wins on cost and risk. The worked arithmetic—96 sessions per month ÷ 12 ports ÷ 30 days equals 0.27 sessions per port per day—illustrates how easily a raw session count can mislead when the denominator is missing.

![Because the ChargePoint figure lacks a denominator, it — Fleet Depot Charging 2026](https://static.mm-ais.com/article-images-ai/fleet-depot-charging-2026-build-only-if-ai-3bbfcdad.jpg)

## Own, rent, or sublet: 2026 fleet table

A 2026 fleet comparing depot options should treat the build decision as a two-gate test, not a default. The table below is the decision instrument: own depot charging wins only when both checks pass — shift-level peak queue above the 15-minute method threshold and a utility confirmation that no transformer upgrade is required. If either check fails, rent or sublet. That verdict is the point of this section, and it should be applied before any capital is committed.

| Option | Capital trigger | Documentation burden | Best fit | Verdict |
| --- | --- | --- | --- | --- |
| Own depot L2 | Only if shift-level peak queue exceeds the method threshold and the utility confirms no transformer upgrade | Utility interconnection, AHJ permit, load calculation | Large fixed-route fleet, multi-shift | Winner only when both checks pass |
| Rent public DC | No capital; demand-charge exposure | Session receipts, queue logs | Peak queue below the method threshold, or utility upgrade required | Winner when an upgrade is required |
| Sublet neighbor depot | No capital; negotiated access terms | Written access agreement, shared queue logs | Moderate fleet with a nearby compatible depot | Fallback when own-depot checks fail and public DC is impractical |

Run the own-depot gate in order. First, pull the shift-level peak queue from your port log and compare it to the 15-minute method threshold; a fleet whose peak queue sits below that line has no capital case for a depot, regardless of how busy the network looks. Second, take the load calculation to the utility and get written confirmation on transformer capacity. If the utility signals an upgrade is needed, the own-depot option is out for 2026 — the schedule risk alone disqualifies it — and the table routes you to rent or sublet.

The documentation burden is where fleets underestimate the own-depot path. Interconnection review, AHJ permitting, and load calculations each consume staff time and introduce dependencies outside your control. Renting public DC shifts that burden to session receipts and queue logs; subletting a neighbor depot shifts it to a written access agreement and shared queue records. Neither rental path eliminates demand-charge exposure, so model that cost against your session profile before signing.

Match the option to fleet shape. A large fixed-route fleet running multiple shifts is the profile most likely to clear both own-depot checks, because concentrated shift overlap is exactly what the peak-queue method measures. A moderate fleet with a compatible depot nearby should price sublet access first — it preserves flexibility while the utilization picture matures. A fleet whose peak queue stays under the threshold should rent public DC and revisit the build question only when the log shows the queue crossing the line.

Re-run the table annually, not once. Shift schedules, route density, and utility capacity all move, and a fleet that failed the own-depot gate this year may pass it next year — or the reverse. Keep the port log current, keep the utility confirmation letter on file, and let the two checks, not network-wide session growth, drive the 2026 decision.

![Fleet Depot Charging 2026](https://static.mm-ais.com/article-images-ai/fleet-depot-charging-2026-build-only-if-ai-0a90a696.jpg)

## Costs, limits, and the worked check

Before any depot charging vote, pull three documents and price them separately: the utility's written transformer upgrade quote, the AHJ permit fee, and the demand-charge tariff from your current electric rate schedule. These three drive the capital and operating cost of an owned build, and none can be estimated from a generic industry average. There is no verified 2026 fleet charging cost figure to lean on, so treat every dollar as a line you obtain from the named source, not a number you assume. If the utility will not issue a transformer quote, that silence is itself a finding: the energization path is unresolved, and an unresolved path fails the second check.

The utilization side is arithmetic you can run this week. Take a representative month of 96 sessions across a 12-port depot: 96 sessions/month ÷ 12 ports ÷ 30 days = 0.27 sessions/port/day. Record the inputs in a 30-Day Port Log, a simple artifact listing each port, each day's session count, and the longest queue observed during peak shift hours. The log is the evidence base; 0.27 is what it produces. Without the log you have no denominator and no peak, and no peak means no way to test the 15-minute method threshold.

Run the 0.27 sessions/port/day figure against the 15-minute method threshold and let the comparison decide. When shift-level peak queue sits below that threshold, the utilization case for an owned build collapses no matter how favorable the demand-charge math looks — low per-port use cannot produce a queue that justifies dedicated capital. The threshold is a gate, not a tiebreaker; it must be cleared before cost enters the decision at all. A low per-port figure also inflates the demand-charge line, since you pay for capacity that few sessions draw against — the cost check and the utilization check fail together, not in isolation.

The remaining failure modes resolve the same way, and the pattern is worth seeing in one place:

| Condition | Rule breaks | Rule still wins |
| --- | --- | --- |
| Peak queue below method threshold | Own build loses | Rent wins |
| Transformer upgrade beyond planned energization | Own build loses | Sublet wins |
| No utilization log | No build | Run log first |
| Neighbor contract shorter than planning horizon | Sublet risk | Rent wins |

![Fleet Depot Charging 2026, photo 2](https://static.mm-ais.com/article-images-pixabay/fleet-depot-charging-2026-build-only-if-9e6e96b2.jpg)

## Five if/then rules for fleet managers

Five if/then rules turn the depot decision from a judgment call into a checklist. Each rule uses a specific threshold, and each one is meant to be applied in order, because a failed check at any step sends you to the rent-or-sublet path rather than deeper into a build plan.

**Rule 1: If shift-level peak queue exceeds 15 minutes and the utility confirms no transformer upgrade, build owned L2.** This is the only combination that clears both gates. The queue figure comes from your own shift-overlap data, not from network session totals. The utility confirmation must be in writing and must name the service you will actually draw from. If either half of the condition is missing, stop and move to Rule 2.

**Rule 2: If the utility requires a transformer upgrade, rent or sublet until the upgrade date is fixed.** A pending upgrade is not a reason to delay operations; it is a reason to avoid capital. Rent or sublet capacity in the interim, and revisit the build decision only once the utility has committed to a firm energization date in writing. Check your AHJ's published permit timelines and treat a permit schedule that slips past your planning horizon as a trigger to stay on the rent-or-sublet path.

**Rule 3: If peak queue is under 15 minutes and nearby public DC is practical, rent; do not build.** A short queue at your own depot means your vehicles are not waiting on your ports. Measure actual drive time and queue length at the public DC sites your routes can reach; if the rental market is doing the work a depot would do at lower committed cost, building converts a flexible operating expense into a fixed asset you cannot easily unwind.

**Rule 4: If peak queue is under 15 minutes and public DC availability is over 10 minutes, sublet rather than build.** Neither condition justifies owned infrastructure, but the longer public drive time argues for securing nearby capacity through a sublease so your drivers are not exposed to public-queue variability. Subletting keeps the commitment short and reversible.

**Rule 5: Re-run all four checks every 12 months, and after any shift-pattern change.** Utilization moves with routes, vehicle counts, and schedules. A depot that failed Rule 1 this year may pass it next year, and one that passed may no longer clear the queue threshold. Put the 12-month review on the calendar with a named owner, and require the same written utility confirmation at each review.

| Check | Threshold | If it fails |
| --- | --- | --- |
| Shift-level peak queue | Above 15 minutes | Rent or sublet |
| Utility transformer upgrade | None required, confirmed in writing | Rent or sublet until date fixed |
| Permit timeline | 12 weeks or less | Rent or sublet |
| Public DC availability | 10 minutes or more | Rent, do not build |
| Review cycle | Every 12 months | Re-run all checks |

The rules are deliberately conservative: they authorize a build only when your own shift data and the utility both agree. Every other outcome routes to renting or subletting, which keeps the fleet operating while the evidence accumulates.

## What to do next

| Step | Action | Why it matters |
| --- | --- | --- |
| 1 | Measure the shift-level peak queue against the 15-minute threshold using the 12-month data set. | This is the primary gate; if the queue does not exceed 15 minutes, the build check fails immediately. |
| 2 | Contact the utility to confirm no transformer upgrade is required for the depot site. | This is the secondary gate; a negative confirmation routes the decision to renting or subletting regardless of queue length. |
| 3 | If the peak queue exceeds 15 minutes AND the utility confirms no transformer upgrade, proceed to owned depot build authorization. | Both gates must pass; satisfying only one is insufficient for a 2026 fleet build. |
| 4 | If the peak queue is at or below 15 minutes, or the utility cannot confirm no transformer upgrade, initiate the rent or sublet capacity pathway. | Failing either check mandates the non-build outcome per the definitive decision rule. |
| 5 | Exclude session volume growth (30-day or 12-week trends) as a factor in the build decision. | Volume metrics do not satisfy the shift-level peak queue threshold or the transformer upgrade check for the 2026 fleet. |
| 6 | Document the outcome: either authorize the owned depot build or lock in the rent/sublet arrangement based on the two-gate result. | Ensures the fleet decision aligns with the 2026 vs 2023 buildout rate comparison and the canonical decision rule. |

## Frequently Asked Questions

**Why can't the ChargePoint figure tell me whether my depot's shift-overlap queue will exceed the threshold?**

Because the ChargePoint figure lacks a denominator, it cannot reveal whether a depot's shift-overlap queue will exceed the 15-minute method threshold.

**What exactly should I measure to get the queue that matters at a depot?**

The queue that matters forms in the sharp overlap of shifts: arrivals per 30-minute window divided by usable ports, not annual sessions divided by 365.

**How much of my own session-and-port log do I need to pull before comparing to the threshold?**

A fleet manager must pull its own session-and-port log for at least 30 days, compute the peak window average, and only then compare it to the threshold.

**What two conditions must both hold before a 2026 fleet should build owned depot charging?**

Only when the shift-level peak queue exceeds 15 minutes AND the utility confirms no transformer upgrade should a 2026 fleet build owned depot charging.

**What happens if either of the two checks fails?**

If either check fails, the comparison table in the fleet section shows that renting or subletting capacity wins on cost and risk.

**How does the worked arithmetic show that a raw session count can mislead?**

The worked arithmetic—96 sessions per month ÷ 12 ports ÷ 30 days equals 0.27 sessions per port per day—illustrates how easily a raw session count can mislead when the denominator is missing.

## Quick answers

| Why can't the ChargePoint figure show whether a depot's shift-overlap queue will exceed the 15-minute method threshold? | Because the ChargePoint figure lacks a denominator. |
| --- | --- |
| What should a fleet manager pull before comparing to the threshold? | A fleet manager must pull its own session-and-port log for at least 30 days, compute the peak window average, and only then compare it to the threshold. |
| When should a 2026 fleet build owned depot charging? | Only when that shift-level peak queue exceeds 15 minutes AND the utility confirms no transformer upgrade should a 2026 fleet build owned depot charging. |
| What wins on cost and risk if either check fails? | If either check fails, the comparison table in the fleet section shows that renting or subletting capacity wins on cost and risk. |
| What does the worked arithmetic illustrate? | The worked arithmetic—96 sessions per month ÷ 12 ports ÷ 30 days equals 0.27 sessions per port per day—illustrates how easily a raw session count can mislead when the denominator is missing. |

Also worth reading: **Fleet TCO 2026: Cloud vs On-Prem for a 50-Vehicle Fleet**: [Fleet TCO 2026: Cloud vs](https://odiggo.xyz/blog/fleet-tco-2026-cloud-vs-on-prem-for-a-50-vehicle-fleet.php) · **Fleet Vibration Thresholds & Downtime ROI: 2026 Reality**: [Fleet Vibration Thresholds & Downtime](https://odiggo.xyz/blog/fleet-vibration-thresholds-downtime-roi-2026-reality.php) · **Overseas Electric Fleet Rollouts: 2026 U.S. Depot Delays—Accelerate or Wait**: [Overseas Electric Fleet Rollouts: 2026](https://odiggo.xyz/blog/overseas-electric-fleet-rollouts-2026-us-depot-delaysaccelerate-or-wait.php)

### Related reading

- [Optimal Idle Cut: Why 15 Minutes Beats 10 or 20 in Fleet Dispatch](https://odiggo.xyz/blog/optimal-idle-cut-why-15-minutes-beats-10-or-20-in-fleet-dispatch.php)
- [Overseas Electric Fleet Rollouts: 2026 U.S. Depot Delays—Accelerate or Wait](https://odiggo.xyz/blog/overseas-electric-fleet-rollouts-2026-us-depot-delaysaccelerate-or-wait.php)
- [Land Cruiser 300 10K Service: 87 Minutes, $412 Cost Explained](https://odiggo.xyz/blog/land-cruiser-300-10k-service-87-minutes-412-cost-explained.php)
- [How to evaluate toll management: Voyager platform U.S. Bank vs Verra Mobility in 3 steps](https://odiggo.xyz/blog/how-to-evaluate-toll-management-voyager-platform-us-bank-vs-verra-mobility-in-3-steps.php)
- [C8 Corvette Manual Swap: Verify the $4,200 Fleet Kit Claim](https://odiggo.xyz/blog/c8-corvette-manual-swap-verify-the-4200-fleet-kit-claim.php)
- [Electric fleet battery monitoring 2026: Ford Pro vs Samsara Before 70%](https://odiggo.xyz/blog/electric-fleet-battery-monitoring-2026-ford-pro-vs-samsara-before-70.php)

### Latest

- [How to evaluate toll management: Voyager platform U.S. Bank vs Verra Mobility...](https://odiggo.xyz/blog/how-to-evaluate-toll-management-voyager-platform-us-bank-vs-verra-mobility-in-3-steps.php)
- [C8 Corvette Manual Swap: Verify the $4,200 Fleet Kit Claim](https://odiggo.xyz/blog/c8-corvette-manual-swap-verify-the-4200-fleet-kit-claim.php)
- [Electric fleet battery monitoring 2026: Ford Pro vs Samsara Before 70%](https://odiggo.xyz/blog/electric-fleet-battery-monitoring-2026-ford-pro-vs-samsara-before-70.php)

Canonical: https://odiggo.xyz/blog/fleet-depot-charging-2026-build-only-if-peak-queue-tops-15-minutes.php
Markdown: https://odiggo.xyz/blog/fleet-depot-charging-2026-build-only-if-peak-queue-tops-15-minutes.php/index.md
