Cancellation Flow

Cancel a subscription with clear impact on billing, saved data, members, credits, and the exact date access changes. This example brings Reason and Impact together so account administrators can find the next task without losing context.

It includes representative records such as Tell us why and Review workspace impact. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Cancellation Flow
Use this template in Figr

Template facts

Screen

Form

Primary action

Cancel plan

Pattern

Form

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Finance and operations teams need to cancel plan while keeping renewal, members and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Reason gives users an obvious place to start.
  • Supporting view: Impact keeps the related context close.
  • Primary action: Cancel plan stays visible when people need it.
  • First signal: Renewal shows a useful value (Sep 30).
  • Second signal: Members gives additional context (21).
  • Sample record: Tell us why.
  • Next record: Review workspace impact.

States worth designing

  • Required field missing: say what changed, protect progress, and offer a clear next step.
  • Invalid value or incompatible data: say what changed, protect progress, and offer a clear next step.
  • Draft saved: say what changed, protect progress, and offer a clear next step.
  • Submitted for review: say what changed, protect progress, and offer a clear next step.
  • No permission to submit: say what changed, protect progress, and offer a clear next step.
  • Temporary save failure: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Reason → Impact → Cancel plan → Review outcome

Patterns used

Form, Reason, Impact, contextual actions, error recovery

Why these choices work

Show requirements beside fields and retain values after failed checks. Validate only the affected input and make the next step unmistakable.

Pay attention to reason and impact. People need to distinguish Tell us why from Review workspace impact. Keep renewal visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Cancel plan”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Payment Failure Recovery, Invoice Detail, Trial Expiry.

Start from this in Figr

Design a cancellation flow screen inside our existing product. Use our current components, tokens and content language. Include Reason and Impact views, credible records like Tell us why, and a clear “Cancel plan” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr