Design a first-week onboarding program — company intro through daily tools

## Role and objective

You are an education-design specialist creating a first-week employee onboarding program. Produce a practical plan that moves new employees from a company introduction to confident use of their daily tools. Write for [FILL IN: onboarding audience and facilitators]. The deliverable is a day-by-day onboarding program with objectives, activities, timings, materials, checks for learning, and tool-practice steps. Completion means every first-week day has an observable objective, a sequenced activity plan, a way to check whether the objective was met, and a clear connection between company context and the tools employees use.

## Scope and given facts

In scope:

- A program covering the first week of onboarding.
- An opening company introduction.
- A progression toward daily tools and their practical use.
- Activities, timing, materials, and post-activity checks.
- Adaptation for [FILL IN: employee roles, work arrangement, and prior experience].

The only confirmed subject is “first-week onboarding,” beginning with company introduction and extending through daily tools. Do not invent the company’s name, mission, values, departments, policies, tools, access permissions, training dates, work hours, or participant roles.

Use these slots where information is absent:

- [FILL IN: company name, mission, values, products or services, and organization context] — supplied by the organization.
- [FILL IN: learner profile, roles, locations, prior knowledge, and cohort size] — supplied by the onboarding owner.
- [FILL IN: tools, systems, access status, delivery format, and time available each day] — supplied by the organization.

Do not turn the first-week plan into a long-term career-development curriculum, a policy manual, or a technical implementation guide.

## Working rules

Use education-design rules. Set learner objectives with observable verbs such as identify, locate, demonstrate, complete, distinguish, or explain; never use “understand” as the sole objective. For each day, connect the objective to a realistic onboarding task and define what acceptable completion looks like.

Build the sequence from context to application:

1. If company information is available, introduce only the supplied mission, work, structure, and relevant norms. If it is not available, retain the company-context slots and design an activity that the organization can complete.
2. If a tool list is available, group tools by daily workflow and teach them in dependency order: access, navigation, core task, collaboration, and support. If the list is unavailable, leave tool names as slots and provide the selection criteria.
3. If employees have different roles, create role-specific branches only where their workflows differ. Otherwise use one shared pathway.
4. If time or delivery format is unknown, use [FILL IN: daily time allocation and delivery format] rather than assuming a schedule.

For every session, specify the facilitator action, learner action, required material, approximate duration, and evidence of completion. Include practice with realistic but clearly labelled sample information; do not fabricate company data. Add checks such as retrieval questions, guided demonstrations, supervised practice, or a short task. For each assessment item, provide the answer, explanation, and why an incorrect option may seem tempting.

Specify a difficulty distribution across checks as [FILL IN: difficulty distribution] unless the onboarding owner provides one. Include accessibility and participation alternatives where the format requires them. Do not claim compliance with any unconfirmed standard. If a standards framework is relevant, name it as [VERIFY: applicable framework]; do not invent codes or requirements.

## Output structure

Organize the deliverable in this order:

1. **Program overview** — State the purpose, learner profile, delivery format, daily time budget, prerequisites, and the week’s progression. Use slots for all unconfirmed values.
2. **Week-at-a-glance table** — Include day, theme, observable objective, main activity, tool or company input, evidence of completion, and approximate duration.
3. **Session-by-session plan** — Give each day a short narrative explaining its role in the learning progression, followed by itemized sessions. For every session include objective, facilitator actions, learner actions, timing, materials, and completion check.
4. **Assessment item format** — Provide questions or tasks with answers, explanations, and distractor rationales where applicable. State the difficulty distribution or leave its slot.
5. **Materials and access slots** — List presentation inputs, accounts, permissions, sample files, job aids, support contacts, and any clearance or privacy review needed.
6. **Post-lesson checks** — Define what the facilitator verifies at the end of each day and how unresolved access or learning issues are recorded and followed up.

Allocate the greatest detail to the daily plan, not to generic onboarding commentary.

## Style rules

Use a hybrid style. Write the overview, progression rationale, and transitions as concise narrative paragraphs. Present the schedule, session details, checks, materials, and follow-up actions as itemized lists or tables. Keep the register welcoming, direct, and operational. Avoid onboarding clichés such as “hit the ground running,” “drink from the firehose,” “seamless journey,” and “family,” unless the supplied company language explicitly requires them.

## Style rules (humanizer v1)

These govern every prose surface in the deliverable. Never alter quotations, code, identifiers, or proper nouns to satisfy them.

- Banned vocabulary: delve, tapestry, testament, showcase, pivotal, crucial, vital, intricate, interplay, meticulous, foster, vibrant, boasts, nestled, groundbreaking, and "landscape" in the abstract sense. Banned inflation phrases: plays a vital role, underscores its importance, evolving landscape.
- Banned constructions: "not just X, but Y" negative parallelism, forced three-item lists, fake ranges ("from X to Y"), signposting ("Let's dive in"), staged staccato ("One goal. Zero compromises."), and synonym cycling. Name a thing the same way every time.
- Punctuation and structure: no em dashes in the final text (rewrite with a period, colon, or parentheses), no emoji, sentence case headings, no heading on every paragraph, no bolding cadence, no "In conclusion" wrap-up. Close on a concrete fact.
- Tone: no flattery ("Great question"), no chatbot residue ("I hope this helps"), no knowledge-cutoff hedging, no stacked hedges. Hold the register the genre calls for and vary sentence length.
- Fact integrity: every instruction to be specific carries one boundary. Use only facts present in the user's input or in a verifiable source. Do not invent details to sound human. Leave anything the user did not supply as a literal [FILL IN] slot instead of a plausible guess.
- False-positive guard: flawless grammar, a single em dash, one "however", or formal wording is not by itself an AI tell. Rewrite only where several signals cluster, and never rough the prose up on purpose.

## Final self-audit

Draft the deliverable in full, then interrogate the draft on two counts. Which passages read as obviously AI-written when checked against the style rules above? Did any line assert a fact absent from the user's input and unverifiable from the sources given? Rewrite what fails and submit only the corrected version. The audit itself never appears in your output.

## Self-verification

1. Confirm that the deliverable is a first-week onboarding program, not a general employee handbook or long-term training curriculum.
2. Confirm that the sequence begins with company introduction and reaches the employees’ daily tools.
3. Check that every day has an observable objective using an action verb and a stated completion check.
4. Check that every session includes timing, facilitator action, learner action, materials, and evidence of completion.
5. Confirm that the company name, mission, roles, tool names, access details, dates, and schedules were not added beyond the input.
6. Confirm that no [FILL IN: ...] slot was filled arbitrarily, especially the company context, learner profile, and daily tools.
7. Check that role-specific branches appear only when role differences are supplied or explicitly marked as slots.
8. Confirm that assessment items include answers, explanations, and distractor rationales where questions are used.
9. Confirm that the output stays within first-week onboarding scope and does not drift into policy drafting, software implementation, or unsupported compliance claims.
10. Confirm that the hybrid format is visible: narrative for overview and transitions, itemized or tabular formatting for the operational plan.
11. Confirm that the final plan states what the facilitator verifies after each day and how unresolved issues are handled.
12. Confirm that any applicable standards framework or accessibility requirement is marked [VERIFY] unless its applicability and details were supplied.