Overview

Requests in BRM are the primary method for employees to initiate spending within the organization. This system is designed to accommodate various types of requests, each potentially requiring different levels of scrutiny. To streamline the process, requests can be customized to meet the specific needs of your organization. When initiating a request, it is mandatory to designate a champion (champ), who will serve as the primary point of contact and facilitator throughout the request process.

Types

BRM currently supports two main types of requests, both centered around tools: Renewals and Purchases.

• Purchases: This request type facilitates the creation of a new agreement or subscription for a tool.
• Renewals: This type of request is used to renew an existing agreement or subscription related to a tool.

Configuration

BRM allows for the independent configuration of each request type. This flexibility means that the information and approval process for a renewal request can differ from that of a purchase request, reflecting the distinct data and approvals each may require. The configuration for each request type involves specifying steps in the process, each centered around a criterion such as finance, legal, compliance, and IT. Each step requires the designation of a gatherer (initially the champ) and an approver, roles critical to the progression and approval of the request.

Process

The request process in BRM is designed to be both flexible and structured:

1. Initiation: Any employee can initiate a request, but they must designate a champ at the outset. The champ is responsible for gathering necessary information and moving the request through the process.
2. Gathering Information: As the gatherer for all steps, the champ is tasked with filling out any required fields and completing steps as they progress through the request.
   1. The Champ and any other member of the Request can also generate a Link, and invite the Vendor to fill in the necessary information. We highly recommend this.
3. Submission and Approval: After the gatherer submits a step, the designated approver reviews the provided information. The approver has the authority to approve and lock each field individually or approve the entire step if all fields are complete, regardless of whether the gatherer has formally submitted the step.
4. Sequential Steps: Certain steps in the request process may be contingent upon the completion of previous steps, creating a sequential flow that ensures all necessary criteria are met before proceeding.

This structured approach ensures that requests are handled efficiently and in accordance with the organization's specific requirements and standards.