Policy lookup | Business Helper AI

Inputs and purpose

Use this workflow to prepare: Plain-language answer citing supplied policy sections.

Start with: Current handbook/policy text and the employee question.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

Procedure

Identify the actual employee question and the relevant policy version, scope and effective date.
Locate the supplied sections that answer it and check related definitions, exceptions and approval roles.
Explain the answer in plain language with section references. If the policy is silent or conflicts with another supplied rule, state that explicitly.
Return the answer and the specific question for the responsible policy owner. Do not invent a company rule or treat an old policy as current.

Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Clarify hiring, onboarding and employee processes.

Possible success measures: Time to hire, time to independence, HR admin hours. Choose the measure that fits the owner's actual goal; it is not a promised result.

Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the input guide, calculation reference or output template. For tool setup, use the shared instructions.

Plain-text instructions

---
name: policy-lookup
description: "Prepare plain-language answer citing supplied policy sections. Use for this workflow with supplied business information."
---

# Policy lookup

## Inputs and purpose

Use this workflow to prepare: Plain-language answer citing supplied policy sections.

Start with: Current handbook/policy text and the employee question.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

## Procedure

1. Identify the actual employee question and the relevant policy version, scope and effective date.

2. Locate the supplied sections that answer it and check related definitions, exceptions and approval roles.

3. Explain the answer in plain language with section references. If the policy is silent or conflicts with another supplied rule, state that explicitly.

4. Return the answer and the specific question for the responsible policy owner. Do not invent a company rule or treat an old policy as current.

## Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Clarify hiring, onboarding and employee processes.

Possible success measures: Time to hire, time to independence, HR admin hours. Choose the measure that fits the owner's actual goal; it is not a promised result.

## Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the [input guide](../../../references/INPUT_DATA_GUIDE.md), [calculation reference](../../../references/CALCULATIONS.md) or [output template](../../../references/WORKFLOW_OUTPUT_TEMPLATE.md). For tool setup, use the [shared instructions](../../../AGENTS.md).