
How to Write Good Flashcard Questions
A flashcard is not a summary with a fold in the middle. It is a question designed to make you retrieve one piece of knowledge from memory. The wording decides whether the card tests recall or merely lets you recognise a sentence you have seen before.
Flashcards turns notes into a deck and lets you review the cards with active recall. Whether you write the questions yourself or edit generated ones, the same rules apply.
Quick answer
Ask about one idea per card and make the answer specific enough to check. Name the scope so the question has a single defensible answer, and keep both sides short enough to answer aloud in a few seconds. Avoid yes-or-no prompts, hidden clues, and questions that could be answered by guessing. If a card keeps failing, rewrite it rather than repeating it.
One idea per card
Broad prompts feel efficient because they cover a lot of material, but they are hard to answer and hard to mark. “Explain photosynthesis” might produce a paragraph, a diagram, or a list of inputs and outputs, depending on the day. Split it into separate cards: what the process uses, what it produces, where it happens, and why it matters.
Make the question unambiguous
Name the scope in the question. “What is the capital of Australia?” has one answer. “What is the capital?” does not. If the course uses a particular definition, say so: “In the module’s definition, what does *validity* mean?” If the answer depends on a period or a place, include it. Ambiguity is not a difficulty; it is noise that makes every review uncertain.
Watch pronouns and vague verbs. “What does it do?” and “Why is this important?” force you to guess what “it” or “this” refers to, especially weeks later. Replace them with the actual subject. “Discuss” and “explain” are also weak unless you state how much detail you need. A specific question is easier to answer and easier to mark.
Avoid clues and recognition traps
Test the card before you trust it
Read the question, look away, and answer aloud. If you hesitate because you are unsure what is being asked, the card is ambiguous. If you can answer in several different ways and all seem defensible, the scope is too wide. If the answer is a paragraph, the card contains more than one idea. Rewrite it and test again.
Keep the back of the card short. A long answer encourages you to read it and nod rather than produce it. If you need context, put a brief note on the front or keep a separate reference page. The card itself should be a prompt and a check, not a chapter.
Review the wording occasionally. Cards that keep failing are often badly written rather than difficult, and a card you can answer without thinking may no longer be worth reviewing. Retire the trivial ones and split the ones that keep producing partial answers.
Pasted material is sent to a server to build the deck, while the deck itself stays in your browser. Do not paste personal notes, private student records, or anything you would not put in an email; the page states what is sent. For the scheduling side, read Leitner System vs Spaced Repetition: How to Schedule Reviews. For the full method, see How to Make Flashcards That Actually Work.
Start with a small deck in Flashcards, write one clear question per idea, and answer it before you look. A modest deck of precise questions is worth more than a large one you can only recognise.
Common questions
What makes a flashcard question good?
It tests one idea, has a specific answer, and cannot be misunderstood without context. Keep it short enough to answer aloud in a few seconds. If you cannot tell whether your answer was right, the question needs rewriting.
Should flashcards use yes or no questions?
Usually not. A yes-or-no card gives a fifty per cent chance of guessing and does not require you to produce the knowledge. Rewrite it as a question that asks for the term, cause, value, or explanation, so the answer has to be recalled rather than guessed.
How do I fix a card I keep getting wrong?
First check whether the question is ambiguous or contains more than one idea. Split it, name the scope, or shorten the answer. Repeating a badly written card trains confusion; rewriting it is usually faster than trying to memorise around the problem.
