You Onboard Every New Hire the Same Way. Why Not Every New Project? 

Eliminate project chaos and permission headaches. See how ATG Setup automates templates, role-based access, and platform sync from project kickoff to closeout.

Here’s a question for every IT leader in AEC: if a new hire showed up Monday morning and nobody had a laptop, an email account or a desk ready, how long would it take for someone to call it a failure? 


About five minutes, probably. Because onboarding is a solved problem. There’s a ticket, a checklist and an owner. Everybody knows what “ready” looks like. So why is it that when a new project kicks off, worth millions of dollars and touching dozens of people, the setup process is whatever the PM remembers from last time?

The New Hire Gets a Checklist

Think about what happens when someone joins your company. HR sends the start date. IT gets a ticket. The laptop gets imaged with the standard build. An email account gets created with the right naming convention. Permissions get assigned by role, not by guesswork. Compliance training shows up in their inbox. The desk is ready. The badge works. By the time they walk in, the company already knows exactly who they are and what they can access. 

It’s defined. It’s documented. It gets audited. And when someone leaves, the same process runs in reverse: access removed, accounts closed, laptop collected. Nobody thinks this is overkill. It’s just how a well-run company works.

The New Project Gets a Copy-Paste

Now think about what happens when a project gets awarded. 

Somebody finds the folder from the last job that looked roughly similar. They copy it, rename it and delete the stuff that obviously doesn’t belong. (Mostly. There’s always a leftover file from the hospital job hiding in the hotel project.) Somebody else sets up the project in the management platform. Someone else creates it in accounting, with cost codes that almost match. Permissions get granted by whoever happens to remember who needs what. And three months later, the architect still can’t see the drawings folder and a subcontractor from two jobs ago somehow can. 


Every project gets set up a little differently, by a different person, in a different order. None of it is anybody’s fault. There’s just no checklist. No owner. No definition of “ready.”
 

Why This Lands on IT's Desk Anyway

Here’s the irony. Project setup usually isn’t IT’s job…but its problems almost always end up there. 

The security questions: Who still has access to that job’s files? Why does a former employee’s account own the closeout folder? Why does an outside partner have permissions nobody can explain? 

The support tickets: “I can’t find the submittals folder.” “Which drive is the current set on?” “Can you restore the file somebody overwrote?” 

The sprawl: duplicate folders, orphaned sites, storage costs creeping up every quarter, and no consistent way to apply retention rules to projects that were never set up the same way twice. 

And the compliance questions, the ones that show up when an owner, an insurer or an auditor asks you to prove who touched what and when. It’s hard to govern something that was never defined in the first place. 

You standardized laptops, accounts and access because inconsistency created risk and wasted time. Projects create the same risk, at a much bigger scale. They just haven’t gotten the same treatment.

What a Project Setup Standard Looks Like

A standard for projects isn’t complicated. It looks a lot like the one you already run for people. 

It starts with a trigger: a project gets awarded, and that kicks off one request instead of six separate ones. It uses a template: the same folder structure, the same naming conventions and the same cost code mapping every time, adjusted for project type instead of reinvented from memory. It assigns access by role: the PM, the superintendent, accounting, the design team and outside partners each get exactly what their role requires, and nothing they don’t. And it creates the project everywhere it needs to exist (project management, design collaboration, file storage, accounting) with the connections between them already in place. 

Then, just like offboarding, it runs in reverse at closeout. Access gets removed. Data gets retained according to the rules. Nothing gets left behind on somebody’s personal drive. 

That’s the shift from a habit to a system. Outcome first: every project ready on day one, set up the same way, secure and connected. Then the process that produces it, every time, without depending on who happens to be doing the setup that week. 

Introducing ATG Setup

That’s why we built ATG Setup: a way to spin up every project the same way, every time. 

One request starts it. Your standard templates drive it. The folder structure, naming, permissions and cost code mapping get applied automatically across the platforms your teams already use, so the project is ready in every system on day one instead of trickling together over the first month. The standard flows one way, from your template out to every new project, so nobody has to remember the rules. And because it’s built on ATG Command ecosystem, the project could seamlessly stay connected after setup, keeping RFIs, submittals and documents in sync for the life of the job. 

For IT, that means fewer tickets, cleaner access and a project footprint you can actually govern. For project teams, it means starting on the work instead of on the folders. And for leadership, it means every project finally speaks the same language, so they can be compared, rolled up and reported on without another translation spreadsheet. 

You already proved this works for people. ATG Setup brings the same discipline to projects. 

Give every new project the same onboarding as a new hire.

Grab some time with our team, tell us how projects get set up today (we promise not to judge the folder named “New Folder (3)”), and we’ll compare notes on what a standard could look like.

Contact Our Team

Learn More About Our Data Solutions