A · Redundant approvals
A company purchases standard supplies within an approved budget. The same routine request passes several people even though some approvals add neither new authority nor a distinct control.
Before · 7
- Employee submits a request
- Re-enter details in another form
- Manager reviews the routine request
- Assistant forwards the request
- Coordinator repeats the approval
- Authorized person checks the budget
- Purchasing places the order
After review · 3
- Submit the request
- Check budget and authorization
- Place the purchase order
Budget and authorization checks stay. Requests beyond delegated limits and exceptional purchases still require approval.
Duplicate entry, two formal sign-offs, and the purely administrative handoff are removed in this policy setting. If a request exceeds delegated limits or is exceptional, the relevant approval stays in place.
B · Duplicate records
A customer request is entered in CRM and then copied into Excel, a departmental spreadsheet, and a separate email summary. Employees reconcile versions even though the main CRM record already exists.
Before · 6
- Receive a customer request
- Create or update the CRM record
- Enter the same details in Excel
- Copy into a departmental sheet
- Email a separate summary
- Process the request
After review · 3
- Receive a customer request
- Maintain one shared CRM record
- Process the request from the record
The shared CRM record and authorized access stay. Required archival copies are assessed separately.
The primary record remains available. Copies required by law, archival policy, or offline continuity are not removed without assessing their purpose.
C · An unused report
Every week an employee builds a status spreadsheet from ERP data. Managers already use live ERP information, and the emailed report is not used for any decision or mandatory obligation.
Before · 5
- Export ERP status information
- Copy the data to Excel
- Reformat the sheet
- Email the report
- Archive another report copy
After review · 0
0 unused reporting stepsThis sub-process is discontinued. ERP data and required reporting stay.
Only the unused reporting sub-process is discontinued. ERP data, operational records and required reporting stay.
The review confirms that this report has no consumer or separate compliance purpose. The entire reporting sub-process is discontinued. Core ERP records and required reporting remain unchanged.