Does SOC 2 require performance reviews, job descriptions and an org chart?

Updated

Not by name. None of the sources fetched for this page says the SOC 2 criteria name performance reviews, job descriptions or an org chart. Windmill, which sells review software, writes that "CC1.4 doesn't explicitly mandate performance reviews". What an auditor looks for is that reporting lines are clear, that people know their duties, and that someone checks whether the duties are carried out. A dated one-page chart, a short description per role and one written review per person a year are the usual way a small company shows that.

What the sources say

Five pages were fetched for this guide: one from a company that sells review software, one from an audit and advisory firm, and three short pages from an audit firm's SOC 2 video series. None quotes a sentence of the criteria that names any of the three documents.

SourceWho they areWhat it says
Windmill (no named author, 26 December 2025)Sells performance review software"While CC1.4 doesn't explicitly mandate performance reviews, they're the most straightforward way" to show evaluation. "Other acceptable evidence can include documented manager check-ins, promotion or compensation review records, training plans, or formal improvement processes"
risk3sixty (Madison Loewe, 22 September 2022)Audit and advisory firm that also sells a GRC platform"Since SOC 2 is customizable, there is no set way to meet the criteria". Lists job descriptions, an organizational chart and performance reviews among common HR responsibilities
KirkpatrickPrice (Joseph Kirkpatrick, 30 November and 7 December 2018)Audit firm; three pages from its SOC 2 Academy seriesAn auditor "might use a company's organizational chart as evidence". Lists annual performance reviews as one of several ways to develop employees, as a question and not as a rule

Sources: (Windmill) (risk3sixty) (KirkpatrickPrice, CC1.3) (KirkpatrickPrice, CC1.4) (KirkpatrickPrice, CC1.5). Three limits. Windmill's article is written to sell reviews. The KirkpatrickPrice pages are from 2018 and are a few paragraphs each. And risk3sixty does not tie its advice to numbered criteria, so this page does not either when it cites that firm. Your CPA firm has the last word for your system.

What the people-side criteria are after

KirkpatrickPrice quotes or summarizes three of the common criteria. They ask for outcomes, and none of the three sentences names a document.

CriterionThe criterion, as KirkpatrickPrice gives itIn plain words
CC1.3"Management establishes, with board oversight, structures, reporting lines, and appropriate authorities and responsibilities in the pursuit of objectives."Who reports to whom, and who is responsible for what
CC1.4Summarized, not quoted: an organization "must demonstrate a commitment to attracting, developing, and retaining competent employees in alignment with objectives"You hire people who can do the job, train them, and check that they can
CC1.5"The entity holds individuals accountable for their internal control responsibilities in the pursuit of objectives."Something happens when a duty is done well, and when it is not

The middle column is taken from the three KirkpatrickPrice pages; the right column is this page's wording. The board part of CC1.3 is covered in the oversight minutes template, and who owns security is covered in does SOC 2 require a CISO?

The small-company version of each document

Org chart

risk3sixty says "The HR system will be the most accurate source for an organization chart", and that management "will need to review the accuracy of these at least annually", meaning the chart, policy availability and job descriptions (risk3sixty). It also ties the chart to access reviews: the listing of all personnel with job titles, managers and employment status is what a user access review should run against, and mismatches go back to HR. A company with no HR system can keep a one-page chart with a date on it. Use the same staff list for the chart and for the access review tool, so the two cannot drift apart.

Job descriptions

risk3sixty calls it a best practice "to attach the job descriptions for their roles to their offer letters and promotion documentation", with agreements playing that part for contractors, so the company collects an acceptance of the responsibilities. KirkpatrickPrice starts earlier, at the job posting, and says a description should accurately portray what the position needs (KirkpatrickPrice). Windmill says "A one-page document per role is sufficient." (Windmill) For a team of ten that is a handful of pages: one per role, not one per person.

Performance reviews

risk3sixty: "Performance reviews should be documented and acknowledged by both employee and manager, to include a review against the job position held by the employee and any improvements requested of the employee." That sentence has four parts a record can carry: it is written, both people acknowledge it, it is measured against the role, and it lists what should improve. Windmill adds that "even a well-structured Google Drive folder works for smaller teams" as the place to keep them.

How it is tested

Windmill, citing Secureframe (a page not fetched for this guide), says auditors check this by sampling: "they'll select a few employee names and ask for evidence of competence evaluation". It gives no sample size, and this page does not add one; how samples are drawn in general is in SOC 2 sampling and sample sizes. Windmill lists the ways this goes wrong:

  • Nothing in writing. "Verbal feedback doesn't count."
  • Some people missing. If most employees have a review and a few do not, the gap is what gets noticed.
  • A skipped cycle. "If your policy says annual reviews but you skip a year, that's a control failure."

All three come from one seller of review software (Windmill), and it offers no count of how often auditors raise them. The third point does not depend on Windmill, though. An auditor tests a company against its own written rule, so a cadence you wrote down and missed is an exception whatever the criteria say.

How often

Windmill: "Most auditors expect reviews at least annually, and annual cadence is the safest default. Some accept rolling reviews or continuous documented check-ins". risk3sixty also treats reviews as an annual task for HR, and KirkpatrickPrice asks "Do you meet with individual employees on an annual basis to conduct performance reviews?" as one question among several. None of them quotes an interval from the criteria. Pick an interval you will keep, write it down, and hold to it through the whole observation period.

What the generated policies already commit you to

Policyseed sells a kit, so read this section as one example of how the obligation gets written down. The excerpts are not typed by hand. They are rendered from the Human Resources Security Policy template for the Northwind Cloud Inc sample intake, so they change when the template does.

Job descriptions and performance conversations (Human Resources Security Policy, 4.10)

Every job description for a role with system access states its security responsibilities. Managers include adherence to security policies in performance conversations and may not waive policy requirements for individuals.

Accountability (Human Resources Security Policy, 4.11)

Violations of security policy are handled through a formal disciplinary process that is proportionate, documented and consistent. Sanctions range from retraining to termination of employment or contract and, where the law requires, referral to authorities.

Contractors (Human Resources Security Policy, 4.9)

Contractors, agency workers and vendor staff with access to Northwind Cloud Inc systems meet the same screening, acknowledgment, training and offboarding requirements as employees. Where the contracting entity performs screening, Northwind Cloud Inc obtains written confirmation that it is equivalent to Section 4.1.

Three things to notice before you approve this policy. First, item 4.10 creates two things an auditor can ask for: a job description for every role with system access that states its security responsibilities, and some record that managers raise policy adherence in performance conversations. Neither depends on an answer you gave in the generator; every company that adopts the set makes the same promise. Second, the policy does not set how often those conversations happen or what the record looks like, so choose that yourself and write it where you will find it. Third, the set does not include a job description, an org chart or a review form. The site has no ready template for them yet; the record below is the smallest version this page can suggest.

A five-line review record

This record is this page's suggestion. It is built from the four parts of risk3sixty's sentence above plus the policy adherence line from item 4.10, and no source prescribes this exact form.

  1. Who and when. Name, role, reviewer, date, and the period the review covers.
  2. Against the role. Two or three sentences on how the person met the responsibilities in the job description, with one example.
  3. Security duties. Training done on time, policies acknowledged, and any policy issue in the period and how it was closed.
  4. What should improve. One or two items with a date, or "none".
  5. Acknowledged. Both names with dates. A reply by email saying "read and agreed" works when it is saved with the record.

Keep the records in one folder with restricted access, one file per person per cycle. If an auditor asks for a sample, you may be able to show that the record exists with the pay and personal details removed; ask your CPA firm what it needs to see before the period starts. Training completion and policy sign-off already have their own records: see SOC 2 policy acknowledgment and the onboarding and offboarding checklist.

A first-year setup for a company under 20 people

  1. Draw the chart. Names, titles, reporting lines and a date. Put a calendar reminder to check it once a year and after every hire or departure.
  2. Write one page per role. Responsibilities, plus the security responsibilities the role carries (who approves access, who reviews code, who handles customer data).
  3. Attach the page to the offer. New hires accept it with the offer letter; for people already on the team, collect a dated acknowledgment once.
  4. Set the review month. Write the interval into your HR policy or handbook and run the first cycle before the observation period ends, so there is a record inside it.
  5. Keep the disciplinary path real. Item 4.11 promises a documented process. If nothing happened in the period, be ready to say so; if something did, the record is the evidence.

For the wider people-side list, including screening before the start date, see does SOC 2 require background checks? For the document risk3sixty lists first for integrity and ethical values, see the free code of conduct template.

Frequently asked questions

Does SOC 2 require performance reviews?
Not by name, according to the sources fetched for this page. Windmill, which sells performance review software, writes that "CC1.4 doesn't explicitly mandate performance reviews" and lists documented manager check-ins, promotion or compensation review records, training plans and formal improvement processes as other acceptable evidence. risk3sixty, an audit and advisory firm, says "there is no set way to meet the criteria". What an auditor looks for is evidence that you check whether people can do their jobs and that you act when they cannot. A written review is the common way to show it.
Does SOC 2 require an org chart?
No fetched source says the criteria name one, but it is the document the sources expect to be asked for. KirkpatrickPrice, an audit firm, says an auditor "might use a company's organizational chart as evidence to understand who reports to who and which responsibilities belong to which employees". The criterion it is discussing, CC1.3, is about structures, reporting lines, authorities and responsibilities. A chart is the shortest way to show those.
We are four founders with no managers. Who reviews whom?
None of the fetched sources answers this, so what follows is this page's suggestion and not a rule. Write down who each founder answers to for security duties (often the CEO, and the CEO to the board or to the other founders as a group), hold one documented conversation a year per person against that person's written responsibilities, and have both people sign and date the record. Ask your CPA firm early whether it accepts this for a team with no reporting layers; risk3sixty's own wording is that reviews are "acknowledged by both employee and manager", which assumes a manager exists.
Do contractors need performance reviews?
The fetched sources do not say so directly. risk3sixty says "personnel is not referring to just employees" and includes contractors and third-party staff who have individual access to your systems, and it says their agreements should cover each of the personnel controls so that some party is responsible for each one. The generated Human Resources Security Policy lists screening, acknowledgment, training and offboarding for contractors, and does not list reviews. If your own policy promises a review for everyone with system access, contractors are inside that promise.
Is an org chart in a slide enough?
No fetched source sets a format. risk3sixty says the HR system "will be the most accurate source for an organization chart" and that management should check its accuracy at least annually. A slide can do the same job when it carries a date, every person's name and title, and who each person reports to, and when it matches the staff list you use for access reviews. An undated chart that still shows someone who left is the version that causes questions.
How often do reviews have to happen?
The fetched sources give no interval from the criteria. Windmill says "Most auditors expect reviews at least annually, and annual cadence is the safest default" and that some accept rolling reviews or continuous documented check-ins. It gives no data for "most", and it sells review software, so treat that as one seller's reading. risk3sixty also describes reviews as an annual task. Whatever interval you write in your own policy is the one you will be tested against.

Policyseed provides governance policy templates and AI tailoring. It is not legal advice and not a compliance guarantee. Management adopts the policies; the CPA firm performs the SOC 2 examination.