Retention Schedule Trigger Date Calculator

Resolve latest caller qualifying retention trigger from observed event inventory plus explicitly declared day period; no legal schedule selection, calendar-year substitution or disposal authorization.

Description

A retention period can begin after the latest qualifying event in a record's event history.

A retention period can begin after the latest qualifying event in a record's event history. Explicit event flags keep unrelated dates from silently becoming retention triggers.1

Resolve latest caller qualifying retention trigger from observed event inventory plus explicitly declared day period; no legal schedule selection, calendar-year substitution or disposal authorization.

When to use Retention Schedule Trigger Date Calculator

Use this tool to resolve latest caller qualifying retention trigger from observed event inventory plus explicitly declared day period; no legal schedule selection, calendar-year substitution or disposal authorization.

Prepare the inventory, measurements or policy dates for the collection and reporting period. Confirm units, record order and any independently established thresholds or permissions.

How to use Retention Schedule Trigger Date Calculator and understand its results

  1. Prepare the inventory, measurements or policy dates for the collection and reporting period. Confirm units, record order and any independently established thresholds or permissions.
  2. Enter eventDayOrdinals, callerQualifyingTriggerFlags, callerRetentionDaysAfterLatestTrigger using the field table and calculation rules, then run the tool.
  3. Read latestQualifyingTriggerOrdinal, modeledRetentionExpiryOrdinal, qualifyingTriggerIndices. The explanation below defines the units, signs, ordering and any flags or placeholder values.
  4. If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
Input fieldMeaningValue type; see rules belowRequirement
eventDayOrdinalsEvent day ordinalslist of numberRequired
callerQualifyingTriggerFlagsCaller qualifying trigger flagslist of numberRequired
callerRetentionDaysAfterLatestTriggerCaller retention days after latest triggerintegerRequired

Pair nonnegative integer event ordinals with binary qualifying flags and supply a nonnegative integer retention period in days. At least one qualifying event is required. Return the latest qualifying day, its calculated expiry and all qualifying zero-based event indices in input order. Event input order need not be chronological.

Paired lists must be nonempty and have equal lengths.

trigger = max qualifying event ordinals; expiry = trigger + declared retention days

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output fieldMeaningValue type
latestQualifyingTriggerOrdinalLatest qualifying trigger ordinalnumber
modeledRetentionExpiryOrdinalModeled retention expiry ordinalnumber
qualifyingTriggerIndicesQualifying trigger indiceslist of number
json
{
  "input": {
    "eventDayOrdinals": [
      10,
      20,
      15
    ],
    "callerQualifyingTriggerFlags": [
      1,
      0,
      1
    ],
    "callerRetentionDaysAfterLatestTrigger": 5
  },
  "output": {
    "latestQualifyingTriggerOrdinal": 15,
    "modeledRetentionExpiryOrdinal": 20,
    "qualifyingTriggerIndices": [
      0,
      2
    ]
  }
}

Limitations and assumptions

The caller selects the trigger policy and period. The calculation does not select legal schedules, substitute calendar years for days or authorize destruction. All ordinals require the same origin.

Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Numeric lists are limited to 100,000 entries; the rules above may require smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.

Alternative or Complementary methods

Use Retention Period Expiry Eligibility Checker: Separate declared expiry from caller hold/review gating, preserving expired-but-held records; eligibility flags are workflow policy, not lawful destruction permission. For a complementary task, use Access Restriction Closure Period End Year Calculator: Resolve explicit whole-year closure policy including closure through final year and opening next year; no automatic privacy law, partial-date period or access-rights determination.

References

  1. Retention Schedule Trigger Date Calculator — tool.io

Similar or alternative tools

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies