Two Training Dogs, One Run, One Card — Don't Print a Lie
One Gate, Two Enrollments
Households with two dogs in board-and-train often share a run. Same owner, same pickup window, one gate clip. The temptation is to print the card you would use for a single dog and hope staff remember there are two programs behind the wire.
That shortcut fails on the first busy afternoon. Night crew logs a timeline update for the wrong enrollment. A float tech feeds from notes that belong to the other dog. A trainer scans a QR and lands on a stay that does not match the name on the collar in front of them.
The kennel card is not decoration. It is the contract between the enrollment record and everyone who walks the wing without memorizing your roster.
What "One Card" Actually Means
Shared run does not mean shared truth. Two active board-and-train enrollments can legitimately occupy one run when they share an owner and your run assignment says they belong together. The print layout should reflect that reality instead of flattening it.
An honest shared training card keeps one set of stay-level facts that are actually shared:
- Run name and location on the floor
- Owner name and phone numbers desk staff need at pickup
- Drop-off date and proposed times that apply to the household stay
It keeps separate anything that can diverge between dogs:
- Program name and length
- Food and medicine instructions
- Training notes and handling flags
- Staff-scan QR codes tied to each enrollment ID
When software detects siblings on the same run for the same owner, the header should read like a shared kennel, not like one dog with a second name scribbled in the margin. Pet photos, program lines, and vaccination summaries belong per dog. Scan codes belong per enrollment so "open the stay" always means the stay you are standing in front of.
Dog training facility software earns trust on the floor when run assignment, printable cards, and staff shortcuts all read from the same enrollment rows. A card that lies is worse than no card, because staff stop scanning.
The QR Row Is Not Optional on Multi-Pet Cards
Single-dog cards can tuck one staff-scan code in the footer. Two-dog cards need two labeled codes, usually in a row under the notes block, each encoding its own training stay.
Staff should never guess which QR matches which collar. Label with pet name. Clip the card so both codes stay visible at the gate. If someone reprints after a run move, reprint the shared card from either enrollment that still shares the run, not two different single-dog cards that disagree about owner phone or schedule.
Scanning should land on the training stay with the shortcuts kennel techs use mid-shift: quick update on the story timeline, training session notes, owner call, handling flags. Wrong enrollment means wrong portal update. Owners notice when the photo is their other dog.
A Concrete Scenario: Littermates in Run 7
A Colorado facility enrolls two adolescent siblings from one household in parallel three-week programs. Same owner, different program tiers, same run for overnight housing. At check-in, the desk assigns Run 7 and prints the training kennel card from the first enrollment.
The printed card shows Shared kennel across the top. Each dog gets a photo column, program line, and food notes in separate rows. Program and vaccination lines list both names. At the bottom, two staff-scan QR codes sit side by side, labeled by pet name.
Tuesday night, a boarding-only float tech covers dinner. She scans the QR for "Moose," logs a calm meal, and adds a photo to Moose's timeline. She scans "Maple" for a separate note about slower eating. She never opens a search screen or asks which enrollment is which.
Wednesday morning, the lead trainer sees both timeline entries on the correct enrollments before session blocks start. When Maple picks up a medical hold mid-week, the trainer reprints the card after the hold is recorded so flags on paper match flags on screen. Run 7 still holds two dogs; the card still tells the truth.
That workflow is not exotic. It is what happens when you refuse to print a single-dog card for a two-dog run.
Print Discipline for Sibling Cards
Print from the run truth, not from habit
If only one dog moved runs, do not leave a shared card on the old gate. Reprint when kennel_run changes for any dog on the card.
Reprint when program facts change Trainer reassignment, tier change, medical hold, equipment switch: the paper view should match the enrollment screen before the next shift that did not sit in the handoff meeting.
Do not split into conflicting singles Printing one card per dog with different owner phone numbers or schedule lines creates two lies instead of one. Use the multi-pet layout or fix the data, then print once.
Treat enrollment ID on the card as an audit hook When a tech says "the card did not match the computer," compare enrollment short ID on the print timestamp to the live record. Mismatch means stale paper, not staff error.
Kennel software for trainers and kennel software for desk staff are different jobs reading the same dogs. Shared-run cards are where those jobs either align or fight.
How This Connects to Daily Operations
At enrollment, decide explicitly whether siblings share a run. If yes, assign the run in software before the first print so sibling detection can build one card with two QR codes. Train kennel staff to scan the code beside the name they are handling, not whichever square is easiest to hit.
Add reprint triggers to your shift checklist: run moves, medical holds, program changes, new float covering the wing. Audit a random run once a week: does the card at the gate match both enrollments on the training dashboard?
Board-and-train software that treats long enrollments as operational records, not boarding-with-extra-notes, makes shared-run cards possible without manual layout work. The goal is simple. Anyone standing at Run 7 should see two programs, one owner, and a scan path that never sends them to the wrong dog.