FirstHR

IT Coordinator Job Description Templates

IT coordinator job description templates for small businesses: 6 versions covering support, assets, projects, and the first IT hire. Free DOCX.

Nick Anisimov

Nick Anisimov

FirstHR Founder

Hiring
16 min

IT Coordinator Job Description Templates for Small Businesses

6 free templates: standard in-house, first IT hire with a provider, support coordinator, asset and procurement, project coordinator, and the hybrid office and IT role. Download as DOCX.

The first time I had to hire an IT coordinator, I could not write the posting. I knew exactly what was broken: nobody knew which laptop belonged to whom, two people who had left six months earlier still had live accounts, and a subscription renewed for a full year on a card nobody was watching. What I could not do was turn that list into a job title.

So I copied a generic IT posting, which asked for server administration and network design, and paired it with a budget anchored to a support salary. Nothing good applied. The technical candidates saw an underpaid engineering job. The organized candidates saw a role they were not qualified for. The gap was mine, not theirs.

An IT coordinator is a coordination role that happens to be about technology. That distinction changes the duties, the screening, the pay benchmark, and the overtime classification. At FirstHR we write hiring templates for small companies without a dedicated IT or HR function, and the six below cover the situations that title actually describes.

TL;DR
An IT coordinator owns the organizational layer of company technology: accounts and access, assets and licenses, ticket triage, vendors, and documentation. Most of these roles are non-exempt, because the federal computer employee exemption requires a primary duty of systems analysis or programming. The nearest wage benchmark, computer user support specialists, has a $61,860 national median. Six templates below, downloadable as DOCX.

What an IT Coordinator Actually Does

An IT coordinator keeps company technology organized, current, and accounted for. The work centers on user accounts and access rights, hardware and license inventory, intake and triage of support requests, vendor coordination, and documentation. Solving hard technical problems is a secondary duty, not the core one.

That framing matters because it sets the screening criteria. The failure mode in this role is a stale inventory or an account that stayed live after someone left, not an unsolved technical fault. Hire for follow-through and record keeping, and treat certifications as a bonus rather than a gate.

The internal owner
You have an MSP, not a person
An outside provider handles servers and networks, but nobody inside the building owns accounts, devices, or licenses. The coordinator becomes the single point of contact and holds the provider to the service agreement.
The queue owner
You have technicians, not order
The technical people can fix things, but requests arrive through four channels and nothing gets logged. The coordinator owns intake, triage, assignment, and follow-up so the team stops working from whoever shouted last.
The asset owner
You are paying for seats nobody uses
Laptops leave with departing employees and subscriptions renew unread. The coordinator builds the inventory and the renewal calendar, which usually pays for a meaningful share of the salary in the first year.
The project owner
You have a migration to survive
A system migration, an office move, or a device refresh needs scheduling, vendor coordination, and user communication. That is coordination work, and giving it to your most technical person is why it keeps slipping.
Name the Gap Before You Name the Role
Write down the three things that are actually broken before you write a single duty. If the answer is stale records, missed renewals, and access nobody revokes, you need a coordinator. If the answer is a network that keeps failing and servers nobody maintains, you need a systems administrator and a different budget. Most bad IT postings are a coordinator problem described in engineer language, and no candidate can fix that mismatch for you.

IT Coordinator vs Specialist, Technician, and Manager

The IT titles ladder by technical depth and by scope of ownership, and coordinator sits at the organizational end rather than the technical end. A coordinator routes and records. A specialist or technician resolves. An administrator owns the systems. A manager owns the function, the budget, and the people.

Picking the wrong rung is expensive in both directions. Post a coordinator role at technician pay and you will get applicants who leave once they realize the work is administrative. Post a technician role with coordinator duties and the inventory stays broken while your new hire chases tickets.

TitleWhat the role centers onNearest BLS classification and May 2025 median
IT coordinatorAccounts, assets, licenses, triage, vendors, documentationNo exact match; benchmark to computer user support specialists, $61,860
IT support specialist or help deskResolving what users report, at the ticket levelComputer user support specialists, $61,860
IT technicianHands-on devices: imaging, deployment, repair, peripheralsComputer user support specialists, $61,860
Network support specialistNetwork and server-side troubleshootingComputer network support specialists, $76,220
Systems administratorOwning and maintaining systems and infrastructureNetwork and computer systems administrators, $99,130
IT manager or directorOwning the IT function, the budget, and the staffComputer and information systems managers, $175,140

If the role you are describing sits between two rungs, name the split explicitly rather than averaging it. Our IT support specialist templates cover the resolution end of that ladder, and the IT manager templates cover the ownership end.

What Belongs in the Posting

An IT coordinator posting has to do four jobs: define the environment, filter for the right kind of candidate, protect you legally, and close the hire. The environment section is the one most postings skip, and it is the one candidates need most.

The parts that set the scope
Headcount, locations, and number of devices you support
The platform you run: Microsoft 365 or Google Workspace
Whether an MSP exists and what it already covers
Who this role reports to and who it escalates to
The parts that filter applicants
Split between coordination and hands-on technical work
Approval limit for purchases, stated as a number
Ticket volume per week, so candidates can picture the load
Certifications marked preferred rather than required
The parts that protect you
FLSA classification stated on the posting
On-call expectations and how on-call time is paid
Access to confidential systems and the confidentiality terms
Equal opportunity statement and essential functions
The parts that win the hire
Pay or a good-faith range, hourly if the role is non-exempt
Certification and training budget
Autonomy: what this person gets to decide alone
A named contact and a real response timeline

Two numbers do more work than any paragraph of prose: ticket volume per week and the purchase approval limit. The first tells a candidate how reactive the job is. The second tells them how much authority they actually get, which is the honest answer to how senior the role is. Our guide to writing a job description covers the general structure in more depth.

6 IT Coordinator Job Description Templates to Download

Download all six as one file or copy them individually. Each follows the same structure: company overview, position summary, key responsibilities grouped by area, required qualifications, a classification and compliance note, an equal opportunity statement, and how to apply. The bracketed fields are the only parts you need to change.

Download All 6 IT Coordinator Job Description Templates
Standard in-house, first IT hire, support coordinator, asset and procurement, project coordinator, and hybrid office and IT. All in one download.
Standard, In-House
The general version
Accounts and access, support triage, assets and licenses, vendors, and documentation. Use this when you already have some IT structure and need the coordination layer.
First IT Hire, Co-Managed
You plus a provider
For a small business with a managed service provider and no internal IT. Built around escalation judgment and holding the vendor to what it agreed to deliver.
IT Support Coordinator
The queue is the job
For an existing support function that needs intake, triage, assignment, follow-up, and reporting owned by one person rather than shared by everyone.
Asset and Procurement
Inventory, licenses, spend
For hardware records, subscription renewals, purchase requests, and invoice reconciliation. The version with the clearest and fastest return on the hire.
IT Project Coordinator
Rollouts and migrations
For scheduling, dependency chasing, vendor coordination, user communication, and closeout on technology projects. Often a fixed-term posting.
Office and IT Coordinator
Two jobs, one person
For the very small company where technology sits with the office coordinator. Includes the percentage split so the posting is honest about the scope.

Template 1: IT Coordinator (Standard, In-House)

The general version, with responsibilities grouped into accounts and access, support and triage, assets and licenses, vendors, and documentation. Use it when some IT structure already exists and the coordination layer is what is missing.

IT Coordinator Job Description (Standard, In-House)
IT COORDINATOR JOB DESCRIPTION
Company: __ ([City, State])
Reports to: [Operations Manager / IT Manager / Office Manager / Owner]
Employment type: Full-time
FLSA status: Non-exempt (hourly, overtime-eligible) unless a duties test is
clearly met. See the classification note.
Compensation: $_ per [hour / year]

ABOUT [COMPANY NAME]

[Company Name] is a [industry] company in [City, State] with [number] employees
across [number] locations. We run on [Microsoft 365 / Google Workspace], [device
platform], and roughly [number] business applications. We are hiring an IT
Coordinator to keep all of it organized, current, and accounted for.

POSITION SUMMARY

The IT Coordinator is the day-to-day point of contact for technology at
[Company Name]. This role handles user accounts and access, tracks hardware and
software licenses, triages and routes support requests, coordinates outside
vendors, and keeps IT documentation accurate. It is a coordination role first
and a hands-on technical role second.

KEY RESPONSIBILITIES

Accounts and access
Create, modify, and disable user accounts across all company systems
Run the technology portion of onboarding: accounts, device, email, licenses,
and access to the specific applications each role needs
Run the technology portion of offboarding: revoke access, recover the device,
reassign licenses, and confirm each step in writing on the last day
Maintain the access matrix that records who has rights to what and why
Support and triage
Receive support requests through [ticket system / email / chat] and log them
Resolve routine issues: password resets, printer and peripheral problems,
application access, basic device setup and configuration
Escalate anything beyond first-line scope to [internal IT / our managed
service provider] and track it to resolution
Keep requesters informed on status rather than leaving tickets silent
Assets and licenses
Maintain the hardware inventory: serial number, assigned user, purchase date,
warranty end, and current location for every device
Track software subscriptions and license counts, and flag renewals [number]
days before they auto-renew
Manage the device lifecycle: procurement, imaging, deployment, refresh, and
secure disposal or wipe
Vendors and coordination
Serve as the first point of contact for [ISP, phone, MSP, software vendors]
Collect quotes, submit purchase requests, and reconcile IT invoices against
what we actually use
Coordinate scheduling for installations, migrations, and site visits
Documentation and security basics
Keep IT documentation, runbooks, and asset records current
Support security routines: multi-factor authentication enrollment, patch and
update tracking, backup verification, and security awareness training
completion
Report suspected security incidents immediately under our incident procedure

REQUIRED QUALIFICATIONS

[Associate degree / bachelor's degree / equivalent experience: set your bar]
[Number] years in an IT support, help desk, or IT administration role
Working knowledge of [Microsoft 365 / Google Workspace] administration
Comfort with [Windows / macOS] device setup and basic network troubleshooting
Organized record keeping: this role fails on messy inventories, not on hard
technical problems
Clear written communication with non-technical colleagues
[CompTIA A+ / Microsoft or Google administrator certification: preferred]

CLASSIFICATION AND COMPLIANCE NOTE (read before posting)

Most IT coordinator roles are non-exempt: hourly and entitled to overtime past
40 hours in a week. The FLSA computer employee exemption is written for
employees whose primary duty is systems analysis, program design, or software
development, and the Department of Labor states plainly that employees whose
work merely depends heavily on computers are not covered by it. Coordination,
support, procurement, and record keeping are not systems analysis. The
administrative exemption is available only where the role genuinely exercises
discretion and independent judgment on matters of significance, such as owning
vendor selection or an IT budget, and it requires payment on a salary basis at
or above the federal threshold. Title alone decides nothing. If this role is
non-exempt, track hours, including after-hours device setup and weekend
migration work. This is general information, not legal advice.

EEO STATEMENT

[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.

COMPENSATION AND HOW TO APPLY

Compensation: $_ per [hour / year], [benefits summary], [on-call policy
and how on-call time is paid]
To apply, email __ with your resume.

Template 2: IT Coordinator (First IT Hire, Co-Managed with a Provider)

For a small business with an outside provider and no internal IT staff. It is built around escalation judgment and vendor accountability rather than technical depth, because that is what the role genuinely needs.

IT Coordinator Job Description (First IT Hire, Co-Managed with an MSP)
IT COORDINATOR JOB DESCRIPTION (FIRST IT HIRE, CO-MANAGED)
Company: __ ([City, State])
Reports to: [Owner / Operations Manager / Finance Manager]
Employment type: Full-time [or part-time at ___ hours per week]
FLSA status: Non-exempt (hourly, overtime-eligible)
Compensation: $_ per hour

ABOUT THIS ROLE

[Company Name] has [number] employees and no internal IT staff. Our systems are
supported by [Managed Service Provider name], who handle servers, network, and
anything deep. What we do not have is anyone inside the building who owns the
day-to-day: accounts, devices, licenses, and the questions that arrive before
anyone thinks to open a ticket. This is that role.

POSITION SUMMARY

The IT Coordinator is our internal technology owner and the single point of
contact between [Company Name] and our managed service provider. You handle
first-line requests, keep the asset and license records straight, run technology
onboarding and offboarding, and make sure the provider is delivering what we
pay for.

KEY RESPONSIBILITIES

Act as the single internal point of contact for all technology questions
Handle first-line support: accounts, passwords, devices, printers, [core
applications]
Decide what to resolve internally and what to escalate to the provider, then
track escalations to closure instead of letting them drift
Own the relationship with our managed service provider: run the [monthly /
quarterly] review, check performance against the service agreement, and raise
issues before they become renewals
Run the technology steps of onboarding and offboarding on the dates HR gives
you, and confirm each step in writing
Maintain the device inventory and the software subscription list, including
renewal dates and true seat counts
Collect quotes and submit purchase requests for approval
Keep our documentation current: what we run, who has access, where things are
Support security basics: multi-factor authentication, patch status, backup
verification, and completion of security awareness training

REQUIRED QUALIFICATIONS

[Number] years in IT support, help desk, or a technology-adjacent operations
role
Working knowledge of [Microsoft 365 / Google Workspace] administration
Ability to work independently: you will often be the only technology person
in the building
Judgment about when to escalate, which matters more here than deep expertise
Organized documentation habits and clear written communication
Comfort holding a vendor to what they agreed to deliver

CLASSIFICATION AND COMPLIANCE NOTE

Treat this role as non-exempt unless a qualified professional tells you
otherwise. A first IT hire at a small company almost never meets the FLSA
computer employee exemption, which requires a primary duty of systems analysis
or programming, and rarely meets the administrative exemption while the work is
first-line support and coordination rather than independent judgment on matters
of significance. Non-exempt means tracked hours and overtime past 40 in a week,
which matters in this role because evening device setup, weekend migrations, and
after-hours outage response are real. Set an on-call policy in writing and
decide how on-call hours are paid before the first incident, not after. This is
general information, not legal advice.

EEO STATEMENT

[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.

COMPENSATION AND HOW TO APPLY

Compensation: $_ per hour, [benefits summary], [on-call and after-hours
pay policy]
To apply, email __ with your resume.
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
See How It Works

Template 3: IT Support Coordinator (Help Desk and Triage)

For an existing support function where the queue itself needs an owner: intake, triage, assignment, follow-up, and reporting. Pair it with the help desk templates if you are also hiring the people who resolve the tickets.

IT Support Coordinator Job Description (Help Desk and Triage)
IT SUPPORT COORDINATOR JOB DESCRIPTION
Company: __ ([City, State])
Reports to: [IT Manager / Support Lead]
Employment type: Full-time
FLSA status: Non-exempt (hourly, overtime-eligible)
Compensation: $_ per hour

ABOUT THIS ROLE

[Company Name] runs a support queue of roughly [number] requests per week across
[number] employees. We are hiring an IT Support Coordinator to own the queue
itself: intake, triage, assignment, follow-up, and reporting. This is the role
that makes a small support team feel organized instead of reactive.

POSITION SUMMARY

The IT Support Coordinator manages the intake and flow of technology support
requests. You log and categorize every request, resolve first-line issues,
assign the rest to the right person or vendor, chase anything that stalls, and
report on what the queue is telling us.

KEY RESPONSIBILITIES

Monitor [ticket system / support inbox / support channel] and log every
request with a category and a priority
Resolve first-line issues directly: accounts, passwords, access, peripherals,
[core applications]
Assign remaining tickets to [internal technicians / the managed service
provider] using our escalation rules
Follow up on stalled tickets and keep requesters informed on status
Maintain the knowledge base and write short how-to articles for the requests
that repeat most often
Track response and resolution times against our targets and report [weekly /
monthly]
Identify recurring problems and raise the root cause instead of reopening the
same ticket every week
Coordinate scheduled work: patch windows, device refreshes, application
rollouts
Support technology onboarding and offboarding on the dates HR provides

REQUIRED QUALIFICATIONS

[Number] years in a help desk, service desk, or IT support role
Experience with a ticketing or service management system
Strong triage judgment: knowing what is urgent versus what is merely loud
Patience and plain language with non-technical colleagues
Accurate written record keeping under time pressure
[CompTIA A+ / ITIL Foundation: preferred]

CLASSIFICATION AND COMPLIANCE NOTE

This role is non-exempt. Help desk and support coordination work does not
qualify for the FLSA computer employee exemption, which is reserved for
employees whose primary duty is systems analysis, program design, or software
development. Pay overtime past 40 hours in a week, and track hours accurately
including any time spent monitoring the queue outside scheduled shifts. If you
expect coverage outside business hours, write the shift or on-call structure
into the posting so candidates can price it honestly. This is general
information, not legal advice.

EEO STATEMENT

[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.

COMPENSATION AND HOW TO APPLY

Compensation: $_ per hour, [shift differential if any], [on-call policy]
To apply, email __ with your resume.

Template 4: IT Asset and Procurement Coordinator

For hardware records, subscription renewals, purchase requests, and invoice reconciliation. This is the variant with the clearest financial return, because reclaimed seats and caught auto-renewals are measurable in the first year.

IT Asset and Procurement Coordinator Job Description
IT ASSET AND PROCUREMENT COORDINATOR JOB DESCRIPTION
Company: __ ([City, State])
Reports to: [IT Manager / Finance Manager / Operations Manager]
Employment type: Full-time
FLSA status: Depends on duties (see classification note)
Compensation: $_ per [hour / year]

ABOUT THIS ROLE

[Company Name] owns roughly [number] devices and pays for about [number]
software subscriptions across [number] employees. Nobody currently owns the
records for either. We are hiring an IT Asset and Procurement Coordinator to
build and keep that inventory, control renewals, and stop us paying for seats
nobody uses.

POSITION SUMMARY

The IT Asset and Procurement Coordinator owns the full lifecycle of company
technology: what we buy, who has it, what it costs, when it renews, and what
happens when it comes back. The role sits between IT, finance, and every vendor
we buy from.

KEY RESPONSIBILITIES

Asset records
Maintain a complete hardware inventory: serial number, model, assigned user,
purchase date, cost, warranty end, and location
Reconcile the inventory physically [quarterly / annually] and investigate
anything missing
Track the device lifecycle from procurement through refresh to secure wipe
and disposal, with a certificate of destruction where required
Issue and recover equipment with a signed acknowledgment on both ends
Licenses and subscriptions
Maintain the software subscription register: vendor, seat count, cost,
renewal date, and owner
Run a [quarterly] usage review and reclaim seats that are assigned but unused
Flag every renewal [number] days ahead so it is a decision rather than a
surprise charge
Confirm license entitlements match actual deployment
Procurement
Collect quotes, compare options, and submit purchase requests for approval
Track orders through delivery and receipt
Reconcile IT invoices against contracts, seat counts, and delivered goods
Maintain vendor contact records and contract terms in one place
Reporting
Report [monthly / quarterly] on technology spend, upcoming renewals, and
refresh needs
Support the [annual budget] cycle with real numbers from the register

REQUIRED QUALIFICATIONS

[Number] years in IT asset management, procurement, or operations
Advanced spreadsheet skills, or experience with an asset management or IT
service management tool
Comfort reading contracts and license terms closely enough to spot an
auto-renewal clause
Accuracy under volume: this role is judged on whether the records are right
Clear communication with vendors and with internal budget owners

CLASSIFICATION AND COMPLIANCE NOTE

Classification here turns on how much authority the role actually holds. An
asset coordinator who maintains records, processes purchase requests, and
follows an approval workflow set by someone else is performing production work
and is generally non-exempt: hourly and overtime-eligible. A coordinator who
genuinely selects vendors, negotiates terms, and commits budget without prior
approval may meet the FLSA administrative exemption, which requires a primary
duty of office work directly related to management or general business
operations, the exercise of discretion and independent judgment on matters of
significance, and payment on a salary basis at or above the federal threshold.
Decide honestly based on the approval limits you will actually grant, and write
those limits into the job description. The computer employee exemption does not
apply to this role at all. This is general information, not legal advice.

EEO STATEMENT

[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.

COMPENSATION AND HOW TO APPLY

Compensation: $_ per [hour / year], [benefits summary], [purchase
approval limit for this role]
To apply, email __ with your resume.

Template 5: IT Project Coordinator

For migrations, rollouts, office moves, and device refreshes: scheduling, dependency chasing, vendor coordination, user communication, and closeout. Often posted as a fixed-term role tied to one program of work.

IT Project Coordinator Job Description
IT PROJECT COORDINATOR JOB DESCRIPTION
Company: __ ([City, State])
Reports to: [IT Manager / Project Manager / Operations Director]
Employment type: Full-time [or fixed-term through the ___ rollout]
FLSA status: Depends on duties (see classification note)
Compensation: $_ per [hour / year]

ABOUT THIS ROLE

[Company Name] has [number] technology projects planned over the next [period]:
[system migration, office move, device refresh, application rollout, phone
system replacement]. Our technical people can do the work. What keeps slipping
is the schedule, the communication, and the follow-through. We are hiring an IT
Project Coordinator to own those.

POSITION SUMMARY

The IT Project Coordinator plans, schedules, and tracks technology projects from
kickoff to close. You keep the plan current, chase dependencies, run status
communication, coordinate vendors and internal teams, and make sure nothing gets
delivered without someone confirming it landed.

KEY RESPONSIBILITIES

Build and maintain project plans, schedules, and task assignments in
[project tool]
Run kickoff, status, and closeout meetings, and publish notes and decisions
Track dependencies, blockers, and risks, and escalate them before the deadline
rather than at it
Coordinate internal teams, vendors, and contractors around scheduled work and
cutover windows
Maintain the project budget tracker and flag variance early
Prepare and send user-facing communication before, during, and after any
change that affects how people work
Coordinate user acceptance testing and collect sign-off
Run project closeout: documentation, handover to support, and a short lessons
review
Support change control: what is changing, when, who approved it, and how to
roll it back

REQUIRED QUALIFICATIONS

[Number] years coordinating projects, ideally technology projects
Familiarity with [project tool] and with basic project scheduling
Enough technical literacy to follow a migration plan and ask the right
questions, without needing to build it yourself
Written communication that non-technical users will actually read
Persistence: most of this role is polite, well-timed follow-up
[CAPM / PMP / Scrum certification: preferred, not required]

CLASSIFICATION AND COMPLIANCE NOTE

Project coordinator classification is contested territory, so decide it
carefully. A coordinator who schedules meetings, updates trackers, and follows a
plan set by a project manager is doing production work and is generally
non-exempt: hourly and overtime-eligible. A coordinator who independently sets
project direction, makes commitments on scope or budget, and exercises
discretion on matters of significance may meet the FLSA administrative
exemption, which also requires payment on a salary basis at or above the federal
threshold. The computer employee exemption does not fit this role, because
project coordination is not systems analysis or programming. Misclassifying
coordinators as exempt is a recurring and expensive mistake. If the role is
non-exempt, plan for overtime around cutover weekends and budget for it. This is
general information, not legal advice.

EEO STATEMENT

[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.

COMPENSATION AND HOW TO APPLY

Compensation: $_ per [hour / year], [benefits summary], [expected
overtime around cutover windows and how it is paid]
To apply, email __ with your resume.

Template 6: Office and IT Coordinator (Hybrid, Small Business)

For the very small company where technology sits with whoever runs the office. It includes an explicit percentage split so the posting is honest about scope. The office coordinator templates cover the administrative half in more depth.

Office and IT Coordinator Job Description (Hybrid, Small Business)
OFFICE AND IT COORDINATOR JOB DESCRIPTION
Company: __ ([City, State])
Reports to: [Owner / Operations Manager / Office Manager]
Employment type: Full-time [or part-time at ___ hours per week]
FLSA status: Non-exempt (hourly, overtime-eligible)
Compensation: $_ per hour

ABOUT THIS ROLE

[Company Name] has [number] employees in [number] office(s). We are not large
enough for a dedicated IT person, and we do not want one yet. We need someone who
keeps the office running and owns the technology side of it: accounts, laptops,
software subscriptions, and the vendor who handles anything deeper.
Be honest with yourself before you post this: it is two jobs. Write the split
you actually expect and pay for both halves.

POSITION SUMMARY

The Office and IT Coordinator keeps daily operations and workplace technology
running at [Company Name]. Roughly [X] percent of the role is technology
coordination and [Y] percent is office and administrative work. You are the
first person people ask when something does not work.

KEY RESPONSIBILITIES

Technology (approximately [X] percent)
Set up new employees: account, email, device, licenses, and access to the
applications their role needs
Remove access and recover equipment on an employee's last day
Handle first-line support and escalate the rest to [our managed service
provider / IT vendor]
Maintain the device inventory and the software subscription list, with
renewal dates
Coordinate technology vendors: internet, phones, copier, software providers
Keep multi-factor authentication enrollment and security training completion
current
Office and administration (approximately [Y] percent)
Manage the front desk, mail, deliveries, and visitors
Order supplies and manage office vendor relationships
Coordinate facilities requests and building access badges
Support meeting logistics, travel booking, and company events
Assist with [expense processing / invoice coding / HR paperwork collection]

REQUIRED QUALIFICATIONS

[Number] years in an office coordinator, office manager, or administrative
role with real technology responsibility
Confident with [Microsoft 365 / Google Workspace] administration at the user
level: creating accounts, resetting access, assigning licenses
Comfort troubleshooting laptops, printers, and conference room equipment
Strong organization: two jobs at once only works with a system
Discretion with confidential employee and company information

CLASSIFICATION AND COMPLIANCE NOTE

This role is non-exempt: hourly and entitled to overtime past 40 hours in a
week. Neither half of the job supports an exemption. Office coordination is
production and administrative support work rather than the exercise of
discretion and independent judgment on matters of significance, and the FLSA
computer employee exemption requires a primary duty of systems analysis or
programming, which this role does not have. Track hours, including early
building openings and any evening setup. If the technology half keeps growing,
revisit the job description rather than quietly loading more onto the same
hourly rate. This is general information, not legal advice.

EEO STATEMENT

[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.

COMPENSATION AND HOW TO APPLY

Compensation: $_ per hour, [benefits summary], [the expected split
between office and technology duties]
To apply, email __ with your resume.

Overtime and the Computer Employee Exemption

Most IT coordinators are non-exempt: hourly, and owed overtime past forty hours in a week. The exemption employers reach for first, the computer employee exemption, almost never applies to this role, and assuming it does is the most expensive mistake in the posting.

The federal rule on computer employees covers systems analysts, programmers, software engineers, and similarly skilled workers whose primary duty is systems analysis, program design, or the development and modification of computer systems or programs. It carries its own pay floor: the standard salary level, or an hourly rate of at least $27.63. The Department of Labor puts the limit plainly in Fact Sheet #17E, which states that job titles do not determine exemption status and that employees whose work is highly dependent on computers, but who are not primarily engaged in systems analysis and programming, are not exempt.

The computer employee exemption almost never fits
The federal computer employee exemption is narrow and specific. It covers systems analysts, programmers, software engineers, and similarly skilled workers whose primary duty is systems analysis, program design, or the development, documentation, testing, creation, or modification of computer systems or programs. It also carries its own pay floor: the standard weekly salary level, or an hourly rate of at least $27.63. The Department of Labor states plainly that job titles decide nothing, and that employees whose work is highly dependent on computers but who are not primarily engaged in systems analysis and programming do not qualify. An IT coordinator handling accounts, tickets, assets, and vendors is doing coordination and support, not systems analysis. Start from non-exempt and make the employer prove otherwise. This is general information, not legal advice.
The administrative exemption is the only realistic route
Where an IT coordinator is genuinely exempt, it is usually under the administrative exemption rather than the computer one. That test has three parts: payment on a salary basis at or above the federal threshold of $684 per week, a primary duty of office or non-manual work directly related to management or general business operations, and the exercise of discretion and independent judgment on matters of significance. The third part is where most coordinator roles fail. Following an approval workflow someone else set, updating a tracker, and routing tickets is production work, not independent judgment. A coordinator who actually selects vendors, negotiates renewal terms, and commits budget is a different case. Write the real approval limit into the job description, then classify to match it. This is general information, not legal advice.
Access rights make this a background and confidentiality question
An IT coordinator can typically reset any password, read any mailbox, and reach any file the company owns. That is a level of access most small businesses grant without thinking about it, and it changes what the hire requires. Put a confidentiality agreement in the offer package rather than the handbook. Decide before the start date whether a background check is appropriate for this position, apply the same standard to every candidate for it, and follow the notice and authorization requirements that apply to consumer reports. Document what access the role receives and why, keep administrator accounts separate from daily accounts, and require multi-factor authentication on both. None of this signals distrust; it is what any auditor, insurer, or customer security questionnaire will ask you to show. This is general information, not legal advice.
Overtime is real in this role, so budget for it
Coordination work clusters at the edges of the week. Device setup happens the evening before a start date, migrations and cutovers happen on weekends because that is when nobody is working, and outage response happens whenever the outage does. For a non-exempt coordinator every one of those hours is compensable, and hours past forty in a week are owed at time and a half. Two practical consequences. First, write the on-call expectation into the posting and state how on-call time is paid, because candidates who have been burned by an unpaid phone will ask anyway. Second, budget overtime into the role rather than treating it as an overrun, especially in any period with a planned migration or office move. Track the hours in a real system, not in memory. This is general information, not legal advice.

The alternative route is the administrative exemption, which requires a salary at or above the federal threshold of $684 per week plus the exercise of discretion and independent judgment on matters of significance. Our breakdown of exempt versus non-exempt classification works through the tests, and the guide to overtime rules covers what a non-exempt coordinator is owed.

Salaried Does Not Mean Exempt
Paying an IT coordinator an annual salary does not make the role exempt. Exemption requires the salary basis, the salary level, and a qualifying duties test, and the duties test is where coordinator roles fail. A salaried non-exempt employee is perfectly legal, and it is often the right structure here: predictable pay, plus overtime when a migration weekend runs long. What is not legal is a salary with no overtime for someone whose day is tickets, records, and purchase requests.

What to Pay an IT Coordinator

No Bureau of Labor Statistics occupation is titled IT coordinator, so the number has to come from the nearest classifications. The closest fit is computer user support specialists, which covers the support and coordination end of IT work rather than the infrastructure end.

The Nearest National Benchmark
The federal occupational classification system has no IT coordinator category. According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), the closest match, computer user support specialists, had a national median annual wage of $61,860, with the 10th percentile at $40,980 and the 90th at $100,540. Adjacent classifications run higher as technical depth increases: $76,220 for computer network support specialists and $99,130 for network and computer systems administrators (U.S. Bureau of Labor Statistics, OEWS national estimates).
PercentileComputer user support specialists (BLS OEWS, May 2025)What it usually means for a coordinator posting
10th$40,980 per yearPart-time, or a hybrid office and IT role in a low-cost market
25th$49,000 per yearFirst IT hire with a provider behind them and no prior coordination experience
50th (median)$61,860 per yearStandard in-house coordinator running accounts, assets, and vendors
75th$79,040 per yearReal asset, license, and budget ownership, or a high-cost metro
90th$100,540 per yearEffectively an IT manager; post the manager role instead

Two adjustments matter. Post the range hourly if the role is non-exempt, because an annual figure implies exempt status you may not have. And state the on-call expectation alongside the rate, since candidates who have carried an unpaid phone will discount your number without telling you why.

Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
See It in Action

Access, Assets, and the Offboarding Problem

An IT coordinator can usually reset any password and reach any file the company owns, which makes this a trust position as much as a technical one. Write the confidentiality agreement into the offer package, separate administrator accounts from daily accounts, and require multi-factor authentication on both.

The other half of the access question is departures. Onboarding gets attention because a new hire cannot work without a laptop, while offboarding gets none, because nothing visibly breaks when an account stays live. That asymmetry is how small companies end up with former employees still holding access months later.

StepWhen it happensWho confirms it
Accounts, email, and license assignedTwo business days before the start dateIT coordinator, in writing
Device issued and receipt acknowledgedStart dateIT coordinator plus the employee signature
Confidentiality agreement signedWith the offer package, before access is grantedHR or the hiring manager
Security awareness training completedFirst weekTraining record, not a verbal confirmation
Access review for the roleQuarterlyIT coordinator against the access matrix
Access revoked across all systemsLast day, not the following weekIT coordinator, confirmed in writing
Device recovered and wipedLast day, or a dated return shipmentIT coordinator, logged against the asset record
License reclaimed or reassignedWithin the billing cycleIT coordinator against the subscription register

Make those steps explicit duties in the job description rather than assumed ones, and tie them to dates HR provides. The onboarding checklist and the employee offboarding checklist cover the full sequence on both sides. For the security routines a coordinator supports, the federal Small Business Cybersecurity Corner is a practical starting point.

Hiring an IT Coordinator Without an IT Department

Small company IT hiring fails in three predictable places: the posting describes a role the budget cannot buy, the offboarding half of the job goes unowned, and the paperwork runs on a separate track from the provisioning. Each has a concrete fix.

The posting describes an engineer and the budget describes a coordinator
This is the single most common failure I see. Somebody writes a job description by pasting duties from three sources, so the posting asks for server administration, network design, and cybersecurity ownership, then offers a rate anchored to a support role. Strong technical candidates read it as underpaid and skip it. Coordination candidates read it as over their head and skip it too. You end up with a small pool of people who match neither half. The fix is to decide what the role is before you write it: the coordination layer, the technical layer, or a deliberate blend with the percentage split written down. If you genuinely need infrastructure ownership, you are hiring a systems administrator, and the pay benchmark moves with it.
Access sprawls quietly because nobody owns the offboarding half
Onboarding gets attention because a new hire cannot work without a laptop. Offboarding gets none, because nothing visibly breaks when an account stays live. Then a departed employee still has access to the shared drive eight months later, and you find out during a security questionnaire from a customer. An IT coordinator is the answer only if the job description says so explicitly: revoke access on the last day, recover the device, reassign the license, and confirm each step in writing. Tie those steps to a date HR provides rather than to a message someone remembers to send. Access removal is one of the few IT tasks where being a day late is a genuine risk rather than an inconvenience.
The paperwork and the provisioning run on separate tracks
At a small company the offer letter, the handbook acknowledgment, the confidentiality agreement, the equipment receipt, the security training, and the account setup are all handled by different people in different tools, and the IT coordinator finds out someone started by seeing them in the lobby. FirstHR closes that gap. The onboarding wizard runs the same sequence for every hire, e-signature covers the offer, the confidentiality agreement, and the equipment acknowledgment, document management keeps the signed records against each employee profile, and training modules deliver security awareness before the first login rather than three weeks after. Offboarding runs the same way in reverse, with the access and asset return steps on a dated checklist. Applicant tracking is coming soon to FirstHR.

Screen for the failure mode you actually have. Hand candidates a messy asset spreadsheet and ask what they would fix first, or describe four simultaneous requests and ask them to rank the order. Both tell you more about a coordinator than any certification does. Every job description on this page sits in our hiring templates library alongside the interview kits.

Key Takeaways
An IT coordinator owns the organizational layer of technology: accounts and access, assets and licenses, ticket triage, vendors, and documentation, with technical resolution as a secondary duty.
Most IT coordinator roles are non-exempt, because the federal computer employee exemption requires a primary duty of systems analysis or programming, which coordination and support work is not.
The only realistic route to exempt status is the administrative exemption, which needs a salary at or above $684 per week plus genuine discretion on matters of significance such as vendor selection or budget.
No BLS occupation is titled IT coordinator; the nearest benchmark, computer user support specialists, shows a $61,860 national median (BLS OEWS, May 2025), ranging from $40,980 to $100,540.
State the environment, the coordination split as a percentage, the ticket volume, and the purchase approval limit as a number, because those four details filter candidates better than any duty list.
Write access revocation and device recovery into the job description as dated, confirmed steps, since a live account after a departure is the most common and most avoidable small business IT failure.
Provisioning and paperwork should run on the same track. FirstHR gives every hire one onboarding sequence, with e-signature for the confidentiality agreement and the equipment receipt, document management for the signed records, training modules for security awareness, and the same checklist in reverse on the last day. Applicant tracking is coming soon to FirstHR.

Frequently Asked Questions

What does an IT coordinator do?

An IT coordinator owns the organizational layer of company technology rather than the deep technical layer. The core duties are user accounts and access rights, technology onboarding and offboarding, hardware inventory and software license tracking, intake and triage of support requests, coordination with outside vendors or a managed service provider, and keeping documentation current. Some coordinators also run purchasing and renewals, and some coordinate technology projects such as migrations and device refreshes. The distinguishing feature is that the role is measured on whether things are organized, current, and accounted for, not on whether a hard technical problem got solved. At a small business the coordinator is often the only internal technology person, escalating anything infrastructure-level to a provider.

Is an IT coordinator exempt or non-exempt under the FLSA?

Most IT coordinator roles are non-exempt, meaning hourly and entitled to overtime past forty hours in a week. The federal computer employee exemption is narrow: it covers workers whose primary duty is systems analysis, program design, or the development and modification of computer systems and programs, and the Department of Labor states that employees whose work is highly dependent on computers but who are not primarily engaged in systems analysis and programming do not qualify. Coordination, support triage, procurement, and record keeping fall outside it. The only realistic route to exempt status is the administrative exemption, which requires payment on a salary basis at or above the federal threshold of $684 per week plus a primary duty involving the exercise of discretion and independent judgment on matters of significance. Following an approval workflow set by someone else does not meet that bar. This is general information, not legal advice.

How much does an IT coordinator make?

There is no Bureau of Labor Statistics occupation titled IT coordinator, so the figure has to be benchmarked against the nearest classifications. The closest is computer user support specialists, where the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025) reports a national median annual wage of $61,860, with the 25th percentile at $49,000 and the 75th at $79,040. Adjacent classifications run higher as the work gets more technical: computer network support specialists at a $76,220 median, and network and computer systems administrators at $99,130. For a coordinator posting, the median is the honest anchor for a standard in-house role. Adjust down for a part-time or hybrid office and IT role, and up where the coordinator carries genuine asset, license, and budget ownership in a high-cost metro.

What is the difference between an IT coordinator and an IT specialist?

The difference is where the work sits. An IT specialist or technician is measured on technical resolution: fixing the device, the account, the network problem, the application error. An IT coordinator is measured on organization: whether accounts are provisioned and revoked on time, whether the inventory matches reality, whether renewals are decisions rather than surprises, whether tickets reach the right person, and whether the vendor delivered what the contract promised. In practice the two overlap at small companies, where one person does both, and that is fine as long as the job description says which half dominates. Getting this wrong is the most common posting error: asking for systems administration depth while paying a coordination rate produces a pool of candidates who match neither half.

Do I need an IT coordinator if I already use a managed service provider?

Often yes, and that is one of the strongest cases for the role. A provider handles servers, networks, and escalated technical work, but it does not know who started on Monday, which laptop went home with which departing employee, or that you are paying for eleven unused seats. Those gaps are internal by nature. An in-house coordinator gives you a single point of contact, decides what to escalate and what to handle, holds the provider to the service agreement at a regular review, and keeps the asset and license records the provider has no visibility into. This co-managed arrangement is common at growing small businesses and is usually cheaper than either extreme. The first IT hire template on this page is written specifically for it.

What should an IT coordinator job description include?

Seven things. State the environment: headcount, locations, device count, and whether you run Microsoft 365 or Google Workspace. State whether a managed service provider already exists and what it covers, because that defines the boundary of the role. Group the responsibilities into accounts and access, support and triage, assets and licenses, vendors, and documentation, so candidates can see the shape. Set the split between coordination and hands-on technical work as a rough percentage. State the FLSA classification and, if the role is non-exempt, the on-call expectation and how on-call time is paid. Name the purchase approval limit as an actual number. Then add pay or a good-faith range, an equal opportunity statement, a named contact, and a response timeline. Everything else is decoration.

How do I hire an IT coordinator without an HR department?

Run a short, fixed sequence and do not improvise it. Write the posting from the template that matches your actual situation, with pay, classification, and the coordination split stated up front. Screen for organization and escalation judgment rather than for certifications, because the failure mode in this role is a messy inventory, not an unsolved technical problem. Use a practical exercise: hand candidates a messy asset spreadsheet and ask what they would fix first. Check references specifically on follow-through. Then treat the start date as a compliance sequence rather than a welcome: confidentiality agreement signed, access documented and granted, administrator accounts separated from daily accounts, equipment receipt acknowledged, security training completed. FirstHR runs that sequence with e-signature, document management, and training modules. Applicant tracking is coming soon to FirstHR.

Ready to transform your onboarding?

7-day free trial No credit card required
Start Your Free Trial