Imagine a small property-management office hiring an office administrator. The offer is accepted, the start date is set and the laptop is ordered. On the Friday before, the office manager realizes nobody has decided what the new administrator will actually work on in the first week, who answers their questions, or what they can handle without asking.
This is a fictional example, but the gap is easy to recognize: the logistics of a first day get planned, while the decisions behind it are left to be made on the day.
A checklist covers equipment, accounts and paperwork. This article is about the short list of decisions that sit behind it, and why they are easier to make before day one than during it.
Decide what the first week is for
A first week can serve different purposes: learning the systems, meeting the people the role depends on, or completing a first real piece of work. Most first weeks include all three, but it helps to say which one comes first. If the office manager expects a completed rent-reminder batch by Friday while the administrator thinks the week is for shadowing, both will judge the week by different measures.
Write one sentence that states the purpose. It will shape every other decision on the list.
Carry forward what the interviews did not establish
Before the panel, decide who asks about what suggests recording an area as “not covered” when an interview did not reach it. Those notes are useful again here. A part of the role nobody asked about during hiring is a reasonable thing to learn about, supportively, in the first week.
That is not a second assessment. It is a way of making sure the first week covers what the hiring process could not.
Make a five-decision first-week note
Before day one, decide and write down:
- Purpose: what the first week is mainly for.
- Go-to person: who answers day-to-day questions, and when they are available.
- First real task: one piece of work to complete, and what “done” means for it.
- Decisions they can make alone: what the new hire can handle without checking first, and what should come to someone else.
- End-of-week conversation: when it happens, who attends and what you will ask.
For the fictional office administrator, the note might read:
Purpose: learn the tenant-request process well enough to handle routine requests.
Go-to person: the senior administrator, available every morning until noon.
First real task: log and route the week's incoming maintenance requests; done means each one has an owner and a date.
Decisions they can make alone: scheduling routine repairs within the approved vendor list; anything involving cost goes to the office manager.
End-of-week conversation: Friday at 3:00 with the office manager; ask what was unclear and what they would change about the request process.
This is an illustrative worksheet for the article, not a claim that a particular product includes a separate first-week file.
Share the note on day one
The note is most useful when the new hire sees it. Reading it together on the first morning turns assumptions into a shared starting point and gives the new hire a reference for the rest of the week.
The organization supplies its own HR and legal review for its onboarding process, including any accommodations. A first-week note is a way to record decisions, not a guarantee of performance, retention or any other outcome.
The aim is modest: by Friday, both people should be able to say what the week was for and whether it did that.
If practical hiring resources would help, compare the hiring packs and their included materials.