Same-Day Emergency Requirements for GCCs and Coworking Spaces

Emergency, urgent or routine: agree the definitions first

If every request is an emergency, the label stops meaning anything. Your vendor cannot prioritise, your admin team pays for premium handling on jobs that could have waited, and the genuine emergencies queue behind the noise. The first job is a shared definition, written on one page and signed off by facilities, admin and the building’s management.

The emergencies that keep recurring

Start with your own incident log. On most GCC floors and in most coworking centres, the same handful of failure types come up:

• Tripped or failed DB or UPS, leaving a floor or a rack without power.
• Water leaks from pantry, washroom or ceiling lines, more likely to surface during the south-west monsoon (roughly June–September) when roof and terrace drainage is tested.
• Access-control or door failures: staff locked out, or a door that will not secure at night.
• HVAC failure in a meeting-critical or equipment area.
• Broken glass in partitions, doors or façade panels.
• Lighting outages in critical areas such as stairwells, corridors and exit routes.

Build a pre-approved item list and rate card, and keep spares on site

In many emergencies the slowest step is not the repair. It is working out what to buy, who can approve it and whether the gate will let it in. A pre-approved list removes the first two.

Start from your incident log and your asset register. List the items you are most likely to need, with a specification for each: for example MCBs and RCCBs in the ratings your DBs actually use (MCBs are covered by IS/IEC 60898-1; check the current edition and confirm ratings with your electrical engineer), emergency-light batteries or fittings, door closers and lock sets for your common door types, glass in your common partition sizes, and pipe fittings, flexible connectors and float valves for pantry and washroom lines. Building a maintenance catalogue covers how to structure such a list.

Then agree a rate card with your vendor for those items and for the attendance or labour on standard emergency jobs, including any after-hours terms. Add the approval rule: who can approve spend within the rate card, and who approves anything outside it. Both belong in the contract or purchase-order framework, so nobody negotiates during the incident.

Keep critical spares on site

A fast vendor still cannot beat a spare sitting in your store room. Choose on-site spares with two questions: which failure stops work or creates a safety risk, and how long would it take to source that part in your location? Items that score high on both belong on the shelf. Critical spares to stock by facility type gives a starting list for different buildings.

Keep spares in one labelled cabinet, note a minimum quantity for each, record every issue and replace what is used. A GCC will usually hold more electrical and IT-adjacent spares; a coworking operator will tend to hold more door, lock and access-control items, plus plumbing basics for shared pantries. Spares only help if people know they exist, so list the cabinet contents in the escalation document.

One call point and an escalation matrix

During an incident people phone whoever they know. Fix that with a single call point on your side and a single call point at the vendor, ideally a monitored number or shared channel and not one person’s mobile.

1. Level 1 – on-site facility executive: raises the request in the agreed format and keeps the area safe.
2. Level 2 – facility or admin manager: approves spend outside the rate card and deals with building management and tenants.
3. Level 3 – vendor coordinator or account manager: confirms the response plan and the expected arrival.
4. Level 4 – senior contacts on both sides: invoked when the agreed time-box passes without progress.

Publish the matrix with names and numbers, and check it every quarter. The time-boxes for each level are for you and the vendor to agree for your site; do not copy them from another building.

What to include in an emergency request

An incomplete request costs a round of clarification calls. Use one template, whether the request goes by phone, email or a messaging group.

Access is the constraint people forget. In a multi-tenant tech park or a leased floor, the vendor may need a gate pass, a material-movement permit or building-management approval before anyone can walk in with a part. Keep a standing approved-vendor list with the security desk and building management so the permit step is a formality.

After-action review

Every emergency is data. Within a few days, hold a short review and record:

• What failed, and the root cause as far as it is known.
• Whether preventive maintenance or a spare would have avoided the failure or shortened it.
• Where time was lost: identifying the part, approval, access or travel.
• Whether the emergency classes, rate card and escalation matrix worked as written.
• What changes to the item list, spares cabinet or permit process follow.

Track repeats by location and asset. A DB that trips repeatedly is not an emergency problem, it is a maintenance problem, and it belongs on the planned work list.

How SupplycZar can help

SupplycZar supplies recurring facility supplies and delivers managed maintenance from Bengaluru. We do not quote a blanket turnaround time: response options and coverage are confirmed for each site, and a defined emergency requirements arrangement is set up in advance, alongside your recurring facility supplies. To start, send your site details, the draft emergency item list and any access rules through the RFQ form.