Keep business-unit requests clear across group functions.

How to build your shared-service request approvals

1. 1

   Describe the job

   Connect business-unit requests to scope review, budget decisions and delivery acceptance.

2. 2

   Review the first version

   Choose how the business-unit requester records the Business unit and how the shared-service reviewer reviews the next step.

3. 3

   Refine the views

   Ask First to adjust the fields and views for the people who will use the app.

4. 4

   Test before sharing

   Walk through the process with a sample record and check who owns the next action.

What to include in your shared-service request approvals

• Keep the Business unit in context

  Keep Business unit, requested service, scope, budget owner, reviewer, approved allocation, delivery owner and unit acceptance together so the next person can understand the request or record.

• When the next step needs a decision

  A sample unit requests a reporting workspace from a group function. Finance returns a query because the budget owner is not yet confirmed.

• Keep unit acceptance visible

  Keep the unit's acceptance separate from approval of the service allocation.

• Choose what each person needs

  Give the business-unit requester a working view and the shared-service reviewer a review view. Keep Business unit and requested service attached to the decision as the work moves between them.