Which manual applies to this machine?

Imagine a service assistant answering a customer who wants to order a replacement part. It finds a part number in a genuine company manual and links to the right page.

The drawing is for the original assembly. The customer’s machine has since been modified, and the replacement-part list for that modification sits in a separate service record.

That is a plausible failure to test before giving an assistant your shared drive. Finding a relevant-looking document and establishing that it applies to the customer's equipment are separate jobs.

Consider the equipment supplier’s document collection. Its files include installation guides, replacement notices, old catalogues and instructions written for particular customers. The service team wants help answering questions about parts and maintenance. Uploading everything may appear to give the assistant more knowledge. It also gives the project a larger collection of conflicting instructions to govern.

Start with a question the service team actually handles. Then use the following checks to decide which evidence can support an answer.

1. Identify the equipment before selecting the instruction

A product family name may not be enough. Depending on the equipment, the relevant distinctions could include model, serial-number range, installed options, software version or a modification performed after delivery.

For the replacement part, ask for the machine’s identification plate or serial number, then check whether the service record shows a modified assembly. A serial number may identify the machine as delivered without describing its current configuration. Ask the service team which evidence settles that difference; collect those fields rather than every field the database contains.

If the customer has not supplied them, the assistant should request the missing identification or route the question appropriately. Guessing the model from the wording of the question is a poor substitute for a decision rule.

For consequential maintenance or safety questions, define the boundary with qualified staff. An assistant that can retrieve a manual is not automatically authorised to instruct someone to perform a hazardous operation.

2. Separate an approved instruction from something that looks official

A draft procedure can have a company logo. An old PDF can have a professional layout. Neither tells the system whether the document is approved for the intended use.

Give each usable document an approval status, an equipment scope and an owner who can confirm them. A newer publication date does not make a manual applicable to an older machine. Exclude drafts and instructions superseded for the equipment in question, rather than discarding every old document.

Historical material can still be valuable. A technician investigating an older installation may need it. The system must preserve the distinction between “this was the instruction then” and “this is the instruction to follow now”. Deleting every older document is not a universal solution.

3. Keep the conditions attached to the sentence

An instruction can be true only under conditions that sit outside the paragraph retrieved by the assistant.

A table heading may restrict a part to a particular configuration. A warning on the previous page may qualify a maintenance step. An appendix may exclude a serial-number range.

Test questions that depend on those conditions. Check whether the answer includes the restriction and whether the user can inspect it in the source. A correct quotation of one sentence is insufficient if its qualifying information has disappeared.

Where the source structure makes this difficult, improve the source representation or narrow the assistant's permitted response. Do not treat a confident summary as evidence that the missing context has been recovered.

4. Treat customer-specific exceptions as customer-specific

Suppose a service note records a special arrangement for one installation. That may be useful evidence for that customer's case. It does not create a general policy for every customer asking a similar question.

The same applies to one-off discounts, warranty concessions and nonstandard modifications. A system needs a way to distinguish a general rule from an authorised exception and to apply access restrictions to the underlying record.

This is one reason to resist the promise that “more documents” will automatically produce better answers. The collection needs a defined job. A manual-answering assistant may not need commercial correspondence at all.

If it does need information from several categories, decide which source governs each type of claim. A salesperson's email should not silently replace an engineering instruction about compatibility.

5. Follow a replacement document all the way through

When a new instruction replaces an old one, who updates the collection? What tells the search system that the old version should no longer support current guidance?

Ask for a demonstration. Replace an approved document in a safe test collection, then repeat a question whose answer changed. Inspect both the answer and its source. Check whether a cached response still contains the old instruction.

Also test removal and access changes. If a document is withdrawn, the assistant should not continue exposing its content through an index or a saved answer to users who no longer have permission. The technical details depend on the platform; the acceptance condition should be clear before procurement.

For a wider purchasing comparison, Glean and self-hosted enterprise search discusses permissions and the work of maintaining connectors. This article's question is narrower: which instruction may support this answer today?

6. Give unresolved conflicts somewhere to go

Two approved-looking sources may disagree. The assistant should not resolve that conflict by choosing whichever sentence sounds more relevant.

Identify who owns the underlying information. Show the conflicting references and the exact question that cannot yet be answered. Give the customer an honest next step rather than an invented compromise.

Keep a record of the resolution so the same conflict does not return indefinitely. That might require correcting a document, clarifying its applicability or updating a rule in the source system. Adding another prompt instruction is not always the right repair.

Build a small collection the service team can defend

Take a recurring product question and select the documents needed to answer it. Include a current manual, an older version and a deliberately ambiguous case in the test. The assistant should answer the clear case and handle the others according to the agreed boundary.

That exercise is more revealing than asking whether it can summarise a folder. It exposes the information the business itself needs to make the answer dependable.

Request a Strategy Session with one product question and the documents your team uses today. We can start by determining what belongs in the answer path and what should stay outside it.