Keep an instruction understandable on its own
A runbook often places a warning, a condition and a sequence of steps in the same section. If a chunk starts at step three, the reader may never see the condition that makes the action safe.
Read each chunk as if it were the only passage returned by your knowledge base. Can you tell what the action applies to, what must happen first and how to check the result?
Use size as a starting point
Precidoc splits source sections using a character limit and prefers available line or word boundaries. It does not identify semantic boundaries with an LLM.
Start with a size that fits an ordinary section. Review any section that becomes several chunks, especially a numbered procedure or a table. Adjust the size and inspect the new result; do not assume one setting will suit every document.
- Keep a condition close to the action it controls.
- Check that a table still has its labels and units.
- Look for warnings that became separated from their steps.
Merge identical text with its references
Repeated passages can create several copies of the same instruction. Exact duplicate merging in Precidoc retains the source references on the remaining chunks.
Two passages with similar wording may still refer to different systems or versions. Exact matching does not detect those differences for you. Read the context before deciding that repetition is redundant.
Check the route back to the runbook
A chunk should still point to the page or section it came from. Use that reference to verify the instruction and to locate the current version of its source.
After editing source text or changing chunk settings, review the result before exporting. The real test comes later: try representative questions in your retrieval system and inspect which passages it returns.