Skip to content

Help documents reach the right reviewer

Users add a document, choose reviewers and send it for approval without confusion about the route. Each role sees help for its next action.

Your document platformWorkspaceAK

Documents

Today
DocumentReviewerStatus
Agreement 24Maria JonesDraft
Choose a reviewer

Your colleague can open the document and make a decision in their workspace.

Flowtomate1 / 3

The first approval

  1. 1Open your workspace
  2. 2Choose reviewer
  3. 3Send document

Documents reach approval

Authors send documents through the route

A checklist shows document addition, reviewer selection and submission for review.

Statuses show the next action

Tooltips beside statuses and buttons help authors and reviewers continue their work.

Each role understands its task

Authors prepare the route, reviewers check documents and administrators set the rules.

From the first step to a finished task

Follow the user journey: take an action and see the result in the workspace.

Your document platformWorkspaceAK

Documents

Today
DocumentReviewerStatus
Agreement 24Maria JonesDraft
Choose a reviewer

Your colleague can open the document and make a decision in their workspace.

Flowtomate1 / 3

The first approval

  1. 1Open your workspace
  2. 2Choose reviewer
  3. 3Send document

Guidance for the task

First submission for approval

Add a document, choose reviewers and send it for review.

Progress 0 / 3

Start with one route

Choose a familiar document and its path from addition to the status that confirms submission for approval.

  1. Name the result

    The author added a document, chose reviewers, submitted it and saw the current status.

  2. Add guidance

    Put the order in a checklist, explain the route with a tour and clarify roles and statuses with tooltips.

  3. Check roles

    Open author and reviewer paths in preview, then publish the rules.

Questions about document workflow onboarding

Can authors and reviewers see different instructions?

Yes. Set rules with role, page, attributes and events. Each role sees its own route.

How do we explain a document status?

Add a short tooltip beside the status. Build a short tour for several related statuses.

Do we need a developer?

If you use Google Tag Manager or Yandex Tag, you do not need a developer. A developer is needed only to install the script directly in your product’s code. Once connected, your team updates and publishes journeys on its own.

How do we introduce a new route?

Show a pop-up to the relevant role and lead users into a tour of the new route. Publish a full explanation in the changelog.

Map the first submission

Show us a document route. In the demo, we will map the path from addition to approval status.

Request a demo

Leave your details. We’ll email you to find a time for the demo.