Skip to content

Main content

Client Contact Safe Window Match Tool

Check a local clock minute against an explicit half-open client-selected contact window, allowing midnight wrap; no contact is made.

Loading tool…

Description

Test start-inclusive/end-exclusive membership, joining the two sides of midnight when start exceeds end.

Contact and disclosure permissions describe what a supplied record says at a particular time. A boolean flag or formatted permission label cannot verify informed consent, identity, authority, or permission for a different purpose.

Test start-inclusive/end-exclusive membership, joining the two sides of midnight when start exceeds end.

When to use this tool

Use Client Contact Safe Window Match when you need to preserve or compare a stated permission without broadening its meaning.

How to use the tool and how it works

  1. Enter minuteOfDay, safeStartMinute, safeEndMinute. 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 withinRecordedWindow. Inspect withinRecordedWindow before interpreting the associated values.

Require minuteOfDay and start in 0-1439, end in 0-1440, and unequal endpoints. Test start-inclusive/end-exclusive membership, joining the two sides of midnight when start exceeds end.1

Input fieldMeaning and unitsAccepted input
minuteOfDayMinute Of DayRequired. Safe integer; minimum 0; maximum 1439.
safeStartMinuteSafe Start MinuteRequired. Safe integer; minimum 0; maximum 1439.
safeEndMinuteSafe End MinuteRequired. Safe integer; minimum 0; maximum 1440.
Output fieldInterpretationReturned shape
withinRecordedWindowWithin Recorded WindowRequired. Boolean.
json
{
  "input": {
    "minuteOfDay": 600,
    "safeStartMinute": 540,
    "safeEndMinute": 1020
  },
  "output": {
    "withinRecordedWindow": true
  }
}

Limitations and assumptions

  • This checks the recorded clock window without timezone conversion, consent verification, emergency handling, or a guarantee that contact is safe.
  • 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

Check the original permission record, its scope, and current organizational requirements before contacting someone or disclosing information.

References

  1. Calculation and input contract: social-work/client-contact-safe-window-match — tool.io

Similar or alternative tools