Filter three fictional agreements to see which records need attention as of October 14, 2026. Unknown Action Date returns C02, Past Recorded Action Date returns C03, and Awaiting Completion Evidence returns all three. A separate C01 version-change scenario invalidates its old date confirmations instead of carrying them into v2.
Keep two dates and one evidence trail
A recorded term end and a recorded action date answer different questions. The term end is the source-confirmed date in the register. The action date is separately supplied and confirmed by the responsible record owner; it is not automatically calculated backward from the term end.
The University of Arkansas supplier-contract guidance emphasizes monitoring contract records, confirming dates, and seeking assistance for unclear language. Its Workday routing and notice examples apply to that institution; confirm your own organization's process when reviewing a real agreement.
To adapt this review, prepare a separate contract list with one row per agreement ID and reviewed version. These fields help you collect the evidence behind each date; the HTML example itself remains read-only:
| Field group | Columns |
|---|---|
| Identity and source | Agreement ID, vendor, version, source-file pointer, recorded signature status |
| Date confirmation | Confirmed term end, confirmed action date or UNKNOWN, confirmation reference, confirmed by, confirmation date |
| Responsibility and review | Record owner, supplied action description, review state, unresolved question |
| Action evidence | Completion-evidence reference, evidence review state, reviewer, reviewed date |
| Comparison | Fixed as-of date, term-date comparison, action-date comparison |
Leave actual approvers, signoffs, and completion references blank until the appropriate records exist. A name in an owner column is not an approval, and a reminder is not completion evidence.
Inspect the fictional register at a fixed date
The dashboard uses a fixed as-of date of October 14, 2026. The page has no control for changing it.
| ID | Source version / recorded signature state | Confirmed term end | Separately confirmed action date | Action evidence |
|---|---|---|---|---|
| C01 | v1 / signed | 2026-12-31 | 2026-11-15 | No completion reference supplied |
| C02 | v2 / signed | 2027-01-31 | UNKNOWN; interpretation pending | No completion reference supplied |
| C03 | v3 / signature state not supplied | 2026-10-01 | 2026-09-15 | No completion reference supplied |
The dates marked confirmed are supplied fictional records, not dates extracted or interpreted by the dashboard. For real agreements, locate the relevant source version and the owner's confirmation before relying on a date. When adapting the template, fill the real confirmation-by/date fields from evidence rather than treating these example statuses as actual approvals.
C01's recorded dates are future relative to the fixed as-of date; its review is still pending. C02 has a known term end and an unknown action date. Preserve UNKNOWN instead of subtracting a default notice period. C03 has both a past recorded action date and a past recorded term end, but its legal status remains unknown. Neither “terminated” nor “renewed” follows from the date comparison alone.
Define every summary count
For this three-row register:
| Summary measure | Count | Meaning |
|---|---|---|
| Agreement records | 3 | Unique supplied IDs |
| Source-confirmed term dates | 3 | Confirmed for the displayed source versions |
| Unknown action dates | 1 | C02 |
| Recorded action dates before as-of | 1 | C03 |
| Actions supported as complete by reviewed evidence | 0 | No completion references supplied |
The final zero means the register supports no completed-action claim. It does not prove that nobody acted. A missing record needs evidence review, not an invented outcome.
Use date-only calendar comparison: earlier than as-of is past, equal is on the as-of date, and later is future. UNKNOWN is a separate state and never counts as a future date. Missing term dates, if added later, also need their own unresolved count rather than a healthy-looking blank.
Inspect a new source version
Choose Load C01 v2 to create the separate version-change scenario. C01's old confirmed dates move to historical context and its current confirmations become pending. The summary becomes two confirmed term dates and one pending, rather than three confirmed. Restore baseline returns the original supplied records.
Filters change the visible rows and their count without sending notices or editing agreements. Keep the displayed source version attached to every date, then resolve real questions in the maintained Excel or CSV register and authorized review process.
Copy a prompt for this example
Build a single self-contained HTML contract review dashboard with embedded CSS and JavaScript. Use a document-review layout with summary counts, filter buttons, an agreement-ID search field, and readable record cards. Stack the content on narrow screens.
Use a fixed as-of date of October 14, 2026. Supply three fictional records. C01 is signed version 1, with term end December 31, 2026 and action date November 15, 2026. C02 is signed version 2, with term end January 31, 2027 and an unknown action date awaiting interpretation. C03 is version 3, with signature status not supplied, term end October 1, 2026 and action date September 15, 2026. None has completion evidence.
Initially show three agreements, three confirmed term dates, one unknown action date, one past action date, and zero evidence-supported completed actions. Provide All, Unknown Action Date, Past Recorded Action Date, and Awaiting Completion Evidence filters. They return three, one, one, and three records respectively before ID search. Explain an empty search result.
Add a Load C01 v2 button that retains version 1 dates as history while making current C01 date confirmations pending. The term summary then shows two confirmed and one pending. Restore baseline resets the scenario and filters.
Keep unknown dates distinct from future dates. Date comparisons do not establish renewal or termination. Keep signature status, source version, and missing evidence visible. Return only the complete HTML file.
Before reviewing the unknown-date queue, NOS can display this prepared HTML register. Choose Unknown Action Date to isolate C02, keep its action date UNKNOWN, and request the actual source clarification before updating the maintained register.