Gate Pass Format: Free Excel Template (Returnable & Non-Returnable)
2026-06-21
A ready-to-use gate pass format with a free Excel template, returnable vs non-returnable fields, a filled example, the gate-pass workflow and FAQ.
A gate pass is the document that controls what leaves — and enters — your premises through the security gate: materials, tools, instruments, finished goods, scrap, even vehicles and visitors. Get the format right and nothing moves out unauthorised, returnable items actually come back, and your security log matches your stores. Here's a ready-to-use gate pass format in Excel, the field-by-field guide, the returnable vs non-returnable distinction, and a worked example.
⬇ Download the Gate Pass template (Excel) — free, no sign-up. Use it as-is or adapt to your ERP / SOP.
What is a gate pass?
A gate pass is a controlled authorisation that records the movement of material, equipment or people across the factory gate. It answers four questions the security guard and the auditor both need: what is moving, why, who authorised it, and (for returnable items) when it must come back. Without it, the gate is a hole in your inventory and your compliance — stock walks out, tools go missing, and you can't prove who approved what.
Types of gate pass
Pick the type first — it changes which fields are mandatory.
TYPE WHEN TO USE KEY FIELD
------------------------- --------------------------------------------------- ---------------------------
Outward — Returnable Item leaves but must come back: instrument for Expected Return Date
calibration/repair, tools, drums, cylinders, dies (and reconcile it)
Outward — Non-Returnable Item leaves permanently: finished-goods dispatch, Reference doc (DC / invoice
scrap sale, samples, rejected material / scrap note)
Inward Coming in: returned goods, vendor delivery, Reference doc + gate log
visitor / contractor entry
Vehicle / Visitor pass Vehicle or person movement (often a separate ID + in / out time
register)
The single biggest control failure is returnable items with no return date and no follow-up — they quietly become permanent losses. The template below forces a return date and a return-reconciliation line.
What a gate pass format must contain
This is the template — each field earns its place in the movement and audit trail.
FIELD WHAT GOES IN IT
----------------------------- --------------------------------------------------------
Gate Pass No. / Date & Time Unique running ID + when issued
Type Inward / Outward + Returnable / Non-Returnable
Issued to / Party Vendor, employee, contractor or visitor (+ code)
Department Requesting department
Reference Doc PO / Work Order / Return note / DC / Scrap note
Item code / Description What is moving
Qty / UOM Quantity + unit
Reason / Purpose Why it's leaving or entering
Expected Return Date MANDATORY if Returnable
Vehicle / Transporter For traceability
Returned On / Qty Filled when a returnable item comes back
Requested by / Authorised by Originator + approval signature
Security check (out / in) Gate security verifies, logs and signs
Remarks Damage, shortage, conditions, debit note ref
A filled gate pass example
Gate Pass No. / Date GP-OUT-2026-0457 · 21 Jun 2026, 14:20
Type OUTWARD · RETURNABLE
Issued to Sharp Tools Pvt Ltd (V-0231)
Department Engineering / Maintenance
Reference Doc Work Order WO-3392
Item Pressure gauge, 0-100 PSI (EQ-118)
Qty / UOM 2 No.
Reason Sent out for calibration
Expected Return Date 05 Jul 2026
Vehicle / Transporter HR-26-AB-1123 · Blue Dart
Returned On / Qty - (open)
Requested / Authorised R. Verma (Engg) · Plant Head
Security (out / in) S. Kumar / -
Remarks Calibration due; AMC vendor
Notice what makes this a control and not just a chit: it's a returnable pass, so there's an expected return date (05 Jul), the return line is left open, and security has to close it on return. An instrument going out for calibration without this is exactly how equipment goes missing between the plant and the vendor.
How to fill it (the parts people get wrong)
- Decide returnable vs non-returnable up front. Returnable items need a return date and active reconciliation; non-returnable items need the dispatch/scrap reference so they tie to a GRN, invoice or DC.
- Never let an item leave without authorisation. Keep an approval matrix by value/criticality — a ₹500 tool and a ₹5-lakh instrument shouldn't need the same signatory. This mirrors a good purchase-order approval workflow.
- Security verifies, logs and signs at the gate — item vs pass, quantity, vehicle. The gate register is your independent record; it should reconcile with the passes issued.
- Age your open returnable passes. A weekly "overdue returnable items" list is the single report that stops slow leakage. If you can't produce it on demand, that's the gap.
- Serial-control every pass. A running number means every pass is accounted for and none can be quietly voided.
The gate-pass workflow
Request raised (dept)
|
v
Authorised? --- no --> returned to requester
| yes
v
Pass issued (serial no.)
|
v
Security verifies item vs pass --> logs in gate register --> signs OUT
|
+--> Non-returnable: closed (tie to DC / invoice / scrap note)
|
+--> Returnable: stays OPEN
|
v
Item returns --> security verifies qty/condition --> signs IN --> pass CLOSED
|
v
Overdue (past return date)? --> escalation / "open returnable" report
Why move off paper gate-pass books
A paper gate-pass book can't answer the questions that matter: which returnable items are overdue right now? did every outward pass get authorised? does the gate log reconcile with stores? The moment movement crosses a gate, it should be:
- Authorised digitally with the right approver by value/type, so nothing leaves on a verbal "ok".
- Linked to the source document — Work Order, GRN, dispatch challan or scrap note — so material movement is traceable end-to-end.
- Reconciled automatically — the "open returnable" and "overdue" lists generate themselves instead of someone flipping through a register.
- Searchable for audits — pull every pass for a vendor, item or date range in seconds.
This is the same shift behind digitising any operational register: the paper format is fine as a starting point, but the value is in the control and the report, not the chit. It's the same thinking we apply to pharma quality and operations workflows.
Gate pass format — FAQ
What is the difference between a returnable and non-returnable gate pass?
A returnable gate pass is for items that must come back (instruments for calibration, tools, cylinders) and must carry an expected return date that you reconcile. A non-returnable gate pass is for items leaving permanently (finished goods, scrap, samples) and should reference the dispatch challan, invoice or scrap note.
Who authorises a gate pass?
The department raises it and an authorised signatory (HOD / plant head, per your approval matrix) approves it before security lets it out. Higher-value or critical items should need a higher approver.
Is a gate pass the same as a delivery challan?
No. A gate pass is an internal security/movement control at your premises; a delivery challan (DC) accompanies goods in transit and is a statutory transport document. A non-returnable outward pass is often raised alongside a DC.
Do we need a gate pass in a GMP / pharma plant?
Yes — material and equipment movement must be controlled and traceable. Returnable instruments going out for calibration, samples leaving for testing, and rejected/scrap material all need a documented, authorised gate pass that ties into your quality records.
Can I get a free gate pass format in Excel?
Yes — download the template above. It includes a filled example, both returnable and non-returnable fields, and a "How to use" sheet. Adapt it to your ERP or, better, digitise the authorisation and the overdue-returnable report.
Flobri turns formats like this into live, authorised workflows — gate passes, GRNs, work orders and quality records — with approvals, a searchable gate log, and an automatic overdue-returnable report. See how Flobri works.