An internal assistant that answers from your own procedures: what it is and what it needs 

An internal assistant is a private tool that answers staff questions from your own procedures, templates and past work, and shows the source document for each answer. It is limited to your people, keeps client files separate and logs what it is asked. It does not reach for public internet answers to your business questions.

What is an internal assistant?

Put simply, an internal assistant is a question-and-answer tool for your own people, built on your own documents.

In many firms, knowledge sits in a few heads and in folders nobody can search. New staff ask the same questions again and again, and senior people lose hours answering them. An internal assistant lets a person ask in plain words, such as how do we handle a late filing for a new client, and get an answer drawn from your own procedures.

It also helps with reuse. Past proposals, letters and checklists already sit in the system, and the assistant can find the most relevant one and point to it, so staff start from your own best work rather than a blank page.

How is it different from a public chatbot?

The difference that matters most is the source. An answer that comes with a link to your own procedure can be checked in seconds, while an answer that comes with nothing has to be taken on trust.

What does it need from you?

It needs material to read and rules about who may see what, and the assistant will only ever be as good as what you give it.

Procedures and templates

Gather the documents that say how work is done: standard procedures, checklists, templates and policies, all of them current. Where two documents disagree, decide which one is right and remove the other, because an assistant that reads contradictory documents gives contradictory answers.

Past work

Past proposals, advice letters, reports and similar items show how your firm actually works, so choose what to include with care. Leave out anything confidential to one client that should not be shared across the firm.

Access rules

Decide who may see which material. Client files often need to stay separate from each other and from general procedures. Write the rules down before the build, and test them before launch.

How does it show where an answer came from?

The assistant first finds the passages in your documents that relate to the question, then writes an answer from those passages alone. Alongside the answer, it shows the document and the section it used.

This helps in three ways. A person can open the source and confirm the answer. A wrong answer can be traced to a wrong document and fixed at the root. And you can see which documents get used often and which are never touched.

What should it never answer?

• Questions your documents do not cover. It should say so plainly rather than guess.
• Anything from a client file the person is not allowed to see.
• Advice that a qualified person must give, such as final legal, tax or clinical advice to a client.
• Questions about people, such as pay or performance, unless your rules explicitly allow it.

A good assistant says I could not find this in your procedures and offers to pass the question to a named person. That reply is a sign the design is working, not a failure.

Who should see it?

Start with a small group who ask a lot of questions, such as new starters and people who answer the same queries every day. Learn from how they use it, then widen access in steps, with rules for each group.

Keep a log of what was asked and what was answered. It shows what staff need to know and helps you spot gaps in your procedures. Tell staff the log exists and why you keep it.

What kinds of questions does it handle well?

It does best on questions whose answer already exists in your documents, the ones staff ask often while the answer sits in a folder nobody can find quickly.

• How do we onboard a new client, and which forms do we use?
• What is our standard wording for this type of letter?
• Which checklist applies to this kind of job?
• What did we do the last time a client asked for this?
• Where is the latest version of this template?

It does poorly on questions that need fresh judgement or depend on facts outside your documents. For those, it should point the person to a named colleague.

How do you start?

1. Choose one area, such as onboarding or one service line, with documents that are already in good order.
2. Gather and clean the documents, removing old versions and contradictions.
3. Set the access rules and write them down.
4. Build the assistant for that area and test it with real questions from your staff.
5. Check the answers and the sources, fix the documents that cause bad answers, and widen the scope step by step.

Keep the first version small. A narrow assistant that answers well earns trust, while a wide one that answers badly loses it quickly.

Plan for upkeep from the start, because procedures change, staff leave and templates get replaced. Agree who reviews the documents each quarter and who removes the ones that are no longer right. Without that routine, even a good assistant slowly gives worse answers. With it, the assistant improves as the firm learns.

What can go wrong?

Most problems come from the documents rather than the technology. Old procedures give old answers, duplicate files confuse the search and missing access rules let the wrong person see the wrong file.

The second problem is trust. If staff catch the assistant out a few times, they stop using it. Show them how to check the source and make it simple to report a bad answer. Then fix reported problems quickly and tell people you have, which is what keeps the tool in use.

Frequently asked

People usually ask how it differs from a public chatbot, what RAG means and how to keep it accurate, and the answers follow. In short, it answers from your documents, shows its source and needs an owner to keep those documents current.