This register displays four version rows for three procedures, with one explicit current version in its fictional baseline. Search and status filters expose the rows behind those counts. A separate conflict scenario demonstrates why a second current claim makes P01 unresolved rather than promoting the newer draft.
Keep a procedure and its versions distinct
The as-of date is October 13, 2026. P01 covers office-material return. Its v1 has illustrative approval A01, an October 1 effective date and designated reference L01. Its v2 is a draft with no approval. Those two rows describe one procedure and its history, not two different office procedures.
P02 v1 covers visitor-handout preparation and remains a draft, with approval and effectivity unknown. P03 v1 covers room-booking notes and is retired under illustrative record R03; its replacement is unknown. That gives three distinct IDs, four version rows and one explicit current version. L01 is a fictional reference label, not a working controlled-file link.
Make the lookup answer the operational question
Search P01 and inspect the version, status, approval, effective date and controlled reference together. Version sorting can help find changes, but a higher number supplies none of the missing authority. Do not attach A01 to v2 simply because both rows share a procedure ID.
Before using a real reference, confirm that its scope fits the task, the exact version has the required authorization, the date applies and the actual linked file matches the designation. The preview cannot check a file it has not been given. Keep real owners, URLs and verification notes in the controlled register. EPA's April 2007 SOP guidance describes a master list of SOPs; it supplies indexing concepts, not a current legal retention rule for this office.
Give unresolved procedures a useful next action
Filter to the gaps and keep P02 and P03 visible. P02 needs an authorized instruction or a confirmed approval route. Promoting its draft would conceal the gap. P03 needs a replacement reference or another confirmed operational route; retirement alone does not tell you what instruction applies today.
Record the question, responsible owner once confirmed, response reference and resulting decision. Leave actual owner names and decisions blank until supplied. Preserve retired history under the team's arrangements instead of deleting it to clean up the screen. A filtered view is a reading aid, not an instruction to archive or withdraw a document.
Reconcile conflicting current claims
Use the conflict button to add a contradictory claim that P01 v2 is current without authorization or effectivity evidence. The visible finding changes to reconciliation required. The baseline's one explicit current designation no longer settles a unique applicable version for P01 while the contradiction remains.
Keep both claims available for review. Ask the responsible authority which version and scope apply, and record the decision rather than resolving it by version number. Reset returns to the supplied baseline; it does not amend an actual register. Likewise, a proposed review date is a plan. A completed review needs a real reviewer, date, referenced version, findings and decision.
Copy this prompt
Create a complete original HTML example in US English for this task: SOP register template. Return one self-contained HTML file. Include all styles, data and JavaScript in the file. Use no remote dependencies. Return the working page, not an outline.
As of 2026-10-13: P01 Office-material return v1 Current, approval A01 effective 2026-10-01 reference L01; P01 v2 Draft approval absent. P02 Visitor-handout preparation v1 Draft authorization/effectivity unknown. P03 Room-booking notes v1 Retired under R03, replacement unknown. Four rows, three procedure IDs, one explicit current baseline. L01 is not an actual link.
Display a searchable version ledger and buttons for all, current, gaps and retired views. Show visible version-row and distinct-procedure counts separately. Search must match IDs and titles without changing source rows. Include owner follow-up questions for P02 and P03. A clearly labeled conflict scenario adds a contradictory current claim for P01 v2 without authority; show reconciliation required instead of selecting the highest version. Keep original rows and history intact. Reset removes the scenario and filters. Empty search results need an explicit zero-row state. No approvals, notices, file deletion or persistence.
Use a page design suited to this particular task, readable text at least 16 px, generous spacing, visible keyboard focus and explicit labels. At 360 px, stack the content without page-level horizontal scrolling. Use type="button" click handlers for actions. Keep source facts and sample results distinct from actual observations. Leave unknown details visible rather than inventing them. Controls update only this temporary page; distinguish local changes from actual records. Provide concise task-specific feedback and a reset that clears entered answers and stale results.
Use the result
Use the gap list to prepare the owner discussion, starting with P02’s missing authority and P03’s unknown replacement. A prepared register view in NOS can put those questions beside the version history. Bring the owner’s actual answers into the controlled index and verify the referenced files before directing anyone to the current instruction.