What does the jurisdiction-specific request clock produce?
Calculate dates from confirmed rules, events, extensions and pauses. Keep the supplied facts, method, result and unresolved items visible for responsible review.
The working area above runs the supported calculator in the browser. It keeps the result inspectable and preserves every unresolved item for responsible review.
What do you need before you start?
- A named owner has defined the task and the organization’s intended use.
- The customer has authority to use every supplied record, source or connection.
- Prepare the result in this browser and resolve visible input errors before exporting.
What information do you enter?
Prepare only the bounded inputs listed below for this calculator.
- Approved rule or contract reference (required). Name the jurisdiction, source, provision and confirmed trigger. This tool does not select a legal rule.
- Rule or contract version (required). Record the version or effective date checked by the responsible person.
- Starting date (required). For calendar days, the trigger date is day zero. For hours, match the date in the exact trigger timestamp.
- Approved period (required). Enter the whole number of days or elapsed hours in the confirmed rule.
- Period unit (required). Calendar days include weekends. Hours require an exact timestamp and count elapsed time.
- Count direction (optional). Choose before for a notice period preceding renewal. Extensions and pauses apply only when counting after the trigger.
- Exact trigger timestamp for hours (optional). Required for hours. Use YYYY-MM-DDTHH:mm:ss followed by Z or a confirmed offset such as -04:00.
- Approved extension (optional). Optional. Enter an approved extension in the selected unit. Blank means zero.
- Approved paused duration (optional). Optional. Enter confirmed non-overlapping paused duration in the selected unit. Blank means zero.
| Field | What to enter | Fictional example |
|---|---|---|
| Approved rule or contract referenceRequired | Name the jurisdiction, source, provision and confirmed trigger. This tool does not select a legal rule. | Fictional approved rule, section 4 |
| Rule or contract versionRequired | Record the version or effective date checked by the responsible person. | Fictional version 2026-09-22 |
| Starting dateRequired | For calendar days, the trigger date is day zero. For hours, match the date in the exact trigger timestamp. | 2026-09-22 |
| Approved periodRequired | Enter the whole number of days or elapsed hours in the confirmed rule.Accepted range 0 to 36500. | 30 |
| Period unitRequired | Calendar days include weekends. Hours require an exact timestamp and count elapsed time.Choose from Calendar days, Hours. | Calendar days |
| Count directionOptional | Choose before for a notice period preceding renewal. Extensions and pauses apply only when counting after the trigger.Choose from After trigger, Before trigger. | After trigger |
| Exact trigger timestamp for hoursOptional | Required for hours. Use YYYY-MM-DDTHH:mm:ss followed by Z or a confirmed offset such as -04:00. | 2026-09-22T09:00:00-04:00 |
| Approved extensionOptional | Optional. Enter an approved extension in the selected unit. Blank means zero.Accepted range 0 to 36500. | 0 |
| Approved paused durationOptional | Optional. Enter confirmed non-overlapping paused duration in the selected unit. Blank means zero.Accepted range 0 to 36500. | 0 |
Download fictional calculation sample (PDF). Requires tailoring and responsible review.
What you can download
Every result must identify its supplied facts, assumptions and unresolved items.
| Free result | Included downloads |
|---|---|
Enter your information, inspect the on-screen result and keep a browser backup. Editing and direct copies of your entered information stay free. |
These supported outputs are free. No checkout is required. |
How does the jurisdiction-specific request clock work?
- 1Define the scope
Choose the exact jurisdiction-specific request clock task, responsible owner and intended use.
- 2Add supported inputs
Provide only the information listed for the calculator. Unsupported material must remain unresolved.
- 3Inspect the result
Review the result, assumptions, source basis and exceptions before relying on any output.
- 4Approve or export
A responsible person decides whether the record is complete enough for the organization’s next step.
Method and sources
Apply the steps above to the supported inputs. Use the listed source sections to review the rule basis, assumptions and limits.
- California Consumer Privacy Act regulationsThe California rules and official materials that must be checked before using a state privacy workflow. Current CCPA regulations and rulemaking records.California Privacy Protection Agency. Reviewed 2026-09-24.
- Privacy FrameworkA voluntary method for identifying and managing privacy risk. Core, Profiles and Implementation Tiers.National Institute of Standards and Technology. Published 2020-01-16. Reviewed 2026-09-24.
- California Consumer Privacy Act FAQsOfficial regulator explanations for California privacy rights operations. Consumer rights, business responsibilities and enforcement.California Privacy Protection Agency. Reviewed 2026-09-24.
- Common Format and MIME Type for Comma-Separated Values FilesThe primary published CSV format reference. CSV records, fields, escaping and MIME type.RFC Editor. Published 2005-10-01. Reviewed 2026-09-24.
- Data Integrity: Identifying and Protecting Assets Against Ransomware and Other Destructive EventsA reference architecture for data integrity and evidence controls. Asset identification, integrity protection and recoverability.National Cybersecurity Center of Excellence. Published 2020-12-01. Reviewed 2026-09-24.
Common questions
What information does the jurisdiction-specific request clock need?
Enter approved rule or contract reference (required). Name the jurisdiction, source, provision and confirmed trigger. This tool does not select a legal rule; rule or contract version (required). Record the version or effective date checked by the responsible person; starting date (required). For calendar days, the trigger date is day zero. For hours, match the date in the exact trigger timestamp; approved period (required). Enter the whole number of days or elapsed hours in the confirmed rule; period unit (required). Calendar days include weekends. Hours require an exact timestamp and count elapsed time. A named owner has defined the task and the organization’s intended use.
What does the jurisdiction-specific request clock produce?
A complete on-screen calculator result. A versioned JSON working record that can be downloaded and restored. Visible unresolved items and decision boundaries for responsible review. Review unresolved findings and limitations before use.
Who makes the final decision?
A responsible person reviews the result. Confirm inputs and rules. Review exceptions and approve consequential actions.
Is this tool free?
Yes. The on-screen result and listed downloads are free. No checkout is required. Keep local backups and review the stated method and limits.
Can I use the jurisdiction-specific request clock for this task?
Calculate dates from confirmed rules, events, extensions and pauses. Confirm inputs and rules. Review exceptions and approve consequential actions.
What still needs review?
Confirm inputs and rules. Review exceptions and approve consequential actions.
This browser workspace does not provide legal advice, certify compliance, make a filing or authenticate a customer decision.
Unsupported cases must stop or remain visibly unresolved.