MILabs
Tools

R2R for private document search and staff questions

R2R explained for small businesses, and how MILabs sets it up to search your own documents.

Updated 2026-08-25

What R2R is

R2R is an open-source retrieval-augmented generation system made by SciPhi. It takes a collection of documents, such as policies, manuals, contracts or product sheets, breaks them into sections and builds an index that can be searched by meaning as well as by keyword. When someone asks a question, the system retrieves the most relevant passages and passes them to a language model, which writes an answer from that material. R2R exposes its functions through an API, so other software in the business can send documents in and receive answers back. Because it can be self-hosted, the document store and index can run on infrastructure the business controls. The project is maintained publicly on GitHub, where its documentation and licence are published. In plain terms, R2R is a layer for searching and questioning existing files, and the answers it gives are only as sound as the documents behind them.

SciPhi: official site

R2R in plain language

Retrieval-augmented generation lets a language model answer from a chosen body of material rather than from its training alone. The files are prepared in advance, the passages closest to a question are gathered, and those passages are given to the model with the question. The reply is then written from that evidence, so it can be traced to a source.

R2R is one open-source option in this category, and its source code can be inspected. Teams weighing it usually ask where indexed files are stored and who can query them, since client details, pricing and personnel records would all pass through the same pipeline.

Preparation carries most of the effort. Documents are converted to text, divided into passages of workable size, and tagged with their origin and permitted readers. Embedding-based search then compares the sense of a question with the sense of each passage, so a query about annual leave can surface a clause worded differently.

Output quality depends on current documents, retrieval that finds the right passages, and a model that stays within them. Those three conditions still need a person to confirm the cited source before an answer is acted on where money, safety or legal duties are involved.

What businesses use it for

  • Answering staff questions about internal policies, procedures and forms
  • Searching contracts, manuals and technical files by meaning instead of exact wording
  • Giving clients a grounded answer drawn from the business's published guides
  • Building a private question layer over project records and past reports
  • Supporting new team members with an index of onboarding material

Who it suits

  • Owners with large folders of policies and manuals that staff keep asking about
  • Firms that need document answers to stay on infrastructure they control
  • Teams with an in-house developer or IT contact who can keep a self-hosted system running

How MILabs sets it up

Setup starts with the owner or team lead, agreeing which document sets R2R should index first and who may see each set. The plan covers where R2R will run, on the business's own server or on infrastructure chosen with the owner. Next, MILabs connects the document sources the business already uses, such as shared drives or the helpdesk, and checks that updated files are picked up. Access rules are set so each person sees only the material their role allows. Finally, the business and MILabs agree who looks after the system after handover: who updates the document store, who reviews answers that look wrong and who applies R2R updates from the public repository. The owner receives a short written note on the configuration and the checks to make.

Builds it fits

Industries it fits

R2R in practice

In a business that runs R2R, most of the daily work happens around the document set rather than inside the software. Each collection, such as the leave policy, supplier terms or service manuals, has a named owner who decides when files are replaced or withdrawn. Staff usually reach the system through a chat window on the intranet or a small internal page that calls the R2R API, and each answer shows the passages it drew on so the reader can open the original.

Permissions follow roles. A receptionist might see the public service guides, while a team lead also reaches the internal risk register. These settings are reviewed whenever someone changes position.

Feedback keeps the layer useful. When an answer looks wrong, staff log the question and the passages involved, and the document owner decides whether the file or the retrieval needs attention. Often the cause is an outdated file, so the fix is editorial.

Over time, the business learns which collections answer well. Dense or duplicated folders tend to produce muddled replies, and a drive full of drafts will echo those drafts back. The job is closer to editorial upkeep than software maintenance.

good questions, straight answers

Frequently asked questions

Who looks after R2R after setup?
The business keeps ownership of the system and its documents. MILabs and the business agree at handover who updates the document store, who reviews answers that look wrong and who applies R2R updates from the public repository. An in-house developer or IT contact usually takes on routine upkeep, and the written configuration note tells them what was set up and why.
What should I check on the vendor's site before using R2R?
R2R is maintained on GitHub by SciPhi, which publishes its installation guide, licence terms and list of supported features. MILabs plans the server capacity and security measures with the owner before anything is installed. That planning is done once, before any installation, so the business knows what it needs from the start. Reviewing the public notes again at each update keeps the setup accurate.
How do I know whether R2R is paying off?
Pick two or three measures before the system goes live, such as how often staff ask the same questions, and how long it takes to find a policy or past document. Compare those measures after a period of use, and review a sample of answers to confirm accuracy. If the same questions keep reaching the same people, or staff stop trusting the answers, the document set or the setup needs attention.
Which industries use R2R?
No single industry is the natural fit for R2R. It suits businesses that hold large, changing collections of written material and need answers from it quickly. Examples include law firms with precedent banks, accounting firms with client guidance, insurance brokers with policy wordings, engineering firms with standards and project files, aged care and disability providers with procedure manuals, and property managers with lease and maintenance records.
What do businesses use R2R for?
Businesses use R2R to put a question and answer layer over documents they already have. Common uses include answering staff questions about policies and procedures, searching manuals and contracts by meaning, and giving client-facing teams a grounded reference for frequently asked questions. Each answer links back to the source document it was drawn from, so the owner can confirm it there.
let's make something happen

Workflow automation: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.