How Long Does It Take to Set Up a New Hire in an AEC Office?

You hired someone great, and they start Monday. Then it hits you on Thursday: do they have a computer, an email account, a Revit license, or any way to open the project files?

This scramble is more common than firms admit, and it has a real cost. A new hire who sits around for three days waiting on a working computer is three days of salary spent watching someone else fix a setup. The good news is that a smooth first day is very doable. It just takes getting ahead of it.

Here is the short version. Setting up a new hire at a firm takes more than a typical office, because it is not just an email account. It is a real workstation, Autodesk software installed with a seat assigned to them, your office templates and standards, file access with the right permissions, and MFA. The hands on work is only about two hours. The catch is when that work has to start. Plan on three weeks, because ordering the workstation is the long pole, not the software. Do it that way and the person is productive on day one. Skip the plan and it drags into days of lost time.

Why an Architecture, Engineering, or Construction hire takes more than a normal office hire

First, set expectations. Onboarding a designer or engineer is heavier than onboarding a typical office worker, and it helps to know why.

A normal office hire mostly needs an email account, a login, and a basic laptop. That is quick. An Architecture, Engineering, and Construction hire needs all of that plus a lot more. A machine that can actually run Revit and Civil 3D, not a consumer laptop from a big box store. If you are not sure which way to go there, we broke that down in our post on whether you need a workstation or a laptop. Autodesk software installed, which is a big, slow install, with a seat assigned to them by name. Bluebeam and any other design tools. Your office templates, families, and standards so their work matches everyone else’s. Access to the right project folders, with the right permissions. And security set up from the start.

So when someone asks “how long does it take,” the honest answer is: longer than you think, because there is more to it than an email address.

Here is the part that surprises people. The Autodesk install is not where the human hours go. That part mostly runs on its own while you do something else. The real time goes into file access, templates, and accounts. Those are the pieces that need someone to think.

The hands on work is only about two hours. The trick is that it starts three weeks before the person walks in.

Start three weeks out, not three days out

The workstation is the long pole. If you do not have a spare on the shelf, you are ordering one, and a machine built for Revit is usually not sitting in a warehouse ready to ship overnight. Between the order, the build, and shipping, two to three weeks is normal. Add a few days if your vendor is backed up.

The Autodesk seat can be a wait too. If every seat you own is already assigned, somebody has to approve buying another one. That is a budget conversation, not a five minute task.

For example, let’s say your new engineer starts on the 1st. You should be ordering hardware and checking your seat count around the 10th of the month before. Everything else can happen in the last week. Miss that, and no amount of preparation on Friday fixes it.

With a plan: about two hours of hands on work

Here is the encouraging part. Once the hardware shows up, the actual work is small. For a firm with a repeatable process, it is roughly two hours of hands on time, and almost all of it happens before the new hire walks in.

The machine gets built to your standard setup. Autodesk software gets installed. Their seat gets assigned in Autodesk Account. Email and accounts get created. MFA gets turned on. File access gets granted. Templates get loaded.

One detail matters here, and a lot of people get it backwards. You can install Autodesk software ahead of time, and you can assign the seat ahead of time. But the license does not actually go live until the new hire signs in with their own Autodesk ID, and that first sign in needs an internet connection. So the right way to say it is: installed and assigned before day one, activated by them in the first five minutes of day one.

Monday morning, they sit down, sign in, and start working. First impression: this is a firm that has its act together. That is what preparation buys you.

Without a plan: days of lost time

Now the version most small firms know too well. Nobody prepped anything, so it all happens after the person arrives.

Monday morning, someone realizes there is no spare computer, so one gets ordered. Now the new hire is waiting weeks, not hours. The Autodesk install takes hours and hits a license snag. The new hire cannot reach the project files because permissions were never set. The office “computer person,” who has their own real job, drops everything to cobble it together between their own deadlines. We wrote a whole post on that person in the accidental IT person problem, and new hire setup is one of the biggest fires they fight.

Meanwhile, your new hire sits there, eager and idle, forming a first impression that the firm is a bit of a mess. Days of salary, gone, and a rough start for someone you worked hard to recruit. All of it avoidable.

What a good onboarding actually includes

A solid onboarding covers these pieces, ideally as a written checklist so nothing gets missed.

• The hardware. A machine that fits the work, ordered early, built and tested. If you are not sure what specs matter, we cover that in our post on whether your workstation is slowing down Revit or Civil 3D.
• The accounts. Email, Microsoft 365 or Google, a Teams or phone extension, and any project software accounts, all created and ready.
• The Autodesk setup. Software installed, and a seat assigned to their own Autodesk ID. Autodesk requires each named user to have a unique ID, and IDs cannot be shared between people. Sharing one login is how you end up with “not entitled” errors and a license fight nobody has time for, which we cover in our post on Autodesk license errors.
• The standards. Your office templates, families, and title blocks loaded, so their drawings match the firm from day one.
• The project access. Not just the file server. If you run BIM 360 or Autodesk Construction Cloud, they have to be invited to each project, one at a time. That is easy to forget.
• The plotting setup. Printers and plotters added, with your CTB or PC3 files in place. Boring, and always the thing nobody did.
• The security. MFA turned on, a spot in your password manager, and a quick word on spotting scam emails. Security belongs in onboarding, not as an afterthought, which we cover in our post on what small firms get wrong about passwords.

Two shortcuts that backfire

These two come up constantly, and both feel efficient. Both cause trouble.

Do not build a “golden image” with Autodesk software baked in. Building one master computer and copying its whole hard drive to every new machine sounds like the smart move. Autodesk says otherwise, in writing: imaging software is not supported, and it can cause licensing conflicts, incomplete installations, and activation problems. The supported way to push Autodesk software to multiple machines is a deployment, which you create in Autodesk Account. Microsoft has moved the same direction for Windows itself, and now points firms at Autopilot instead of traditional imaging. So the goal is right. Every machine should come out the same. Just get there with a written build standard and a deployment, not a disk copy.

Do not hand a new hire a sheet of passwords. We have all seen the printed login sheet sitting on the desk on day one. It undoes the password manager and the MFA you just set up, and it is the first thing an auditor or a cyber insurance carrier will ask about. The better version takes the same five minutes. Issue a temporary access pass, which is a single use code that expires, then have them set their own password and register their own MFA on their own phone.

That last part matters. You cannot finish MFA setup for somebody before they exist on site. If your IT person registers the second factor on their phone, your IT person now holds it, and the whole point is gone. What you do before day one is turn the policy on. What they do on day one is register.

The file access detail that breaks Revit

“Give people only what they need” is good security advice. Applied blindly to a Revit project folder, it breaks worksharing.

Revit creates a backup folder right next to the central model. It holds editability and ownership information, and it has to stay put. If your permissions let people open the central file but not write to that folder, sync with central starts failing and nobody knows why.

So set permissions per project folder, not per file, and make sure the whole folder including the backup folder is writable by the team on that project. Tight is good. Too tight is a support ticket.

One more, while we are here. Do not put a workshared Revit central file in a synced folder like OneDrive, Dropbox, or Box. Those services are not built for it, and Autodesk’s own answer for worksharing over the internet is Revit Cloud Worksharing with BIM Collaborate Pro. Getting this wrong on a new hire’s first week is how a model gets corrupted.

Make it repeatable, and it gets easy

Here is the real secret. The first time you set up a new hire, it is work. After that, it should be a checklist you run, not a problem you solve from scratch every time.

Write down the steps once. Write down your build standard, so every new machine gets the same software, settings, and folders. Keep a simple onboarding checklist that anyone can follow. Then each new hire is a known, smooth routine instead of a fresh scramble.

Be honest about your size, though. If you are a three person firm that hires once every two years, do not build a whole system. A one page checklist is enough, and anything fancier will be out of date before you use it again. The bigger your hiring pace, the more the process pays for itself.

The same idea applies in reverse when someone leaves, which we cover in our post on what happens when a former employee still has access to your files.

Being proactive here pays off twice. Your new hire has a great first day, and your team does not lose hours putting out an avoidable fire. Proactive beats reactive, even for hiring.

Frequently asked questions

We make new hire setup a non event

A great first day tells a new hire they joined a sharp, well run firm. A chaotic one tells them the opposite, on day one. We help small architecture and engineering firms around Knoxville build a fast, repeatable onboarding process: hardware ordered on time, software installed and licensed the supported way, access set correctly, and security in place before the person walks in.

If your last new hire spent their first days waiting on a working setup, give us a call. We will build an onboarding process that gets the next one productive on day one. So your team can focus on welcoming them, not on wiring them up.

Sources: Autodesk: To use imaging software to distribute products; Autodesk: hard disk clone is not supported; Autodesk: account sharing restrictions; Autodesk: user authentication and license activation; Autodesk: create deployments from Autodesk Account; Autodesk: about backup files for workshared projects; Autodesk: how to use cloud synced services with Revit files; Microsoft: configure a Temporary Access Pass; Microsoft: Windows Autopilot overview