How we architect employee onboarding on Smartsheet Control Center — a provisioned workspace and dashboard for every hire, 30/60/90 day milestones that track themselves, and manager rollups by cohort, department, and start date.
Most organizations have an onboarding checklist. Very few have a way to see, on any given Tuesday, which of their last thirty hires are behind on which task and whose manager needs to hear about it. The work spans HR, IT, facilities, and the hiring manager, and no single system owns the whole of it.
The design principle is the same one that makes Control Center worth using anywhere: build the structure once as a blueprint, then let the system create it identically every time a hire is approved. Nobody copies a folder. Nobody forgets a step.
A new hire record enters through an HR intake form or arrives as a Data Shuttle extract from the HRIS, matched on employee ID. That record is what triggers provisioning — hire approved, workspace exists, no manual step between the two.
Control Center provisions a workspace for each new employee from a blueprint: the task plan, the 30/60/90 milestone structure, the document library, and a personal dashboard. Role and department variations are handled as separate blueprints, not manual edits.
Each hire gets their own view — what is due this week, what is coming at day 30, who to contact, and which documents to read. They see their onboarding, not a corporate checklist filtered down to them.
Above the individual workspaces, reports roll every active hire into views by manager, department, cohort, and start month. A manager sees their people; HR sees the program; leadership sees whether onboarding is working.
The reason ramp plans fail is that they require someone to remember to check them. Building the milestones as dated, owned, dependency-linked tasks means status is a property of the data rather than something a manager has to report.
Accounts, equipment, badging, payroll, benefits enrollment, mandatory training, team introductions. These tasks have owners outside the hiring manager, which is exactly why they need assignment and automated reminders rather than a checklist someone owns informally.
Role-specific training, systems access at working depth, shadowing, first owned deliverable, and a structured 30-day check-in that is a task with a due date rather than a calendar invite that gets moved twice and then dropped.
Full workload, goal setting for the first review period, and a 90-day review that closes the onboarding record. Completion is a gate, so an incomplete onboarding stays visible instead of quietly expiring.
With every hire on an identical structure, the program becomes measurable: time to complete by department, which tasks stall most often, how cohorts compare, and which managers need support. That is the reporting layer a checklist can never produce.
Three choices shape whether this scales or becomes another system HR maintains by hand.
Smartsheet is the work management layer, not a second employee database. The HRIS owns the employment record; Smartsheet owns the tasks. Data Shuttle keeps them synchronized on employee ID so nobody maintains two sources of truth.
Cost is driven by how many genuinely distinct onboarding structures you run, not how many people you hire. Ten hires a year or a thousand is the same build if they share a blueprint. Most organizations need fewer variants than they expect — differences are usually task-level rather than structural.
Onboarding data is sensitive. New hires should see their own workspace and nothing else; managers see their reports; HR sees the program. Dynamic View handles row-level and field-level access, and that model gets designed before the first sheet is built, not retrofitted afterward.
No. New hires interact through Dynamic View or a published dashboard, which requires no license on their side — only the owning organization is licensed. Licenses are needed for the people building and administering the solution, typically a small HR and IT group.
No, and it should not. Workday, UKG, ADP, or whatever holds your employment records stays the system of record. Smartsheet manages the onboarding work that sits around that record — the cross-departmental tasks, ramp plans, and reporting your HRIS was never designed to run.
It depends on hiring volume. If you onboard a handful of people a year, templates and automations get you most of the way and Control Center is hard to justify. It earns its cost when manual workspace creation starts producing drift, or when you need to push a blueprint change out to onboardings already in progress. We would rather tell you it is premature than sell it to you.
Yes, and it is usually the same architecture with a different blueprint — a provisioned checklist spanning IT, HR, facilities, and the manager, with a hard completion gate because the compliance stakes on offboarding are higher. Teams commonly build onboarding first and add offboarding as a second phase.
The 90-day review is the natural handoff. Goals set at day 90 carry into the first full review cycle, and the same permission and rollup patterns used here apply directly to review workflows — which is why organizations that build one often build the other.
Tell us how many people you hire, how many distinct roles they fall into, and what your HRIS is. That is enough for us to tell you whether this is a template build or a Control Center build.
Pick a time that works. We will come prepared with questions about your hiring volume, role mix, and reporting needs.
Architecture, components, and outcomes from grant portfolios, construction programs, and more.