FTCE General Knowledge Test common mistakes
FTCE General Knowledge Test · Understand the traps and how to avoid them.
The writer turns the argumentative prompt into a personal narrative or a neutral two-sided report - telling a story about how the issue affected them, or summarizing 'both sides' - instead of taking one clear position on the specific issue named in the prompt.
Timed-prompt anxiety pushes candidates toward the fastest thing to produce (a story or a summary), and many have been trained that 'balanced' writing sounds mature, so they hedge rather than commit to a defensible claim.
What to do instead
Before drafting, copy the exact issue from the prompt into your scratch space, then write one sentence of the form 'X should/should not ___ because ___ and ___.' Every body paragraph must begin with a reason that plugs into that sentence. If a sentence does not advance that claim, cut it.
Support consists of vague generalities - 'in today's society,' 'everyone knows,' 'throughout history' - rather than a named example, scenario, or concrete consequence, so body paragraphs are assertion plus restatement rather than development.
Under a 50-minute clock, the brain grabs the first available sentence, and generic phrasing feels like it fills space. Candidates also worry that a made-up example is 'wrong,' so they retreat to abstraction.
What to do instead
In the planning minutes, force two concrete specifics before writing: a named event, law, study, or a fully described hypothetical situation (a specific student, a specific budget line, a specific town). After each topic sentence, write 'For example,' and do not move on until a specific detail is on the page.
Time collapses at the end: the essay stops mid-argument with no conclusion, and the last third is written in imprecise, error-laden prose because the candidate spent 15+ minutes planning or tried to force a long five-paragraph structure.
Candidates plan and draft without a clock checkpoints, and they believe length is what scorers reward, so they over-write the introduction and run out of runway.
What to do instead
Set fixed checkpoints: 5 minutes planning and outlining, 28–30 minutes drafting, 8–10 minutes to write the conclusion and revise, 5 minutes to proofread. Read the clock at the end of the introduction and at the end of the second body paragraph; if you are behind, shorten the remaining body paragraph rather than skipping the conclusion.
During proofreading or error-identification items, the candidate reads for meaning instead of structure, so transposed words, misspellings, and subject–verb disagreement across an interrupting phrase ('The list of items on the desk were...') pass as correct.
Skilled readers automatically repair errors while comprehending, so a sentence that makes sense feels correct; the eye also skips over small function words.
What to do instead
Read backwards word by word from the last sentence to the first for spelling and transposition, then read forwards to check agreement. Mentally delete any prepositional or appositive phrase between the subject and the verb before deciding whether the verb matches.
The candidate judges sentences by whether they 'sound right,' which lets comma splices, run-ons, sentence fragments, and wrong-case pronouns ('between you and I') survive because those constructions are common in speech.
Spoken-language patterns are deeply overlearned and are accepted as 'standard' by the ear; the ear detects formality, not grammatical correctness.
What to do instead
Apply a structural test rather than listening: count the subjects and verbs in the sentence. Two independent clauses require a period, semicolon, or comma plus coordinating conjunction - a bare comma is a splice. For pronouns, drop the other party from the sentence ('between you and I' → 'between I' fails, so 'me'), and check that every pronoun has one clear, correctly numbered antecedent.
On main-idea and author's-purpose questions, the candidate selects an option that is factually true in the passage but is only one supporting detail, or true-but-not-answering-the-question on any item.
Recognizing familiar wording produces a feeling of recognition that gets mistaken for correctness; options that recycle passage language feel safest even when they answer a different question.
What to do instead
Before looking at the choices, cover them, state the question in your own words, and predict the answer. Then ask of the chosen option: 'Does this cover the whole passage or just one paragraph?' and 'Does this answer the exact question asked, or just repeat something true?' Reject any detail-only option for a main-idea question.
The candidate skims past qualifiers - EXCEPT, NOT, LEAST, 'best describes,' 'primarily' - and answers the reverse of what was asked, or picks the most extreme option because it sounds decisive.
Timed reading rewards speed, and negation words are short and easy to skip; the first option that is broadly true exerts pull regardless of the qualifier.
What to do instead
Before reading the options, underline the qualifier in the question stem and restate the task ('which one is FALSE'). On EXCEPT/NOT items, mark each option T or F against the passage and select the odd one out. Treat absolute words (always, never, all, none) as red flags that require explicit textual support.
On inference, tone, and vocabulary-in-context items, the candidate answers from general knowledge or personal opinion instead of from what the passage actually supports, and defines words by their most common outside meaning rather than their use in the sentence.
Inferences feel like gaps the reader should fill with what they already know, and a familiar word triggers its dictionary default before the context is examined.
What to do instead
For every inference or tone choice, go back and put a finger on the line(s) that justify it; if you cannot point to textual evidence, discard the option. For vocabulary, substitute each answer choice back into the original sentence and reread it - the correct choice must preserve the passage's logic without distortion.
The candidate correctly performs the computation but reports the wrong quantity - area instead of perimeter, total cost instead of the difference asked for, the discounted price instead of the amount saved, or an answer in the wrong unit.
Once the arithmetic starts, attention shifts to the mechanics and the question stem stops being read; word problems bury the sought quantity at the end of a long setup.
What to do instead
Before computing, circle the words naming the quantity and write a labeled target next to your work ('target = amount saved, in dollars'). After solving, reread the last sentence of the problem and attach units to your number; if the units or the label do not match the target, redo the final step.
Percent and proportion relationships are set up backwards - percent increase and percent-of confused, 'part' over 'whole' inverted, the original amount used as the base when the new amount is required - producing a plausible-looking but wrong answer.
Percent language is compressed ('a 20% decrease, then a 10% increase'), and the candidate pattern-matches to a remembered formula instead of identifying which quantity is the base.
What to do instead
Transcribe every percent statement into an equation with named quantities before calculating ('new = original × (1 − 0.20)'). Estimate first with round numbers - a percent decrease must produce a smaller number - and reject any computed result that contradicts the estimate.
The candidate burns many minutes on a single hard item, or races the last items with sign, order-of-operations, and transcription errors, and never checks whether an answer is reasonable.
Test-takers are conditioned to finish every question in order, so a stuck item feels like an obligation rather than a choice; fatigue near the end also erodes checking behavior.
What to do instead
Run the section in two passes: answer everything you can do quickly, mark and skip anything that stalls you past about a minute, then return. Write one step per line on scratch paper and copy numbers directly from the screen. Before submitting each answer, plug it back into the original equation or context as a sanity check.