Main change
State that manager approval is needed before submitting an equipment request.
AI use case · HR
A practical hr communication workflow with a synthetic example, reusable prompt, expected output, review checklist and common failure to avoid.
Workflow overview
Policy messages need to be adapted for different audiences.
Use approved policy text; draft a plain-language explanation; preserve meaning; have HR approve the final version.
Tools to explore: Claude, ChatGPT. Choose an organization-approved account and verify the features available to it before using the workflow.
Example input
Illustrative example · not client work
Fictional policy: from 1 December, equipment requests require a manager’s approval before submission to operations. Urgent cases must be discussed with operations. No service-level deadline has been specified.
Identify the person responsible for the task, the source material the tool may use and the format needed by the next person in the process. Keep missing facts visible instead of asking the model to fill them from guesswork.
Reusable starting point
Replace the bracketed fields with approved context. Use the example to practise the method before considering a connection to a live business system.
Draft a clear employee announcement based only on the approved policy. Preserve the effective date, approval requirement and urgent-case exception. Do not invent response times, eligibility or escalation contacts. Include a short FAQ and mark unanswered questions for HR review. Policy: [insert approved text without personal data]
Expected result
State that manager approval is needed before submitting an equipment request.
Preserve 1 December without adding an unsupported year.
Explain that urgent cases need discussion with operations; do not invent a response deadline.
Before the output is used
Learn from an error
The draft promises that operations will respond within one business day. The policy contains no such promise, so the wording must be corrected.
Keep a record of the error and the correction. Re-test the revised instruction with a different input so a change that fixes one example does not hide another problem.
Evaluate the whole task
Count changes to policy meaning, unsupported promises and editing required. Review readability without treating simpler wording as permission to remove important conditions.
Agree the quality criteria before comparing task time. If the reviewer cannot verify the answer or the workflow repeatedly exceeds its source boundary, narrow the scope or return to the established process.
No personal records are needed for the example. Use approved policy text and a general audience description instead of identifiable employee information.
No. This is an illustrative learning workflow. It shows a way to frame and review a task, without claiming client deployment, measured savings or guaranteed results.
Related learning
Connect this exercise to the department’s wider work.
Explore training for this roleReview a relevant training curriculum.
Explore explore the tool programBuild a repeatable quality check.
Explore evaluate ai outputYour next chapter with AI
Tell us what you want to train, improve, automate or build.