Is a gate pass a legal document?

A gate pass is a contractual control, not a statutory record. It exists because you decided who may enter your premises and on what terms, and its authority comes from your contract with the contractor rather than from any rule. That distinction matters on the day it is tested: a gate pass can be issued, withdrawn and designed however you like, but it proves entry and nothing else, and nobody is obliged to surrender one on the way out.

What is a muster roll in contract work?

A muster roll is the attendance register kept for workers engaged through a contractor: names, parentage, sex, the dates attended and remarks. It was a statutory record rather than an operational one, which is the point most often missed. It is written up for the day, it is retained for inspection, and it was never designed to answer the question of who is standing inside the plant at this minute.

What is Form 25 muster roll?

The premise needs correcting twice. Under the Contract Labour Central Rules 1971 the muster roll was Form XVI, prescribed by rule 78(1)(a)(i), and there was no central Form 25. Form 25 is a state-rules numbering variant, so an answer that gives it as the central form is wrong wherever those state rules do not apply. The larger correction is that the parent Act is repealed, so a search for the old form number is a search for a form from a regime that has been replaced.

What is rule 76 of contract labour?

Rule 76 of the Contract Labour Central Rules 1971 was the employment card, Form XIV, to be issued to each worker within three days of employment. It was not the muster roll, which sat at rule 78. The two are confused constantly because both are contractor record-keeping duties in the same part of the same rules, and because the Act those rules were made under has been repealed, an answer built on either number is answering about a regime that no longer governs.

What is a contract labour management system?

In practice the phrase describes compliance software: it holds contractor documents, licences, worker records, wage data and the statutory registers, and it produces returns. It is bought by HR or by a compliance function and it is good at what it does. It is not a presence system. None of it is wired to the question an EHS Head asks at an assembly point, which is how many contract workers are on site right now and whether they have all arrived.

What is a gate pass management system?

A gate pass management system issues and records entry authorisations at a boundary: who requested the pass, who approved it, what it permits, when it was issued and when it expires. Some read a card or a face at the gate. All of them record an event at a line, which means the quality of your count depends entirely on whether people are as disciplined about leaving as they are about arriving. They are not, and no system fixes that at the gate.

How do you account for contract workers during an evacuation?

Start from the admission that the intake record is not a count. Fix a named owner per contractor at each assembly point, give that owner a written list he can read in the open air, record arrival against it by name rather than by tally, and reconcile the shortfall against who the gate believes is inside. Then decide in advance what happens when the two disagree, because they will. The part nobody writes down is who has authority to declare the count closed.

The gate pass says they came in. It cannot say they came out.

Q: Does the Contract Labour Act still apply in India?

No. The Contract Labour (Regulation and Abolition) Act 1970 is one of the thirteen central enactments repealed by the Occupational Safety, Health and Working Conditions Code 2020, which came into force on 21 November 2025, and the Occupational Safety, Health and Working Conditions (Central) Rules 2026 were notified on 8 May 2026. Most of what is published online about contractor registers still describes the 1970 regime as live law. Check your own register obligations against the Code and the 2026 Rules rather than against the old rules.

02 The gap

Why does the gate pass not tell you who is still inside?

Because it was never asked to. A pass is issued at a boundary and it records one thing well: that somebody with an approval crossed a line at a time. Every part of the system is built around that moment. The approval workflow, the photograph, the validity window, the contractor code, the register at the security desk.

Then the day goes on. People move between units. Some finish early. Some leave through a gate that is not the one they entered. Some hand the pass back and some keep it in a shirt pocket for a fortnight. On a normal Tuesday none of that matters, because nothing depends on the number being right.

It matters once, and it matters completely. The alarm goes, the plant empties into the assembly points, and somebody has to say whether everybody is out. For employees that question is usually answerable, because there is a payroll, a shift roster and a supervisor who knows his people by face. For contract workers it is answerable only to the extent that the intake record can be trusted several hours after it was written, by somebody reading it in the open air, under pressure, probably on a phone.

This is not a small part of the plant. The Annual Survey of Industries for 2023-24 puts contract workers at around 42% of the manufacturing workforce. On a site with eight hundred people inside the fence, the group whose presence is recorded only by an intake pass is not a rounding error at the muster point. It is one person in every two and a half.

So the honest statement of the problem is not that the gate pass is bad. It is that the gate pass is an intake control being used as a presence record, and the two are different instruments.

What is a contract labour muster roll, and does it still apply?

Alongside the gate pass there has always been a register. The contract labour muster roll is the attendance record kept for workers engaged through a contractor: names, parentage, sex, the dates attended, remarks. It was a statutory document, and it is the thing most people reach for when they are asked to produce evidence about who was working on site.

Two things about it are worth being precise on, because almost everything written about it online is imprecise about both.

The first is what it is for. A muster roll is written up for the day. It is a record of attendance, retained for inspection, and the inspection it anticipates is a labour inspection rather than an emergency. It answers whether a person was engaged and paid. It has never answered, and was never meant to answer, where that person is standing at 14:40 on a Thursday.

The second is harder, and it is the reason this page exists.

What changed when the OSH Code replaced the contract labour Act?

The Contract Labour (Regulation and Abolition) Act 1970 is repealed. It is one of thirteen central enactments subsumed by the Occupational Safety, Health and Working Conditions Code, 2020, which came into force on 21 November 2025. The Occupational Safety, Health and Working Conditions (Central) Rules 2026 were notified on 8 May 2026.

RepealedContract Labour (Regulation and Abolition) Act 1970

And with it the Central Rules of 1971 that prescribed the contractor registers. Under those rules the muster roll was Form XVI, prescribed by rule 78(1)(a)(i). Rule 76 was a different duty entirely: the employment card, Form XIV, to be issued within three days of employment.

In forceOccupational Safety, Health and Working Conditions Code, 2020

From 21 November 2025, with the Central Rules of 2026 notified on 8 May 2026. The contractor licensing regime is consolidated and the register obligations sit here now rather than in the 1971 rules.

What this page will not do is tell you which form replaces Form XVI. That answer is in the 2026 Rules and it should be read there, by somebody who has read them, with a date against their name. A page that guesses a form number is how a wrong number gets inherited for the next five years, and there is already a great deal of that about on this subject.

Here is why it matters commercially rather than academically. Your compliance register, your contractor agreements, your audit checklist and your induction pack were in many cases written when the 1970 Act was live. They were correct then. Nothing in the chain that copied them forward was ever asked which instrument it was citing. That is the same failure that leaves drill calendars across the country pointing at the repealed Factories Act 1948, and it is the single commonest finding when anybody actually looks.

What is actually on page one of these questions

On the gate pass query, the results are two gate-pass software vendors, an integrator and a business-to-business marketplace. On the muster roll query they are HR and compliance software sites and a state labour portal. Not one of them is addressed to an EHS Head, and the muster roll results describe the 1971 regime as though it were live.

The related searches tell you the same thing more bluntly. Eight of the eight related searches on the muster roll query are format or download requests. The demand is for a document, and the document being offered is from a repealed regime.

Measured, not asserted. Google results for gate pass system contract labour and contract labour muster roll, read individually on 13 September 2026 from an Indian IP with personalisation off, recorded in the VijAI PulseAI module demand register. The repeal position was verified separately on 4 October 2026 against the Code’s own schedule of repealed enactments.

None of this is solved by a better register. You can keep a perfect muster roll under whichever form now applies and still not know, at the assembly point, whether the four fitters from the mechanical contractor are out. The register is a statutory artefact. The count is an operational one. The thing that closes the gap is being able to see who is standing at the point.

The 30-day pilot One plant. Two cameras at one assembly point. Thirty days.

Your cameras already look at the muster area. For thirty days we count what they see and put a clock on it, so at your next drill you can read the contractor shortfall against the arrivals rather than against an intake sheet. No new hardware, one module, one plant.

Start a 30-day pilot →

What does an evacuation roll call site attendance checklist need?

Not another register. The register is a compliance document and you already have one. What is missing on most sites is something a named person can read out loud at an assembly point while two hundred people are arriving around him. An evacuation roll call site attendance checklist is that document, and it is nine fields, every one of which is either a fact about your site or a decision taken in advance.

Nine rather than ten or eight, deliberately. This is the fourth document in this cluster and each one carries a different artefact, because a checklist that is a rearrangement of the previous one is a brochure with headings.

01The assembly point, and which gate feeds it

Named, not described. And the gate or gates whose intake record is the source of the expected roll for this point, because a point fed by two gates has two sources and somebody has to decide at three in the morning which one is authoritative.

02The contractor, and the owner of its count by role

One named role per contractor per point, and a deputy. By role and never by name, so the position does not go stale when a person moves. The deputy field exists because the owner is frequently the person who is unaccounted for.

03The expected roll, and the moment it is taken from

The list of who the gate believes is inside, fixed at the moment the alarm sounded rather than at the morning issue of passes. A roll taken at 08:00 is wrong by lunchtime on any site with movement, and the difference between those two timestamps is the single largest source of a false shortfall.

04Arrival recorded by name, not by tally

A tick against a name, not a running number. A tally tells you a count is short. A list tells you who is missing, and only one of those two can start a search. This is the field that most intake-driven processes do not have, because the intake record is a count of passes rather than a list of people.

05The shortfall, with the last known place of work

Each remaining name with the unit, floor or vessel the person was last working on, taken from the work permit rather than from recollection. A search party needs a direction more than it needs a number.

06Who may declare the count closed, and on what basis

By role, with the basis written down: all names ticked, or a stated reconciliation of the difference. This is the line an investigation reads first and it is the line most often absent. An unwritten authority becomes whoever is most senior and most certain, which is not the same thing as whoever has the list.

07What happens when the gate and the point disagree

Decided in advance, in one sentence, because they will disagree. Whether the search is launched on the gate’s number or the point’s list, and who pays for the delay if the answer turns out to be a pass that was never surrendered.

08The contractor’s own obligation, and where it is written

The clause in the contract that obliges the contractor to produce a current list and to attend the point with it. If that clause does not exist, the checklist is a request rather than a requirement, and it will be honoured on a good day and not on a bad one.

09Where the completed sheets are kept, and for how long

A location a second person could find in ten minutes, and a retention period. If producing the last four completed sheets takes a week of looking, the gap is not compliance. It is retrieval, and retrieval is what an inspection tests.

What does one look like when it is filled in?

A blank format is table stakes. The filled one is what gets copied, so here is one, anonymised, from a mechanical contractor at a single assembly point during a rehearsal. The numbers are the point: the gate believed nineteen, seventeen arrived, and the two names took four minutes to establish because the list existed.

A worked checklist · mechanical contractor, one assembly point, during a rehearsalIllustrative example

01 · Assembly point: Muster point 04, east yard, fed by Gate 2 only. The single-gate answer is what made the rest of this straightforward, and it is not the common case.
02 · Contractor · count owner: Mechanical maintenance contractor · owner: contractor site in-charge, deputy: his senior fitter. Both by role. The figures in this example are illustrative and the site is not a client of ours.
03 · Expected roll: 19 persons, taken from the Gate 2 record at 14:38, the minute the alarm sounded. The morning issue of passes had said 21, and the difference is two men who had finished at noon.
04 · Arrivals, by name: 17 of 19 ticked against the printed list by 14:44. Six minutes, and the only reason it was six and not twenty is that the list was printed and on the point before the alarm.
05 · Shortfall: 2 names, both last permitted to the cooling tower platform, taken off the work permit rather than from anybody’s memory. That gave the search a direction in the same minute it gave it a number.
06 · Count closed by: Site EHS officer at 14:51, on a stated reconciliation: one man found at the second assembly point, one pass never surrendered at the previous shift change. Note that the closing authority was not the most senior person standing there.
07 · Gate and point disagreed: Yes, by one. Resolved as a pass not surrendered the previous evening, and logged as a finding against field 07 rather than settled in conversation. This is the field that paid for the exercise.

Read the last two rows again, because they are the whole value of the document. One of the two missing people was at a different assembly point, which is a real event and a real four minutes. The other was never on site at all. Without a list, both appear as the same thing: a count that is short by two. With a list, one is a person to go and find and the other is an administrative discrepancy, and the difference between those two decisions is whether anybody is sent back into the plant.

Can you take this away?

Yes, and with no form in front of it. Copy the block below into your own document system and make it yours. It is nine lines because the checklist is nine fields.

The Contractor Roll Call Checklist · blank, one per contractor per point

CONTRACTOR ROLL CALL · ASSEMBLY POINT CHECKLIST    one per contractor, per point

01  ASSEMBLY POINT ................ named, and the gate(s) that feed it
02  CONTRACTOR · COUNT OWNER ...... by role, plus a deputy
03  EXPECTED ROLL ................. number, and the TIME it was taken from the gate
04  ARRIVALS ...................... ticked by NAME against a printed list, not tallied
05  SHORTFALL ..................... each name, with last permitted place of work
06  COUNT CLOSED BY ............... role, time, and the basis stated
07  GATE vs POINT DISAGREEMENT .... what we do, decided before today
08  CONTRACT CLAUSE ............... where the contractor's duty to attend is written
09  RETENTION ..................... where the sheets live, and for how long

RULE OF THUMB  a tally tells you the count is short. A list tells you who is missing.
               Only one of the two can start a search.

Current against · the Occupational Safety, Health and Working Conditions Code, 2020, in force 21 November 2025, and the Central Rules, 2026, notified 8 May 2026 · the Contract Labour (Regulation and Abolition) Act 1970 and its Central Rules, 1971, recorded as repealed · the Annual Survey of Industries 2023-24. Re-verified October 2026.

Enquire Now

What does a large public-sector utility actually do?

One of the most revealing things in the search behaviour on this subject is that buyers do not only look for a format. They look for how a specific named plant does it. The literal query that surfaced in the harvest names a large public-sector utility, and it is asked by people who want to copy a working arrangement rather than read a principle.

Nobody serves that demand, so here is the pattern as it appears on the sites where it works, without naming anyone.

What the arrangement does	Why it works	Where it lands in your checklist
The expected roll is pulled at the alarm, not at shift start	It removes the single biggest cause of a false shortfall, which is ordinary movement during the day	Field 03
The contractor’s own supervisor attends the point with a printed list	It puts the duty on the party who knows the faces, and it survives a network outage and a flat phone battery	Fields 02 and 08
The authority to close the count is written down, and it is not the most senior person present	It separates the decision from the hierarchy, which is what stops a confident guess from becoming an all-clear	Field 06
Gate and point disagreements are logged as findings, not settled in conversation	Within two quarters the passes stop going home in shirt pockets, because the discrepancy has an owner	Field 07

This is a pattern, not a benchmark, and it is described from search behaviour and from what sites tell us rather than from a survey. There is no claim here about outcomes, because none has been measured in a way that would survive a question from your Plant Head.

What gets this sent back, and why is it almost never the gate?

An expected roll taken at the morning issue of passes. It is the obvious place to take it from and it is wrong by every movement since. On a site with two shifts and inter-unit work it can be out by a tenth of the contract headcount by mid-afternoon, and the error always runs in the direction of reporting people missing who went home at noon.

A count kept as a number rather than a list. Nobody decided this. It is what happens when the document is designed by whoever owns the gate, because at a gate a number is the natural unit. The cost only appears at the point, when the shortfall is two and there is no way to say which two.

No written authority to close the count. The question has never come up, because every drill has ended with somebody saying it looks complete and nobody disagreeing. It is the field most often empty and the first one an investigation asks about, and the gap is invisible until the one time the count does not reconcile.

The contractor has no contractual duty to attend the point with a list. The arrangement works anyway, on the strength of a good site in-charge. It is a personal arrangement wearing the clothes of a system, and it leaves with him.

A register kept beautifully under a repealed rule. The file is immaculate, the forms are the old ones, and the reason nobody has noticed is that an immaculate file does not invite a second look. This is the only one of the five that is a paper problem, and it is also the one that is cheapest to fix and least often fixed.

Every one of those five is a condition rather than a person. That is accuracy and not diplomacy: all five survive a change of staff, and four of them were created by a system that was reasonable when it was built. Not one of them is a failure at the gate. On the sites where this gets looked at properly, the gate is usually run well, and what is thin is the document between the gate and the assembly point.

Enquire Now

What the gate pass proves, and what it does not

A gate pass proves that a person with an authorisation crossed your boundary at a time, and that somebody approved him being there. That is worth having. It is how you keep people off a plant who should not be on it, and it is the basis of nearly every contractor control that follows.

What it does not prove is presence. An entry record becomes a presence record only if exit is enforced as rigorously as entry, and on an operating plant it never is. Not through carelessness. Through traffic: shift changes, multiple gates, early finishes, a fitter who walks out with a vehicle through the materials gate because that is where the vehicle is.

And this is where the line has to be drawn clearly, because the question is often asked in a different form. We are asked how to track where contract workers are during the day. That is a question we do not answer and a product we do not sell. Continuous location tracking of workers is a different thing from accounting for people at an assembly point, it is bought for different reasons, and the distinction is not a technicality. One is a safety record of a moment. The other is surveillance of a shift.

Where does VijAI fit, and where does it not?

Your cameras are already pointed at the assembly points, because that is where you put cameras. During a drill or a real evacuation VijAI counts what they see and puts a clock on it, so the contractor shortfall is read against arrivals at the point rather than against an intake sheet written hours earlier. Arrival times, person by person where the view allows it, and the minute the count closed.

It runs on the cameras you have. Zero new hardware, which on this particular problem matters more than usual, because the alternative proposals all involve issuing something: a new card, a tag, a wearable, to a workforce that turns over constantly and whose employer is not you. A contractor control that requires you to distribute hardware to other companies’ employees is a control that degrades every month.

100+ plants and sites run VijAI on cameras that were already installed, and the survey tells you which of your assembly points are among them. On most sites the main point is.

One line so nothing is misread. VijAI evidences that a person was present at a stated place at a stated time. It does not maintain your statutory register, it does not certify your compliance under the Code or the 2026 Rules, it does not decide whether a count has reconciled, it does not track anybody through the working day, and it is not a life-safety system. The duty to account for people on your premises sits with you and stays there. What changes is what you can put behind the sentence you write afterwards.

Which deployment model you end up on is decided at the survey and never priced before it. Where a contractor population is involved most plants land on on-premise edge, because the question of whose employees are in the footage is easier to answer when the footage never leaves the fence. Hybrid and cloud are both available.

The rest of the contractor count, in four pages

L0 · THE MODULE

PulseAI

What the counting module is and how it reads a camera you already own. Start here if you want the capability before the compliance argument.

The module →

L2 · THE SPECIFICATION

Choosing a system that can close a count

The twelve questions to put to any vendor, and what the category actually sells today. Read it before you let anybody quote you for badges or tags.

The specification →

L1 · THE REQUIREMENT

How often a drill is required, and under which rule

The six-month rehearsal at a major accident hazard installation, the report that goes to the authority, and why most drill calendars cite a repealed Act.

The requirement →

L3 · THE RECORD

The evacuation drill record

The document that carries each individual rehearsal, every field it needs, and the reasons one comes back from review.

The document →

Sources · the Occupational Safety, Health and Working Conditions Code, 2020, in force from 21 November 2025, and its schedule of repealed enactments, which includes the Contract Labour (Regulation and Abolition) Act 1970 · the Occupational Safety, Health and Working Conditions (Central) Rules, 2026, notified 8 May 2026 · the Contract Labour (Regulation and Abolition) Central Rules, 1971, now repealed with their parent Act, for the muster roll at rule 78(1)(a)(i) in Form XVI and the employment card at rule 76 in Form XIV · the Annual Survey of Industries 2023-24 for the contract-worker share of the manufacturing workforce · the VijAI PulseAI module demand register, harvested 13 September 2026, for the page-one and related-search measurements described above. Every instrument here is named and none is hyperlinked, under the standing rule on this site. On this subject that matters more than usual: the pull to link a gazette is strong, and a link would hand the reader somebody else’s copy of a rule whose currency is the entire point of the page.

Model	Where the video is processed	Where it fits
On-premise edge	Entirely inside the plant. Nothing leaves your network.	Licensed areas, sites with a data-residency rule, and plants with no dependable outbound link.
HybridRecommended	Detection at the edge, dashboards and reporting hosted. Footage stays on site. Only events leave.	Most plants. Video stays inside the boundary and head office still gets one view across every site.
Cloud	Processing and storage hosted.	Single sites, short pilots, and estates already running their VMS this way.

The gate pass tells you who came in. It does not tell you who is still inside.

Three numbers, and the first one is the whole problem