Guides / Vendor packet
A vendor packet is the set of documents a school, park, library or district collects from an outside provider before a youth program starts. Most ask for an application, a signed service agreement, a certificate of insurance, a business license, proof of background checks, references and a lesson outline.
Hosts call it the packet, the paperwork or the application. The job is the same. A vendor packet is the file a host builds on every outside provider before that provider's instructors are in a room with children, and the file the host goes back to if anyone later asks who was there and what was checked.
Youth enrichment has no statewide rulebook of its own. For most after-school classes, camps and clubs, what a provider has to show is whatever the host wrote into its packet, plus whatever a funder or risk pool attached to the money. The packet is the rule.
In coordinators' own words, a packet for a youth program provider usually holds these pieces.
Many packets add a code of conduct or the host's child protection policy for each instructor to sign, training certificates, and a roster of every adult who will be on site. One city's contract instructor requirements, for example, list a business operations tax certificate, a certificate of insurance naming the city as additional insured, fingerprinting for instructors, their employees and subcontractors, and a 2-hour mandated reporter training certificate for anyone teaching youth.
Sources: enrops interviews with host coordinators, June to October 2026; City of Sacramento, Leisure Enrichment new instructor requirements; City of Salinas, Insurance Requirements, Addendum A, rev. Dec 13, 2019.
More people than the coordinator who collects it. The coordinator gathers the pieces and chases the gaps. Legal, often a city attorney's office or district counsel, writes the agreement and sets the insurance bar. HR sets the background check rules, sometimes for employees and contractors alike. A risk manager, or the host's risk pool, decides what coverage and limits to ask for.
That split is why a packet is slow to change. The person who collects it is rarely the person who owns the rule, so a coordinator who wants to accept something new usually has to forward it to someone else first. If that someone is your legal or risk office, this page is written for them.
“They'll answer one or two questions out of the five questions, and we have to go back and forth with it.”
A recreation coordinator at a city parks department
Three things cause most of the back and forth. Every host writes its own packet, so a provider working with ten hosts fills out ten versions of the same facts. The facts expire on their own dates: insurance renews on the policy date, not the term date, and a check run two years ago may not meet this year's rule. And the people change; the substitute who joins in week six was never in the packet.
“It takes me roughly 10 hours per school to fill everything out and get it organized.”
The founder of a school sports program at five schools
For the host, the cost lands in the busiest weeks. Packets are due a couple of months before a season so classes can go in the activity guide, and the gaps surface right before the deadline. A missing business license can hold up a whole camp week:
“If I don't get that, we can't have your camps run.”
A youth recreation coordinator, on a missing business license
Use this as a starting point. Each line asks for a fact and the date beside it, because a dated fact can be checked and an undated one cannot.
Write lines 2 to 7 the way you write the rest of your packet: specific, dated and checkable. These are your conditions; enrops does not set them.
Worked example
A city parks department runs twelve summer camp weeks with outside providers. A robotics provider will send three instructors and a substitute. The packet is due eight weeks before the first camp so the weeks can go in the activity guide.
The provider sends the application, the signed agreement and a certificate. The certificate shows general liability only, the business license lapsed in March, and the substitute is not on the roster. Without a checklist, that is three separate emails over three weeks.
With the dated checklist above, the coordinator sees all three gaps in one pass and sends one note naming each. The provider fixes them before the deadline, and the policy's expiration date goes on the calendar that day.
The packet gets rebuilt because the facts live in email attachments, one host at a time. With a provider record, the provider keeps one current, dated record of the facts every packet asks for, and each host reads it. The host's own agreement still gets signed, and the host still runs any check it requires.
“If it's your company sending me, that's how they're sending me their stuff.”
A city recreation coordinator
Providers name the catch themselves: a shared record is only worth keeping if hosts accept it.
“Knowing that schools and districts would actually accept them without requiring additional changes or going through separate approval processes.”
The owner of a language program, on what would make one record worth it
That is why the record follows the host's packet, not the other way around. The host sets the requirements; the record shows, for each one, what is on file and as of when. Providers can read how one record works across every host. If you host programs in Oregon, see what state rules add to the packet there, and browse more guides for hosts.
On an enrops provider record, the packet becomes five rows for every instructor, each with its own as-of date. Your own agreements sit in their own row, signed and dated, so the version you can point to later is the one on file.
Example view
One row per instructor, each with its own as-of dateYour service agreement and code of conduct, signed and dated Apr 2, 2026.
Status shown with each provider's consent. enrops displays verification status from the provider's screening partner; it does not run or certify checks.
The set of documents a host collects from an outside provider before a youth program starts, usually an application, a service agreement, a certificate of insurance, a business license, background check proof, references and a lesson outline. The host approves the provider from it.
Ask for each item with a date: the signed agreement, a certificate of insurance with the abuse and molestation line and your organization as additional insured, a current business license, screening status and training certificates for every adult, and a roster that includes substitutes and volunteers.
The coordinator collects it, but the rules usually belong elsewhere: legal sets the insurance bar and writes the agreement, HR sets background check rules, and a risk manager or risk pool sets coverage limits. Send each office the pieces it owns.
Agreements and the roster every term, insurance at every policy renewal, and screening and training on the cycle your packet sets. A packet collected in September can be out of date by spring.
Usually, if the class meets in a school building. The district's facility-use or volunteer rules often apply, and the PTA's own agreement with the provider should ask for the same dated items a district would.
The facts can be the same; the forms usually are not. A provider with one current, dated record can answer every form from it, and some hosts read the record directly, alongside their own checks.
The host's guide to outside provider safety: what to ask every provider for, how to read what comes back, and how to keep it current. Every number carries its source.
This page explains common packet practice for hosts. It is not legal advice; your own counsel, HR and risk office decide what your packet asks for. Quotes are from enrops interviews with hosts and providers in 2026, shared anonymously.