Approval queue with KPIs
Pending plans listed with spend, GP ROI, below-target warning and scope.
CollMind TPM · Approval
Approval workflow: who approved what, looking at which number
Submitted plans appear in the approval queue with spend, GP ROI and status against target. Approvals and rejections are recorded with a reason and their history is never deleted. Nobody can approve a plan they submitted, and each user sees only their own customer-group and category scope.
The challenge
Approvals live in email threads
Promotion approvals are often given by email or in meetings. Later, nobody can find who approved what, when, or looking at which number, and the same person can both prepare and approve a plan.
- Approvers do not see a plan’s KPIs on one screen.
- Approval reasons and history are not recorded.
- Who can see which customers and categories is not defined.
How it works
- Step 1
Plan is submitted
The planner submits a plan that has passed the budget check.
- Step 2
It enters the queue
The plan lands in the approver’s queue with spend, GP ROI and target status; plans below target are flagged.
- Step 3
It is reviewed
The approver sees product-group detail and a KPI summary in the plan review.
- Step 4
A decision is made
Approval or rejection is recorded with a reason; in the standard template, finance approval is added when the budget is exceeded.
Key capabilities
Approve or reject with a reason
Decisions are recorded with reasons; approval history is never deleted.
Segregation of duties
Nobody can approve a plan they submitted; the rule checks the person, not the role.
Approval templates
Standard (category manager; finance on overrun) and two-level approval.
Roles
Administrator, category manager, planner, finance and read-only.
Scope
Each user’s scope is customer group × category; users without a scope see no data.
Screens
Who it is for
Category managers
Review queued plans with their KPIs and decide with a reason.
Finance
Approves plans that require a budget overrun.
System administrators
Define users, roles and scopes.
Screenshots use demo data; brand, customer and user names are illustrative. The product UI is shown in Turkish.
Roadmap
Coming next
The items below are not yet available; they are in development or planned.
- Planned
Threshold-based approval template
- Planned
Overdue reminders and approval delegation
Let’s define your approval rules together
We will show how your approval flow and permission structure are set up in CollMind TPM.