SECURITY
KEPT
RIGHT.
STRUCTURED
A secure campus begins with well-defined systems, clear responsibilities and disciplined processes. Every safeguard has a purpose, and every person has a role.
MONITORED
Constant vigilance keeps risks under control by detecting potential threats early and enabling timely action before they escalate.
MANAGED
Effective management turns challenges into solutions, ensuring safety measures evolve with changing needs.
NOT JUST SECURITY
BUT A SYSTEM
ENSURING
SAFETY FROM
EVERY ASPECT
Safety · Security · Operations
Safe Campus, Smart Community and Shared Responsibility
At RBU, Security should make people feel protected—not intimidated. Security is not only about stopping people, checking people and enforcing rules. It is also about how we treat people while doing it. I expect our security team to be firm in their duty, but respectful in their conduct. At RBU, security and courtesy must go together.
❞THE OTHER SIDE OF SECURITY
Behind every security decision is a person — and behind every security guard is a responsibility.
A security guard is often noticed only when he stops someone, checks an ID, refuses entry, or asks someone to wait. What we see is the interruption. What we may not see is the responsibility behind it.
Security personnel work in a job where they are expected to remain alert, deal with people throughout the day, enforce procedures, and sometimes say “No” when others are in a hurry. They face repeated questions, arguments, and pressure to make exceptions. Long hours, fatigue, inadequate training, and the absence of proper communication skills can sometimes turn firmness into irritation — and irritation into rude behavior.
But understanding the reason does not make poor behavior acceptable. A security guard has the right to be firm. He does not have the right to be disrespectful.
At the same time, the person being checked has a responsibility to understand that the guard is performing a duty — not personally challenging them. An ID check is not an insult. A request to wait is not an act of disrespect. A refusal to bypass a procedure is not an attempt to inconvenience someone.
The standard is simple: security must be firm, but the manner must remain professional. That requires more than telling guards to “be polite.” It requires training them to communicate, teaching them how to handle difficult situations, making procedures clear, and giving them the confidence to enforce rules without becoming confrontational.
And it requires all of us to recognise that respect works both ways. Because good security is not just about what we enforce. It is also about how we enforce it.
Myth vs Reality
“To be effective, Security has to be tough.”
Security has to be professional. A security guard must be firm when necessary, calm under pressure, clear in communication, and respectful in conduct. Stopping someone, checking an ID, refusing entry, or enforcing a procedure does not require shouting, arguing, or humiliating the person. Authority does not come from aggression. It comes from knowing the procedure, applying it consistently, and communicating it with confidence.
SECURITY SKILLS NEED PRACTICE TOO
Building better behaviour through regular training
Good security is not created by giving a guard a uniform and a set of instructions. The way a guard speaks, listens, handles pressure, and resolves a difficult interaction are skills — and skills improve with practice.
At RBU, behavioural improvement in the Security team will therefore be approached as a continuous training process, not as a one-time lecture. Regular soft-skill training and behavioural briefings will focus on practical situations that security personnel actually face: dealing with an angry student, stopping a faculty member at the gate, handling an impatient visitor, refusing an unauthorized request, responding to a complaint, or managing a disagreement without allowing it to escalate.
The objective is not to make Security less firm. It is to bridge the gap between firmness and courtesy.
WHEN SECURITY BEHAVIOUR BECOMES THE RISK
Security incidents do not always begin with a physical threat. Sometimes they begin with a tone, a gesture, or a poorly handled conversation.
“I KNOW WHO YOU ARE”
Familiarity should never replace verification. But verification should also never become an unnecessarily confrontational exercise. Professional Security verifies without making the person feel suspected.
THE RAISED VOICE
The moment a routine security conversation becomes a shouting match, the risk has changed. What began as an ID check or gate-pass issue can quickly spiral into an unnecessary campus confrontation.
“JUST LET ME GO”
Pressure, urgency, or seniority should not make a security procedure disappear. At the same time, the guard must know how to communicate the requirement without turning a routine restriction into a personal conflict.
THE WRONG BODY LANGUAGE
Pointing fingers, blocking someone aggressively, standing too close, sarcastic remarks, or dismissive gestures can escalate an otherwise manageable situation. Professionalism is visible before a single word is spoken.
THE ESCALATION GAP
A good security system must know when a guard should stop arguing and call a supervisor. Not every disagreement needs to be won at the gate. Some need to be escalated smoothly through proper channels.
WHEN A SECURITY CHECK BECOMES A CONFRONTATION
Case Study: Freshers' Party Auditorium Access Dispute
The Situation Examined
During Saturday's Freshers' Party, a faculty member on duty at the Auditorium raised a complaint about the manner in which the Security In-charge spoke to her while she was carrying out her responsibility of maintaining student discipline.
The matter was looked into. The situation, on examination, was more nuanced than the complaint alone suggested. The Auditorium was already full to capacity, and every time the faculty member came out through the entrance and then attempted to re-enter, opening the door created an opportunity for students waiting outside to rush inside. Security personnel were struggling to control the crowd and prevent further entry. The Security In-charge therefore asked the faculty member to remain either inside or outside so that the entrance could be controlled.
The security concern was genuine. The manner in which it was communicated was not. The faculty member was performing a bona fide duty. At the same time, understanding the operational difficulty at the entrance would have helped avoid friction. The lesson is not about deciding who was right or wrong — it is about recognizing how a simple operational challenge can become a personal confrontation when communication breaks down.
What Should Have Happened
Security should have explained calmly: “Ma'am, we understand you are on duty. The auditorium is completely full and every time this door opens, students are trying to rush inside. May we request you to coordinate with us so that we can manage the entrance safely?”
The same operational instruction — a completely different outcome.
The Core Learning
- Security personnel will sometimes have to say “No,” “Please wait,” or “You cannot enter this way.” That is part of their job. But how they say it matters.
- Those working with Security also need to understand the operational challenges that may not always be visible from the other side of the gate or door.
- A security problem should never become a people problem. Firmness is necessary. Courtesy is not optional.
LOST, FOUND & RETURNED
The Phone That Is Still Being Hunted
Thursday: A fresher was practicing for the cultural programme at the Basketball Ground when he accidentally dropped his Nokia keypad phone. He realised only after some time and returned to the ground, asking students if anyone had seen it.
He was told that a girl student had found the phone and was asking around to locate its owner. But no one knew who she was. That was enough for Security to start looking. The possibility that she might be a hosteller led to messages being circulated in the hostel WhatsApp groups, and the wardens were alerted. Security also continued checking for information. But so far, no one has come forward. The search is still on.
THE RULE IS THE RULE. THE PERSON IS STILL A PERSON.
Security has a difficult job. There will be moments when a guard has to stop a faculty member, question a visitor, refuse a request, or control a crowd. Sometimes the person on the other side may be in a hurry, may not understand the situation, or may strongly disagree with the decision.
But there is an equally important responsibility on the Security side: never allow firmness to become rudeness.
At the same time, those of us on the other side of the security process must recognise that the guard may be dealing with a crowd, an access-control problem, an overcrowded venue, or a situation that we cannot immediately see. The answer is not to choose between Security and the campus community. The answer is to make both sides understand each other better.
As Head of Security Operations, my responsibility is clear: I will not dilute security procedures. But I will insist that my team learns to communicate those procedures professionally. Regular soft-skill training, scenario-based briefings, and supervisory feedback will become part of that effort.
And I would ask the University community for one thing in return: if a security decision appears wrong, question it through the proper channel — but do not turn the gate, corridor, or venue entrance into the place where the argument is fought.
The Security team must learn to stop, listen, explain, and act. The campus community must know that Security is there to protect, not provoke. We will not compromise on security. We will not compromise on courtesy either. That, ultimately, is the other side of security — protecting the campus without losing respect for the people we are protecting.
94656 00041
Save it. Share it. Immediate assistance is a call away.