Missing Chronology (Timeline Anchors)
Short Explanation
Missing Chronology is the absence of dates or traceable timeframes for stated patterns or repeated conduct. The Minimum Viable Review Standard requires an ANCHOR: when the conduct occurred, expressed as a date or traceable timeframe, not a general reference to a period. The reference identifies this as the most common point of failure: most escalation files fail at the timeline level, because conduct is described while dates are not, and without dates the pattern cannot be independently established. Missing timeline anchors for a stated pattern is an escalation trigger that requires secondary review before record entry. A file whose sequence cannot be reconstructed cannot demonstrate that prior steps preceded escalation or that a response was timely, which are the questions later review asks first.
Why It Matters
Order determines meaning. Without dates, a pattern cannot be independently established and escalation that references the pattern cannot be supported, which is precisely where files fail under audit and dispute.
Reviewer Questions
- Are dates or date ranges present for each stated pattern or repeated conduct claim?
- Is timing expressed as a date or traceable timeframe, not a general reference to a period?
- Can the sequence be reconstructed from the file alone?
- Does escalation language reference conduct that carries specific dates?
Common Failure Pattern
Related JRS Sections
Move from this concept to the full reference, then to the calibration and pilot environment where the conditions are applied to records.