PlaysbyMoat8
Back to the library
The workflow guideSupport

Answer employee questions from internal policies

Retrieve the relevant sections of company documents and draft a grounded answer in the team’s messaging app.

6 implementation stepsIntermediate

How this works

Retrieve the relevant sections of company documents and draft a grounded answer in the team’s messaging app.

Answer only from policies that apply to the employee’s role and location. Retrieval should expose the exact supporting passage and effective date, while unanswered or contradictory questions move to the policy owner.

Before you start

Defined operating scope

Employees repeatedly ask questions answered in current approved policies.

Required source material

Obtain Internal procedures. If connectors are unavailable, use authorized files with the same fields.

Decision and exception rules

Only an expired policy answers the question. Report that current guidance is unavailable and request the replacement.

Prepare the inputs

employee_scope
Required

Role, location and access group

Use authenticated attributes, not claims inside the question.

question
Required

Text

Identify the requested policy topic.

policy_corpus
Required

Documents with versions and permissions

Exclude superseded or inaccessible material.

owner_map
Required

Topic-to-owner routing

Provide a responsible fallback for unanswered questions.

Implementation, step by step

  1. Establish the working record

    • Confirm the selected records, effective versions and responsible owner.
    • Check employee_scope, question, policy_corpus, owner_map before beginning. Record the source version and the selected scope; an unavailable value stays unknown rather than becoming an inferred fact.

    Checkpoint: The input record identifies the selected employee_scope and any missing required fields.

  2. Index the current approved policies with document permissions

    • Index approved policy versions with access metadata; maintain replacements and effective dates instead of appending every version equally.
    • Check every material answer sentence against an accessible, current passage.

    Checkpoint: A saved intermediate result for: Index the current approved policies with document permissions.

  3. Retrieve the relevant passages for an employee’s question

    • Retrieve passages matching the topic and employee scope, checking jurisdiction or location applicability where the policy distinguishes them.
    • Test a question from another access group to verify that restricted content is not revealed.

    Checkpoint: A saved intermediate result for: Retrieve the relevant passages for an employee’s question.

  4. Draft an answer supported by those passages

    • Draft a direct answer with citations and clearly stated limits; do not combine incompatible regional rules into one invented policy.
    • Check every material answer sentence against an accessible, current passage.

    Checkpoint: A saved intermediate result for: Draft an answer supported by those passages.

  5. Hand off missing or ambiguous answers to the policy owner

    • Send the owner a focused question containing the applicable passages and ambiguity, while giving the employee an honest unresolved status.
    • Test a question from another access group to verify that restricted content is not revealed.

    Checkpoint: A saved intermediate result for: Hand off missing or ambiguous answers to the policy owner.

  6. Package the result and unresolved work

    • Check permissions and answer accuracy.
    • Policy documents provide evidence, not permission to access other employee records.

    Checkpoint: Policy answers. Unresolved items remain visible in the review record.

Decisions along the way

Only an expired policy answers the question.

Report that current guidance is unavailable and request the replacement.

Two current documents conflict.

Quote the conflict and refer it to the policy owner rather than choosing by wording confidence.

The employee lacks access to the retrieved document.

Exclude its content and route through the authorized support channel.

What you will produce

internal-policy-assistant-result.json

JSON

Policy answers. Label proposed and completed states separately.

Include: question · applicable_policy · answer_draft · citations · uncertainty · handoff_owner · status · evidence_reference · review_note

internal-policy-assistant-review.md

Markdown

Keep the evidence and unresolved decisions needed to apply this result, including exceptions involving owner_map.

Include: source_reference · question · owner · next_action

Check the result

  • Check every material answer sentence against an accessible, current passage.
  • Test a question from another access group to verify that restricted content is not revealed.
  • Inspect employee_scope and question in both the original and output; confirm that record identity and interpretation survived the transformation.
  • Check permissions and answer accuracy.

When something goes wrong

Only an expired policy answers the question.

Report that current guidance is unavailable and request the replacement. Retain the affected evidence and recovery status.

Two current documents conflict.

Quote the conflict and refer it to the policy owner rather than choosing by wording confidence. Retain the affected evidence and recovery status.

The employee lacks access to the retrieved document.

Exclude its content and route through the authorized support channel. Retain the affected evidence and recovery status.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Answer employee questions from internal policies for the following bounded example; prepare the result for review.

Inputs

Synthetic example: Employee scope is Location B. Policy P-4 says Location A may expense travel meals; P-7 covers Location B but contains no meal guidance.

Expected result

Synthetic expected result: Answer states that the available Location B policy does not establish meal eligibility. It does not apply the Location A rule; route the question to the expense-policy owner.

Run a small pilot

Start small

Trial a representative batch containing the ordinary case and the exception demonstrated above.

Record the baseline

Record current preparation time, review effort and correction types for the same records.

Agree success criteria

Agree acceptable review and error limits; measure correct grounded answers in a reviewed sample; appropriate escalation rate.

Stop or revise

The employee lacks access to the retrieved document. Pause affected records and apply this recovery: Exclude its content and route through the authorized support channel.

Keep the scope clear

  • Policy documents provide evidence, not permission to access other employee records.
  • The assistant explains approved wording; exceptions and policy changes belong to responsible people.

Check before using

Check permissions and answer accuracy.

Business activities

  • Support and develop employees
  • Maintain shared company knowledge

Editorially adapted workflow; not independently tested.

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: Internal procedures

Start with one recurring task, agree which sources to use, and review the first result with your team.

Discuss this workflow

What does your team do?

Choose the recurring work you would like to improve.

A field guide, made for work.

Plays is a curated library of anonymized business workflows. Each recipe explains the inputs, steps, tools, and checks you can adapt to your team. These are editorial guides, not independently tested implementations.

When you share a company website, the guide may read a limited number of public pages on that website. Messages and retrieved page text are sent to our AI provider, NVIDIA, to recommend relevant workflows. Share a general description rather than confidential information.

Saved workflows and selected activities stay in this browser. Your chat history and selected company website are kept in this tab and cleared when you reload or start a new chat. The server does not store conversations. Live source monitoring is not enabled.

If you allow analytics, PostHog receives page views and actions such as workflow saves, skill downloads and link clicks. Random browser and session identifiers connect these actions without identifying you by name. Your choice and browser identifier expire after 90 days; sessions restart after 30 minutes of inactivity or 24 hours. We use local storage, not analytics cookies. Messages, company URLs, search text, full referrers and IP addresses are not sent. There are no person profiles or session recordings. You can decline or withdraw in Analytics settings; Do Not Track and Global Privacy Control keep analytics off.

Read the Plays Privacy Notice ↗