Know when to use Requests or Approvals

Workroomly Editorial
Begin the lesson ↓

Share this resource

Copy the link to share this page with your team.

Separate tracking your own request from reviewing a decision assigned to you.

Know when to use Requests or Approvals

Pulse has two related areas with different purposes:

  • Requests helps you follow requests you have made.
  • Approvals helps you find requests that need a decision in a review process.

Being able to see a request is not the same as being the person who should approve it.

Follow the right route

1. If you want to know where your own request stands, open Pulse → Requests. Find its exact reference and read its stage.

2. If you are responsible for a review, open Pulse → Approvals. Choose the relevant category and look for the same reference—not another request with a similar name or amount.

3. Check the current stage and your responsibility for that decision. Your organisation may set different reviewers or limits for manager review, Finance review and later processing.

4. Read the request and its supporting information before considering a decision. A request being visible does not make it ready for approval.

Understand the people involved

The requester explains the need. The reviewer or approver decides at a particular stage. The process owner resolves routing questions. A later operator may carry out the purchase, reimbursement or other work.

One person can perform several roles in a small team, but the decisions still differ. Being a workroom administrator does not automatically make you the appropriate reviewer for every business request.

If a request you should review is missing, check the category, stage and workroom, then ask the process owner to check the routing. An empty queue does not prove that everything has been approved.

Your result is a clear route: use Requests to track, and Approvals to review the decisions that belong to you.

Continue learning

In this series: Track requests and decisions — guide 3 of 6.

Turn what you learned into the way the team works.

Mark this lesson complete once the workflow exists in your workspace—not simply when you reach the bottom.