Revision Notice - Everyday Interface Patterns

A static revision notice shows Clarify trial terms, requested by Priya, Needs revision, and next step Update paragraph two.

Program

Revision notices should show the exact request and next step without approving, saving, sending, or notifying anyone.

approval_revision_notice.html

Visuals: captured from real browser rendering

<section class="revision-notice" aria-labelledby="revision-title">
  <h2 id="revision-title">Approval revision</h2>
  <p class="status" role="status">Needs revision</p>
  <p><strong>Request</strong> Clarify trial terms</p>
  <p><strong>Requested by</strong> Priya</p>
  <p><strong>Next step</strong> Update paragraph two</p>
  <button type="button">Review revision</button>
  <p class="note">Static revision notice only; the button does not route, save, send, approve, notify, or call a workflow service.</p>
</section>
<style>
  .revision-notice { display: grid; gap: 10px; max-width: 38rem; border: 1px solid #b45309; padding: 12px; background: #fffbeb; }
  .revision-notice p, .note { margin: 0; }
  .status { border: 1px solid #f59e0b; background: #fef3c7; padding: 8px; font-weight: 700; }
  .revision-notice button { justify-self: start; padding: 8px 12px; }
  .note { color: #475569; }
</style>

Label the revision notice.
The section is labelled by its visible heading.
Expose the revision status.
The status is exposed as status text.
Show the exact request text.
The request is exact pinned data.
Show the requester row.
The requester is exact pinned data.
Show the next step.
The next step is exact pinned data.
Check revision honesty.
Status, request, requester, next step, and no workflow service.

status surface Needs revision is visible and exposed as status text.

request text Clarify trial terms is exact pinned request text.

no notification service The lesson should not imply routing, saving, sending, approving, notifications, or workflow APIs.