VIP visit tomorrow

Protocol is the duty with no statute and no forgiveness. Almost everything in this playbook is practice — the accumulated convention of how districts run visits — and that is precisely why it must be learnt as procedure: there is no bare act to fall back on when the convoy is early and the dais is wrong. A Deputy Collector’s usual role is liaison officer — attached to the dignitary or to one segment of the visit — with the DRO running the whole board from the Collectorate’s protocol section (the H section, which handles VIP visits, vehicles and allied subjects).

The first sixty minutes

(The sixty minutes here are the first hour after the visit lands on you — usually the evening before.)

1. Get the programme — you, from the DRO/H section. The minute-to-minute programme is the constitution of the visit: arrival mode and time, receiving line, route, each engagement with its duration, seating, speaking order, meal arrangements, departure. If only a draft exists, work from the draft and note its version — programmes change until the wheels touch down, and half of protocol is knowing which version is current.
2. Fix your own assignment in writing — the DRO assigns. Which dignitary or segment, from which handover point to which, with whom you hand over on either side. Get the mobile numbers of the officers at both handover points and of the dignitary’s personal staff, and confirm them by an exchanged message tonight.
3. Read the programme against the warrant of precedence — the DRO’s call, your check. Who receives the dignitary at the district border, at the helipad, at the venue — these are set by the standing protocol instructions and precedence conventions: the receiving officer’s rank matches the dignitary’s entitlement, and the order of the receiving line is precedence order. The classic wreck is a mismatched reception — a dignitary entitled to the Collector received by a Tahsildar, or precedence inverted in the line. Flag doubts tonight; nobody can fix them at the helipad.
4. Coordinate the security layer — the police own it; you facilitate. Route, venue access, frisking arrangements, the carcade composition — for highest-protected dignitaries these run under the classified “green book” security guidelines and the decisions belong to the security agencies; the civil administration facilitates and does not negotiate. Your job at the interface: know the police officer commanding each point on your segment, and never promise an access or a route change that is security’s to give.
5. Drive the route — you, tonight or at first light. Every liaison officer’s non-negotiable: the actual route at the actual time of day if possible, noting travel times, choke points, the alternate route the police have planned, and where the conveniences, fuel and turnaround points are. The programme’s timings become real or fictional on this drive — say so upward if they are fictional.
6. Walk the venue — you, with the venue officer. Dais layout against the seating plan, the speaking order against the mike arrangements, the entry the dignitary uses versus the entry the public uses, the holding room, and the exit plan — including the early-exit plan, because dignitaries leave early more often than late.
7. Confirm the support cast — through the H section. Vehicles (with drivers who know the route), the pilot and escort arrangement, guest-house or holding-room readiness, meals per the advance party’s indications, and the officers detailed at each engagement. Everything confirmed today by message; everything reconfirmed tomorrow at dawn.

The first twenty-four hours

Visit day runs on one discipline: stay one engagement ahead. The liaison officer is physically at the next point before the dignitary leaves the current one — which means you leave each venue during the closing item, not after it. The programme in your hand (and your phone), you track drift in real time: a fifteen-minute slip at the first engagement is reported to the DRO immediately, because the district will trim or hold later items and the trimming must be decided by someone who can see the whole board.

At handovers, hand over affirmatively — find your counterpart, transfer the dignitary’s staff contact, state the drift (“running twelve minutes late; lunch shortened”), and only then fall away. Silent handovers are how dignitaries end up alone in corridors.

Around the visit proper, the bandobast machinery runs its own track: police deployment along the route and venue, and where an order is needed — restricting assembly near a venue, regulating vehicular movement — a written s. 163 order with recited facts, sought by the police and issued by the competent Magistrate. Traffic and crowd inconvenience is the visit’s public face; the administration that warns the public in advance (press note, diversions published) spends less goodwill than the one that surprises them.

After departure, the visit closes on paper: the post-visit note (what was committed by the dignitary — assurances made at the dais become follow-up files), expenditure and requisition regularisation, and the return of everything borrowed. The liaison officer’s own note — what worked, what nearly failed — goes to the DRO; the next visit is built on it.

Cover yourself — the record

By tonight (the night before), there must exist, on paper or confirmed message:

• The programme version you are working from, with its issue time.
• Your assignment order — segment, handover points, counterparts.
• The contact sheet — every officer on your segment, the dignitary’s staff, the police commanders at your points — confirmed by exchanged message.
• Your route notes with timings from the actual drive.
• Any doubt you flagged (precedence, timing feasibility, venue problems) — flagged in a message, not just orally, so the decision that overruled you is on record too.

After the visit: the post-visit note, the assurances register entry for anything announced, and requisition/expenditure papers closed within the week.

Legal hooks

Protocol is practice, but it touches law at defined points:

• BNSS s. 163 — route and venue orders where the police seek them: written, fact-recited, promulgated.
• The security guidelines for protected dignitaries — classified; their operational meaning for you is jurisdictional: security decisions belong to the security agencies.
• The warrant of precedence and standing state protocol instructions — conventions with the force of instruction; the H section holds the current compilations.
• Financial rules — requisitions, hired vehicles and visit expenditure are drawn and regularised under the ordinary treasury discipline; visits do not suspend the audit.

Who to call

• The DRO — the visit’s chief of staff; all doubts route here.
• The Collectorate H section superintendent — programmes, vehicles, guest houses, the paper.
• The SP’s designated bandobast officer — your security counterpart for the segment.
• The dignitary’s personal staff — the advance party’s named contact; the only reliable source on the dignitary’s actual intentions.
• Your handover counterparts — the liaison officers on either side of your segment.
• The venue’s owning officer — the school headmaster, the function-hall manager, the temple executive officer: whoever controls the ground.

Mistakes that end careers

• The wrong receiver. Precedence errors at reception are the protocol sin that travels fastest — the aggrieved dignitary’s office calls the Chief Secretary’s office before the convoy leaves the helipad. Check the receiving arrangements against entitlement tonight.
• Working from a stale programme. Version three is circulating and you are executing version two: the visit forks in front of you. Confirm the version at dawn and at every handover.
• Negotiating with security. The liaison officer who “adjusts” access for a local notable against the police’s list owns whatever follows. Requests go to the police commander; his answer is the answer.
• Being behind the dignitary. A liaison officer following the convoy is furniture. One engagement ahead, always.
• The unlogged assurance. The dignitary announces a bridge, a compensation, an enquiry — and no one writes it down. Weeks later the follow-up query arrives and the district has no record of its own event. The assurances go in the post-visit note the same evening.
• Freelancing with the media. Visit-day statements belong to the designated officer. A liaison officer quoted on the record about the dignitary’s programme or mood has volunteered for the next controversy.

Questions you’ll actually get

“The local MLA’s people want five more passes to the dais.” Passes are the police’s and the H section’s, per the approved plan — route the request there immediately and tell the asker exactly whom you routed it to. Never issue, never promise, never carry loose passes. The dais list is a security document, not a courtesy.

“The dignitary is now coming by road, not helicopter. What changes?” Everything upstream of the first engagement: receiving point (district border, by convention, with the receiving officer per entitlement), route, timings, pilot arrangements. Get the revised programme issued — even as a one-page amendment — rather than adjusting by phone; every officer on the old plan is now standing in the wrong place.

“It’s raining and the open-air venue is drowning.” The venue decision belongs to the DRO/Collector with the security agencies — your job is to surface it early with options (the covered alternative you noted on your walk-through) rather than to preside over a soaked dais at 2 pm. The liaison officer’s value is the hour of warning.

“The visit was cancelled at midnight. What do I do with the morning?” Stand down the segment affirmatively: message every officer on your contact sheet, release the venue and vehicles, and make sure the public-facing arrangements (diversions, closures) are lifted with the same energy they were imposed. A district still holding traffic for a cancelled dignitary at noon is the story the visit leaves behind.