The IT Checklist for Closing the Office Over Summer
TL;DR: The shutdown list has five headings: power off the clients, leave the server/NAS running and monitored; verify the final backup; wire the server-room temperature to an alarm (the empty office's number-one risk is the air conditioning); actually test remote access; and leave the emergency chain (who gets called, who holds keys) in writing. The return morning starts with the power-up order: network first, then servers, then clients.
Many businesses close collectively for a week or two in summer; production stops, phones switch to auto-reply, doors lock. For IT systems there is no such thing as a holiday: the server keeps running, backups keep writing, email keeps flowing — and if something goes wrong, nobody is in the corridor to notice. The empty-office weeks are the year's quietest and riskiest IT period; this list exists to pass them without incident.
One Week Before the Shutdown
- Schedule pending updates early: server and critical-system updates happen a week before the shutdown, not on its eve — if something breaks, the team is still there. A big change on closing eve entrusts the problem to the holiday.
- Take proof of the backup: a final full backup is taken and verified with a sample restore; the off-site copy is confirmed current. For the empty office's worst scenarios — fire, flood, burglary — this is the only real answer.
- Actually test remote access: a real VPN connection is attempted to every system someone might "just check" during the holiday (cameras, critical applications, server management) — a broken VPN discovered after the shutdown stays broken. MFA devices and vault access travel with the people going on leave.
- Write the emergency chain: who is called if the alarm fires, who can enter the building, what is IT support's holiday number — one page, held by both management and building security.
The Last Day: the Shutdown Order
| System | Decision | Note |
|---|---|---|
| User computers | Off | Energy saving + storm risk; unplugging is cleanest |
| Server / NAS | Leave on | For backups, mail flow and remote access; must be monitored |
| Network backbone (modem, firewall, switches) | Leave on | On the UPS; this is remote access's road |
| Cameras and alarm | Leave on | Check recording space; try remote viewing |
| Printers, screens, office devices | Off | Standby drain + needless risk |
| Air conditioning (server room) | On — and alarmed | See below: the empty office's number-one risk |
The Empty Office's Number-One Risk: Heat
The classic summer-shutdown disaster: the server room's air conditioning fails on day two, the room temperature climbs, and the server either shuts itself down in self-protection or meets hardware damage — unseen for two weeks. Prevention is three layers: an independent temperature sensor + phone alarm in the room (the server-room edition of cold-chain logic), an automatic safe-shutdown threshold on the server at high temperature, and pre-holiday servicing of the air conditioner where possible. On the electrical side, the UPS arrangement is storm season's insurance.
The Digital Side: Closed but Not Vanished
- Auto-replies and forwarding: date-ranged auto-replies on all addresses including shared boxes; a duty address/phone for urgent matters. A holiday announcement on the PBX and mobile forwarding where needed.
- Duty access: decide who checks the channels that keep flowing — e-commerce, the quote form — and how often. "We'll look when we're back" is a two-week customer loss in some businesses.
- A phishing note: holiday season is the season of "the MD needs an urgent transfer from abroad" scenarios; one line in the closing email reminds the team that the verification reflex stays on holiday too.
The Return Morning: the Power-Up Order
Day one starts with an order, not with coffee: verify network and internet first; check server/NAS health and the holiday's backup runs; review pending updates; power up the clients; run a five-minute function test (email, shared folders, printer, business application). Read the alert list that accumulated over the holiday that same morning — if the systems talked for two weeks, do not start the week without hearing what they said.
The Holiday Period with Yamanlar Bilişim
For customers under a maintenance agreement, shutdown week is a standard service window: the pre-closing check (backup verification, temperature alarm, remote-access test) runs on our checklist, systems stay under our monitoring through the holiday, and critical alerts land with us, not with an empty office. On the return morning the report is waiting: what happened, what was done, what is clean.
FAQ
Frequently Asked Questions
Couldn't we shut the server down too — nobody will use it for two weeks?
You can — as a conscious decision with the right order: if email is in the cloud and no remote access is needed, a powered-off server is the safest server. But backup jobs, integrations and return-day boot risks must be counted; the "off" decision needs as much planning as "leave on".
Does the temperature alarm need an expensive system?
No; network-attached sensors that alert on threshold violation are modestly priced. What matters is not the device but the chain: sensor → alert → the person who will see that alert on holiday. Define all three and the system works.
If something breaks during the holiday, how does anyone respond — everyone is away?
Three levels are built in advance: remote intervention (VPN + management access solves most problems), on-site access (an authorised person who can enter + key/alarm plan) and the support provider's holiday availability. For a business with a maintenance agreement, all three are already in the contract.
Building management wants to cut all power during the shutdown — what do we do?
Ensure the server/network line stays on its own breaker and settle it with building management in writing: which circuit stays on, and who is informed if a cut becomes necessary. The unannounced breaker is the classic opening scene of holiday failures.
We work partially — the office is empty but the team continues from home. Does the list change?
The core stays; two emphases grow: remote-access capacity (if everyone connects at once, do the line and licences suffice?) and physical monitoring of the office (an unattended office plus active systems makes the heat and security alarms even more critical).
Author
Serdar YAMAN
Yamanlar Bilişim Expert
Writes content on IT infrastructure, cybersecurity, and digital transformation at Yamanlar Bilişim. Get in touch for any questions.
Professional Support
Get help on this topic
Let's design the IT Management solution you need together. Our experts get back to you within 1 business day.
support@yamanlarbilisim.com · Response time: 1 business day
Keep Reading
Related Articles
Turkey's e-Invoice and e-Archive Mandate: the IT Readiness Guide
The scope of Turkey's electronic invoicing mandate widens every year, and in most companies the transition gets squeezed into the final week. Integration method, accounting-software compatibility, the fiscal seal, ten-year archiving and the outage plan — the IT half of the regulation, in one guide.
The Office-Move IT Checklist: Everything Working by Monday Morning
In an office move, furniture fits in the truck; what stops the business is the internet not yet connected, the phones silent, the server not powered up. A scheduled, field-tested IT checklist running from eight weeks out to the post-move tail.
The New-Employee IT Onboarding Package: a System That Works at 09:00 on Day One
A new employee's first day is the first photograph of how the organisation runs: a ready device and open accounts at their desk, or three days of "we told IT, we're waiting"? The onboarding package built on role-based access templates and one trigger from HR.