Loading page
About this tool
Turns a role, team and access list into a first-week onboarding document prompt with an hour-by-hour split across the standard sections.
The Onboarding Doc Prompt Builder turns a job title, role family, seniority and access list into an AI prompt that produces a complete first-week onboarding document with an hour-by-hour timetable. It divides the week's available hours across six standard sections — access and tooling, team and mission, product primer, how the work gets done, a supervised first contribution, and rituals and feedback — using the largest-remainder method on quarter-hour blocks, so the allocations always add back to the exact total instead of drifting through rounding. It is built for hiring managers and people-ops teams who need the generated document to carry a real schedule, a named first deliverable and 30/60/90-day checkpoints rather than an open-ended reading list.
Open Onboarding Doc Prompt Builder on AltFTool — it loads instantly in your browser.
Add your input to the workspace.
Adjust the options until the result looks right.
Copy or download the output and put it to work.
The week's hours are apportioned by section weight in 15-minute blocks, so the generated document says how long each part should take and the parts sum to the exact total.
Eight role families set the first-week deliverable and the emphasis, and four seniority levels change how much scaffolding the document provides — a junior gets defined jargon, a lead gets the stakeholder map and pending decisions.
Any link, tool, person or policy you did not supply is written into the prompt as TODO(fill) with a description of what belongs there, so nothing fabricated reaches a new hire.
Six sections, in this order: accounts and access, team and mission, product and domain primer, how the work actually gets done, one supervised first contribution, and rituals plus the feedback loop. Access comes first because a new joiner blocked on a login cannot start anything else. This tool generates a prompt that demands all six with a time budget for each.
Budget for productive onboarding time rather than the full working day — 4 to 6 hours a day is realistic once meetings, setup friction and breaks are removed, giving roughly 20 to 30 hours in a five-day week. This tool takes your figure and splits it, allocating the largest share (25%) to the supervised first contribution and 15% to access and tooling.
It is the conventional set of ramp checkpoints at 30, 60 and 90 days, each stating what 'on track' looks like. The generated prompt asks for one short paragraph per horizon written in observable terms — shipped work, decisions owned, systems understood — rather than sentiments like 'feels settled'.
Use a Markdown runbook when it lives in the repo next to the code, a collapsible wiki page when it must scan in under a minute, and a flat checklist when the priority is completion tracking rather than context. This tool writes a format-specific prompt for any of the three from the same inputs, including the exact structural rules for that format.