slipstream Book a call
Use caseCorporate legal

Policy and playbook assistant

Answers from your own policies, with the citation attached.

The problem

The policy exists. It is forty pages long, it was updated in March, and the version people quote is the one somebody pasted into a deck in 2023.

How we would run it.

Five stages, applied to this work →
  1. STAGE 1EvidenceCollect the policies, the real questions people ask about them, and the answers currently given. The gap between the three is the problem.Leaves behind: a written picture of the current state, with its gaps named.
  2. STAGE 2BaselineTest retrieval against those real questions before building anything. If the source material cannot answer them, no model will.Leaves behind: a baseline measurement both sides agree on.
  3. STAGE 3DesignDecide the answerable scope, the citation format, and what the assistant must refuse. Refusals are designed, not left to chance.Leaves behind: a design your architecture and risk leads have approved.
  4. STAGE 4ShipRelease to one team with citations on every answer and an obvious route to a human when the answer is not there.Leaves behind: working software or a live process, in production.
  5. STAGE 5ProveReport answer quality on the held-out question set, refusal behavior, and how often people follow the citation.Leaves behind: a result measured against the baseline, and an instrument you keep.

What you get

  • — Curated policy set with ownership and review dates
  • — Assistant that answers with citations to the source paragraph
  • — Refusal and escalation behavior, specified
  • — Held-out question set with approved answers, for re-testing

What it needs from you

  • — Current, approved policy documents — and a named owner for them
  • — Real questions from the last quarter
  • — Somewhere to put it that people already use

How we'd know it worked

  • — Answer quality on the held-out question set
  • — Share of answers where the citation supports the answer
  • — Repeat questions reaching lawyers
Where it starts

Starts as a sprint. Grows into a program.

SPRINTPrompt & Workflow Starter KitTen tested prompts for the work your team actually repeats.Read more → PROGRAMAI Build — pilot to productionOne use case, built and put into production, with evidence it works.Read more →

This describes our approach, not an account of a client engagement.

Start with one sprint.

Two to three weeks, one approver, a deliverable you keep. Scope, date and fee back within one business day.

Scope this as a sprint