A Rubric Needs Examples is easier to use when the handoff is visible: criterion → example → edge case → revision. This evergreen guide explains what to check and what to record; it does not replace a current notice, manual, code, or office instruction.

Start with the identity

Before changing a setting, filing a request, or interpreting a number, identify the exact asset, office, account, device, parcel, or notice. Similar labels can point to different processes. Write down the version, location, and date so another person can reproduce the check.

What to capture

criterion: note the observed value, the date, and the source that supports it.
example: note the observed value, the date, and the source that supports it.
edge case: note the observed value, the date, and the source that supports it.
revision: note the observed value, the date, and the source that supports it.

Field rule: separate what you observed from what you inferred. If a safety condition, deadline, eligibility rule, or equipment limit is unclear, stop and ask the responsible professional or office.

Make the handoff useful

Compare the observation with the governing source, then state the next action and its owner. Keep the original notice, screenshot, measurement, or receipt with the record. A concise trail prevents a routine exception from becoming a confident mistake.

Common shortcut to avoid

Do not rely on a remembered menu path, a generic county answer, a single app number, or an old screenshot when the current source is available. Requirements can vary by jurisdiction, equipment, account, or date.

Sources: NIST AI risk measurement resources. Educational literacy guide; current local rules, manuals, office hours, and notices control.