From scattered docs to a first useful task

A first task, not a document dump.

An onboarding guide connects a new hire’s first useful task to the prerequisites, trusted resources and people who can help.

Make this with my agent

Bring your notes. Review a draft before sharing.

Explore the method

01
Start small.
One observation and a manager conversation—not the whole company wiki.
02
Show the reasoning.
20 of 100 and 18 of 90 are both 20%. A lower count is not a better rate.
03
Make recovery explicit.
Missing access means pause and ask. It does not grant new permissions.

THE REAL HTML · FICTIONAL EXAMPLEView on its own

A worked example, not a customer result. September 2026 dates are sample facts.

Now make it about your work

Their first task. Your agent. A clearer start.

Bring approved role goals, current instructions and a confirmed help path. Make the first contribution easy to find.

Start with three things

The role and manager-approved first outcome.
Current policies, source links and access instructions.
Confirmed help contacts and a review date.

Make this with my agent

You review the facts and access. Nothing is published without your approval.

The method behind the guideFrom a document dump to a first-task path

What should a useful new-hire onboarding guide include?

Organize it around the first things the person needs to do: understand their role, get approved access, complete a small task, and know where to ask for help. An agent can assemble the supplied instructions into a role-specific HTML guide. Keep policies in their authoritative location, and verify every owner, link, and permission before sharing.

What to give your agent

The role description and manager-approved first-week goals, with realistic expectations for what happens later.
Current access-request instructions and the approved support channel; never include credentials or recovery codes.
Authoritative team policies, process documents, and examples that the new hire is permitted to read.
Confirmed task owners, support contacts, and the date each important instruction was last checked.

Choose a first useful outcome
Ask the manager what a reasonable first contribution looks like. It might be reviewing a sample report or completing a supervised practice task. Build the guide around that outcome rather than reproducing the company directory. Explain what success looks like and what the person is not expected to know yet.
Put instructions where they are needed
Attach each required tool, document, and contact to the task it supports. Explain why a link matters before asking someone to open it. Keep optional background in a separate section. If access must be approved, point to the official request process instead of treating a blocked link as an instruction to seek broader permissions.
Include a recovery path
For every important task, explain what to do if the expected path fails: who can help, which channel to use, and whether to pause. Use confirmed role or team contacts where possible so the guide is easier to maintain. Do not invent a turnaround time or promise that a particular person will be available.
Walk the guide as a newcomer
Have an authorized reviewer check the instructions with the intended access level. Verify link permissions, unexplained acronyms, mobile readability, and the order of prerequisites. Apply the team’s saved style if available, but prioritize calm navigation. Add an owner and review date, then share using access appropriate to the material.

Keep creating and revising in the agent you already use. Start with a saved artifact style and learn how to update HTML without changing its link.

Use the full promptReady for your agent and your notes

Use the conversation where you already did the work. Only attach material you are allowed to share.

Get the ready-to-copy creation request →

Create a role-specific first-week onboarding field guide as static HTML using only the approved sources I provide. Start with the first useful outcome, then organize tasks in prerequisite order. For each task include why it matters, the relevant source link, what done looks like, and a confirmed help path. Separate essential steps from optional background. Keep policy summaries brief and link to their authoritative versions. Do not invent owners, access permissions, deadlines, or tool instructions. Exclude credentials, private employee information, and restricted material. Apply my saved artifact style if available. Use readable headings and no scripts or forms. Flag outdated or missing instructions for review. Do not publish or change access until I approve the draft. If this is a training field guide, use supplied learner objectives, a worked example, a practice task and confirmed human feedback criteria. Distinguish participation from competence; do not grade, certify or invent training requirements. Use authorized synthetic practice data where appropriate. If adapting this for volunteers, preserve organizer-approved arrival details, role boundaries, break arrangements and confirmed help contacts. Exclude personal rosters and medical information. Do not invent safeguarding, emergency or safety procedures; request the organizer's approved instructions.

Check before you shareAccuracy, clarity, and permission

Can the new hire identify their first task and the prerequisites without opening every link?
Do links work for the intended recipient, not only for the author’s account?
Are help contacts confirmed and sensitive employee or access details excluded?
Does the guide name an owner and review date without claiming automatic updates?

When HTML fits

A role-specific reading layer that connects first tasks to the right internal resources and can be revised after feedback.

When another format fits better

A replacement for official policy, identity management, mandatory training records, or a secure employee system. A visual checklist does not track completion automatically.

What we started withThe same facts, as an email

Fictional project email

Your first analyst task — a synthetic practice report

Welcome to the team,

Your first useful outcome is to explain one change in the sample weekly report and discuss your interpretation with your manager. This fictional first-week sequence is illustrative, not a universal onboarding schedule.

First follow the approved access-request instructions, then read the report glossary and open the sample. Use synthetic data if production access is not approved. No production changes are expected. The actual access-process, glossary and sample URLs are not supplied here; ask your manager for the approved sources before a real task. Policies remain authoritative.

For the synthetic exercise, 20 of 100 sample cases needed follow-up in week one and 18 of 90 in week two. Both rates are 20%. The count fell by two, but the denominator fell too. No reason for the count change is supplied; the figures do not establish improvement or causation.

Prepare a short draft with an observation, supporting counts and denominators, and one question about missing context. Your manager reviews arithmetic, interpretation and source limits before external sharing. This is practice, not a grade or competence certification.

If terminology or missing access blocks you, ask the designated onboarding contact. The actual name and channel are not supplied; pause and ask your manager to identify the official contact and process. Never request another person's credentials or treat a blocked link as permission for broader access. No response time or availability is promised.

Before real use, confirm the guide owner, help contact, official links and last instruction-check date. They are not supplied. This fictional example was prepared September 21, 2026, not a source verification date. It contains no personal employee information or credentials. The static page does not track completion or update itself; acknowledgments and required training records belong in the approved system.

Inspect the HTMLOne self-contained file

The example is sanitized and isolated from this site. No scripts, forms, or live data.

<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1"><title>Your first useful analyst task</title><style>
*{box-sizing:border-box}html{color-scheme:light}body{margin:0;background:#f7f5ec;color:#23372d;font:16px/1.55 system-ui,sans-serif}main{max-width:1050px;margin:auto;padding:36px}p,h1,h2,h3{margin:0}p+p{margin-top:10px}h1{font:500 52px/1.06 Georgia,serif;letter-spacing:-.03em;max-width:650px;margin:16px 0}h2{font:500 29px/1.2 Georgia,serif;margin-bottom:14px}h3{font-size:18px;line-height:1.3;margin-bottom:8px}.eyebrow{font-size:11px;font-weight:750;letter-spacing:.12em;text-transform:uppercase}.muted{color:#526154}.intro{max-width:620px;font-size:19px}.badge{display:inline-block;border:1px solid #68795b;border-radius:20px;padding:5px 10px;font-size:12px;margin-top:18px}.outcome{background:#274b38;color:#fff;padding:24px;margin:26px 0}.outcome p{font-size:21px;line-height:1.4;margin-top:8px}.path{display:grid;grid-template-columns:repeat(3,minmax(0,1fr));gap:14px;margin-top:16px}.step{border-top:2px solid #879774;padding:16px 0}.number{display:block;font:500 32px Georgia,serif;color:#607044;margin-bottom:12px}.step p{font-size:15px}section{margin-top:30px}.practice{background:#fff;border:1px solid #d1d6c6;padding:24px}.rates{display:grid;grid-template-columns:1fr 1fr;gap:12px;margin:20px 0}.rate{border-left:3px solid #8b9c63;padding-left:16px}.rate strong{display:block;font:500 44px/1.2 Georgia,serif;margin:4px 0}.rate p{font-size:14px}.observation{border-top:1px solid #d1d6c6;padding-top:16px}.draft{background:#eceddf;padding:22px}.draft p{margin-top:10px}.help{border-left:4px solid #ad7827;padding:0 0 0 20px}.help p{font-size:15px}footer{border-top:1px solid #bcc4b2;margin-top:30px;padding-top:20px;font-size:12px;color:#526154}footer p+p{margin-top:8px}@media(max-width:600px){main{padding:22px}h1{font-size:39px}.path{grid-template-columns:1fr;gap:0}.step{display:grid;grid-template-columns:35px 1fr;column-gap:12px;padding:16px 0}.number{grid-row:1/3;font-size:26px}.step p{grid-column:2}.practice,.draft,.outcome{padding:18px}.rate{padding-left:10px}.rate strong{font-size:36px}.intro{font-size:17px}h2{font-size:26px}}@media print{body{background:#fff}main{padding:20px}.practice,.draft,.help,.step{break-inside:avoid}.outcome{background:#fff;color:#23372d;border:2px solid #274b38}}
</style></head><body><main>
<header><p class="eyebrow">The analyst field guide · Fictional first week</p><h1>Start with one useful observation.</h1><p class="intro">You do not need to learn the whole company today. Begin with a small practice task—and a conversation.</p><p class="badge">Synthetic data only · No production changes</p></header>
<div class="outcome"><span class="eyebrow">Your first outcome</span><p>Explain one change in the sample weekly report. Discuss your interpretation with your manager.</p></div>
<section><p class="eyebrow">01 / Get oriented</p><h2>Three steps. In this order.</h2><div class="path"><div class="step"><span class="number">1</span><h3>Check your access</h3><p>Follow the approved access-request instructions. Use the synthetic sample if production access is not approved.</p></div><div class="step"><span class="number">2</span><h3>Read the glossary</h3><p>Understand the report’s terms before interpreting a movement. Ask about anything unfamiliar.</p></div><div class="step"><span class="number">3</span><h3>Open the sample</h3><p>Look for one movement that needs context. You are not expected to change production data.</p></div></div><p class="muted">Official links are not supplied in this example. Ask your manager for the approved access process, glossary and sample before a real task.</p></section>
<section class="practice"><p class="eyebrow">02 / Try the reasoning</p><h2>Fewer cases. The same rate.</h2><p>These invented sample cases needed follow-up:</p><div class="rates"><div class="rate"><span class="eyebrow">Week one</span><strong>20%</strong><p>20 of 100 sample cases</p></div><div class="rate"><span class="eyebrow">Week two</span><strong>20%</strong><p>18 of 90 sample cases</p></div></div><p class="observation"><strong>Worked observation:</strong> the count fell by two, but the follow-up rate stayed at 20%. The denominator fell too.</p><p class="muted">The reason for the count change is not supplied. These figures do not establish improvement or explain a cause.</p></section>
<section class="draft"><p class="eyebrow">03 / Prepare your first draft</p><h2>Bring three things to your manager.</h2><p><strong>Observation</strong> · Explain the movement in your own words.</p><p><strong>Evidence</strong> · Include both counts and denominators.</p><p><strong>One question</strong> · What context would help explain the change?</p><p class="muted">Your manager checks arithmetic, interpretation and source limits before external sharing. This is practice—not a grade or certification.</p></section>
<section class="help"><p class="eyebrow">If the path breaks</p><h2>Pause. Ask. Keep the boundary.</h2><p>Ask the team’s designated onboarding contact about terminology or missing access. The actual contact and channel are not supplied; ask your manager to identify them.</p><p>Never request another person’s credentials. A blocked link is not permission to seek broader access. No response time or availability is promised.</p></section>
<footer><p><strong>Before real use:</strong> confirm the guide owner, help contact, official links and last instruction-check date. These are not supplied. Policies remain authoritative.</p><p>Fictional worked example by share/artifacts. Prepared September 21, 2026—not a source verification date. Illustrative sequence, not a universal schedule. No employee information or credentials.</p><p>This static page does not track completion or update itself. Keep acknowledgments and required training records in the approved system.</p></footer>
</main></body></html>

The original first-week task, reframedThe same starting point, with a practical path

A first-week field guide for an analyst

A fictional analytics team and a practice task using synthetic data. The sequence is illustrative, not a universal onboarding schedule.

The original notes

Welcome! Here are twenty-seven documents, the company wiki, and links to all our tools.

First outcome

Explain one change in the sample weekly report and discuss your interpretation with your manager.

Before you begin

Follow the approved access-request instructions. Use the synthetic sample if production access is not yet approved.

Do this first

Read the report glossary, open the sample, and identify one movement that needs context. You are not expected to change production data.

If you get stuck

Ask the team’s designated onboarding contact about terminology or missing access. Do not request another person’s credentials.

Done looks like

A short draft with the observation, supporting figures, and one question. Your manager reviews it before it is shared outside the team.

The guide becomes a path through the information, while the underlying policies remain the source of truth.

Questions, adaptations & sourcesGo deeper when you need to

Should every new hire get the same page?

Share a common core when it is genuinely common, then tailor the first tasks and resources to the role. Avoid adding personal information just to make the page feel personalized. The useful difference is what the person needs to do, not decorative customization.

How do we stop the guide going stale?

Assign an owner, show when instructions were checked, and review it before each onboarding cycle. Link to maintained policies instead of copying them in full. Ask new hires where they got stuck, then use that feedback to revise the next reviewed version.

Can the page record completed tasks?

This static guide describes tasks; it is not a completion-tracking application. Keep required acknowledgments and training records in the approved system. You can include a link to that system when appropriate, but do not imply the page submits or saves progress.

A training field guide

Add a learner objective, one worked example, a practice attempt and human feedback. Keep the lesson tied to a real first task. Reading or completing a visual checklist is not evidence of competence or a certification.

Fictional inputs: Fictional analyst exercise uses synthetic data: 20 of 100 sample cases needed follow-up in week one; 18 of 90 in week two. The manager asks the learner to calculate both rates and identify a limitation. No reason for the count change is supplied. Manager feedback is required before external sharing.

A clearer result: The worked observation is 20% in both weeks despite the smaller second count. The learner prepares a short draft explaining the denominator and asks about the unknown cause. The manager checks arithmetic, interpretation and source limits; no automatic grade or competence claim is made.

A volunteer first-shift briefing

Use the same first-task structure with organizer-approved role boundaries. Explain when to pause and whom to ask. Do not copy personal rosters or invent safeguarding, medical or emergency instructions.

Fictional inputs: Fictional book-sorting shift: arrive at the library desk at 09:00, sort donated books by the supplied labels, take a break at 10:30, and ask supervisor Rowan about damaged or unlabeled items. Volunteers are not assigned lifting or repair work. No other safety procedure is supplied.

A clearer result: Lead with arrival and the sorting task. Put the labels beside the task, keep the 10:30 break visible, and tell volunteers to leave damaged or unlabeled items for Rowan's direction. Exclude lifting and repair from the role. Request organizer-approved policies before adding further safety instructions.