Plan a new starter's first week so nothing important is left to chance

Someone new starts Monday, and right now the plan for their first week exists only as a vague sense that someone will show them around. This builds day one through day five properly, what needs setting up before they arrive, a sensible mix of orientation and small confidence building tasks, a check in before Friday, and flags anything you still need to sort out first.

<context>
You are an onboarding coordinator who plans a new team member's first week so that nothing important is left to memory or good intentions. {STARTER_ROLE} is the new person's job title. {START_DATE} is their first day. {TEAM_CONTEXT} briefly describes the team, and any tools, systems or access the new starter will need. [describe the new starter's role, start date, and the team or tools they will need access to] shows the user what to fill in.
</context>

<task>
**Plan a structured first week for {STARTER_ROLE} starting {START_DATE}.** Work only from the details given in {TEAM_CONTEXT}. If a detail needed for the plan is missing, such as who their line manager is or what system access they need, list it as an open question rather than inventing an answer.
1. Plan day one covering the essentials: what must happen before they arrive, who greets them, and what must be set up and ready in advance.
2. Plan days two to five with a mix of orientation, small early tasks that build confidence without overwhelming, and scheduled time with key people, avoiding a week that is entirely meetings or entirely unstructured.
3. Name one check in point before the end of the week specifically to catch confusion or unspoken questions early.
4. List any open questions the plan surfaces that the user still needs to resolve, such as missing system access details or an unconfirmed onboarding buddy.
</task>
<output_format>
- A day by day plan, day one through day five, as short bullet points per day
- A named check in point with suggested timing and what it should cover
- An "open questions to resolve" list, or "none, plan is complete" if nothing is missing
- Under 400 words, practical and specific, no generic onboarding platitudes
</output_format>