IELTS Writing Task 1 Salary Table Comparison Checker: Spot Errors Before Test Day

You're staring at a salary table. Six columns. Four rows of data. Twenty minutes on the clock.

And you've got to describe it accurately without tanking your band score.

Here's what makes salary tables tricky: they look simple, but they're one of the sneakiest question types in IELTS Writing Task 1. Most students stumble in exactly two ways. They misread the numbers. Or they describe trends that don't actually exist in the data. Both mistakes cost real band points.

This post shows you how to catch these errors before the examiner does. You'll learn what examiners are actually looking for, see real examples of weak versus strong descriptions, and get a practical system for verifying your data accuracy every single time using a salary table comparison checker.

Why Salary Data Comparison Loses You Band Points

Task 1 scores depend on four criteria: Task Response, Coherence & Cohesion, Lexical Resource, and Grammatical Range & Accuracy. For tables, Task Response is where you win or lose points. The band descriptors are clear: you need to "select and present the main features" and "make accurate comparisons."

One wrong number kills that.

Salary tables force you to work with precise figures. A Band 7 response needs accuracy. Band 5 responses lose marks because comparisons are "partially accurate" or "unclear". You can't fudge numbers. The examiner has the original table right in front of them while they're scoring.

Quick tip: Salary tables usually show data across job roles, years, departments, or regions. Your job: spot patterns, compare groups, highlight the biggest contrasts. Don't invent trends that aren't there.

The Accuracy Trap: Glancing Instead of Reading Your Table Description

Most students glance at a table and write their first instinct without double-checking. Then they lose 2-3 marks before they even finish the introduction.

Here's a real example. Say you see this table:

Position Year 1 Year 2 Year 3
Manager $45,000 $48,500 $52,000
Analyst $32,000 $34,200 $36,800
Coordinator $28,000 $29,400 $30,900

Now look at two responses to this salary table:

Weak response: "Managers earn the most at $45,000 across all years. Analysts earn less, while Coordinators earn the least. Salaries increase slightly each year."

What went wrong? The student caught the overall pattern but ignored the actual numbers. "Salaries increase slightly each year" is vague. A 5% jump is totally different from a 15% jump. The reader has no idea what "slightly" means.

Strong response: "Managers earn significantly more than other positions, starting at $45,000 in Year 1 and rising to $52,000 by Year 3—a $7,000 increase. Analysts and Coordinators follow the same upward trend, though their salaries remain considerably lower, at $36,800 and $30,900 respectively in Year 3."

See the difference? The second response uses actual figures, compares them across positions and years, and describes the scale of change. That's Band 7 territory. The first one is Band 5 because it's too generic and lazy.

How a Salary Table Comparison Checker Actually Works

A salary data comparison checker isn't magic. It's a system that forces you to slow down and verify three specific things before you submit.

First: Does every number match the table? Read your draft and check each figure against the source. If you wrote $52,000, point to that cell and confirm it's correct. This takes 90 seconds and catches careless errors.

Second: Did you describe the actual comparison, not an imaginary one? If the table shows Manager salaries rising from $45,000 to $52,000, you can say "salaries increased by $7,000 (15%)." You cannot say "salaries doubled." A checker flags when your claim doesn't match the data.

Third: Did you cover the main features? Band 7 responses identify the highest, lowest, and most significant changes. Band 5 responses pick only one. A checker confirms you've hit all the key comparisons.

Real-world breakdown: In the exam, you get 20 minutes for Task 1. Spend 3 minutes reading the table carefully, 12 minutes writing, and 5 minutes checking. Skip the checking step, and you're gambling with your band score.

Three Common Salary Table Mistakes

Mistake 1: Confusing rows and columns. You read the manager's Year 3 salary as Year 1. Or you compare the wrong departments. This happens under pressure. A checker makes you point to the exact cell before you describe it.

Mistake 2: Rounding carelessly. You write "$35,000" when the table says "$34,200". That's not rounding—that's inaccuracy. Examiners catch this immediately. A checker flags it in seconds.

Mistake 3: Describing data that doesn't exist. You write "Salaries peaked in Year 5" but the table only goes to Year 3. You're inventing information. Band descriptors call this "inconsistent with the data." It's an automatic mark loss. A checker prevents this by flagging any claim not visible in the table.

Weak: "The salary data shows that all three positions experienced rapid growth. Managers saw the largest increases, while Coordinators remained stable."

The problem: "rapid growth" and "remained stable" are unsupported. The data shows steady increases across all positions. The language contradicts the table.

Strong: "All three positions showed consistent salary growth over the three-year period. Managers experienced the largest absolute increase of $7,000 (16%), while Coordinators increased by $2,900 (10%). Analysts fell between these two, with a $4,800 (15%) rise."

Now you've quantified the growth and shown exact comparisons. This is testable, accurate, and worth band points.

The Verification Checklist: Before You Finish Your Task 1 Description

You've written your response. Now comes the paranoid part: checking it like your score depends on it.

Because it does.

  1. Read each number aloud. Say "$45,000" out loud and point to that cell. Your brain catches errors faster when you use two senses. This takes 60 seconds.
  2. Highlight every comparison you made. Find "Managers earn $7,000 more" in your text. Now find both numbers ($45,000 and $52,000) in the table. Do they match? Mark them.
  3. Check for invented trends. Did you say salaries "peaked" or "dropped"? Look at the table. Do the numbers actually peak or drop, or are they consistently rising? If you used words like "dramatic," "minimal," or "stable," does the percentage change support that?
  4. Count your main features. How many positions did you compare? How many time periods? Band 7 responses usually compare at least 3-4 key features. Count before you finish.
  5. Read your intro sentence twice. This is where many students overstate or understate. "The table shows salary data for three positions" is accurate. "The table reveals shocking disparities in pay" is editorializing. Keep it neutral.

Real Example: Salary by Department Over Four Years

Here's a realistic exam structure. The table shows average salaries for Finance, HR, Operations, and IT departments across four years. A weak response might say:

Weak: "The four departments have different salaries. Finance employees earn the most and IT employees earn the least. Over time, all salaries went up. This shows that companies value Finance more than IT."

Why is this Band 5 at best? It's vague ("different salaries," "went up"), it lacks specific numbers, and the last sentence is opinion, not description. The table never says what companies "value."

Strong: "The table presents average annual salaries for four departments across a four-year period. Finance consistently offers the highest salaries, starting at $68,000 and reaching $74,500 by Year 4, an increase of 9.6%. In contrast, IT salaries begin at $52,000 and rise to $56,800, representing 9.2% growth. Operations and HR fall between these extremes, with Operations rising from $58,000 to $63,200 and HR moving from $55,000 to $59,800. All four departments show steady upward salary trends, with Finance maintaining the largest wage premium throughout."

This response does three things the weak one doesn't: exact starting and ending figures, percentage increases that show the scale of change, and direct comparisons across all four departments. That's Band 7 or 8 work.

Pro tip: When you write percentages, show your math. "A $7,000 increase on a $45,000 base is a 15.6% rise." This proves you understand the data, not just copying numbers.

Building the Checking Habit in Your Study Routine

You won't have a checker in the exam. But you can use one in practice to build the muscle memory of accuracy. Here's the realistic timeline:

Week 1-2: Write Task 1 responses without checking. Submit them. See what errors you catch versus what a checker flags. Most students miss 15-20% of their mistakes when working fast. Track your personal weak spots.

Week 3-4: Use an IELTS writing checker on every practice response. Don't just look at the score—read the feedback. Why did it flag that number? What comparison did you miss? Some students always round too much. Others skip the smallest category. Know your patterns.

Week 5+: Write under timed conditions (20 minutes). Then use a checker on your draft. This simulates exam conditions while letting you verify accuracy. By exam day, you'll have a mental checklist running automatically as you write. You won't need the tool anymore.

The goal is to train your brain to spot mistakes in real time, not become dependent on tools.

Why Examiners Focus on Number Accuracy in Task 1

IELTS Writing Task 1 isn't a creative exercise. It's a test of your ability to extract information accurately and describe it clearly. The band descriptors for Task Response specifically mention "accurate" at Band 8, "accurate with minor lapses" at Band 7, and "partially accurate" at Band 6.

One wrong salary figure is a "lapse." Two or three wrong numbers slide you into "partially accurate" territory. A checker ensures you stay in the "accurate" band.

Think of it this way: you wouldn't submit a financial report with wrong numbers. Your IELTS essay is professional communication. Accuracy matters more than flowery vocabulary. When you're describing data, precision is your job. Period.

How Percentages Make Your Response Stand Out

Weak responses report numbers. Strong responses report numbers with context. If the Manager salary goes from $45,000 to $52,000, that's a $7,000 jump. But is that 5% growth or 20% growth? A reader can't tell without the percentage.

Band 7 writers include both. "Managers saw their salary increase from $45,000 to $52,000, a 15.6% rise." Now the reader understands the scale of change. This shows you actually analyzed the data, not just transcribed it.

Calculating percentages takes 10 extra seconds per comparison. It's worth it. Examiners notice.

Questions About IELTS Task 1 Number Accuracy

Not without signaling it. If the table shows $34,200 and you write $34,000, that's an inaccuracy in the examiner's eyes. If you need to round, use "approximately" or "roughly" to signal the rounding. Better option: use the exact figures from the table. It takes the same number of words.

Band 7 responses usually compare across 3-4 key features (positions, departments, years, or categories). What matters more is depth: compare highest to lowest, identify trends, and explain the scale using percentages or absolute figures. Quality beats quantity.

You're not required to, but it's impressive. Band 8 responses often include percentages because they show you understand data magnitude. A $5,000 increase on a $50,000 salary (10%) is different from a $5,000 increase on a $100,000 salary (5%). Percentages push your response from Band 6 to Band 7.

Use concrete language tied to numbers. Instead of "salaries skyrocketed," write "salaries increased by 18%." Instead of "minimal growth," write "salaries rose by $2,000 over four years." By anchoring every claim to specific data, you can't accidentally invent a trend. If the data doesn't support the word, cut it.

Describing means reporting what the data shows: "Managers earn $7,000 more than Analysts." Interpreting means explaining why or judging it: "Managers earn more because their role is more valuable." Task 1 asks for description only. Stick to facts and comparisons. Save interpretations for Task 2.

Check your Task 1 with a free IELTS writing checker

Test your IELTS writing with an instant accuracy check. Our IELTS essay checker catches data errors, verifies your comparisons, and scores your response in seconds. See exactly where you lose band points.

Check My Essay Free