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.
Description
Expiry and release for disposition are separate workflow conditions.
Expiry and release for disposition are separate workflow conditions. A record can be past its declared retention date while a hold or incomplete review still blocks eligibility.1
Separate declared expiry from caller hold/review gating, preserving expired-but-held records; eligibility flags are workflow policy, not lawful destruction permission.
When to use Retention Period Expiry Eligibility Checker
Use this tool to separate declared expiry from caller hold/review gating, preserving expired-but-held records; eligibility flags are workflow policy, not lawful destruction permission.
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 Period Expiry Eligibility Checker and understand its results
- Prepare the inventory, measurements or policy dates for the collection and reporting period. Confirm units, record order and any independently established thresholds or permissions.
- Enter declaredRetentionExpiryOrdinals, legalHoldFlags, requiredReviewCompleteFlags, asOfDayOrdinal using the field table and calculation rules, then run the tool.
- Read expiredRecordFlags, callerEligibilityFlags, holdBlockedExpiredCount. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- 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 field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| declaredRetentionExpiryOrdinals | Declared retention expiry ordinals | list of number | Required |
| legalHoldFlags | Legal hold flags | list of number | Required |
| requiredReviewCompleteFlags | Required review complete flags | list of number | Required |
| asOfDayOrdinal | As of day ordinal | integer | Required |
Enter aligned nonnegative integer expiry ordinals, binary hold and review-complete flags and a nonnegative as-of ordinal. Expiry equality counts as expired. Return binary expired and caller-eligibility lists, plus the count of expired records blocked by a hold; incomplete reviews independently prevent eligibility.
Paired lists must be nonempty and have equal lengths.
expired = expiry≤asOf; eligible = expired AND noHold AND reviewComplete Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| expiredRecordFlags | Expired record flags | list of number |
| callerEligibilityFlags | Caller eligibility flags | list of number |
| holdBlockedExpiredCount | Hold blocked expired count | number |
{
"input": {
"declaredRetentionExpiryOrdinals": [
10,
20,
30
],
"legalHoldFlags": [
0,
1,
0
],
"requiredReviewCompleteFlags": [
1,
1,
1
],
"asOfDayOrdinal": 25
},
"output": {
"expiredRecordFlags": [
1,
1,
0
],
"callerEligibilityFlags": [
1,
0,
0
],
"holdBlockedExpiredCount": 1
}
} Limitations and assumptions
These flags apply supplied workflow facts, not a legal determination or destruction authorization. Incorrect holds, dates or review records produce incorrect eligibility results.
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 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. For a complementary task, use GDPR-Style Personal Data Retention Conflict Flag Checker: Audit conflicting independently established retention/deletion deadlines and preserve legal holds for separate review; no GDPR interpretation, precedence resolution or deletion advice.
References
Similar or alternative tools
- 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.
- GDPR-Style Personal Data Retention Conflict Flag Checker
Audit conflicting independently established retention/deletion deadlines and preserve legal holds for separate review; no GDPR interpretation, precedence resolution or deletion advice.