Turn an onboarding pack into a checked FAQ

Spend about five minutes reading these six clauses. Use a local text document or paper for your work. You need no HR qualification, account or paid tool to complete this exercise.

Use only this invented material. Do not paste employee records, candidate CVs, health details, salary data or internal policies into an unapproved tool. This exercise does not make employment decisions or provide policy or legal advice.

1. S1. Fictional Northstar Studio welcome guide, version 3. New starters complete the security introduction within five working days after their account is activated. If access fails, contact the onboarding coordinator. The guide does not define local holidays.
2. S2. Equipment note, version 2. Request a standard laptop at least three working days before the start date. Delivery depends on stock and shipping; a request does not guarantee delivery on day one.
3. S3. Office welcome guide, version 3. On the first day, arrive at reception at 09:00 local office time.
4. S4. Welcome email template, version 3. On the first day, arrive at reception at 09:30 local office time. No document in this pack says which arrival instruction takes priority.
5. S5. Buddy note, version 1. A buddy conversation is optional. Ask the onboarding coordinator to arrange one if useful. The pack does not give the coordinator's contact details or promise a response time.
6. S6. Pack scope. This fictional pack contains no home-office allowance amount, eligibility rules or approval process. It is training material, not an employer policy or legal advice.

Before drafting, mark the timing conditions, the delivery caveat and the two arrival instructions. A version number alone does not tell you which document takes priority.

Spend about five minutes drafting. Copy the complete prompt below into an approved AI chat if you have one. It includes every source and question; no upload, connection or paid feature is needed. Save the actual output and tool name if you use AI.

No AI account? Answer the questions yourself, then review the deliberately flawed draft in the next step. All reading and checks work without an account. Label this route manual practice. The supplied draft is an editorial example, not a recorded model response.

1. When must I finish the security introduction, and what if access fails?
2. When should I request a laptop, and is day-one delivery guaranteed?
3. What time should I arrive at reception on my first day?
4. Must I have a buddy conversation, and how do I arrange one?
5. How much home-office allowance will I get?

Spend about ten minutes reviewing your draft and this deliberately flawed example. For each claim, record the source ID, the error or missing caveat, and your correction. Check the source text yourself even when an AI citation looks convincing.

UNVERIFIED AI-STYLE DRAFT FOR REVIEW
1. Finish security training within five calendar days of your start date. If access fails, wait until your buddy meeting.
2. Order your laptop three days before you start and it will arrive on day one.
3. Arrive at reception at 09:30; the email overrides the guide.
4. A buddy meeting is mandatory. Email [email protected] and expect a reply within 24 hours.
5. Every starter receives a $300 home-office allowance.

Check conditions as well as numbers. Five working days after account activation is different from five calendar days after a start date. A request deadline is not a delivery promise. Two plausible times do not justify choosing one.

Spend about five minutes scoring your final FAQ. Give each answer one point for the correct source references and one point for all required facts and caveats below. Ten points are possible. A guessed arrival time, invented benefit or missing delivery caveat requires revision regardless of the total.

• Question 1 uses S1. Keep working days, account activation and the access-failure contact. Flag the missing calendar information before calculating a due date.
• Question 2 uses S2. Keep at least three working days, a standard laptop, stock and shipping limits, and no day-one guarantee.
• Question 3 uses both S3 and S4. Retain both local-office times, state the unresolved conflict and request confirmation without choosing a winner.
• Question 4 uses S5. Keep the conversation optional and coordinator-arranged. Do not invent contact details or a response time.
• Question 5 uses S6. Say the amount, eligibility and approval process are absent. Request an approved policy without inferring an entitlement or a zero allowance.

Revise until every answer meets both checks. Ten points means this small fictional exercise meets its rubric, not that a real FAQ is approved. In a workplace, follow your employer's AI rules and have the responsible human confirm sources, conflicts and current policy before sharing.

OpenAI's safe-use guidance supports human review, workplace rules and checking cited sources. Its file guidance describes summary and extraction tasks. Neither source validates the invented company clauses or an AI-generated answer.

Use the last five minutes to save one practice document titled "Synthetic onboarding FAQ review". Include the source pack, five final answers with IDs, original draft, correction log and rubric result. Add whether you used AI or worked manually and what you checked yourself.

Your unresolved list should include which arrival time is correct, the working-day calendar and activation date before a due-date calculation, coordinator contact details, and the missing allowance policy. Do not send this fictional FAQ to real employees.

Example correction-log entry to adapt after checking it yourself: "Question 3. The draft chose 09:30 without support. S3 says 09:00 and S4 says 09:30, both in local office time. I retained both and requested confirmation. Arrival time remains unresolved."