yourtech
← All posts

Setting Up a New Hire Shouldn’t Take You All Day

August 25, 20264 min readJay Frontela

The Monday Morning Scramble

New person starts today. You knew about it for three weeks. And yet here you are at 8:15 on a Monday, digging through a drawer for a laptop somebody returned in March, trying to remember the admin password, and texting your office manager to ask which software this role actually needs.

By 11:30 the new hire has been sitting in the break room reading the employee handbook twice. By 2:00 they have an email address but no access to the shared drive. On Thursday they finally get into the CRM because somebody remembered it exists.

Every small business I work with in Palm Beach County has lived this exact morning. It’s not a sign anybody’s bad at their job. It’s a sign nobody ever wrote the process down.

What the Scramble Actually Costs

Let’s put a number on it, because the number is worse than it feels.

Say the owner or office manager burns four hours getting one person set up. At a loaded cost of $50 an hour, that’s $200. The new hire sits idle for a day and a half at $25 an hour, another $300. Hire six people a year and you’re at roughly $3,000 in pure friction, plus whatever your new employee now privately thinks about how organized this place is.

Then there’s the part that shows up later. When you’re rushing, you take shortcuts. And the shortcuts are where the security problems get born.

The Phrase That Creates Security Holes

Here it is: just give him the same access as Maria.

Sounds efficient. It’s the single most common way small businesses end up with everybody holding admin rights to everything.

Because Maria has been there six years. She covered for the bookkeeper in 2023, so she has payroll access. She helped with the website once, so she has the hosting login. She was temporarily made a local admin to install a plugin and nobody ever removed it. Copy Maria’s permissions and your brand new employee, on day one, can see salaries and delete the company file server.

Do that four or five times and permissions in your company have nothing to do with job roles anymore. They’re just sediment.

Build a Role Template Instead

Stop provisioning people. Start provisioning roles.

Sit down for one hour, list every job type in your business (front desk, technician, sales, bookkeeper, manager), and for each one write down:

  • Which security group or distribution list they belong to
  • Which shared folders they need, and read only versus read and write
  • Which applications and licenses they get
  • Whether they need a laptop, a desktop, or a phone
  • What they specifically should NOT have

That last line matters as much as the rest. Writing down that a front desk role never touches payroll makes the exception obvious the day somebody asks for it.

Then, and this is the important part, assign access to groups, not to individual people. Put the person in the Sales group and the Sales group has the folders. When they move to a different role, you move them between groups instead of hunting through nine systems trying to remember what they were given.

The Checklist That Turns Four Hours Into One

Here’s the skeleton. Adjust it to your business and keep it in a shared doc where your manager can run it without you.

One week before start date

  • Confirm the role template and who approves it
  • Check license counts (nothing stalls a Monday like discovering you’re out of Microsoft 365 seats)
  • Pull a machine, image it, patch it fully, install the standard app set
  • Enroll the machine in your management and antivirus tools before it leaves the office

Day before

  • Create the account, add it to the correct groups, do not add anything custom
  • Set a temporary password with forced change at first login
  • Pre-stage MFA enrollment so it’s their first task, not an afterthought
  • Create the email signature, set up the mailbox, add them to the right shared inboxes

Day one

  • They log in, change the password, enroll MFA on their phone. Fifteen minutes, done together.
  • Ten minute walkthrough: where files live, how to report a suspicious email, who to call when something breaks
  • Show them the password manager and how to use it. Do this on day one and you never fight the sticky note habit later.

Day thirty

  • Ask what they still can’t access. There’s always something.
  • Remove any temporary access granted during training

Now Run It Backwards

Your offboarding checklist is the same list in reverse, and it’s the one most businesses never build at all. Disable the account (don’t delete it, you’ll want the mailbox), convert it to a shared mailbox, forward the email, collect the hardware, remove them from every group, wipe the phone profile, change any shared credentials they knew, and revoke their building access.

Same document. Two columns. If a checkbox exists on the way in, it exists on the way out. That one habit closes more security gaps than most of the software people try to buy.

Where This Gets Easy

Once the process is written, the tooling makes it fast. Group based permissions in Microsoft 365, standard machine images pushed automatically, remote management that installs the app set without anybody touching a keyboard. That’s the point where onboarding stops being an event and becomes a form somebody fills out.

Getting to that point is a couple of days of work, not a couple of months. We build these templates for businesses from Delray Beach to West Palm, then run the process for you so nobody’s scrambling at 8:15 on a Monday again.

Bring us your next hire and we’ll build the checklist around them. Always happy to troubleshoot.

// Let's talk

Want this checked on your systems?

Send me a message. I'll tell you what I see in plain English and you decide what's next.

Start a conversation