How Should MSPs Use Job Descriptions?

MSPs should use job descriptions as a standing management tool for the people already in each role, not just as a way to attract the next hire. A good job description sets the standard for what a role contributes, names the few duties that matter most, and defines how success is measured, so employees and managers work from the same page. For two roles where that clarity pays off, see why your MSP needs a dispatcher and how to decide whether to hire a sales manager.
This post covers what a job description is for, what Bering McKinley's standards say belongs in one, how it differs from a job posting, how it supports accountability, and when to update it.
How Should MSPs Use Job Descriptions?
Use them as the written standard for each role, long after the hire is made. Many businesses write a job description with a short-term mindset, aimed at whoever reads it next, and then file it away once the role is filled. That throws away one of the most useful tools you have for the people already on your team. A detailed description spells out exactly what you want someone in the role to contribute and the responsibilities they are expected to meet every day. When an employee starts to drift, it gives both of you a fixed reference point to come back to and a standard to strive for. It also protects the employee, because work that falls well outside the description becomes a conversation about the role instead of a quiet addition to someone's workload. Bering McKinley's standard is that a candidate receives the job description before being hired and can find it easily once they are in the role.
- Treat the job description as a working document, not a recruiting ad.
- Use it as the reference point when someone drifts off track.
- Share it before the hire and keep it easy to find afterward.
What Should an MSP Job Description Include?
Bering McKinley's standard calls for five parts: a brief description, minimum criteria, essential duties, measurements of accountability, and the employment details. The brief description is a short overview of the role written at a 10th-grade reading level, so anyone can understand it. Minimum criteria should be objective and stated in yes-or-no terms, such as a four-year degree in marketing rather than a vague phrase like "marketing experience." Essential duties are the top three to five responsibilities of the role, not an exhaustive task list. Measurements of accountability are the KPIs or standards that show whether the person is meeting expectations. The employment details note whether the position is exempt or non-exempt, its pay band, and who it reports to. For sales roles, the standard adds a brief explanation of the compensation plan, with the full plan kept in a separate document. Writing the description before you interview or post the role also clarifies what you are actually looking for.
- Keep the overview short and easy to read.
- Limit essential duties to the three to five that matter most.
- State how success is measured, plus pay band, status, and reporting line.
How Is a Job Description Different From a Job Posting?
A job posting markets the role to candidates, while a job description defines the role for everyone who works in it. Bering McKinley's standards draw this line clearly. The posting is built to attract applicants and can change with the hiring market. The description reflects your role table, the document that lists every role in a department with its pay band, minimum criteria, and the accomplishments needed to advance. BMK's standard is to complete the role table first and write job descriptions from it, which forces management to define each role deliberately and helps expose gaps in the organizational structure. When the two documents get confused, the description turns into marketing copy that sits on a job board and never guides anyone. Write the description first, then build the posting from it, so the promises you make to candidates match the job they will actually do once they join your team.
- Write the posting from the description, not the other way around.
- Build the role table before the job descriptions.
- Don't let the description live only on a job board.
How Do Job Descriptions Keep Your Team Accountable?
They make expectations specific enough that both the employee and the manager can tell whether the job is getting done. The more detailed the description, the better your people understand what they are supposed to do and how to do it. Treat it as a written agreement on responsibilities between an employee and their manager, so each side keeps up its end of the arrangement. The measurements of accountability do most of the work here: when the KPIs or standards are written down, a performance conversation becomes a review of facts instead of a debate about opinions. Bering McKinley's role table standard adds a second layer. Performance reviews should include time to discuss the employee's path to the role they want next, using the minimum criteria and accomplishments in the role table as short- and long-term goals. That turns the job description from a document in a drawer into a map of how to grow inside your MSP.
- Make expectations specific enough to measure.
- Use the description as a shared agreement between employee and manager.
- Tie reviews to the next role's criteria in the role table.
When Should You Update Your MSP's Job Descriptions?
Update a job description whenever the responsibilities of a role or an employee change, not only when you have an opening. As an MSP grows, duties shift and new responsibilities tend to get added informally, one request at a time. If the written description no longer matches the work, it stops being useful as a standard and starts causing confusion about who owns what. Bering McKinley's standards assign HR managers and department managers to review job descriptions regularly and update them to reflect changes in roles or responsibilities. The same standards call for keeping job descriptions aligned with the role table and career paths, making them accessible to every employee, and training both new hires and existing staff on how to use them. Looking at the description during each performance review is a simple way to catch the gaps before they grow, because that is when the role and the actual work get compared side by side.
- Update the description when the work changes, not just at hire.
- Assign managers to review descriptions on a regular schedule.
- Keep descriptions aligned with the role table and visible to all staff.
Frequently Asked Questions
How should an MSP use job descriptions?
An MSP should use job descriptions as the ongoing standard for each role, not just a hiring document. Give the description to candidates before they are hired, keep it easy to find, and refer back to it when performance drifts, when duties change, and during reviews. It tells employees what they own and protects them from work outside the role.
What should be included in an MSP job description?
Bering McKinley's standard calls for a brief description of the role at a 10th-grade reading level, objective minimum criteria, the top three to five essential duties, and measurements of accountability. It should also note whether the role is exempt or non-exempt, its pay band, and who it reports to. Sales roles add a brief summary of the compensation plan.
What is the difference between a job description and a job posting?
A job posting markets an open role to attract candidates. A job description defines the role in full for the person doing it and their manager, and it reflects the role table. Write the description first and build the posting from it, so what you advertise matches the job and the description keeps guiding the employee after the hire.
How often should job descriptions be updated?
Update a job description whenever the responsibilities of the role or the employee change, and review all descriptions on a regular schedule. Bering McKinley's standards assign that review to HR and department managers and call for keeping descriptions aligned with the role table. Checking the description during performance reviews is a practical way to keep it current.
What is a role table for an MSP?
A role table lists every role in a department, with its responsibilities, pay band, minimum criteria, and the accomplishments needed to move to the next level. Bering McKinley's standard is to build it before writing job descriptions and to make it visible to employees, so everyone can see the career path and what it takes to advance.
Should employees see the pay bands for other roles?
Under Bering McKinley's role table standard, yes. Employees can see the pay band for each role, but not the salaries of individual coworkers. That transparency shows people what each step on the career path pays and what it takes to get there, which reduces guesswork about raises and promotions and makes reviews more productive.
Related Resources from Bering McKinley
Want to Continue the Conversation?
Clear roles and job descriptions are part of building an MSP that runs without you in every decision. Vision gives your MSP a strategic plan, a consultant who holds your team accountable every month, and your numbers tracked against BMK's standards.
%20logo.png?width=2000&height=369&name=BMK%20(just%20text)%20logo.png)