Crew operations
Crew scheduling that isn't a group chat
Built for Twin Timbers Tree Service because scheduling a crew over text messages stops working somewhere around the sixth person. Now opening up to everyone else with the same problem.
CREWBOSS wasn't designed as a product. It was built for one tree service that needed it, which is generally the reason tools end up actually working.
It's now being opened up, because the problem isn't specific to Twin Timbers: post the gig, let people claim shifts, and have a record afterwards of who worked what.
What it does
- Post gigs and shifts with location, timing and what's needed.
- Self-signup, so scheduling stops being one person's second job.
- See who's where across active jobs.
- A record afterwards of who worked what, which matters for billing and payroll.
Who it's for
- Tree services running multiple crews across jobs.
- Fire and mitigation contractors with seasonal and on-call staff.
- Any field operation where the schedule currently lives in a group chat.
Common questions
How do you schedule a tree service crew?
Post shifts somewhere the whole crew can see them and claim what they can work. The gain isn't the posting — it's that double-booking becomes impossible and there's a record once the season is over, which is what payroll and billing disputes turn on.
Is CREWBOSS only for tree services?
It was built with one, so the vocabulary comes from that, but nothing in it is specific to trees. Any crew-based field operation works the same way.
What is Twin Timbers?
The tree service CREWBOSS was built for. It exists because they needed it.
Start here
Model the risk first: FUELBREAK
Scheduling tells you who's working. FUELBREAK tells you which ground is worth their day — assessment at parcel and landscape scale, built by a firefighter.
See what FUELBREAK does