Begin with the documents
Retrieval-augmented generation searches an approved collection and uses relevant passages to support an answer. It does not automatically make outdated or contradictory information correct. Inventory the sources, owners and update process first.
Remove duplicates where appropriate and preserve document versions. A policy from three years ago should not compete equally with a current approved policy without a visible rule. Decide how the system handles scanned pages and documents that cannot be parsed.
Preserve meaning during ingestion
Split content along meaningful boundaries such as headings, paragraphs and tables. Attach source IDs, page numbers, section names and access metadata to each chunk. Those details support both retrieval and a citation a reader can actually verify.
Keep ingestion repeatable. When a document changes, the system should update or remove its old chunks rather than accumulating conflicting copies. Track parse failures so missing knowledge is not mistaken for successful indexing.
Retrieve within the user’s permissions
Apply access rules before the model sees the material. Hiding a restricted citation after generation is too late: the answer may already contain the protected information. The retrieval layer needs the current user or tenant scope.
Test isolation with real role combinations, including users whose access has been revoked. Index deletion, source deletion and access changes need defined propagation behavior. Avoid treating vector similarity as authorization.
Evaluate retrieval separately from writing
An elegant answer cannot compensate for retrieving the wrong passage. Create a set of representative questions and identify the sources that should answer them. Examine source coverage, retrieval recall and whether a reranker improves relevant ordering.
Then evaluate the final answer for support. Every important assertion should be grounded in retrieved evidence or explicitly described as an inference. Conflicting sources, incomplete context and missing answers need understandable responses.
Make citations usable
A citation should lead to the supporting document and, when available, the relevant section or page. Display enough context for a reviewer to assess the claim without repeating the full search.
Check links and permissions at the point of access. A citation to a document the user cannot open is usually a sign of a broken permission boundary or a poor experience. Keep source freshness visible when it affects the answer.
Turn the thinking into a project
Use the project planner to describe your objective, integrations and constraints. The result is a discussion brief, with no invented price or delivery commitment.
Plan your project