An onboarding artifact is a cited document written for one new hire before their day one. It covers the company, the team, the role, who owns what, why things are the way they are, and what's happening now. Every claim links to the thread, page or record it came from, and the hiring manager approves it.

What is an onboarding artifact?

It's the document a good manager would write for a new hire if they had a free week.

Four things define it:

  1. It's written for one person. One new hire, one role, one team. Not a page for everyone who joins.
  2. It's written from what already exists. The content comes from the tools the team works in: Slack, Confluence, Jira, Google Drive, the CRM.
  3. Every claim is cited. Each statement links to the thread, page or record behind it.
  4. A person approves it. The hiring manager reads it, corrects it and approves it before the new hire sees anything.

It arrives finished. The new hire doesn't have to search for it, assemble it or ask for it.

Firstweek writes onboarding artifacts. The term describes the document, though, and a manager with enough time could write one by hand. Almost none have the time, which is the whole problem.

What goes in one?

Six sections, moving from the widest view to the most immediate.

The last three are what separate an artifact from a welcome packet. Most onboarding material covers the company and stops at the team. The questions a new hire actually asks are about ownership, history and what's on fire.

How is it different from a checklist, a wiki and a chatbot?

Each of those does a job. None of them does this one.

A checklist is a list of tasks. Keep it. The longer comparison is Firstweek vs. an onboarding checklist.

A wiki holds the raw material, and an artifact is often written partly from it. Having access to a hundred pages isn't the same as knowing which six matter. See Firstweek vs. your company wiki.

A chatbot needs a question. In week one a new hire doesn't know what exists, so they don't know what to ask. An artifact is finished before the question. See Firstweek vs. an AI chatbot.

Why is every claim cited?

Because a new hire has no way to judge an unsourced statement about a company they joined four days ago.

A citation lets them check. "The enterprise tier is annual-only" becomes a sentence with a link to the thread where that was decided. They can see who was in it, when it happened and what the alternatives were.

Citations do the same for the manager. Approving a document is quick when each claim can be opened and confirmed. They also show a claim's age, which matters, since a decision from two years ago may have been reversed since.

For teams in regulated industries, the citations are also a record. Each statement in the artifact can be traced to its source.

Who approves it?

The hiring manager. Every artifact, before the new hire sees it.

This isn't an optional review. Nothing is delivered until the manager approves it. They can correct any statement first, and their corrections are kept with the artifact.

The step exists because written records are incomplete. A thread can describe a plan that was dropped in a meeting the next day. The manager knows. Their ten minutes of reading are what turn a well-sourced draft into something the team stands behind.

Can I see one?

Yes. The sample artifact is a complete one, with its citations, written for a fictional company's new hire. The product tour shows how one is put together, from connecting sources to the manager's approval.

When Firstweek writes one, it reads your tools through read-only connections and summarizes at ingest. Raw messages and documents are never stored. The security page has the detail.

FAQ

What is an onboarding artifact in one sentence?

A cited document written for one new hire, covering the company, the team, the role, who owns what, why things are the way they are and what's happening now, approved by their hiring manager before day one.

Is an onboarding artifact the same as an onboarding checklist?

No. A checklist lists tasks and due dates. An artifact explains the context around them. Most teams keep both.

Who writes an onboarding artifact?

A manager can write one by hand. Firstweek writes them from the tools a team already uses, and the hiring manager approves each one.

Does every new hire get the same artifact?

No. Each artifact is written for one person's role and team, from what those sources say at the time.

Run it on your next hire. 30 days. Then we talk. Start a pilot or see a sample artifact. How it works for scaling teams.