Raising an Approval Request
Raise a request when your role cannot complete the change. The confirmed example is a wallet credit.
Why the Reason Matters
The approver only sees what you write. A good reason says what should change, why, and any member context.
Good:
Member Emma Wilson was unable to attend due to a studio closure. Requesting a wallet credit of 50.
Avoid:
Please approve.
On the current list, the requester’s text appears on the card (for example a short note under the title). Vague text makes Sophie Bennett’s job harder.
Workflow — Raise a Request
Step 1 — Start the restricted action
Open the record — for a wallet credit, the member and their wallet.
Step 2 — Enter the change
Enter the amount or other details Fitnez Studio asks for.
Step 3 — Add a reason
Explain the change clearly.
Step 4 — Review
Check member, amount, and reason.
Step 5 — Choose an approver if the form asks
See Choosing Who Should Approve. Do not assume you pick a name unless the form shows that field.
Step 6 — Submit
Submit so the request is Pending.
There is no screenshot of the form used to raise a request. Button labels such as Request or Submit are not confirmed. The list shows the result: a Wallet Credits card with a reason, Requested by, date, and amount.
What the Approver Needs
They should be able to see:
- What you asked for (title such as Wallet credit of 100 for a member)
- Your reason
- Who requested it
- When
- Amount and method, such as 100 · Cash
What Happens Next?
The request should appear on Approvals → Permission Requests. Track it on Tracking Your Requests. Do not treat the wallet (or other record) as changed while status is Pending.