Skip to content

Main content

Consent Recontact Permission Date Gap Tool

Compare explicit civil dates with a supplied validity duration, with no policy chosen automatically.

Loading tool…

Description

Return signed permission age and supplied validity remainder.

Participant time, compensation and renewal timing depend on explicit assumptions about visits, expenses, comprehension and applicable rules. A supplied rate or elapsed-time threshold can support bookkeeping while fair compensation, accessibility and valid consent require a broader contextual assessment.

Return signed permission age and supplied validity remainder.

When to use this tool

Use Consent Recontact Permission Date Gap when checking the stated research payment, burden, reading-time or renewal convention.

How to use the tool and how it works

  1. Enter lastPermissionDate, referenceDate, validityDays. 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 ageDays, remainingDays. Use the output convention below.

Return signed permission age and supplied validity remainder. Require nonnegative whole validityDays and valid date-only inputs; ageDays is the UTC day difference, remainingDays = validityDays-ageDays.1

Input fieldMeaning and unitsAccepted input
lastPermissionDateLast Permission DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
referenceDateReference DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
validityDaysValidity DaysRequired. Safe integer; minimum 0.
Output fieldInterpretationReturned shape
ageDaysSigned UTC-midnight day difference; future permission date is not rejected.Required. Safe integer.
remainingDaysRemaining DaysRequired. Safe integer.
json
{
  "input": {
    "lastPermissionDate": "2026-10-01",
    "referenceDate": "2026-10-26",
    "validityDays": 30
  },
  "output": {
    "ageDays": 25,
    "remainingDays": 5
  }
}

Limitations and assumptions

  • Future permission dates give negative age; no appropriate renewal policy, consent validity or legal expiry is selected.
  • 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.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Use participant-centered evidence and the original protocol and consent process; review payment, accessibility and renewal choices with the responsible ethics and professional teams.

References

  1. Calculation and input contract: bioethics/consent-recontact-permission-date-gap — tool.io

Similar or alternative tools