Building a Custom Methodology Pack for Your House Language

When the Three Seeded Packs Are Not Enough

Pet Ops ships three methodology packs at setup: Neutral, Balanced, and Science-Based. Most facilities stop there. They assign Balanced to the four-week board-and-train obedience track, Science-Based to the reactive-dog program, and Neutral to private lessons that have not standardized on one camp.

That covers a lot of buildings. It does not cover every product a training operation sells.

Some facilities run a sport-detection curriculum with search-area vocabulary their head trainer spent years refining. Others use balanced tools on the floor but refuse camp-marked words in owner-facing updates. A few want working-level fields from the Balanced pack on one program without adopting the full Balanced label because their intake language already says something else.

Custom methodology packs exist for that gap. You build a pack in Training Admin, define the fields your house language needs, and assign it to a program template the same way you would assign a seeded pack. The floor gets a documentation shape that matches what you sold, not a compromise built from someone else's camp defaults.

What "House Language" Actually Means Operationally

House language is not a philosophy manifesto taped to the break-room fridge. It is the vocabulary your staff already uses on the kennel row and the fields they reach for between dogs.

A detection sport program might track odor-source placement, alert style, and search-pattern criteria. A facility running balanced equipment with force-free owner communication might need working-level checkboxes internally while keeping portal updates on neutral terms like cue, criteria, and fluency. A behavior-modification track that blends camps might need ABC logs plus a custom "management plan reviewed" checkbox that your lead trainer invented after the third insurance audit.

If trainers keep skipping fields because the form does not match how they talk, or if they invent personal note templates in a shared drive, you have a house-language problem. A custom pack turns that informal vocabulary into required fields on the enrollment record.

Start From Fields, Not Philosophy

The mistake is opening the pack editor and debating training camps before you have watched a week of real session notes.

Start with three questions:

What do trainers write by hand that the current form lacks? Read ten recent session notes from your most consistent trainer and ten from your newest hire. Highlight the phrases that repeat. Those phrases become field labels or dropdown options.

What do evening kennel staff need to read during handoff? If morning trainers document working level but night staff only see a generic "session went well" text box, add a structured working-level field on the session note surface.

What do owners see that must match intake language? Owner-facing surfaces pull from the same pack vocabulary. If you sold "foundation phase" at enrollment, the scorecard should say foundation phase, not a seeded pack's default stage names.

Then open the Packs tab in Training Admin. Create a custom pack with a unique slug. Use the pack fields editor to add, reorder, and mark required the fields you identified. Set each field's surface: session notes, scorecard, behavior log, or enrollment drawer. Pick field types that match the data: dropdown for alert style, number for threshold distance, checkbox for equipment checks.

Programs come next. Build the program once, adopt one from the Pet Ops library, or duplicate one you already run. Your custom four-week detection board-and-train might carry odor-recognition skills, search-pattern homework, and the session fields those skills need. When you define the program template, attach those skills so new enrollments seed the right scorecard rows without manual setup per dog.

Build the Pack Before You Hire Into It

Custom packs pay off at onboarding. A new trainer assigned to programs with a defined pack inherits the documentation shape on day one. They are not copying the last trainer's personal Google Doc or asking which fields matter for this building.

The sequence that works:

1. Draft fields with your lead trainer on paper or in a spreadsheet first.
2. Build the pack in admin and attach it to one pilot program template.
3. Run two enrollments through the full cycle: intake, daily sessions, owner update, graduation.
4. Adjust field order and required flags based on what staff skipped or duplicated.
5. Roll the template out to additional programs only after the pilot notes read cleanly at handoff.

Renaming or deactivating a seeded pack is fine when your facility does not run that camp. You cannot delete system packs, but you can stop offering them on new templates if Balanced or Science-Based fields would confuse your staff. Custom packs fill the space between "use Neutral everywhere" and "force everyone into a camp they do not sell."

A Concrete Example: Custom Pack for a Detection Sport Track

A facility in the Pacific Northwest runs three programs: a seeded Balanced four-week obedience board-and-train, a seeded Science-Based reactive-dog track, and a six-week sport-detection board-and-train that is neither.

Detection clients were sold on alert style, odor-source criteria, and search-pattern proofing. Trainers on that track kept writing those terms in free-text notes because the Balanced pack surfaced working-level and equipment fields they did not need, and the Science-Based pack buried ABC logs they also did not need.

The head trainer built a custom pack called "Detection Foundations." Session notes got dropdowns for alert style (sit, freeze, scratch), numeric fields for odor-source distance, and a required checkbox for "search pattern completed as planned." Scorecards tracked detection-specific skills with stage movement along the 3 Ds framework. The program carried odor-recognition and vehicle-search skills with matching homework.

The Balanced and Science-Based programs stayed on their seeded packs. Detection enrollments in the next kennel row used different fields without staff mentally toggling camp vocabulary per run.

Thursday turnover, float kennel staff read a detection note with alert style and search criteria in labeled fields. They did not parse paragraphs to find whether the dog alerted correctly. Owner updates that week used the same vocabulary the desk used at intake, so week-four graduation did not introduce new terms the client never heard.

Where Custom Packs Go Wrong

Three patterns undo the work.

Rebuilding philosophy instead of documenting the sold product. A custom pack with forty fields nobody fills out is worse than Neutral. Start small. Add fields when trainers prove they need them.

One custom pack for the entire organization. Custom packs belong on program templates, same as seeded packs. A detection pack on the puppy class template creates the same drift you were trying to fix.

Owner-facing updates that ignore the custom vocabulary. Internal notes can be perfect while portal updates still use generic encouragement. Align published updates with the pack fields staff actually document.

Treating custom packs as a fourth shipped camp. Pet Ops seeds three methodology packs. Custom packs extend your own programs. They are not a marketing claim about which training camps the software endorses.

How This Connects to Daily Operations

A custom methodology pack turns house language from tribal knowledge into program setup.

Dog training methodology software ships three seeded packs plus a pack builder for the fields your programs need beyond the defaults. Board-and-train software enrollments inherit whichever pack the program template carries, so a custom detection track documents in detection vocabulary from intake through graduation without sharing forms with obedience programs in the same row. Dog training documentation software keeps internal notes pack-specific while trainers still control what reaches owners through the portal.

Facilities that build custom packs before they scale stop renegotiating vocabulary every time they add a program. They define the product, build the pack, assign the template, and let the floor run inside a shape that matches what they sold.