A digital gate pass system for manufacturing replaces paper gate registers with a controlled electronic record for everything crossing the boundary people, vehicles, materials, tools and scrap. It routes each movement to the right approver, timestamps entry and exit at every gate, and tracks returnable items until they are physically closed.
It is 2:10am at Gate 4. A tempo is waiting. The driver has a gate pass signed by a maintenance engineer who went home at six. It says "1 no. hydraulic pump returnable." The guard on duty has never seen the pump, has no way to check whether it is the plant's pump or a vendor's, and has eleven trucks behind him.
He lets it go. He is not being careless. He has no better option.
That pump will be discovered missing during the next physical verification, about seven months from now, by which point nobody will remember the tempo, the engineer will have changed roles, and the gate register page will be water-damaged.
This is the real problem a gate pass system solves and it is almost never a visitor problem.
A factory gate pass is not one document it is seven
Most content on this topic quietly assumes "gate pass" means "visitor pass." In a working plant it means at least seven different things, each with its own requester, approver and failure mode.
- Visitor pass guest, auditor, customer. Approved by the host. Lowest value, most attention.
- Contractor / labour pass a contract worker entering for a shift, conditional on induction and document validity.
- Vehicle pass truck, tempo, tanker, forklift or staff two-wheeler.
- Material inward pass goods arriving against a PO, challan or return.
- Material outward non-returnable (NRGP) finished goods, samples, sold scrap. Anything leaving permanently.
- Material outward returnable (RGP) items out for repair, calibration, job work, demo or temporary loan. The one that leaks.
- Scrap and tool/asset passes usually lumped in with the above, and usually where the value actually walks out.
Get the taxonomy wrong and you build a system that handles five per cent of your gate traffic beautifully.
The pass-type comparison table
This is the table to take into your requirements meeting. Adapt the approver column to your own delegation of authority the point is that it should be different per row, not one signature for everything.
| Pass type | Who requests | Who typically approves | What must be recorded | Common failure |
|---|---|---|---|---|
| Visitor pass | Host / employee | Host, or host's manager for restricted areas | Name, ID reference, photo, host, purpose, in/out time, area permitted | Exit never marked; visitor "still inside" for three days |
| Contractor / labour pass | Contractor supervisor | Contract cell or EHS, subject to induction validity | Worker identity, contractor, induction status, ID, shift, gate used | Supervisor vouches verbally for faces the guard has not seen |
| Vehicle pass | Transporter, logistics or employee | Logistics for freight, admin for staff vehicles | Vehicle number, driver name and licence reference, transporter, purpose, in/out time, gate | Driver entered but vehicle never logged out; yard count wrong |
| Material inward | Supplier / transporter | Stores on verification | Challan or invoice reference, PO reference, item and quantity, vehicle, weight if applicable, receiving gate | Quantity recorded from the challan, not from what was actually counted |
| Material outward NRGP | Dispatch, stores or user department | Stores head plus plant head or finance, per value slab | Item, quantity, value, reason, buyer or consignee, vehicle, tax document reference, gate | Approved on value below slab by splitting one movement into three passes |
| Material outward RGP | User department (maintenance, QA, projects) | Department head plus stores, with an expected return date | Item, serial or asset number, quantity, vendor, reason, expected return date, condition and photo at exit | No return date, so the pass can never be overdue and never gets closed |
| Scrap removal | Stores or production | Stores head plus finance or plant head; contract-linked | Scrap type, weight in and out, vehicle, weighbridge slips, contractor, auction or contract reference | Tare weight taken casually; loaded weight never independently checked |
| Tool / asset movement | Maintenance, IT, projects | Asset owner plus stores | Asset tag, serial number, custodian, destination, expected return, condition photo | Treated as "internal", never passed through the gate record at all |
Two things this table makes obvious. First, a single approval workflow cannot serve all eight rows if your system only supports one approval chain, you will end up either over-approving visitors or under-approving scrap. Second, only two rows need an expected return date, and those are exactly the two rows that go missing.
Returnable vs non-returnable gate pass and why returnable items disappear
A non-returnable gate pass (NRGP) covers material leaving permanently: dispatch, sale, disposal. A returnable gate pass (RGP) covers material expected back: repair, calibration, job work, demo, temporary loan. It sounds administrative. It is the difference between a tracked movement and an untracked one.
Why returnable items go missing, in rough order of frequency:
- No expected return date. Nothing can be overdue. An RGP without a return date is an NRGP with better manners.
- Nobody owns closure. Security saw the exit. Stores never saw the item. The sending department considers the job done when the vendor collects.
- Partial returns go unrecorded. Five out, three back, pass marked "returned".
- The item comes back different. A pump returns with a replaced casing and a new serial. Nobody reconciles serial to serial, so the asset register quietly diverges from reality.
- It returns through a different gate. Out from Gate 2, back at Gate 1, three weeks later, on nights. Gate 1 has no memory of the original pass.
- The pass ages out of sight. An RGP from March sits fifty pages behind where anyone is looking in June.
A digital system fixes 1, 5 and 6 almost automatically, because the pass is a record with a state rather than a line in a book. Points 2, 3 and 4 are process decisions you must make deliberately.
The returnable gate pass reconciliation checklist
Run this as a standing monthly review. It takes about an hour once the data is digital, and it is the fastest way to find out whether your gate pass system is real.
At issue
- Item described specifically enough to be identified on return make, model, serial or asset tag, not "1 no. motor"
- Quantity and unit of measure stated
- Photograph of the item taken at the gate, attached to the pass
- Condition noted at exit (working / not working / physical damage)
- Vendor name, address and contact captured not just "sent for repair"
- Expected return date set, and set realistically, not as a default 30 days
- Approving department head recorded by name
- Tax document reference captured where one is required for the movement
- Vehicle number and driver recorded
- Exit gate recorded
While open
- Open RGPs visible to stores in one list, sorted by due date
- Automatic alert to the requesting department 7 days before the due date
- Escalation to the department head on the due date
- Escalation to plant head at due date plus 30 days
- Extensions allowed only with a fresh approval and a new date, recorded on the same pass
At return
- Return recorded against the original pass number, regardless of which gate it comes back through
- Physical count matches partial returns logged as partial, with the balance left open
- Serial or asset tag verified against the exit record
- Condition on return recorded, with a photograph
- Stores acknowledges receipt, not only security
- Pass closed by a named person with a timestamp
- If the item will not return, the RGP is formally converted to an NRGP with fresh approval never just cancelled
Monthly
- Ageing report of open RGPs: 0–30, 31–60, 61–90, 90+ days
- Every 90+ item has a named owner and a written explanation
- Write-offs removed from the open list and reflected in the asset register
- Count of passes closed late, by department
That last line matters more than the software. Publish the ageing report by department and open RGPs fall without any other intervention.
Multi-gate plants: when material leaves by a different gate than it entered
In any plant with more than one gate, the binding constraint is that gates cannot see each other. Paper makes this structural: Gate 1 has Gate 1's register.
The failure modes are specific:
- A vehicle enters at the main gate and exits at dispatch. Two half-records, no matched pair, no dwell time.
- A returnable item leaves by the maintenance gate and returns through goods inward. The return is booked as a fresh receipt and the RGP stays open forever.
- A contractor enters at Gate 3 for a shutdown and leaves at Gate 1 with the crowd. Your on-site headcount is wrong, which matters during an evacuation.
- The same vehicle number appears in two gate registers the same day and nobody notices it never left in between.
What to require of any system:
- One pass, one identity, all gates. The pass number is valid and queryable at every gate, not just the issuing one.
- Gate-stamped events, not gate-owned records. Each scan writes an event gate, direction, time, operator to the same pass.
- Open-movement visibility. Any guard at any gate can see what is currently inside that should not be, and what is outside that should be back.
- Direction enforcement. A pass already marked "exited" cannot be exited again without an explicit override, and the override is logged with a reason and a name.
- Gate-level permissions. A pedestrian gate should not be able to release a scrap vehicle.
Vehicle entry: the pass nobody owns
Vehicle passes fail because ownership is split. Security controls the barrier, logistics the schedule, stores the unloading and nobody controls the record.
The minimum useful record is short: vehicle number, driver name and licence reference, transporter, purpose, in and out time, and the gate for each. Add weighbridge slips for bulk and scrap.
Two habits are worth building. Record driver and vehicle as separate entities, because drivers change mid-shift and a pass tied only to a person breaks when the relief driver arrives. And measure dwell time from day one dwell time per transporter is the most persuasive number a gate system produces, and usually the one that funds the project.
If the yard is your bottleneck rather than the gate, see our guide to visitor and vehicle management for warehouses.
Night shift, unmanned gates and what happens when the internet drops
Design for 2am, not for 11am. A gate system that only works when reception is staffed and the link is up is a daytime system with a night-time hole.
Three specific requirements:
- Pre-approval with time windows. Night movements should be approved during the day, with the pass valid only inside a stated window. The guard executes a decision; he does not make one.
- A named on-call approver per pass type. If an unplanned movement must happen at 2am, the system should show the guard exactly whose approval is required and how to reach them and log that approval, not a verbal one.
- Offline capability at the gate. Plant gates sit at the edge of coverage. The pass must stay verifiable and the movement recordable, with sync when the link returns. VizMan's offline visitor management system is built for this constraint it runs at the gate without internet, prints visitor and material passes, and logs inward and outward couriers and materials locally.
Decide in writing what a guard does when the system is genuinely unavailable. A numbered paper slip with mandatory same-shift digital entry is a workable answer. "Use judgement" is not.
Where the handover breaks: security, stores and the approving department
Three parties hold one record between them, and most gate pass failures sit on a seam.
| Seam | What should happen | What actually happens |
|---|---|---|
| Department → Stores | Department raises the movement; stores verifies the item and stock impact before it reaches the gate | Item goes straight from the shop floor to the gate; stores learns about it later, or never |
| Stores → Security | Security receives an approved, itemised pass and checks the physical load against it | Security receives a signed slip and checks the signature, not the load |
| Security → Gate exit | Exit is stamped against the specific pass, with gate and time | Exit is a tick in a register; the pass and the physical movement drift apart |
| Vendor → Return | Return is booked against the original pass number | Return is booked as a new inward receipt; original pass stays open |
| Return → Stores | Stores confirms receipt, condition and serial, and closes the pass | Security accepts the item; stores never formally acknowledges; nobody closes anything |
The fix is not more signatures. It is making the pass a single object that each party updates in turn, with the next party unable to act until the previous one has.
What to log so the pass survives an audit
An auditor asks one narrow question: show me this movement was authorised, executed as authorised, and closed. Log to answer that.
- Pass number, type and creation timestamp with creator identity
- Requesting department and named approver for each approval step, with timestamps
- Full item detail: description, quantity, unit, serial or asset tag, value where applicable
- Reason for movement, in a controlled list rather than free text
- Vehicle number, driver identity, transporter
- Gate, direction, operator and timestamp for every physical crossing
- Photographs at exit and at return
- Expected return date, all extensions with approvals, and actual return date
- Closure record: who closed it, when, on what evidence
- Every override or exception, with reason and approver
- References to any related tax document, without duplicating the document itself
Overrides are the most valuable log you will keep a system with zero recorded overrides is being bypassed outside the system. And gate records contain personal data: driver names, licence references, photographs. Retention and access rules apply, as covered in our DPDP Act guide for visitor data.
Gate pass vs delivery challan vs e-way bill do not confuse the three
These are three different documents with three different purposes, and conflating them creates both compliance and operational risk.
A gate pass is your internal control document. It authorises a movement across your boundary and records that it happened. It has no statutory standing.
A delivery challan is a GST document. Under Rule 55 of the CGST Rules, goods may be transported without an invoice on a delivery challan instead in specified cases including "transportation of goods for job work" and "transportation of goods for reasons other than by way of supply." The rule prescribes the particulars the challan must carry, including its date and number, consigner and consignee details with GSTIN where registered, HSN code and description, quantity, taxable value, tax rate and amount, place of supply for inter-State movement, and signature. Where it is for supply of goods, the challan must be prepared in triplicate original for consignee, duplicate for transporter, triplicate for consigner.
An e-way bill is a separate transport document with its own thresholds and rules.
The implication is simple: your gate pass should reference the challan or e-way bill number, not replace it and not generate it. Your ERP issues tax documents. Your gate system records that the matching physical movement actually happened which gate, what time, verified by whom. Confirm any tax requirement with your own finance team before building a rule around it.
What a digital gate pass system does, what it does not, and what to ask vendors
Be blunt about the boundary, because vendor content in this category routinely over-claims.
What a gate and visitor management system genuinely does well: identity capture and OTP verification at entry, passes that persist across repeat visits, QR check-in, role-based views for security, reception, host and admin, blocked-list enforcement, and exportable timestamped entry and exit logs. VizMan's factories solution covers this layer, including multi-visit passes for daily drivers and contractors, courier in/out logging and audit-ready exports. The offline product prints material passes and logs inward and outward materials at the gate without internet.
What it does not do: it is not your inventory system, asset register, tax document engine or permit-to-work system. The people side of contractor entry induction, document validity and the audit evidence pack is a separate discipline, covered in our contractor safety induction guide for factories.
Questions to ask any vendor, including us:
- Can the system model more than one pass type, each with its own approval chain?
- Can a pass carry an expected return date, and can it escalate automatically when overdue?
- Can a pass issued at one gate be closed at a different gate?
- Can partial returns be recorded against an open pass?
- Does it store item-level detail with serial numbers and photographs?
- Does it work at the gate when the internet is down, and what syncs when it recovers?
- Can it reference not duplicate a challan, PO or e-way bill number?
- Can it export an ageing report of open returnable passes?
- Can approval limits vary by value slab, and can it detect a movement split to stay under a slab?
- Where is the data stored, who can see driver and worker personal data, and what is the retention policy?
Score every vendor on all ten. Most demos answer one to five brilliantly and go quiet from six onwards.
A practical rollout order
Do not launch eight pass types at once. Sequence by pain.
- Returnable outward passes first. Smallest volume, highest value, clearest win. Digitise open RGPs, set real return dates, publish an ageing report.
- Vehicle entry second. Start measuring dwell time. It builds the case for everything else.
- Contractor and visitor passes third. Highest volume fix throughput before adding rules.
- Non-returnable and scrap last. These touch finance slabs and weighbridge process, so they need the most agreement.
Run one gate in parallel with paper for two weeks before retiring the register. Then take gate two.
A gate pass system is not really about the gate. It is about whether your plant can answer three questions on demand: what left, did it come back, and who said it could go.
Paper answers the third badly and the first two not at all. You can close that gap on one pass type, at one gate, in a fortnight.
Start with your open returnable passes. Count them. The number will make the decision for you.
See how VizMan handles gate entry at Indian factory gates. QR and OTP check-in, multi-visit passes for daily contractors and drivers, courier and material logging, blocked lists, role-based access for security and admin, exportable audit logs, and an offline option that keeps working when the link drops.
|
See how VizMan works for your site
Book a VizMan demo for factories or explore the factories solution.
|
This article is operational guidance, not legal or tax advice. Verify any statutory requirement against the current rules with your own advisers before building it into a process.
Explore more from VizMan: Visitor management system · Pricing · All blogs · Book a demo
Official sources
Legal references in this guide were checked against official government texts:
- Rule 55, CGST Rules, 2017 (delivery challan) CBIC tax repository
- The Digital Personal Data Protection Act, 2023 (official text, MeitY)
- The Digital Personal Data Protection Rules, 2025 (MeitY)
This guide is general information, not tax or legal advice. Confirm GST treatment of returnable and non-returnable movements with your tax adviser.
