Give a new employee a clear path to contribute safely and effectively. Before the start date, choose a supervisor, identify the first assignment, arrange the necessary equipment, and prepare access to the systems and project information required for the role. Avoid granting broad access simply for convenience. Confirm that project records, client information, and credentials are handled under the firm’s security practices.
At the start, explain role expectations, reporting relationships, timekeeping, expense rules, file naming, document control, cybersecurity, and client communication. Show the employee how to ask for help and how to raise a technical concern. Make clear who assigns work, who reviews it, and who has authority to approve or issue deliverables. A new employee should understand that schedule pressure does not replace required review.
Confirm licenses, credentials, and any jurisdiction-specific restrictions that affect the work being assigned. Ask the employee to describe prior experience and training, then compare that account with the role’s actual needs. Previous experience may not transfer directly to your clients, software, codes, or quality procedures. Set learning goals tied to real tasks, with supervision appropriate to the employee’s experience.
Pair the person with an experienced colleague who has time for questions. Schedule check-ins after the first few days and during the first assignments. Ask what information, access, or tools are missing, and assign someone to close each gap. For example, if a new engineer cannot find current survey standards or does not know which design template to use, resolve that before the next deadline.
Keep employment documents and training records securely, and ask HR or counsel which records the firm must retain and who should have access. Onboarding does not transfer professional responsibility or replace formal safety and technical training.
Give the new employee a named supervisor and a written first month plan that covers project assignments, software access, file standards, safety procedures, and review expectations. Set up the accounts and equipment before their start date, then pair them with a teammate for the first project tasks. For example, have them review a completed plan set and its comment history before preparing a similar sheet. Schedule regular short check-ins so questions surface early, and explain who can approve technical work, client commitments, and time entries.
This is general education, not legal, tax, or engineering advice; licensed PE judgment and local codes govern.
