Standard Operating Procedure: CMU New Hire Onboarding

The objective of this onboarding SOP is to provide a seamless, standardized, and professional integration process for all new hires at Carnegie Mellon University (CMU). By following this structured workflow, hiring managers and department administrators ensure that new employees are administratively compliant, technologically equipped, and culturally integrated from day one. This process is designed to minimize transition friction, uphold university security standards, and optimize immediate productivity.

Phase 1: Pre-Arrival Administrative Logistics

• Workday HCM Initiation: Ensure the new hire’s offer letter is fully executed and the "Hire" business process is initiated in Workday.
• Identity Management: Confirm that the new employee has received their Andrew ID activation link. Verify the status of their email account setup.
• Security & Compliance Training: Assign mandatory university compliance modules (e.g., Data Privacy, Conflict of Interest, Title IX) via the internal learning portal.
• Hardware Procurement: Request necessary IT assets (laptop, monitor, peripheral devices) through the department’s IT liaison or the central Service Desk at least two weeks prior to the start date.
• Workspace Preparation: Coordinate with facilities to ensure office space, desk assignments, and keycard/building access are provisioned.

Phase 2: First-Day Integration

• University Orientation: Ensure the employee is registered for and attends the official CMU New Employee Orientation session.
• Access Verification: Test access to the physical office, internal shared drives (Box/OneDrive), and necessary departmental software suites.
• Andrew ID & Duo Security: Verify that the employee has successfully configured Duo Mobile for multi-factor authentication, as this is essential for all CMU systems.
• Team Introduction: Conduct an initial department-level meet-and-greet to introduce the new hire to immediate team members and key stakeholders.
• Goal Setting: Review the initial 30-60-90 day plan to ensure clarity on role expectations and key performance indicators (KPIs).

Phase 3: First-Week Competency Building

• System Access Audit: Review all platform access (e.g., S3, Workday, Canvas, internal databases) to ensure the employee has the correct permission levels.
• Policy Review: Walk the employee through department-specific handbooks, communication protocols, and meeting cadences.
• Tooling Deep-Dive: Schedule "how-to" sessions for department-specific workflows, project management software, and document version control standards.
• Benefits & Wellness Review: Direct the employee to the HR Benefits portal to finalize payroll, tax withholding, and retirement plan selections.

Pro Tips & Pitfalls

• Pro Tip: Create a "Buddy System." Pair the new hire with a peer mentor (not their direct manager) who can answer informal questions about university culture and office norms.
• Pro Tip: Document everything. Maintain a shared onboarding folder that contains links to FAQs, org charts, and essential "how-to" documentation to reduce dependency on managers.
• Pitfall - The "Firehose Effect": Avoid overloading the new hire with documentation on Day 1. Spread out technical training over the first two weeks to avoid cognitive fatigue.
• Pitfall - Compliance Lag: Failure to complete mandatory training in the first 30 days can lead to system access suspensions. Set clear deadlines in the onboarding calendar.

Frequently Asked Questions

Q: What should I do if the new hire has issues with their Andrew ID? A: All Andrew ID and authentication issues should be directed to the CMU Computing Services Help Center. Ensure the hire has their official CMU ID number ready for verification.

Q: How do I request special software licenses not included in the standard build? A: Submit a request through the university’s software portal or your departmental IT support. Note that some specialized software may require internal budget approval or department head sign-off.

Q: Is the onboarding process identical for remote vs. on-campus employees? A: While the core administrative tasks remain the same, remote onboarding requires additional emphasis on virtual meeting etiquette, VPN configuration, and proactive digital check-ins to ensure the employee feels connected to the university culture.