CPA ISC Passing Score

The passing score is 75 scaled

AICPA sets a passing standard of 75 on a scale from 0 to 99. The result is not the percentage of questions answered correctly. Scores are scaled so performance can be compared across different exam forms. The passing standard applies to each CPA section, including ISC.

AICPA does not publish a fixed raw number of correct answers that produces a passing score. Candidates therefore cannot calculate an official result by counting remembered answers or comparing a question-bank percentage with 75.

ISC score weighting

ISC assigns 60 percent of the score weight to multiple-choice questions and 40 percent to task-based simulations. This is a scoring proportion, not a statement that each MCQ is worth a fixed fraction of each TBS. Nor is it the same as the distribution of visible questions: ISC has 82 MCQs and 6 TBSs.

Maintain practice in both formats. MCQs can test concepts and applied judgment about systems, risks and controls. Simulations ask candidates to organize evidence and complete structured responses. Because simulations contribute 40 percent, an MCQ-only plan leaves a substantial part of the assessment unpractised.

Why a raw percentage does not convert

A raw percentage describes the share of responses correct in a particular set. An official section score is scaled. Exam forms can differ, and some items may be pretest questions that do not count. Candidates cannot identify those items during the test. AICPA does not publish a universal conversion chart from raw answers to scaled scores.

A commercial course may display bank accuracy, completion or a readiness indicator. Those measures are specific to its question pool and method. They can help show a trend when measured consistently, but they are not AICPA scores and do not promise a passing result.

Use a failing score report carefully

Candidates who fail may receive a Candidate Performance Report with comparative information about content-area performance. The report does not identify exact questions missed or provide a raw answer key. Area-level information is less precise than the overall score, so treat it as one signal alongside your notes and practice history.

Translate a relative weakness into a specific task. If system architecture is a gap, identify which concepts are unfamiliar and solve fresh examples. If control analysis is weak, practise moving from risk to objective to control and evidence. If SOC reporting is difficult, compare report purposes, users, criteria and periods.

Continue reviewing other Areas while targeting a weakness. A retake plan should not create a new gap by dropping material that previously felt strong. Mix new questions across the blueprint and assess transfer instead of repeating the exact items whose answers you now remember.

Track readiness without predicting a score

Separate MCQ and TBS progress in your study log. For MCQs, record the Area, concept, confidence and reason for each miss. For TBSs, note whether you identified the right evidence, applied an appropriate framework and completed the fields. Review several sessions to find recurring errors.

Look for stable reasoning on fresh mixed practice. Can you explain why a control addresses a particular risk? Can you distinguish privacy from confidentiality when the facts require it? Can you interpret a SOC report without treating it as a universal assurance? These checks are more informative than a single percentage from familiar material.

What to do after a score release

Record the score and any performance report, then give yourself time to review the exam experience without trying to reconstruct secure questions. Compare the report with your pre-exam study log and note which gaps were recurring. Build a retake plan with defined objectives, fresh practice and both item formats.

Schedule only after checking the ISC window and NTS period. Disciplines are administered during the first month of each calendar quarter. If the next window does not allow enough time for deliberate review, a later date may be more practical. No practice metric guarantees what the official scaled score will be.

Distinguish score weight from item count

The MCQ and TBS weight percentages do not mean that each question in a format has an identical value or that 60 percent of visible questions is the official MCQ contribution. ISC has 82 MCQs and 6 simulations, but the two components are weighted 60 and 40 percent respectively. Question count and scoring weight describe different features of the exam.

This distinction matters when reviewing a practice dashboard. A high volume of short questions can dominate reported accuracy while leaving case skills underdeveloped. Include enough varied simulations to practise evidence selection, control reasoning and complete responses. Do not infer component performance from the relative number of questions attempted.

A disciplined score-review routine

First, note what you remember about the experience without trying to recreate protected exam items. Record whether time pressure affected MCQs or TBSs, whether you left fields blank and which task types felt unfamiliar. These observations complement a performance report but do not replace it.

Second, group your study records by blueprint Area and skill. Separate content errors from execution errors. A content error means you lacked or confused a rule. An execution error may mean you understood the concept but overlooked evidence, misread a requirement or failed to finish. Assign each type a different practice action.

Third, set a few measurable goals. “Improve security” is too broad. “For a new scenario, identify the threat, objective, control and evidence” can be practised and checked. For SOC, “distinguish report purpose and intended user before drawing a conclusion” is a clear target.

Finally, choose a date only after checking preparation, eligibility, NTS validity and the quarterly window. A score below 75 does not reveal how many hours a candidate needs. Use fresh work to determine whether the revised plan is improving performance.

Do not reverse-engineer a raw cutoff

Candidates sometimes try to estimate how many questions they can miss. Public scoring information does not provide a fixed raw threshold. Item difficulty, test form and score scaling mean that remembered items cannot be converted into an exact result. Even an apparently strong practice percentage may measure a familiar subset rather than the breadth of the examination.

Use scores from practice to compare like with like over time. If the provider changes question pools or the set difficulty differs, a direct comparison may be misleading. Record content Area and confidence in addition to accuracy. The reason for an error often matters more than a one-point change in percentage.

For a failed attempt, focus the next cycle on demonstrable improvement. Can you explain a SOC finding with evidence? Can you identify an incomplete data extract? Can you evaluate a security control against the stated risk? These actions are observable, unlike trying to guess how many additional answers were needed.

Understand area feedback in context

A content-area rating is comparative feedback, not a precise percentage. It can suggest where your performance was weaker relative to a reference group, but it cannot tell you exactly which topic or item caused the result. Pair it with your own study records and identify patterns before choosing a retake focus.

Do not stop practising a strong area solely because the score report labels it stronger. Mixed tasks can combine areas, and knowledge can fade. Maintain a smaller cumulative review dose while directing more time toward demonstrated gaps.

For candidates who pass, the same scale means only that the passing standard was met. It does not certify mastery of every ISC topic or replace the professional judgment required in practice.

Use score facts to set expectations

A score of 75 is a threshold on the reporting scale, not a target practice percentage. A candidate should aim to demonstrate consistent knowledge and application across the blueprint rather than attempting to calculate a margin above the passing line. The official scoring method does not disclose a fixed conversion from practice items.

The equal relevance of content and process is important. A candidate can know the terminology but lose accuracy when facts are combined in a case. Another candidate may work quickly but select a control that does not address the stated risk. Practice should test both the knowledge and the reasoning process.

If you pass, retain your official result and continue with the remaining exam and licensure steps. If you do not pass, use the report as one input to a new plan. Neither outcome is explained solely by one practice-bank score.

The practical meaning of a scaled score

The score gives a consistent pass standard across forms. It does not tell a candidate which item was answered incorrectly or provide a simple list of missing concepts. The most practical use is to recognize the threshold, understand component weights and make the next study cycle evidence-based.

Avoid absolute statements about a close result. A score one point below passing is not a formula for exactly one more correct response. Focus on repeatable skill improvement rather than reverse engineering points.

A decision point, not a raw tally

The passing standard is a clear threshold, while the method for converting item performance is not a public raw-score chart. Candidates should prepare for the content and tasks rather than count guessed points.