A request may begin by email, be chased by message, discussed by phone and finally recorded in a spreadsheet. Work appears to move forward, but nobody can see the whole process.
In this project, applications and approvals between departments relied on documents and fragmented communication. Finding out who held a request, why it was returned or when it was approved took time.
The problem was not a missing form
Receiving a request through a digital form is a starting point, not a complete process. The team needed answers to practical questions:
- Who may submit this request?
- Which department reviews it first?
- Where does it go if information is missing?
- When is higher-level approval required?
- How will decisions and explanations be retained?
Without these rules, a form simply creates another inbox.
The system decision
We built a role-based portal that kept submission, review, return and approval on the same record. A user saw only the requests and actions allowed by their role. Each action recorded its owner, date, status and explanation.
When a request moved to another department, the information was not copied into a new record. Its history stayed together.
Why permissions are part of the workflow
Not everyone in an organization should see or change everything. Hiding menu items alone is insufficient. The permission model governs who may open, review or view a record, who may approve it, and which fields a department may change. We therefore designed roles before screens.
Operational result
The request’s status, owner and history became visible in one place. “Who has it now?” could be answered in the portal instead of through phone calls. The system was handed over to the internal team and remains in use.
The client and internal request details are withheld. The evidence for this account is the recorded workflow, role structure, handover and active use; it does not claim an unmeasured time-saving percentage.
Where this structure may apply
- Purchasing requests
- Technical support and maintenance
- Internal service applications
- Document and content approvals
- Dealer or supplier applications
- Reviews involving several departments
Engin Sistem does not impose a generic approval template. We map the real decision chain, exceptions and responsibilities, then turn it into a process people can follow while the organization keeps control.
Common questions
Is a request portal only for large organizations? No. It can help a medium-sized business when several roles, approval stages and reliable records are needed. Workflow complexity matters more than company size.
Does every request follow the same approval order? No. Different paths can depend on request type, value, department or other rules. The necessary exceptions should be clarified first.
Can email notifications be used? Yes, for new tasks, returns, delays or approvals. The authoritative record remains in the portal, not in email.