Safety Contact Acknowledgment Flag Tool

Description

Reject acknowledged true when contacted is false.

Security administration uses retention periods, control owners, acknowledgments, recovery targets, and test records. Arithmetic and labels can make these records consistent, but they do not demonstrate that a control works or that a policy is adequate.

Reject acknowledged true when contacted is false.

When to use this tool

Use Safety Contact Acknowledgment Flag when you need a narrow security-record calculation or formatter under supplied policy values.

How to use the tool and how it works

Enter contacted, acknowledged. Use the units and conventions below.
Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
Read awaitingAcknowledgment. Inspect awaitingAcknowledgment before interpreting the associated values.

Reject acknowledged true when contacted is false. Return awaitingAcknowledgment when contacted but not acknowledged.^[1]

Input field	Meaning and units	Accepted input
contacted	Contacted	Required. Boolean.
acknowledged	Acknowledged	Required. Boolean.

Output field	Interpretation	Returned shape
awaitingAcknowledgment	Awaiting Acknowledgment	Required. Boolean.

json

{
  "input": {
    "contacted": true,
    "acknowledged": false
  },
  "output": {
    "awaitingAcknowledgment": true
  }
}

Limitations and assumptions

This checks two recorded flags, not successful communication, emergency readiness, or a safety response.
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 the complete control evidence, applicable policy, and operational tests before making a security decision.

References

Calculation and input contract: security-studies/safety-contact-acknowledgment-flag — tool.io

Similar or alternative tools

Message Ack Delay Pair
Require acknowledgedTimeSeconds no earlier than sentTimeSeconds and subtract for delaySeconds.
Case Handoff Receipt Delay
Require receivedTimestampSeconds no earlier than sentTimestampSeconds and return their difference.