Confirmation dialogs
Confirmation dialogs ask the user to commit to a consequential action. The copy must make the consequence unmistakable — without being so alarming that users second-guess routine tasks.
The four rules
1. Title names the action exactly
The dialog title should be a short, specific statement of what is about to happen — not a question, not a vague label. Use the same verb that appears in the action button.
Do
”Delete consultation"
"Remove stakeholder"
"Revoke access"
"Archive project”
Don’t
”Are you sure?"
"Confirm action"
"Delete?"
"Warning”
2. Body describes the consequence fully
The body text must tell the user exactly what will be lost, changed, or affected. Be specific. Name the item. If the action affects other things (related data, dependent records), say so.
Do
”Deleting Northern Rail Corridor Consultation will permanently remove all responses, reports, and activity history. This cannot be undone.”
Don’t
”This consultation will be deleted. Are you sure you want to do this?“
3. Primary action repeats the action verb
The confirm button must use the same verb as the title. Never use “OK”, “Yes”, “Confirm”, or “Proceed”. The label should make the button self-explanatory — the user should be able to read just the button and know what happens.
Do
Title: “Delete consultation” → Button: “Delete consultation”
Title: “Revoke access” → Button: “Revoke access”
Title: “Archive project” → Button: “Archive project”
Don’t
Title: “Delete consultation” → Button: “OK”
Title: “Revoke access” → Button: “Yes, revoke”
Title: “Archive project” → Button: “Confirm”
4. Cancel is always “Cancel”
The secondary action is always labelled “Cancel”. Never “No”, “Go back”, “Keep”, or any other variation. “Cancel” is the standard label users expect — deviating from it creates friction and confusion.
Full examples by action type
Delete consultation (Open Point)
Delete consultation
Deleting Northern Rail Corridor Consultation will permanently remove all responses, reports, and activity history. This cannot be undone.
Remove stakeholder (Open Point)
Remove stakeholder
Removing Sarah Chen will revoke their access to this project and remove them from all consultation distribution lists. You can add them back at any time.
Revoke access (Open Point)
Revoke access
Revoking access for Marcus Oliveira will immediately sign them out of all sessions and remove their ability to view or edit this project. They will not be notified.
Archive project (Open Point)
Archive project
Archiving Waterfront Precinct Plan 2025 will move it out of your active projects. All data and reports will be preserved. You can unarchive it at any time from Project Settings.
Truly irreversible actions: type to confirm
For actions that cannot be undone and have significant scope — deleting an entire account, permanently purging exported data, transferring ownership — add a type-to-confirm step. This forces a deliberate action and dramatically reduces accidental deletion.
The pattern
- Ask the user to type a specific string — the project name, the word “delete”, or similar
- The confirm button stays disabled until the input matches exactly
- The instruction text tells the user exactly what to type: “Type Northern Rail Corridor to confirm.”
- Don’t use this pattern for routine deletions — it creates friction that erodes trust if overused
Do — instruction text
”To permanently delete this project and all its data, type the project name below:“
Northern Rail Corridor
[text input]
Don’t — vague instruction
”Please confirm you want to delete this by typing ‘yes’ below:“
[text input]
“Yes” doesn’t identify what the user is deleting and can be typed carelessly.
Tone guidance by severity
- Reversible actions (archive, unpublish, remove from list): matter-of-fact body copy, note that it can be undone. No need for alarming language.
- Irreversible actions (delete, purge, permanently remove): state “This cannot be undone” or “This is permanent” clearly — not as a disclaimer at the end, but as part of the consequence description.
- Actions affecting others (revoke access, remove from project): say who is affected and what they will experience (e.g. “They will be signed out immediately”).
Was this page helpful?