01
Where this one gets misread
Chunking is invisible in a demo and decides what the system can find at all. A passage split across two chunks can become unfindable even though the document is indexed and the search looks healthy.
Glossary
What is chunking?
Chunking is the splitting of source content into smaller units for indexing and retrieval. Where the boundaries fall changes what a system can find later.
Updated 21 Aug 2026
02
Questions to ask
Ask for a worked example on your own material, and the evidence needed to reproduce it.
- Are boundaries chosen by fixed size, by document structure, or by layout?
- What happens to a table or a clause that spans a break?
- Can you see the chunks behind a given answer?
- What triggers a re-chunk when a source changes?
03
How Marella uses the term
We use “Chunking” only where a product mechanism or an evaluation method backs it up, and we say when the behaviour depends on how a deployment is configured.
- Backed by a product mechanism or an evaluation method
- Deployment differences flagged
What this page does not prove
- B1A definition is not a claim about how the product performs.
- B2Vendor implementations vary.
- B3Test the term against a representative workflow.
Related pages
Test the claim on your documents
Pick a real piece of work, agree what a good answer looks like, then go through the results together.