Check items for this visit only. Nothing is stored or submitted. Use your approved systems for evidence and sensitive information. This is an operational checklist, not a legal determination.
0 items checked
Preserve the dated question, governing sources, applicable changes, source locations, operating record, reviewer and unresolved gaps so another person can reproduce the review. Begin with the decision the packet supports: a disputed charge, renewal assessment or entitlement question. Identify the entity, service and period rather than filing an undirected collection of documents.
Record both the date of the review and the date the question concerns. A document received today may describe a position that applied earlier. Keep those boundaries distinct so a later reviewer does not confuse when evidence arrived with when a provision took effect.
List the master agreement, order, schedules, amendments and relevant exceptions supplied for the question. Record document names and stable source locations. Identify which changes affect the service or entity under review and which provisions remain unchanged.
Citations should let another authorized person locate the supporting passage, not merely open a large folder. Keep the surrounding definitions and referenced schedules available where they affect meaning. If a source cannot be located, record the request and owner instead of treating the missing material as an empty obligation.
Illustrative example: a later pricing amendment is available, but its referenced schedule is missing. The amendment evidences that a change was agreed and may identify its effective date. It does not necessarily establish every product or price in the unavailable schedule.
Record the affected invoice or renewal decision, what the available wording supports and the precise question the schedule must resolve. Assign someone to request it. A risk entry is more useful when it connects that uncertainty to a specific decision than when it simply says “documentation incomplete.”
Include the invoice line, inventory record or other operating evidence being assessed, with its period and version. Explain any mapping between supplier labels and agreement terms. Preserve the original label alongside the reviewed mapping so another person can challenge it.
List assumptions separately from evidenced facts and attach open requests to an accountable owner. Note which decisions can proceed on the available record and which need further review. An evidence trail supports scrutiny; it does not promise audit acceptance or replace legal and professional judgment.
Check who needs access to the packet and which underlying records they are entitled to see. Avoid exporting sensitive attachments simply because they are convenient. Include permitted source locations and a route for requesting authorized access when a reviewer needs more context.
Name the person responsible for the review, the decision owner and the person maintaining the evidence. These may be different people. Capture their review date and outstanding follow-up so the packet remains useful when responsibility passes between teams.
Keep a dated record of additions, corrected mappings and revised conclusions. When a missing schedule arrives, connect it to the earlier request and explain which part of the assessment changed. Retain the earlier basis rather than rewriting history.
LineageAI connects source relationships, dates, scope and evidence. Use this checklist to assess whether your own review packet makes those connections clear, regardless of where the final decision is recorded.