Skip to content

Main content

Policy Version Effective Date Choice

Select the latest not-future policy version from explicit unique effective dates without applying repeal, supersession or jurisdiction rules.

Loading tool…

Description

Choose the most recently effective supplied policy version by an as-of date.

Administrative records depend on policy dates, authorization scope, attendance denominators and accounting definitions. A calendar-date shift does not skip holidays, a quorum fraction is not a quorum decision, and a weighted voting fraction differs from economic ownership. Recorded signatory presence does not authenticate a signature or establish authority.

Choose the most recently effective supplied policy version by an as-of date.

When to use this tool

Use Policy Version Effective Date Choice when you already have versionCodes, effectiveDates, asOfDate and need to choose the most recently effective supplied policy version by an as-of date.

How to use the tool and how it works

  1. Enter versionCodes, effectiveDates, asOfDate. Follow any array-alignment requirements below. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read found, versionCode, effectiveDate. Inspect found before interpreting the associated values.

Require aligned arrays and unique effective-date strings; validate every date and asOfDate. Select greatest effective date<=asOf, regardless of list order; return found and selected fields, or empty strings when absent.1

Input fieldMeaning and unitsAccepted input
versionCodesLiteral version labels aligned with unique effectiveDates; input order need not be chronological.Required. Array of text; maximum UTF-16 length 8192; maximum items 256.
effectiveDatesEffective DatesRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
asOfDateAs Of DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
Output fieldInterpretationReturned shape
foundTrue when a policy date is <=asOfDate; false distinguishes empty output placeholders.Required. Boolean.
versionCodeVersion CodeRequired. Text; maximum UTF-16 length 8192.
effectiveDateEffective DateRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "versionCodes": [
      "v1",
      "v2"
    ],
    "effectiveDates": [
      "2025-01-01",
      "2026-10-01"
    ],
    "asOfDate": "2026-11-01"
  },
  "output": {
    "found": true,
    "versionCode": "v2",
    "effectiveDate": "2026-10-01"
  }
}

Limitations and assumptions

  • Version codes may be empty or repeated, so consult found. No document, authority, applicable scope, supersession beyond dates or actual policy is verified.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Check controlled policies, meeting records, contracts and account definitions. Apply the complete applicable rules when actual approval, payment or governance matters; local version selection and arithmetic do not make those determinations.

References

  1. Calculation and input contract: business-administration/policy-version-effective-date-choice — tool.io

Similar or alternative tools