Crew Hiring and a 90-Day Ramp (For Owners—and the Office Manager Supporting Them)

Grunlo is field service operations software for landscaping, lawn care, and similar route-based businesses—this article is written primarily for owners who still carry the hiring risk on their shoulders, with a smaller slice for the office manager who turns your standards into a daily system.

This is not legal advice, and it is not a replacement for your state’s employment rules, insurance requirements, or payroll provider. It is a practical ramp: how to protect quality, margin, and customer trust during the first 90 days after you bring someone new onto a crew.

The real goal: predictable behavior before “culture workshops”

Most bad hires do not fail on skill—they fail on uncertainty:

• They do not know what “on time” means at your company.
• They do not know who is allowed to promise what to a customer.
• They do not know where the schedule officially lives.

Your 90-day job is to remove uncertainty faster than bad habits can form.

Days 1–14: boring standards beat inspirational speeches

Define three non-negotiables (write them down)

Examples owners actually enforce in strong crews:

1. Start standard — truck rolls at X; yard wheels do not turn before Y.
2. Customer boundary — who may text a customer, and from which channel.
3. Quality evidence — what “done” looks like on common job types (photos, edges, debris, gate closed—whatever matches your brand).

If you cannot explain each in two sentences, your new hire is improvising—and your customers will notice before you do.

Put the schedule somewhere the whole team believes in

If the crew routes around the official board, you do not have a software problem—you have a trust problem. The onboarding mindset here mirrors what we wrote for software adoption: start small, earn credibility, then expand—see The first 30 days with new scheduling software.

For what belongs on the device itself (and what becomes dangerous clutter), read What to put on your field tech’s phone.

Days 15–45: crews, calendars, and accountability (where your office manager earns their keep)

This is the window where “we hired a good person” either becomes a reliable teammate or a quiet drain on dispatch.

If you have an office manager, give them explicit ownership of:

• Crew membership and roles — who is on which crew, and who is the leader in the field. Grunlo models crews as groups that inherit schedule templates and route together; see Crews.
• Working hours reality — templates and overrides that match what you can actually staff. See Staff scheduling.
• Access and invites — the boring work of getting people into the system with the right permissions. The Help Center separates “who can log in” from “how crews operate day to day”: start at Managing your team, then use Adding & managing staff as the operational checklist.

Owners should stay involved enough to catch policy drift (extra promises, extra tools, extra “helpful” side channels). Your office manager can execute; you still own the standard.

Days 46–90: time, quality, and the moment you promote autonomy

Time tracking: turn it on when payroll discipline becomes the bottleneck

Some owners want time clocks on day one. Others wait until labor cost variance shows up. Neither is morally superior—it depends on how tight your payroll truth needs to be.

When you are ready, field techs punch from the mobile flow described in Clock in & out, and the office reviews entries in Time clock.

Quality reviews should be weekly at first—even if they are short

Pick a cadence the owner can keep:

• two “good job” specifics
• one correction with a clear next visit expectation
• one systemic note (truck stock, route cluster, estimate language)

If you only give feedback when something catches fire, your best new hires will leave first—they are the ones who care.

How Grunlo helps (without pretending software hires people)

Grunlo does not choose your people for you. It reduces operational drag once you decide who is on the team: crews, schedules, routing, field updates, and (when you choose to use it) time tracking live in one place instead of being rebuilt from memory every Monday.

If you are still setting up the basics, the in-product checklist is a good parallel discipline: Onboarding checklist.

Key takeaways

• Week one is behavior, not branding—define punctuality, customer boundaries, and “done” before you add complexity.
• Days 15–45 are systems—crews, schedules, and access should be clean enough that dispatch is not playing detective.
• Time clocks are a timing decision—use them when labor truth matters more than onboarding friction.
• Owners set standards; office managers operationalize—if both roles collapse into one person, prioritize the smallest system that prevents customer surprises.

Related reading

• Blog: When the schedule breaks — new hires amplify schedule chaos if communication standards are weak
• Blog: Why customers leave — inconsistent quality is a top churn driver
• Blog: 5 ways to reduce drive time — unrealistic routing burns new hires fast