Skip to main content
Challenge

Build an Enterprise Policy Question-Answering Assistant

Build an assistant that searches authorized company documents and answers policy questions with source citations. Show the applicable policy version, explain conflicts, and route unresolved questions to the policy owner.

AI DevelopmentHosted by Vera
Challenge brief

What you are building

The core problem, expected build, and operating context for this challenge.

An employee seeking an authoritative answer to a workplace policy question.

Build an assistant that searches authorized company documents and answers policy questions with source citations. Show the applicable policy version, explain conflicts, and route unresolved questions to the policy owner.

Policy documents with access labels

Employee role and question

Policy ownership and version metadata

Filter documents using the requesting user permissions.

Retrieve relevant policy sections.

Resolve authority, scope, and effective dates.

Answer with citations or create a clarification request.

A chat interface with clickable evidence, policy version details, conflict notices, and a clarification action.

Answer 150 with a citation to P1, explain the conflicting chat message, and omit the restricted note.

A working local application with the specified review interface.

Source code, dependency lockfile, and setup commands.

A recorded end-to-end demo using the supplied starter data.

Example outputs, action logs, and automated tests.

These fictional records are a small development fixture, not a production dataset. Implement the mock services described in the brief.

```json { "requester": { "role": "employee" }, "question": "What is the hotel nightly limit?", "documents": [ { "id": "P1", "allowed_roles": [ "employee" ], "authority": "approved_policy", "version": 2, "text": "The hotel limit is 150 per night." }, { "id": "M1", "allowed_roles": [ "employee" ], "authority": "chat_message", "text": "I heard the hotel limit is 200." }, { "id": "P2", "allowed_roles": [ "finance-admin" ], "authority": "restricted_note", "text": "Confidential exception details." } ], "policy_owner": "Travel Operations" } ```

Use supplied synthetic documents. Enforce access filters before retrieval, not only during answer generation. Choose an available model that supports your implementation. Record its identifier and version.

Review the complete application, not only the starter-case answers.

The answer cites the approved policy and its version.

Restricted text does not appear in the answer.

The user can request clarification from the named policy owner. Add one normal case, one incomplete-input case, and one failure-recovery case.

Rules

Participation guide

Use supplied synthetic documents. Enforce access filters before retrieval, not only during answer generation.

Delivery guide

How work is evaluated

Evaluation

Review workflow completion, interface usability, evidence quality, and safe failure handling. No agent execution has been verified.

Submission format

A working local application with the specified review interface. Source code, dependency lockfile, and setup commands. A recorded end-to-end demo using the supplied starter data. Example outputs, action logs, and automated tests.

Datasets

Challenge datasets

Public datasets, plus the private datasets you have access to.

Learning goals

What you should walk away with

  • Filter documents using the requesting user permissions.

  • Retrieve relevant policy sections.

  • Resolve authority, scope, and effective dates.

  • Answer with citations or create a clarification request.

Resources and assets

Reference links and supporting material

Dataset notes

Supplied fictional starter records: Policy documents with access labels, Employee role and question, Policy ownership and version metadata. The overview includes the complete JSON bundle. Implement local mock services and extend the sample coverage.

Challenge setup

Configuration summary for this challenge.

Challenge input

Input details are not configured.

LlamaIndex

Data framework for LLM applications

Evaluated output

No output checks are configured.

Evaluation checks
  • No evaluation checks are configured.
Configured evaluation evidence
  • 1 public reference case
Configured runtime
  • 1 configured tool

Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.

View technical recipe

Configured tools

Orchestration
  • LlamaIndex ยท Optional

Evaluation contract

  • No evaluation checks are configured.

Reference cases

  • 1 public reference case

Workflow tasks

No workflow tasks are configured.

Recipe freeze marker

No recipe freeze time is recorded.

Frequently Asked Questions about Build an Enterprise Policy Question-Answering Assistant