Home>Case Studies>Digitising gate pass and material movement across two plants
ManufacturingOperationsWorkflow Automation

Gate passes that no longerlive in a paper register.

How a heavy electrical manufacturer replaced paper gate pass registers and physical signature chains with a digital challan system - configurable approval hierarchies, automated return tracking for returnable items, and an audit trail covering every movement in and out of two plants.

A gate pass moving through approvals and out through a gate, with a dashed return path
ClientTBEA and GE
IndustryHeavy electrical & engineering
FunctionStores, security & operations
ScopeReturnable and non-returnable movement
EngagementBuild and deploy
01

The situation

Material moves in and out of a plant constantly - tools going out for repair, dies going to a vendor, scrap leaving for disposal, equipment coming back from calibration. Every movement needs a gate pass, and every gate pass needs approvals before security will let anything through.

All of it ran on paper. A challan was written into a register, walked between departments for signatures, and filed. Nobody could say from a desk which passes were pending, whose signature was holding one up, or which returnable items were overdue back. Returns were reconciled by reading back through the register, and when an audit asked for the movement history of a particular item, someone went and found the books.

Nobody could say from a desk which passes were pending, or which returnable items were overdue back.

02

What we built

We built a web application carrying the full gate pass lifecycle - creation, approval, gate exit, and closure - for both returnable and non-returnable movement. A requester raises a challan against a material type and a destination; the system numbers it automatically and routes it through an approval hierarchy configured by role and department rather than hard-coded, so a change in the org chart does not need a change in the software.

Each stage sends an email, so nothing waits on someone noticing. Returnable passes carry an expected return date and raise alerts once it passes - the part a paper register could never do. Everything is searchable by date, department, requester, or material type, and any view exports to Excel or PDF for audit. Where master data already lives in the ERP, the application synchronises with it rather than keeping a second copy that can drift.

Inside the system

The parts that carry a challan from request to closure.

Raising and approving

  • Returnable and non-returnable challans in one register
  • Automatic numbering and document control per gate pass
  • Approval hierarchy configured by role and department
  • Email notification at every approval and completion stage
  • Multi-level access for requesters, approvers, and administrators

Tracking and reporting

  • Return tracking against expected dates, with overdue alerts
  • Dashboards and MIS for open, pending, and completed challans
  • Search and filter by date, department, requester, or material type
  • Export to Excel or PDF for audit and review
  • Secure login, user-based permissions, and audit logs

What it looks like

Two screens from the system: the challan register, and the approval trail behind a single gate pass.

The record challan register, listing gate passes with type, vendor, and quantities
The register - every challan with its type, counterparty, and despatched against received quantity. Names and vendors shown here are dummy data.
A single gate pass with its workflow history, showing each approval stage and timestamp
One gate pass, with the workflow history underneath it: each approval position, who acted, and when. This is what replaced the signature chain.
03

What changed

Outcomes as reported by the client. We have not attached percentages to them, because the ones worth quoting are the ones the client measured themselves.

01

The register became something anyone could query

Open, pending, and completed challans are visible from a dashboard rather than reconstructed from a book. A requester can see where their pass has reached, and an approver can see what is waiting on them.

02

Returnable items stopped going quiet

Every returnable pass carries an expected return date and raises an alert once it passes. Overdue material surfaces on its own rather than being noticed at stock-take.

03

Audit evidence is retrieved, not reassembled

The movement history of any item, with its approvals and timestamps, is a search rather than a hunt through registers. The client reports both manual errors and approval turnaround came down.

04

How it was built

Deployed on the client’s own infrastructure, synchronising master data with the ERP already in use.

Backend.NET MVC
DatabaseMicrosoft SQL Server
Front endHTML5, CSS3, jQuery
InterfaceResponsive, role-based UI

What still moves through your plant on paper?

Gate passes, material requisitions, work permits, tool issue - the same shape of problem wherever a physical movement needs a signature before it can happen. Tell us how yours works today and we will tell you honestly what it would take to change.