Discovery → “We Need a Handbook”
Quick Snapshot
Business: Agritourism farm (80 seasonal employees)
Problem: Handbook, SOPs, and training content mixed into one document
What changed: Clear documentation structure → lower risk, easier updates, consistent guidance
Investment: $2,000
Client and Business
An agritourism farm had grown to 80 seasonal employees and reached a point where formal documentation was no longer optional.
They had reached the point where informal communication was no longer enough.
They needed an employee handbook to:
protect the business
create consistency across owners and supervisors
give staff a clear, shared reference point
They started with a base template from a business cooperative they belonged to and began building from there.
But as the document grew, so did the complexity.
How this started
The owner reached out for a review while the handbook was still being written—before sending it to an employment attorney.
What came up in the conversation
As we walked through the draft together, a few patterns became clear:
the handbook was trying to serve multiple purposes at once (a common issue in growing small businesses)
operational procedures (how to do the work) were mixed into policy sections
onboarding and training information was embedded in areas meant for compliance
language varied between conversational, instructional, and policy tone
updates felt difficult because everything was tied together
The goal was straightforward:
“We just want to make sure this is right before we finalize it.”
They weren’t looking to redesign everything—just validate what they had and get guidance in an area that was new to them.
Why this approach made sense
At this stage, continuing to edit the handbook wouldn’t have solved the problem—it would have reinforced the same structural issues.
The document was still trying to do too many things at once.
Instead, the focus shifted to defining a clear documentation structure first—so every decision moving forward had a consistent foundation.
This centered on separating:
Employee Handbook → policies, expectations, and protections
SOPs (Standard Operating Procedures) → how work actually gets done
Onboarding / Training Materials → how employees learn and apply expectations
Appendices / Forms → supporting documents and references
This also included aligning language and tone so the document would be:
appropriate for an employment attorney review
clear and usable for supervisors
understandable for seasonal employees
What the work included
reviewing the existing handbook draft and cooperative template
identifying where content created risk, confusion, or unnecessary complexity
separating content into:
handbook vs SOP vs onboarding vs appendices
refining language to align with policy vs instruction vs training intent
flagging areas to review with an employment attorney
providing plain-language examples for how each section should be written
delivering a structured guidance document with clear next steps
completing a quality control review after the first round of revisions
What they received
Documentation Structure & Guidance Packet (multi-page)
Clear definition of:
what belongs in the handbook
what should move to SOPs
what belongs in onboarding/training
Section-level guidance for revising the current document
Language direction to support consistency and clarity
Identified areas for attorney review
A system that could be used for future updates—not just this version
What changed
Instead of continuing to revise a single document, the owner shifted to building a documentation system that could scale with the business.
The handbook became:
more focused
easier to navigate
more appropriate for legal review
Operational details were moved into SOPs, allowing:
procedures to be updated without rewriting policies
clearer expectations for supervisors managing seasonal staff
more effective onboarding and training development
Most importantly, future decisions became easier.
Instead of asking:
“Where do we put this?”
They now had a structure that consistently answered:
“What type of information is this—and where should it live?”
What this prevented
mixing legal, operational, and training content into one document
rewriting policy every time procedures changed
confusion for supervisors managing seasonal staff
delays and uncertainty before attorney review
building documentation that becomes difficult to maintain over time
Investment: $2,000 (Targeted Discovery Engagement)
Initial scope began at $1,500 and expanded to include structured guidance and quality control review.
This example reflects a representative scenario based on real client work and common patterns across similar organizations. Details have been adjusted for clarity and confidentiality.