# GRE Diagnostic Service: Read Your Report and Act | topin

On this page

## Find the diagnostic after your official results

ETS lists the service in your ETS account. Look for GRE Diagnostic Service after selecting the relevant General Test administration. Keep the test date with any notes you save, particularly if you have several results. The report is useful only when you know which sitting it describes. An account containing multiple dates is not a reason to combine their rows into one anonymous dataset.

Official General Test scores normally appear after 8–10 days; diagnostic access follows approximately 15 days after testing. These are different availability windows. If your official report is present but the diagnostic is not yet available, check the elapsed time first. After that approximate window, use ETS support for an access problem rather than assuming the diagnostic is a second score release.

The six-month access window gives you time to analyse the result, but do not postpone review until your next application season. Save your own summary while access is available: the question category, outcome, difficulty, time and resulting practice task. Record information about your performance without trying to recreate confidential exam questions from memory.

Read the report once to understand its headings before making a retake decision. A disappointing score can tempt you to classify every wrong answer as carelessness. A reassuring score can tempt you to ignore correct answers that consumed too much time. Both reactions lose information. Your first review should simply separate observations from explanations.

## Read each field without inventing missing information

__ETS diagnostic field meanings; checked 5 October 2026__
| Field                   | What it tells you                                         | What it does not establish                       |
| ----------------------- | --------------------------------------------------------- | ------------------------------------------------ |
| Reference number        | Sequence within a diagnostic category                     | The original question number on your exam        |
| Question type           | The response format or reasoning category                 | The exact question wording or cause of an error  |
| Right / Wrong / Omitted | Correct, incorrect, or viewed without a recorded response | Whether a correct answer was reasoned or guessed |
| Difficulty level        | A category from 1, easiest, to 5, hardest                 | A fixed number of scaled-score points            |
| Time spent              | Total time spent on that question                         | How much of that time was productive             |

ETS Help defines Omitted as a question viewed without a recorded response. It also says questions you never reached are excluded. Therefore, a diagnostic row count is not automatically the complete number of questions in a section. Keep any separate recollection of unfinished work labelled as a recollection; do not silently turn a missing row into a confirmed wrong answer.

The public Help page includes legacy examples with 20-question sections and old browser references. Its field definitions are useful, but use the current GRE structure for question totals and timers. Treat a worked interface example as an explanation of a field, rather than evidence that the present exam has reverted to the older format.

Difficulty is a description, not a diagnosis. A wrong level-1 item deserves examination, but one observation does not establish that all your foundations are weak. A correct level-5 item may show successful reasoning or a fortunate guess. Pair the row with fresh work before attaching a broad conclusion to your ability.

## Group rows by the skill you can actually repair

Begin with separate Verbal and Quant summaries. Then group by question type, and for Quant add mathematical content area where available. ETS categorises Quant under arithmetic, algebra, geometry and data analysis, with further distinctions for format, setting and Data Interpretation. Those labels provide a starting structure; they do not tell you the missing concept by themselves.

For each group, count correct, wrong and omitted rows and calculate the total time spent. Keep the denominator beside any percentage. Three wrong answers out of four viewed questions is a different evidence base from three out of fifteen. If a category contains only one or two items, describe the observations without announcing a stable weakness.

Compare effort with output. A group can have respectable accuracy while using a disproportionate share of time. Another group may contain fast wrong answers, suggesting that the next investigation should examine reading or method selection. These are hypotheses, not conclusions. The same timing pattern can come from unfamiliar content, a misread instruction or an unproductive approach.

For example, an illustrative algebra group might contain six viewed items: four correct, two wrong and 11 minutes spent. That is 67% observed accuracy after rounding and 110 seconds per viewed item on average. Write those numbers as a summary of this invented example, not as a GRE benchmark or a conversion to a predicted Quant score.

Choose at most two groups for the first repair cycle. That is our workload recommendation, not an ETS rule. A shortlist keeps the investigation concrete: what new evidence would distinguish a content gap from a timing problem? Keep the other groups in your notes so they can be revisited after the first changes are tested.

## Work through an original report-reading example

__Invented diagnostic summary for demonstrating the method; these are not ETS test questions or score predictions__
| Group                            | Viewed outcomes    | Time       | First investigation                             |
| -------------------------------- | ------------------ | ---------- | ----------------------------------------------- |
| Numeric Entry, arithmetic        | 2 right; 2 wrong   | 8 minutes  | Check answer form, units and arithmetic method  |
| Quantitative Comparison, algebra | 4 right; 1 wrong   | 10 minutes | Check whether the slow methods can be shortened |
| Text Completion                  | 2 right; 3 wrong   | 6 minutes  | Separate context reasoning from word knowledge  |
| Reading Comprehension            | 4 right; 1 omitted | 9 minutes  | Test completion and a move-on decision          |

Start with Numeric Entry because it combines low observed accuracy with substantial time. You do not yet know whether the problem was rounding, fractions, units or arithmetic. Use a small fresh set containing those features. After each answer, explain the requested quantity and the required entry form before checking the solution. The [Numeric Entry guide](/gre/quant/numeric-entry) provides a method to test.

The invented Quantitative Comparison group has four correct out of five, so simply adding more of the same questions may miss the problem. Ask whether the ten minutes came mainly from one item or from a slow method across all five. Fresh practice should record the approach as well as the time. A correct answer can still reveal an expensive habit.

The Verbal rows suggest two separate investigations. For Text Completion, try fresh examples first without answer choices and then with them; this can expose whether you understand the sentence relationship. For Reading Comprehension, an omitted item prompts an examination of how you allocated time. Do not call it a vocabulary problem merely because it occurred in Verbal.

The outcome of this review is a pair of practice questions about your process, not a verdict about your intelligence. Your notes should now say what you will test, what you will observe and what would change the next session. That is the point where a diagnostic report begins to become useful.

## Use an error log with evidence and a next action

Create six columns: diagnostic category, observed pattern, suspected cause, fresh test, repair and verification. Keep the suspected-cause column visibly separate. Without that separation, an early guess such as poor concentration can become the permanent explanation for every mistake. The fresh test is the step that either supports or replaces it.

A useful entry reads: arithmetic Numeric Entry; two wrong answers and high time; possible unit or answer-form problem; solve six original unit-conversion questions; write the requested unit before calculating; check another fresh set after a gap. An unhelpful entry reads: silly mistakes; be more careful. The first changes a behaviour you can observe.

Suppose an original practice question asks for the average speed over equal distances travelled at 30 and 60 kilometres per hour. The answer is 40, found from total distance divided by total time, rather than the arithmetic average of 45\. If you choose 45, log a rate-model error. That practice result gives stronger causal evidence than the diagnostic label arithmetic alone.

Use confidence notes for fresh practice: certain, reasoned but unsure, or guessed. You cannot recover a precise confidence rating from an old diagnostic row, but you can collect it next time. Correct guessed answers deserve review because their outcome does not establish that the method will work again. Correct slow answers deserve a different repair focused on efficient reasoning.

If you use accommodations, compare practice conducted under the same conditions and keep the timers visible in your notes. A time observation from one approved setup should not be judged against another setup without explanation. The [accommodations planning guide](/articles/gre-accommodations-request-timeline) explains how to rehearse approved conditions using official practice.

## Verify the repair before another full test

Our suggested cycle is investigate, repair, transfer and integrate. First use a fresh short set to identify the likely cause. Then practise the missing idea or decision. Next use different questions requiring the same idea. Finally return it to mixed timed work. The intervals and set sizes are your planning choices; ETS does not prescribe this sequence.

For a concept gap, successful repair means you can explain why the method applies before carrying out the calculation. For a reading error, name the exact condition you previously skipped and show where you check it now. For a time problem, demonstrate a decision to move on while useful time remains. Define the success condition before looking at the next result.

Use [topin’s free GRE mock](/gre/practice-test), marked on the official scale, as a fresh complete checkpoint after the targeted work. Keep its result labelled as practice. A preparation score is not an official ETS result, and one improvement cannot prove that a particular repair caused the entire change. Review the recurring error categories as well as the headline scores.

Retesting the same familiar material can make progress look larger than it is. Keep a small supply of unseen questions for verification and compare like with like: the same timer, response format and difficulty where practicable. If untimed understanding improves but timed performance does not, the next task is integration rather than restarting all the content lessons.

Use the existing [GRE study plan](/articles/gre-study-plan) to place those repair sessions into your calendar. The diagnostic adds priorities to that plan; it does not require a completely new schedule. After one cycle, return to the saved report and check whether the second priority still needs attention.

## Know which questions the report cannot answer

The diagnostic describes Verbal and Quant performance. It does not supply a writing-argument critique, a university admission probability or a guaranteed retake gain. Keep Analytical Writing feedback and programme requirements in separate records. Otherwise, a detailed Quant analysis can distract you from an application requirement that the diagnostic never measured.

Do not reverse-engineer a scaled score by assigning points to difficulty levels. ETS reports scaled scores separately, and this diagnostic is not a published raw-score conversion table. Likewise, do not read a difficult-looking collection of rows as proof that your next result must be higher. Your reliable evidence is the official result plus reviewed fresh practice.

ETS distinguishes this service from Question-and-Answer Review, a separate service for eligible New York test takers. A diagnostic category list should not be treated as that service or as a set of released questions. Use the current bulletin for eligibility if you need an actual question-review appointment.

End the review with one short record: the two strongest observed patterns, the causes you tested, the repairs that transferred and the remaining uncertainty. If the new work does not support your first explanation, change the explanation. A useful error log is allowed to become shorter as problems are resolved.

## Try a full GRE mock free

Timed like test day, every section scored, every answer explained.

[Take the free mock ](/gre/login)

## FAQs

When is the GRE Diagnostic Service available?

ETS says approximately 15 days after the General Test, for six months following that administration. Official scores normally appear earlier, after 8–10 days.

Is the GRE Diagnostic Service free?

Yes. ETS lists it as a free General Test service accessed through your ETS account.

What do difficulty levels 1–5 mean?

They run from the easiest category to the hardest. They are not points you can add together to reconstruct your scaled score.

Why does the report have fewer rows than expected?

ETS Help says unviewed questions are excluded. Viewed questions without a recorded response are marked Omitted. Check the selected administration and current format before interpreting the count.

Can the diagnostic tell me exactly why I got a question wrong?

It provides performance categories and timing, not a confirmed cause. Use those observations to select fresh practice that tests your suspected explanation.

## Sources (checked 5 October 2026)

* [ETS: GRE Information Bulletin 2026–27, Diagnostic Service and review services](https://www.ets.org/content/dam/ets-org/pdfs/gre/gre-info-bulletin.pdf)
* [ETS: GRE Diagnostic Service Help, field definitions and omitted items](https://grediagnostic.ets.org/GREDWeb/gred/help.jsp)
* [ETS: diagnostic Quantitative Reasoning categories](https://grediagnostic.ets.org/GREDWeb/gred/quantitative.jsp)
* [ETS: General Test score availability](https://www.ets.org/gre/test-takers/general-test/scores/get-scores.html)
* [ETS: General Test scores and diagnostic access](https://www.ets.org/gre/test-takers/general-test/scores.html)
* [ETS: current test structure](https://www.ets.org/gre/test-takers/general-test/prepare/test-structure.html)

## Related articles

[All GRE study guides ](/gre)

* [GREStudy plans & strategyGRE percentages and ratios: solve the right baseLearn GRE percentages and ratios with original worked questions, changing bases, reverse percentages and ratio changes, plus a practical checking routine.Updated 5 Oct 2026](/articles/gre-percentages-ratios-word-problems)
* [GREStudy plans & strategyGRE weighted averages and mixtures: totals firstSolve GRE weighted averages and mixtures with original questions on unequal groups, missing means, concentration and replacement, with checks for every model.Updated 5 Oct 2026](/articles/gre-weighted-averages-mixtures)
* [GREStudy plans & strategyGRE probability without replacement: update each drawWork through GRE probability without replacement using original questions on ordered draws, either order, complements and combinations, with exact fractions.Updated 5 Oct 2026](/articles/gre-probability-without-replacement)
* [GREStudy plans & strategyGRE combinations and permutations: does order matter?Choose combinations or permutations on GRE Quant with original worked problems on committees, roles, repeated letters and restrictions, plus counting checks.Updated 5 Oct 2026](/articles/gre-combinations-permutations)