Prepare an HR scenario review from approved policies
Compare an employment scenario with internal procedures and prepare questions from several organizational perspectives.
How this works
Compare an employment scenario with internal procedures and prepare questions from several organizational perspectives. Use this when an HR team needs to prepare questions about an employment scenario before deciding how to proceed. Multiple review perspectives should expose omissions and communication concerns without pretending that simulated consensus establishes compliance.
Retrieve the applicable internal procedure, create a factual scenario summary and examine it from management, HR-process and communication perspectives. Keep policy quotations, interpretation questions and suggested wording separate. An authorized HR professional reviews consequential interpretations and decides the next action.
Before you start
Approved procedure
Obtain the current internal policy, applicable entity and effective date.
Factual scenario
Collect only the necessary events and relevant records.
Responsible reviewer
Identify the HR owner who can resolve interpretation and confidentiality questions.
Prepare the inputs
- scenario_facts
- Required
dated events, roles and relevant evidence
Separate observed facts from allegations or assumptions.
- procedure
- Required
versioned policy passages
Check applicability and do not substitute a generic policy.
- decision_question
- Required
specific issue requiring review
Avoid expanding into unrelated personnel judgments.
- audience_scope
- Required
permitted reviewers and communication purpose
Exclude personal information unnecessary for the review.
Implementation, step by step
Create a neutral brief
- Summarize the scenario in chronological order with evidence references.
- Mark disputed facts and remove unnecessary identifying details.
Checkpoint: The review starts from a shared factual account.
Retrieve relevant procedure
- Locate the steps, responsibilities and exceptions that may apply.
- Preserve the exact section references and flag ambiguous applicability.
Checkpoint: The policy map is traceable.
Examine separate perspectives
- List operational questions, HR-process questions and communication concerns independently.
- Label these as simulated analytical perspectives rather than actual stakeholder opinions.
Checkpoint: The roundtable reveals distinct gaps.
Consolidate questions
- Combine duplicates and identify the facts or qualified interpretations needed.
- Do not convert a majority of generated opinions into a decision.
Checkpoint: The HR owner receives a focused question queue.
Prepare the handoff
- Draft a factual summary and optional communication wording within confirmed policy.
- Keep decisions and external messages pending the responsible owner's action.
Checkpoint: The packet is ready for professional review.
Decisions along the way
Policy is silent on the situation
State the gap and ask the HR owner rather than inventing a rule.
Facts are disputed
Present both accounts with attribution and avoid a premature conclusion.
Communication would reveal unnecessary details
Use a role-level summary and restrict the full evidence packet.
What you will produce
hr-scenario-review.md
MarkdownA preparation packet for an authorized HR reviewer.
Include: facts · policy_refs · perspectives · questions · limits
hr-question-queue.csv
CSVA focused list of unresolved matters.
Include: question · evidence_gap · policy_section · owner · status
Check the result
- Verify policy version and applicability.
- Check factual statements against their sources.
- Confirm simulated perspectives are not attributed to real people.
- Ensure no employment decision is implied by generated agreement.
When something goes wrong
Policy versions conflict
Hold the interpretation and ask the policy owner to identify the governing version.
Scenario lacks key dates
Keep procedural timing unresolved until dates are confirmed.
Assistant produces legal certainty
Replace it with the specific policy evidence and qualified-review question.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Synthetic: review a request to change a work schedule.
Inputs
Policy requires manager review and HR confirmation for permanent changes. The employee requested a temporary two-week change; the policy does not define temporary exceptions.
Expected result
Synthetic result: identify the temporary-versus-permanent applicability question, prepare operational coverage questions and draft neutral acknowledgment wording. Do not declare the request approved or prohibited.
Run a small pilot
Start small
Review a few anonymized scenarios with an HR professional.
Record the baseline
Record preparation time and missing questions found.
Agree success criteria
Agree factual accuracy and question usefulness before recurring use.
Stop or revise
Stop decision recommendations when policy applicability or material facts remain unresolved.
Keep the scope clear
- Simulated perspectives do not establish legal compliance or stakeholder approval.
- The workflow prepares evidence and questions; authorized people own employment decisions.
Check before using
Have an authorized HR professional check interpretation and confidentiality; simulated viewpoints do not establish compliance.
Business activities
- Support and develop employees
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Approved HR policies · A de-identified workplace scenario
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow