Use handoff summary when responsibility or conversation context transfers to another person, team, shift, agent, or system and the receiver needs concise current state, what happened, open questions, next actions, risks, and source links; use assignment for ownership selection, summary box for page key facts, and activity log for historical evidence.
Use handoff summary when responsibility or conversation context transfers to another person, team, shift, agent, or system and the receiver needs concise current state, what happened, open questions, next actions, risks, and source links; use assignment for ownership selection, summary box for page key facts, and activity log for historical evidence.
Practice the judgment: Imagine this situation: The receiver has to read a long transcript because the summary omits the actual question, outcome, and blockers. Write the person's goal, choose one of these patterns, and show the state that helps the person continue. Use the decision rules and source trail below to explain your choice.
Review the underlying principle →| Dimension | Handoff summary | Assignment | Summary box | Activity log | Comments | Notification center | Approval workflow | Review queue | Share dialog | Permission denied state |
|---|---|---|---|---|---|---|---|---|---|---|
| UI or UX | UI + UX - Concise transfer packet for responsibility, conversation, case, or task context | UI + UX - Responsibility control for assigning a work item to eligible people, teams, roles, bots, or no owner | UI + UX - Highlighted region for key information from a longer page | UI + UX - Searchable and exportable record of system, user, or administrative events | UI + UX - Object-attached comment composer and comment list with authorship, replies, state, permissions, and moderation | UI + UX - Durable user-opened notification history and action drawer | UI + UX - Routed decision workflow for requests that require authorized approval | UI + UX - Actionable queue for triaging many items that need human review | UI + UX - Object-level sharing control for recipients, link scope, roles, delivery, copy-link, native share, and access management | UI + UX - Authorization and access-boundary state |
| UI guidance | Render handoff summary as a transfer packet that names sender, receiver, transfer reason, current status, source object, generated or updated time, summary structure, next action owner, urgency, risks, and links back to transcript, ticket, log, case, or source records. | Render assignment as a responsibility field on a specific work item with current assignee, unassigned state, eligibility-filtered candidate picker, self-assign affordance, reassign and clear controls, notification outcome, and visible responsibility wording. | Render a summary box as a labelled region with a specific heading, short body, scannable key points or next steps, and only links that directly support the summarized page task. | Render activity logs as evidence-oriented records with event time, actor, action, object, source system, scope, result, and technical context such as IP address or location when available. | Render comments as anchored contributions with author identity, timestamp, body, optional attachment or selection context, edited state, reply target, and state labels such as open, resolved, hidden, deleted, or assigned. | Provide a persistent notification entry point, usually a bell or inbox control, with a count that represents new unseen notifications rather than every unread item forever. | Render approval workflow as a routed request record with requester, object, requested action, approver eligibility, required rule, current gate, due date, decision controls, comment history, and outcome consequences. | Render review queue as an actionable worklist with queue scope, counts, filters, sort order, row reason, owner, priority, age or SLA, status, preview context, selection, and row actions. | Render share dialog as an object-specific access panel that names the shared object, current access, recipient entry, link scope, role, notification and message choices, copy-link state, external-domain warnings, expiration, download controls, and revoke or manage-access actions. | Show the blocked object or action, current account, permission level, required role, owner, and request path when revealing that information is allowed. |
| UX guidance | Make the transfer trustworthy by exposing what is known, what is unresolved, what was attempted, what the receiver must do next, which facts came from source records, what is stale or generated, and which details are hidden by permission or policy. | Make assignment changes traceable and reversible enough for teamwork: explain who owns the item now, who was notified, whether the assignee can act, what changed in assigned-to-me views, and what happens to existing watchers, reviewers, collaborators, or queues. | Use summary box when users need the essential facts, eligibility notes, deadlines, documents, or next steps from a longer page before reading every detail. | Use activity log when users need to investigate, audit, verify, or troubleshoot actions across accounts, objects, systems, settings, or security boundaries. | Preserve comment drafts, anchors, authorship, notifications, edit history, deletion outcomes, and resolved or hidden states so conversation context remains trustworthy across reloads, permissions, moderation, and return visits. | Use a notification center when users receive enough asynchronous system or collaboration updates that they need a durable place to review, triage, and act later. | Make the approval route understandable over time: who has the request, what decision is needed, what happens on approval or rejection, what blocks self-review, and where the requester can revise or withdraw. | Use review queue when a team repeatedly processes a changing set of tickets, comments, pull requests, content items, cases, requests, or records that require human inspection and action. | Use share dialog when a user is granting, narrowing, distributing, or reviewing access to a concrete object such as a file, folder, document, dashboard, board, recording, report, calendar item, or media asset. | Use permission denied state when the system knows the user is authenticated but their role, group, share, license, policy, or approval status blocks a specific object or action. |
| Good UI | A support conversation handoff shows customer, issue, AI steps already attempted, account status, reason for escalation, current sentiment, open question, next action, queue, owner, and source transcript link. | An issue sidebar shows Assignee: Maya Chen, Assign to me, Change assignee, Clear, eligible teammate search, reviewer separate from assignee, and a note that the new assignee will be notified. | A benefits guide has a summary box headed Before you apply with deadline, required documents, and Start application link above the detailed eligibility rules. | An organization audit log table shows timestamp, actor, action, target object, app, IP address, result, and a Details drawer with before and after fields. | A document margin comment shows the selected paragraph, author, timestamp, body text, Reply, Resolve, Assign, and Copy link actions with the composer focused on that selection. | A bell opens a drawer with Unread and All filters, showing comment mentions, approval requests, export results, and background-job failures in newest-first order. | A production deployment request shows requester, service, environment, change summary, required reviewer group, self-review restriction, wait timer, Approve and Reject with reason controls, and a timeline of route changes. | A moderation queue has Held, Likely spam, Reported, and Escalated tabs, row evidence, policy reason, reviewer claim state, approve/remove/escalate actions, and bulk-action preview. | A report share dialog shows the report title, current viewers and editors, a recipient field, role dropdown, Notify people checkbox, message field, link set to Restricted, Copy link, and Manage access. | A report page says Quarterly revenue report requires Finance viewer access, shows the current account, names the report owner, and offers Request access and Switch account. |
| Bad UI | A generated summary omits a blocker or invents a resolution. | Automatic assignment points to a stale default owner. | A pale box repeats the entire page introduction, every related link, and several unrelated policy notes. | An export button downloads a different date range and timezone than the on-screen filtered log. | A Notes textarea sits under a record and calls itself comments even though every user overwrites the same field. | Users ignore the center because duplicate low-value messages inflate the badge. | A stale email approval applies to a request version that has changed. | The most urgent or oldest item is buried by default sort. | A dialog asks for an email address but hides whether the person gets viewer, commenter, or editor access and whether an email will be sent. | A denial page says Something went wrong and shows Retry even though the user lacks a required group. |
| Good UX | A night-shift operator accepts a case handoff, checks open tasks and contingency notes, asks one clarification question, and confirms responsibility. | A triager changes a support ticket from unassigned to Priya, adds a handoff note, sees that Priya has access and capacity warning, and the ticket appears in Priya's assigned-to-me queue. | A user scans the box, learns they need photo ID and proof of address, then continues into the detailed instructions with the same terms repeated in context. | An admin filters to failed SSO events, expands one entry, copies the event ID, exports the filtered range, and sees that records older than 180 days require a different archive. | A reviewer comments on a selected line, adds an action item for Dana, receives a reply, resolves the comment, and can reopen it from the resolved filter. | Opening the notification drawer clears the new-notification badge while unread items remain available for later triage. | A finance approval requires both manager and controller approval; the first approval advances the sequence, a rejection stops downstream processing, and the requester sees the exact rejection reason and revise action. | A reviewer claims the oldest SLA-at-risk ticket, opens a preview, assigns it to Billing, returns to the queue with the row removed, and lands on the next oldest item. | A manager adds finance@example.com as Viewer, keeps the link restricted, writes a notification note, copies the link, and sees that the file can be unshared from Manage access. | A user opens a restricted report, sees which account is signed in, requests viewer access with a reason, then sees that the request is pending with the owner. |
| Bad UX | A receiver gets an assignment notification and must read 80 chat messages to learn why the customer is blocked. | An automatic assignment silently routes every new component issue to a former maintainer and leaves the team with stale ownership. | Users treat static summary guidance as a current alert because the styling mimics alerts. | A user marks a notification read and the corresponding activity evidence disappears from the only log. | A user writes a long comment, loses network connection, and the draft disappears when the page reloads. | Users mark all notifications read and lose the only record of an export job they still need to download. | The first approver clicks Approve and the system marks the whole request approved even though policy required everyone to approve. | A reviewer marks a pull request reviewed from an old queue row after the author pushed new commits and re-requested review. | A private file becomes publicly editable because copy link implicitly changed scope. | Every workspace control is disabled after one missing permission, including safe navigation and read-only tasks. |
| Best fit | Responsibility, context, or conversation control transfers to another person, team, queue, shift, AI agent, live agent, or system. | A user must set, change, or clear who is accountable for a work item. | A longer page has a small set of key facts or next steps that users need early. | Users need to inspect recorded user, admin, system, security, or integration events. | Feedback must preserve author, timestamp, reply, resolution, assignment, or moderation context. | Users receive multiple asynchronous updates across objects, jobs, collaborators, approvals, or reminders. | A submitted request needs authorized approval before a deployment, purchase, access grant, publication, content change, policy exception, financial action, or workflow step can proceed. | A team or individual repeatedly reviews many independently queued items. | A user needs to share one object or a small set of selected objects with people, groups, domains, links, or device targets. | A signed-in user lacks permission to view, edit, publish, export, delete, approve, share, administer, or configure a resource. |
| Avoid when | The page only needs key facts for the same reader. | The user only needs to mention or notify someone in conversation. | The highlighted content is an urgent status, outage, validation result, or severe consequence. | The goal is only to show a readable milestone history for one case or process. | The user is simply entering a long answer into a form field. | The product has only occasional current-action feedback that a toast or inline status can handle. | The user only needs to check their own answers before submission. | The task is a single request moving through a governed approval route. | The task is inviting a person to become a workspace, organization, or team member rather than sharing a specific object. | The operation failed for network, server, validation, data, or timeout reasons after permission was granted. |
| Required state | Default handoff summary with sender, receiver, reason, status, and source object. | Unassigned item state. | Default summary box with heading, concise body, key points or next steps, and optional task-specific link. | Default log state with event records, result count, visible timezone, retention window, and permission scope. | Empty comment list and first-comment composer. | Closed entry-point state with zero, new-unseen, and unread-but-seen counts. | Draft or submit-ready request handoff state | Queue loading and count state | Object identity and current access summary state | Whole-object access denied state. |
| Accessibility burden | Use clear headings for situation, background, assessment, recommendation, actions, risks, source links, and receiver status. | Label the assignment field with the current assignee, item name, and responsibility meaning. | Expose the box as a labelled region or group with a heading that fits the page heading hierarchy. | Use table or structured list semantics so actor, action, object, timestamp, result, and scope are perceivable together. | Label the comments region with the object or selection being discussed. | Announce new notification arrival with status semantics when appropriate, but avoid interrupting users repeatedly for low-priority center items. | Use labelled request summary, approver, status, due date, decision, comment, and history regions. | Use labelled queue name, count, filters, sort, group, row status, selection, preview, and action controls. | Use labelled fields for recipient entry, role, link scope, notification toggle, message, expiration, password, download controls, copy-link, send, revoke, and stop-sharing actions. | Move focus to the permission message when it replaces page content or blocks a workflow. |
| Common misuse | Sending only an assignment notification and calling it a handoff. | Treating a mention as an assignment. | Repeating the whole page in a highlighted box. | Using vague activity labels that omit actor, action, object, timestamp, or result. | Using one shared Notes field as a comment system and overwriting prior contributors. | Treating the badge count, unread count, and total notification count as one number. | Treating the first approval as final when the rule requires more approvers. | Treating review queue as approval workflow and hiding many-item workload controls. | Treating native OS share as if it grants product access. | Treating authorization denial as a generic retryable error. |