Skip to content

Main content

Consent Signature Version Date Order

Compare explicit consent-version and signature calendar dates without assessing consent validity.

Loading tool…

Description

Compare a supplied consent-signature date with a version effective date.

Research records distinguish a participant's stated preference, a recorded permission assertion, version dates and professional roles. A label does not authenticate consent or authority, while travel minutes and compensation shares capture only selected aspects of burden or payment. Ethical interpretation requires the surrounding circumstances and evidence.

Compare a supplied consent-signature date with a version effective date.

When to use this tool

Use Consent Signature Version Date Order when you already have versionEffectiveDate, signatureDate and need to compare a supplied consent-signature date with a version effective date.

How to use the tool and how it works

  1. Enter versionEffectiveDate, signatureDate. 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 signatureBeforeVersionDate, signedDaysAfterVersion. Inspect signatureBeforeVersionDate before interpreting the associated values.

Parse both as real UTC YYYY-MM-DD dates; return signature<version and the signed calendar-day difference signature-version.1

Input fieldMeaning and unitsAccepted input
versionEffectiveDateVersion Effective DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
signatureDateSignature DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
Output fieldInterpretationReturned shape
signatureBeforeVersionDateSignature Before Version DateRequired. Boolean.
signedDaysAfterVersionSigned Days After VersionRequired. Safe integer.
json
{
  "input": {
    "versionEffectiveDate": "2026-10-28",
    "signatureDate": "2026-11-01"
  },
  "output": {
    "signatureBeforeVersionDate": false,
    "signedDaysAfterVersion": 4
  }
}

Limitations and assumptions

  • Equality is not before. Calendar dates provide no within-day order, actual consent, version applicability, authority or legal judgment.
  • 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

Review original consent, preference, version and role records with the applicable oversight process. Evaluate understanding, voluntariness, scope and actual circumstances rather than treating a local flag, date gap or financial fraction as an ethical determination.

References

  1. Calculation and input contract: bioethics/consent-signature-version-date-order — tool.io

Similar or alternative tools