Demand Response Window
Check demand-letter acknowledgment timing against a supplied window.
Description
A demand acknowledgment window adds caller-selected calendar days to a receipt date.
A demand acknowledgment window adds caller-selected calendar days to a receipt date. It checks the supplied acknowledgment against that interval.1
Check demand-letter acknowledgment timing against a supplied window.
When to use Demand Response Window
Use this tool to check demand-letter acknowledgment timing against a supplied window.
Prepare the supplied policy terms, dates, assumptions or recorded indicators requested. Keep monetary amounts on one currency basis and select the applicable thresholds separately.
How to use Demand Response Window and understand its results
- Prepare the supplied policy terms, dates, assumptions or recorded indicators requested. Keep monetary amounts on one currency basis and select the applicable thresholds separately.
- Enter demandReceivedDate, acknowledgmentDays, acknowledgedDate using the field table and calculation rules, then run the tool.
- Read acknowledgmentDeadline, responseDays, daysLate, onTime. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| demandReceivedDate | Demand received date | string | Required |
| acknowledgmentDays | Acknowledgment window (days) | integer; minimum: 0 | Required |
| acknowledgedDate | Acknowledged date | string | Required |
Enter parseable UTC dates in chronological order and nonnegative integer acknowledgment days. Return deadline, response days, clipped late days and onTime when late days are zero. Equality passes.
deadline=received plus days; responseDays=floor((acknowledged−received)/day) Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| acknowledgmentDeadline | Acknowledgment deadline | string |
| responseDays | Response days | integer; minimum: 0 |
| daysLate | Days late | integer; minimum: 0 |
| onTime | Acknowledged on time | boolean |
{
"input": {
"demandReceivedDate": "2025-01-01",
"acknowledgmentDays": 10,
"acknowledgedDate": "2025-01-08"
},
"output": {
"acknowledgmentDeadline": "2025-01-11",
"responseDays": 7,
"daysLate": 0,
"onTime": true
}
} Limitations and assumptions
Native dates can normalize. No business-day calendar, jurisdictional legal deadline, demand service or actual acknowledgment is verified.
Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Extremely large text inputs are rejected. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors. A successfully returned false flag is an evaluated outcome; its meaning is explained above.
Alternative or Complementary methods
Use Records Request SLA: Measure a records-request response against a caller-supplied SLA. For a complementary task, use Filing Expiration: Calculate a financial-responsibility filing expiration from a supplied duration.
References
-
Demand Response Window — tool.io
Similar or alternative tools
- Records Request SLA
Measure a records-request response against a caller-supplied SLA.
- Filing Expiration
Calculate a financial-responsibility filing expiration from a supplied duration.