1. Purpose and users
Approval and Control provides maker-checker oversight across the ERP. It is used by approvers, senior approvers, managers, control teams, and auditors.
The purpose is to stop sensitive work from moving forward without review. Instead of one user creating and approving the same important action, the system can route the record into an approval queue for a decision.
2. Approval queue
The approval queue lists pending items that require action. Approvers review the linked record, understand the request, and approve or reject with comments. The action history remains attached to the approval.
This queue can include operational, finance, workshop, procurement, stock, trip, and nomination decisions depending on the permissions and workflows enabled.
3. Trip approvals
Trips can be submitted for approval before dispatch. The system checks readiness before submission, including customer, route, revenue, and compliance of assigned resources.
Once submitted, the trip waits for an approval decision. Approval allows the trip to continue toward assignment and dispatch. Rejection sends the trip back for correction.
4. Truck nomination approvals
Truck nominations can require approval before they become executable. The nomination must pass capacity and availability checks before it can be submitted.
Approval confirms that the nominated truck, trailer, driver, depot, and customer request are acceptable. Only approved nominations can be converted into trips.
5. Workshop and stock control approvals
Workshop estimates, requisitions, stock adjustments, and other control-sensitive records can use approval gates. This protects cost, inventory, and release decisions.
For example, a workshop estimate may need approval before parts are reserved or work begins. A stock adjustment may require review before inventory quantity is changed.
6. Approver roles and escalation
The system includes Approver and Senior Approver roles. Normal approvers handle standard decisions, while senior approvers can be used for higher-value or escalated control actions.
Role-based permissions determine who can see the approval queue, who can process approvals, and which modules the person can influence.
7. Audit and accountability
Every approval action preserves actor, action, time, comments, and linked record context. This makes the approval process reviewable by managers and auditors.
Users should treat approval comments as business evidence. A clear comment explains why the action was approved or rejected, especially when the decision affects cost, dispatch, safety, or compliance.
8. Daily use
In daily use, users create or submit controlled records, the system routes them to approval, approvers review and decide, the original module updates status, and audit history preserves the decision.
Approval and Control does not replace the live module. It sits across modules as a decision layer, ensuring critical actions are checked before they affect operations.