Make a first-week plan for a new teammate

A first-week plan often contains everything the organization wants a new person to know. That can produce a long reading list without helping the person understand what matters today, who can answer a question, or how their role connects to current work.

Onboarding should follow the organization’s employment, accessibility, security, and privacy practices. This article offers a coordination framework, not human-resources or legal guidance.

Start with access that enables real tasks

List the accounts, equipment, spaces, and permissions needed during the first week. Assign an owner to each access request and test that it works before a scheduled task relies on it.

Provide a secure route for obtaining credentials and reporting a problem. Do not send passwords in an onboarding document or ask the new teammate to work around an access control.

Build context in layers

Begin with the role, the team’s current priorities, and the people connected to the work. Introduce deeper history when it explains a present decision. A complete company archive can remain searchable without becoming required reading on day one.

Use descriptive links: “current quarterly priorities” and “approved customer terminology” are better than a list of unlabeled documents.

Arrange useful relationships

Schedule a small number of conversations with a clear purpose. The new teammate may need to meet a manager, a close collaborator, and someone who understands the customer or system. Explain what each person can help with.

Avoid filling every hour with introductions. Leave time to process notes, complete setup, and follow a question while it is fresh.

Give one bounded contribution

Choose a real task that matters and can be completed with the context available. Define what done means and who will review it. A fictional exercise can teach a tool, but a small authentic contribution helps the person see how work moves through the team.

The task should not secretly depend on undocumented knowledge. If it does, treat the missing context as an onboarding finding rather than a failure by the new teammate.

Check understanding in both directions

Ask what remains unclear and which part of the plan felt unnecessary or missing. Invite the person to explain the current priority and next action in their own words. This checks the onboarding material as much as the individual.

Do not require a new colleague to disclose health, family, or other personal information to justify an access or working need. Use the organization’s appropriate confidential process.

End with a map of week two

Record the next contribution, important relationships, unresolved access, and a date for feedback. Remove completed setup tasks from the active view so the plan becomes a current guide rather than a permanent checklist.

A successful first week does not prove that someone has absorbed the organization. It gives them enough safety and context to ask better questions and begin useful work.