# Policy value record

The `PolicyValueRecord` family — 5 operations.

A policy value is one dated window in your policy schedule — a setting from the platform’s fixed list (the appointment lead time, the maximum days ahead a booking may be made, the no-show window, the overbooking switch, and the fraud-alert thresholds, one per signal) given a whole-number value inside the setting’s bounds, from a start instant to an end (always present; far in the future means the standing value). Each window is anchored to exactly one organization or one store or warehouse: at a place, the store’s window wins over the organization’s, and the built-in default stands wherever no window covers. The start defaults to now and is never in the past, so the schedule is always an honest history of which value applied when; a window that starts inside the previous one trims that predecessor, and one that overlaps any other window refuses, naming the blockers. The setting, value and window are fixed once written — supersede with a new window; only a window that has not yet taken effect can be cancelled. The caption is the one thing you can edit.

## Operations

| Operation | Kind | What it does |
| --- | --- | --- |
| [createPolicyValueRecord](/reference/policy-value-record/createPolicyValueRecord/) | mutation | Schedule a policy value for an organization or a location — e.g. a fraud-alert threshold. |
| [doomPolicyValueRecord](/reference/policy-value-record/doomPolicyValueRecord/) | mutation | Cancel a policy value window that has not started yet. |
| [policyValue](/reference/policy-value-record/policyValue/) | query | One scheduled policy value — the key, the value, where it applies, and when. |
| [policyValues](/reference/policy-value-record/policyValues/) | query | Your group’s policy schedule, page by page — every value window ever set, kept forever. |
| [updatePolicyValueRecord](/reference/policy-value-record/updatePolicyValueRecord/) | mutation | Rename a policy value window. |