A good IT manager’s day should begin with control, not chaos. Before the inbox, meetings and urgent requests take over, a short and repeatable review can expose overnight failures, clarify priorities and give the support team a shared plan.
This daily IT manager checklist covers the signals that matter most: service health, security, backups, tickets, changes, business risk and handover. It is designed for busy internal IT teams, outsourced support leads and anyone responsible for keeping technology secure, available and useful.
The aim is not to check everything manually. It is to confirm that monitoring is working, review exceptions, assign ownership and decide what needs attention before users discover it first.
What should a daily IT checklist achieve?
A checklist should help you make decisions, not create another administrative task. By the end of the morning review you should be able to answer five questions:
- Are our critical systems and services available?
- Did anything fail, degrade or change overnight?
- Are our data, users and devices adequately protected?
- Which tickets, risks and planned changes need an owner today?
- What must colleagues or senior stakeholders know?
For most organisations, a focused review takes 15 to 30 minutes. If it regularly takes much longer, that is often a sign that alerts are too noisy, information is spread across too many systems or responsibilities are unclear.
The first 30 minutes: establish operational control
1. Review overnight alerts and critical services
Start with the systems that would stop the organisation from working: internet connectivity, identity, email, core business applications, servers, storage, telephony and remote access. Check the monitoring platform and service dashboards before relying on user reports.
- Look for outages, degraded performance and alerts that have repeated overnight.
- Confirm critical services are reachable from the locations where staff actually work.
- Review cloud-provider and supplier status pages for acknowledged incidents.
- Check whether today includes a deadline, event, payroll run, onboarding or other business-critical activity.
Top tip: maintain a short list of “business-critical today” services. The technical priority is not always the business priority; a normally minor system can become essential on the day it is needed for a deadline.
2. Triage security signals
Review high-severity alerts from identity, endpoint protection, email security, firewalls and cloud platforms. Pay particular attention to unusual sign-ins, impossible travel, newly created privileged accounts, malware detections, suspicious inbox rules and disabled security controls.
Do not measure security health by the number of alerts closed. Confirm that each meaningful alert has evidence, an owner and a next action. If an incident may still be active, preserve logs and begin the incident process before making broad changes that could destroy evidence.
If you need urgent assistance, Astley Digital provides emergency recovery support for cyber incidents, compromised websites, failed servers and attacks.
3. Verify backup and recovery health
A successful job notification is useful, but it is not the same as a recoverable backup. Review failures and missed jobs, storage capacity, retention, protected-system coverage and the date of the last successful restore test.
- Investigate every failed or incomplete backup; do not allow failures to become normal.
- Confirm new systems and users have been added to protection policies.
- Check that at least one copy is suitably isolated from the production environment.
- Track repository capacity and retention changes before storage becomes critical.
- Schedule restore tests and record the result, recovery time and any missing dependencies.
Microsoft 365 and Google Workspace still need an independent recovery plan. Our fully managed cloud backup service protects users from accidental deletion, retention gaps and account compromise.
Control the support queue before it controls the day
Review the ticket queue as a risk register, not simply a list ordered by arrival time. Consider impact, urgency, age, contractual target and whether work is blocked. A single issue affecting payroll or a new starter may deserve attention before ten low-impact requests.
4. Check the support workload
- Unassigned: every actionable ticket should have a clear owner.
- Awaiting a reply: identify tickets stalled by the customer, a colleague or a supplier.
- Ageing: challenge tickets that have remained open without a meaningful update.
- Reopened: look for incomplete fixes or recurring root causes.
- SLA risk: act before a target is missed, not after the report turns red.
- High-impact changes: watch joiners, leavers, permissions and access requests carefully.
Top trick: insist that every active ticket has one owner, one next action and one next review time. “In progress” is not a useful plan by itself.
5. Run a short team huddle
A five-minute huddle can prevent duplicated work and quiet assumptions. Cover the most important service risk, who is handling it, planned changes, absences and anything another team member may need to take over. Keep deep troubleshooting outside the huddle unless everyone genuinely needs to contribute.
Review today’s changes and maintenance
Unexpected change causes a large share of avoidable incidents. Review scheduled deployments, patches, supplier work and configuration changes before they happen.
For each material change, confirm:
- a named owner and an approved time window;
- the expected outcome and a practical test plan;
- a backup or recovery point where appropriate;
- a rollback plan that can actually be performed;
- the people who need advance or completion communication;
- any dependency on a supplier, licence, credential or colleague.
For high-risk work, define the point at which you will stop and roll back. Deciding this during an incident is much harder than deciding it beforehand.
Use a midday reset
The morning plan rarely survives unchanged. Take five minutes around midday to review new priority tickets, unresolved alerts, supplier updates and work that is drifting. Reassign tasks if needed and tell stakeholders early when a timescale or service level is at risk.
This small reset is particularly valuable on busy service desks: it catches work that arrived after the morning review and prevents a difficult issue from quietly sitting with someone who needs help.
End the day with a useful handover
A strong handover records what the next person needs to act, not a diary of everything that happened. Capture:
- active incidents and current business impact;
- what has already been tried and the evidence gathered;
- the next action, owner and expected update time;
- changes completed, deferred or rolled back;
- supplier cases and their reference numbers;
- anything that must be checked overnight or first thing tomorrow.
Before signing off, confirm that critical alerts are owned, backup failures are escalated, urgent tickets have been updated and scheduled overnight work is understood.
Seven tips that make the checklist work
- Time-box the routine. Review dashboards and exceptions; do not spend the entire morning gathering data manually.
- Use red, amber and green consistently. Define what each status means so that risk is comparable across services.
- Record evidence. A timestamp, screenshot, alert reference or restore result is more useful than “checked and fine”.
- Write actions with an owner and time. “Alex to contact the supplier by 10:30” is actionable; “awaiting supplier” is not.
- Automate collection, not judgement. Let monitoring gather signals, then use human review to understand impact and priority.
- Remove noisy alerts. Alerts that nobody trusts hide the one warning that matters. Tune, route or retire them.
- Test recovery regularly. A backup strategy is only credible when a representative restore has succeeded and been documented.
How to use the printable IT checklist
The Astley Digital printable contains two complementary sheets:
- Page 1 — Daily IT manager checklist: use this for the morning control review, security and backup status, important changes, risks and decisions.
- Page 2 — Daily support checklist and handover: use this with the service desk to track priority tickets, suppliers, maintenance and end-of-day ownership.
You can print one copy each day, laminate a blank copy for a physical control board or use the headings to build the same rhythm into your ticketing and documentation platform.
Turn daily checks into managed assurance
A checklist is most effective when it sits behind reliable monitoring, clear documentation and people who have time to act. Astley Digital can support your internal team or take responsibility for day-to-day operations through our managed IT services, managed server services, cloud backup and responsive technical support.
If you want fewer surprises and clearer ownership across your IT environment, talk to our team. Existing customers can also raise a support ticket whenever they need help.
Ready for a clearer technology plan?
Tell us what is slowing your organisation down. We will help you identify the practical next step.
