Use Claude to Turn an Approved Process Document into an Onboarding Checklist

A process document explains how work should happen. An onboarding checklist explains what a new teammate must do, what “done” means, and which details still need an owner.

This end-to-end workflow uses a Claude Project to turn one approved process guide into a checklist, a first-week plan, and an open-questions list. It does not assign real people or change the source policy.

Evidence label: documentation-based tutorial with a fictional process guide and illustrative outputs. Anthropic documents Projects and project knowledge; this is not a recorded Claude run, a Cihan personal test, or a measured onboarding result.

What you need

A Claude account with Projects available. Anthropic says Projects can hold uploaded documents and project instructions, and that project knowledge is used across chats in that project.
The fictional process guide below, or a short process document approved for your AI environment.
A human process owner who can approve names, permissions, deadlines, and exceptions.

Read What are projects? — Anthropic Help Center and How can I create and manage projects? before following UI labels. Claude surfaces can change.

1. Prepare the complete fictional source

Create new-hire-access.md:

# New hire access process

1. The manager confirms the person's start date and team.
2. The IT queue receives the request through the internal form.
3. IT grants email and document access after the manager confirms the team.
4. The manager requests finance-system access separately if the role needs it.
5. The new hire completes security orientation before handling customer data.
6. The process owner reviews exceptions every Friday.

Unspecified: who approves exceptions, the response target for IT,
and the exact security-orientation location.

These are fictional instructions. The missing details are deliberate: a checklist must preserve them rather than quietly inventing owners or deadlines.

2. Create the Project and add the source

In Claude, open Projects and create a project named New hire access practice. Add new-hire-access.md to the project knowledge area. If your interface uses different labels, follow the current Anthropic help page rather than assuming this exact layout.

Add project instructions such as:

Use the project knowledge as the only policy source. Preserve every
source step. Mark missing owners, dates, permissions, targets, and
locations as OPEN QUESTION. Never assign a person, deadline, approval,
or access right that the source does not specify.

3. Request the onboarding pack

Start a chat in the Project and paste:

Create an onboarding pack from the approved process guide.

Return:
1. A numbered checklist that preserves the six source steps.
2. A first-week plan grouped by before start, day one, and first week.
3. An acceptance check for each step: what evidence shows it is done?
4. An OPEN QUESTIONS table with the missing owner, IT response target,
and security-orientation location.
5. A source map showing the source step behind each checklist item.

Do not invent people, dates, access levels, approval rights, deadlines,
or system names. If the source is silent, write OPEN QUESTION. Keep
“finance-system access” conditional on role need. Do not edit the source
policy or claim that any access was granted.

4. Check the outputs against the source

The checklist should contain six steps. It should keep finance-system access conditional, preserve the Friday exception review, and show the three unspecified details as open questions.

An illustrative acceptance row could look like this:

Checklist item	Evidence of completion	Source	Status
IT receives the request through the internal form	Request ID or queue record	Step 2	Needs human confirmation
Security orientation is complete before customer data work	Approved completion record	Step 5	Needs location and record owner

The pack must not name “Sarah” as the approver, turn Friday into a calendar deadline, or state that every new hire receives finance-system access.

5. Turn gaps into a review handoff

Ask Claude to export the open questions as a short message for the process owner. Review it before sending. A useful handoff asks who approves exceptions, what IT response target applies, and where orientation completion is recorded. It does not ask Claude to resolve those questions.

Keep the original guide with the checklist. When the process changes, update the source and rerun the review; do not patch the checklist silently.

Troubleshooting

The chat ignores the uploaded guide: confirm the file is in project knowledge, then ask it to quote the relevant source step for one item.
Owners or dates appear from nowhere: add the “OPEN QUESTION” rule again and compare the output with the source line by line.
The interface has no Projects label: check the current Anthropic help page and use a normal chat only as a clearly labeled fallback.
The checklist compresses two steps: require one output item per numbered source step before accepting the pack.

TRY / SKIP / USE: TRY this with the fictional process; SKIP real employee or access data unless your organization approves it; USE the checklist only after the process owner checks every item and open question.

Sources and next step

The output is a reviewable draft of the onboarding pack. The process owner still owns the policy.