Franchisee onboarding: document chunking for procurement

Review document chunking for procurement in Franchisee onboarding. Check document scope, failure paths and source evidence through controlled tests.

What the documents look like

Opening support is a transfer of operating capability, so the material set differs from legal franchise filing. The working documents are training attendance sheets, opening checklists, SOP manuals, and assessment scores. Procurement and supplier records usually arrive as attachments mixed into supervisor app uploads and the headquarters SOP library, so one store's purchase list, supplier qualification page, and goods receipt record may belong to different submission batches. The brief states these materials update per store, per month. Chunking therefore has to preserve document identity and version so that any retrieved fragment can be traced back to its source item.

Constraints at the document chunking step

Chunking follows the structure of each material. The date column of an attendance sheet, the material line items of a checklist, and the step descriptions of an SOP manual each form separate segments. A conditional sentence stays in the same chunk as the item it constrains. Original data and retrieval indexes are treated separately: one group of original data can map to multiple indexes, and when several vectors resolve to the same original data group, the vector score takes the highest value. Retrieval is a recall process and does not perform authorization checks. Purchase approval, supplier admission, and contract effectiveness require separate downstream implementation.

Hypothetical drill sample: the source text is "March 2024 Opening Materials Checklist, item 7: cashier counter petty cash has been counted, supervisor signature field blank; the same month's Supplier Qualification Page states that a food supplier's business license is valid until June 2024; the March 2024 training attendance sheet shows the store owner attended the inventory counting course." The draft sentence to be judged is "the store completed cashier counter petty cash counting in March and obtained supervisor confirmation." The review scope is that store's March 2024 opening support package. The draft sentence turns a blank signature field into completed confirmation, which is an unsupported statement.

Configuration and implementation checks

Configuration itemValue or check on this pageNote
Search modeHybrid retrievalSupplier numbers and material models use full-text recall; natural-language questions use semantic recall
Reference limitHypothetical trial starting value 3000 tokensOpening support packages contain long individual materials; this value allows comparison of reference completeness across settings
Minimum relevanceHypothetical trial starting value 0.4Compared with 0.3 and 0.5 to observe whether unrelated fragments decrease
Question optimizationEnabled or disabled according to observed effectEnable for follow-up questions about supplier qualifications; a single clear question can leave it off
Result rerankingEnabled when a ReRank model is availableThe rerank score supports filtering together with minimum relevance
Chunk verificationAttendance sheets, checklists, and SOP steps segmented separatelyDocument identity and version are retained; conditional sentences are checked against their constrained items

Three common errors

  1. Treating retrieval recall as authorization. Entering "a certain supplier qualification page" and retrieving a record only shows that the page was recalled. Supplier admission status still needs checking against the validity period stated on the qualification page and the approval record.
  2. Treating a successful upload as an updated index. After material changes, the actual training and index state needs checking. The upload action itself does not show that retrieval results have refreshed.
  3. Writing a pending review as confirmed. In the hypothetical sample the supervisor signature field is blank, while the draft sentence states supervisor confirmation was obtained. This is an unsupported statement and should be recorded as pending verification.

How to verify the setup

  1. Enter the hypothetical sample source text and the draft sentence, then compare the signature status field between the draft sentence and the source. The source signature field is blank and the draft sentence states confirmation, so the observed result is that the sentence is unsupported.
  2. Enter "cashier counter petty cash" and "supplier business license validity period" as separate searches, then compare whether the recalled fragments fall on the corresponding checklist and qualification page. The observed result is that fragments can be traced back to source items and do not mix in materials from other stores.
  3. Enter a clear paper input of an empty result [] to check the downstream display design, then compare whether reference content is empty when the result is empty. The observed result is that downstream handles it as an empty reference and does not interpret the empty result as business non-existence. Libraries using different vector models cannot be associated together; check the identifier first, exclude non-matching ones, and record the actual observation.