All playbooks
ModerateAn afternoonResearchers, legal teams, anyone who needs to search their own corpus

Turn a pile of documents into a private knowledge base you can question

Drop in PDFs, Word files and web pages, then ask questions in plain language and get answers with the source passage attached. It can run entirely on your own machine.

What you end up with

  • Hundreds of documents normalised into structured text instead of scattered files
  • A Q&A interface that quotes the source paragraph behind every answer
  • Data never leaves your machine, if you choose local deployment

The sequence

  1. 1. Turn documents into clean text

    Scanned PDFs and heavily formatted Word files break here first. Parse them, then spot-check a dozen pages to confirm tables and headings survived. Most bad retrieval traces back to this step.

  2. 2. Build the index and retrieval layer

    This decides whether one question finds the right paragraph. Chunk size and whether you keep heading structure matter more than which model you pick.

  3. 3. Test retrieval before tuning generation

    Write 20 questions whose answers you know the page of, and check only whether the right passage was retrieved. Wrong retrieval defeats any model; right retrieval lets an ordinary model succeed. This step gets skipped, and then everyone blames the model.

  4. 4. Put a usable interface on top

    Connect retrieval to a chat UI and constrain the system prompt to answer only from retrieved passages, and to say so when nothing matches. Without that constraint the model starts inventing.

Only need one piece of this?

You don't have to build the whole chain. Every tool above is listed on its own, with a summary, pros and cons, and a starting point.

NextTurn a recording into minutes with action items