The Four-Week Program Can Be Full When the Two-Week Still Has Rooms

When Open Runs Lie to the Front Desk

The occupancy board can look fine on a Tuesday morning. Ten runs show available tonight. The desk quotes a four-week board-and-train start for next Monday because the calendar says there is room.

By Wednesday, leadership is asking why a fifth long-stay dog arrived in a month when the senior trainer already had four active four-week enrollments on a tight documentation cadence. The runs were never the bottleneck. The four-week program was.

Facilities that run more than one board-and-train length, or more than one program tier on the same floor, need capacity that respects program boundaries, not just kennel inventory.

One Headcount, Two Different Commitments

Boarding occupancy answers a simple question: how many dogs are sleeping here tonight?

Board-and-train occupancy answers several at once: which program template, how many sessions per week, which trainer owns the arc, how many owner updates are due, and how long the run stays locked if the stay extends.

A two-week obedience track and a four-week behavior-mod track might share the same run bank. They should not share the same enrollment limit if your trainer roster cannot run both at peak volume. Selling the longer program when the shorter track still has room is valid product design. Selling the longer program because the building has empty runs is how facilities overcommit trainer time while the kennel chart still looks green.

Per-Program Caps as an Operator Control

Strong operators set limits at the program level: a maximum concurrent count for the four-week reactive track, a different cap for the two-week tune-up, maybe no cap on a short refresh program that shares documentation templates with day training.

Those caps belong in the system that approves enrollments and checks dogs in, not in a spreadsheet the desk checks when they remember. When software enforces a program cap at approval and check-in, the desk gets a clear signal that this program is full, even when organization-wide run counts still show slack.

Pet Ops stores a concurrent enrollment limit on each training program, with organization-wide capacity as a separate check. A blocked approval should say whether the program cap or the facility cap fired, so staff are not arguing about open runs when the real limit is trainer load on that template.

Managers who need a one-off exception should use an explicit override, not a workaround that only works when the owner knows someone on staff. Overrides without logging recreate the old problem: capacity rules that exist until Saturday gets busy.

A Tuesday Enrollment Call Gone Wrong

Picture a facility with twelve training runs and two active program tiers: a two-week skills intensive and a four-week behavior track. The four-week cap is four dogs in-house at once because one lead trainer owns those cases and weekly video updates are part of the standard.

A returning client wants the four-week track for a dog that did well in puppy class. Runs 9 through 12 are empty on the boarding view. The desk sees availability and holds a start date.

At approval, the system returns program full: four of four on the four-week template, even though eight runs are physically open. That is the correct outcome. The fix is not to cram a fifth long-stay dog onto the floor. The fix is to offer the two-week intensive if it matches the goals, start a waitlist for the four-week tier, or push the start date to when the next graduation opens a slot.

Without per-program enforcement, the desk learns this only after check-in, when the trainer discovers a fifth long arc and session spacing already slipped last week.

How Per-Program Caps Pair With Org-Wide Limits

Program caps and facility caps solve different problems. The organization limit protects total dogs in training against run inventory and overnight staffing. The program limit protects template-specific load: session minutes, documentation depth, and which trainer skills are in play.

You want both visible when someone commits an enrollment. If only the org cap exists, every program competes for the same bucket until a senior trainer burns out. If only program caps exist, you can still overfill the building.

Board-and-train management software earns its place when enrollment approval, check-in, and forward occupancy read from the same enrollment records, not when capacity lives in three places that disagree.

Setting Caps Without Guesswork

Caps should follow rules you already believe in:

• Trainer ownership. Count active enrollments per primary trainer before you raise a program limit.
• Session frequency. A program that promises daily training blocks needs a lower cap than one with three sessions per week.
• Update cadence. Programs with weekly video expectations consume desk and trainer time even when runs are empty.
• Graduation clustering. If four-week programs tend to end the same week, your cap should leave room for boarding overlap, not assume perfect staggering.

Write the cap next to the program name in admin, review it in the weekly program review, and adjust when you hire or when a tier changes length. Changing caps quietly mid-season without telling the desk recreates manual exceptions.

What the Desk Should Say When a Program Is Full

Scripts stay boring and honest:

“We have room in the building, but our four-week program is at capacity for the trainer team through March 10. I can start you on the two-week track March 3, hold a four-week spot for March 11, or walk through which length fits your goals.”

That sentence only works if the system blocked the four-week enrollment before money changed hands. Otherwise the desk improvises, and improvisation becomes policy.

How This Connects to Daily Operations

Board-and-train facilities sell programs, not nights in a run. When capacity is tracked per program template, the front desk can quote honestly, trainers keep session spacing predictable, and owner updates stay tied to the workload you actually planned.

Per-program enrollment limits belong in the same stack as session records and owner-visible timelines, so “full” means the program tier is full, not that someone misread a boarding chart. That is the operational case for board-and-train software that treats each program as structured training work, and for dog training facility software views that show committed enrollments by template, not just dogs in kennels tonight.