The EDAIC Wrong-Answer Log: A Practical Template

An EDAIC wrong-answer log should change what you do next. If it is only a list of question numbers and correct answers, it will grow quickly and teach very little.

The useful unit is one statement-level error pattern: what you believed, why the belief failed, which authoritative source corrected it, and how you will test the corrected rule in new wording. This matters for Part I because each multiple true/false stem contains independently judged statements. One stem can therefore reveal several different kinds of error.

Below is a copyable Markdown template, a practical taxonomy and a weekly workflow. There is no imaginary download: copy the table directly into your notes, spreadsheet or paper system.

If the statement structure itself is unfamiliar, review the EDAIC MTF technique guide before interpreting every miss as a content gap.

What the log is designed to detect

The log answers five questions:

1. Which concepts repeatedly cause errors?
2. Which errors come from reading or decision process rather than missing facts?
3. Which correct answers were guesses?
4. Which sources or rules may be outdated or conflicting?
5. Did the correction transfer to a new statement after a delay?

It is not a transcript of every explanation. Keep the question bank for full item history and the textbook for full teaching. The log holds only information that changes future behaviour.

The core error taxonomy

Use one primary code and, when necessary, one secondary code.

K — knowledge gap

You did not know the relevant fact, relationship or definition.

Repair: study the minimum authoritative section, close it, reconstruct the concept, then answer a new statement.

M — mechanism or model gap

You remembered fragments but not the causal or mathematical relationship, so you could not predict an unfamiliar variation.

Repair: draw, derive or explain the model from memory. Create a transfer question that changes one variable.

R — reading error

You missed a negative, timeframe, population, comparison or other qualifier in the stem or statement.

Repair: copy only the decisive qualifier—not the protected question—and write a reading checkpoint such as “state the population and direction before answering”.

O — overgeneralisation

You converted a tendency into an absolute, applied a rule outside its conditions or assumed that a familiar association always holds.

Repair: write the rule with its boundary conditions and one counter-context.

U — outdated or uncertain source

Your answer relied on an older guideline, local practice, memory of a superseded classification or an explanation that conflicts with a current authoritative source.

Repair: verify the issuing body, version and section. Record the date checked. Escalate unresolved conflicts rather than choosing the answer you prefer.

G — guessing

You had insufficient knowledge or confidence and selected an answer without a defensible model. Record this whether the result was wrong or correct.

Repair: identify the missing distinction. A lucky correct answer belongs in the log because the next wording may expose it.

C — confidence error

You were highly confident and wrong. This often indicates a stable misconception rather than simple forgetting.

Repair: contrast the incorrect mental rule with the corrected one, then retest with substantially different wording.

T — timing or test-process error

Knowledge was available, but pace, navigation, answer transfer, fatigue or repeated changing of answers produced the miss.

Repair: define one process experiment for the next timed set.

The copyable Markdown template

Copy this table:

Add two optional fields when useful:

• Question ID: an internal platform identifier, not copied examination wording.
• Linked concept note: a link to the one page that explains the model.

Do not paste live ESAIC questions, recalled stems or protected content into the log. Official candidate regulations state that examination questions may not be copied. Use original practice IDs and your own abstracted error description.

How to write each field

Paper/domain

Choose the most specific useful domain while keeping Paper A or Paper B visible. “Pharmacology — context-sensitive behaviour” is more actionable than “Paper A”; a five-line microcategory is not.

Confidence

Rate confidence before reading the explanation:

• low — guess or weak recognition;
• medium — plausible answer, incomplete justification;
• high — could explain the rule and still chose incorrectly.

High-confidence errors receive priority because familiarity will not naturally prompt review.

My incorrect rule

Write what your mind actually did:

• “I assumed the relationship was linear at all values.”
• “I treated a common association as mandatory.”
• “I applied the adult framework to every population.”
• “I remembered the direction but not the condition.”

Do not write “I was careless”. That label explains nothing.

Corrected rule

Use one or two sentences in your own words. Include the condition that controls the truth value. If you cannot compress the correction accurately, link to a concept note rather than forcing a misleading slogan.

Decisive qualifier

Record the word or relationship that changed the answer: timing, direction, comparator, population, probability, “may” versus “must”, or an assumed constant. This builds statement-reading skill.

Source/version

Use an authoritative text, current guideline, official document or primary source. Record edition/page or issuer/version/section and the date checked. A question-bank explanation is a starting point; verify anything consequential or conflicting.

Transfer prompt

Create a new, original prompt that tests the same rule from another angle. Do not make a trivial synonym swap. Change the variable, context or direction so that recognition of wording cannot carry the answer.

Retest

Set a delayed date. Record whether the transfer answer was correct and whether confidence matched. If it fails again, update the underlying concept—not merely the row.

The spaced-repetition guide can help you set review intervals, but the log should still prioritise consequential and recurring misconceptions.

A worked non-content example

Suppose a statement is wrong because you ignored a condition.

This preserves the learning pattern without reproducing a question.

The five-minute post-set workflow

Step 1: capture candidates

Mark:

• every wrong statement;
• every low-confidence correct statement;
• every high-confidence disagreement with the explanation;
• every item where timing changed the decision.

Step 2: cluster

Before creating rows, group errors that share one model. Five incorrect statements may need one concept repair and several transfer prompts, not five copied explanations.

Step 3: classify

Assign the primary code. If you cannot distinguish K from M, ask: “Would recalling one fact solve this, or do I need to understand a relationship?” Use R only when knowledge was truly available.

Step 4: verify

Open the most appropriate source. For an official exam rule, use ESAIC. For a clinical or scientific claim, use an authoritative current reference. Record version and section.

Step 5: schedule

Choose a realistic retest. Important high-confidence errors return sooner; stable low-priority details can wait. Keep the queue smaller than your capacity.

The question-bank effectiveness guide shows how this fits into a complete review.

Why immediate feedback matters

Retrieval makes you expose a current mental model. Corrective feedback can then update it. Experimental work has found that retrieval followed by immediate feedback can support correction of false memories more effectively than passive restudy in the studied tasks. Broader retrieval-practice research also supports testing as a learning event rather than merely an assessment.

The lesson is not “errors are automatically good”. Unsupported errors can persist. The sequence is:

1. commit to an answer;
2. rate confidence;
3. inspect accurate feedback;
4. explain the discrepancy;
5. retrieve again after a delay.

ESAIC's evidence-based learning guidance similarly recommends active recall and regular review of missed true/false statements.

Try 10 EDAIC questions free — no card required. After the set, log only the error patterns and guesses that deserve a future decision. AnesCORE is independent of and not endorsed by ESAIC.

The weekly wrong-answer review

Set aside 30–45 minutes once a week.

Count patterns, not just errors

Summarise:

• errors by Paper A and Paper B;
• errors by domain;
• high-confidence errors;
• repeated codes;
• rows with no source;
• overdue transfer tests;
• concepts that failed more than once.

Find the smallest useful repair

Choose up to three:

• one foundational model to relearn;
• one reading habit to practise;
• one outdated source to resolve;
• one paper imbalance to correct;
• one timing experiment.

Do not rewrite the whole log.

Retest before rereading

For due rows, attempt the transfer prompt first. If correct with a sound explanation, mark the row “corrected” and move it to spaced maintenance. If wrong, reopen the source and revise the model.

Feed the study plan

Convert the patterns into next week's sessions. If R errors dominate, add deliberate statement parsing to mixed sets. If M errors dominate in one domain, schedule concept reconstruction before more questions. If T errors appear only in long sessions, adjust mock practice.

Our study-plan guide can hold those actions; the log supplies the evidence.

Metrics worth tracking

Avoid obsessing over total rows. Track:

• repeat-error rate: errors already seen as a proportion of current errors;
• high-confidence error count: ideally falling;
• correction rate: due transfer prompts answered correctly with explanation;
• source-complete rate: active rows with authoritative version tags;
• paper balance: active unresolved errors in A versus B;
• time to repair: delay from first error to successful transfer.

These are learning metrics, not official predictors of passing. A falling error count can also mean you are choosing easier questions, so interpret it with coverage and first-attempt difficulty.

Compare repeated patterns with the common EDAIC preparation mistakes rather than treating one weak set as a diagnosis.

Common ways logs become useless

Copying the explanation

This records the provider's prose, not your misconception. Replace it with incorrect rule versus corrected rule.

Logging everything

The queue becomes unreviewable. Log wrong, guessed, high-confidence-conflict and recurring process items. Let the platform retain routine correct history.

Never retesting

Without transfer, the row documents an intention. Add a date and result.

Using “careless” as a diagnosis

Specify the missed qualifier, timing behaviour or decision step.

Hiding lucky answers

Correct guesses inflate confidence and remain vulnerable. Capture them under G.

Trusting one explanation blindly

Verify conflicts and version-sensitive facts. Do not let an unsourced explanation overwrite an authoritative current source.

Reproducing protected questions

Store an ID and abstracted lesson. Never copy real or recalled EDAIC content.

Frequently asked questions

Should I log every wrong EDAIC question?

Log every meaningful wrong statement, lucky guess, high-confidence conflict and recurring process error, but cluster items sharing one misconception. Do not copy full explanations.

Should the log be a spreadsheet, notebook or app?

Use whatever you will update and retest. A spreadsheet helps filtering; paper can reduce friction; linked digital notes help source/version tracking. The fields matter more than the tool.

When should I retest an error?

Retest after enough delay to require retrieval, then adjust based on importance and recurrence. There is no universal interval for every topic.

What if the question-bank explanation conflicts with my textbook?

Check edition and date, then consult a current authoritative source or guideline. Mark the row U until resolved. Do not simply choose the answer that protects your score.

Do correct guesses belong in the log?

Yes. A correct low-confidence guess is not stable knowledge and can fail under new wording.

Can the error log predict my EDAIC result?

No. It is a formative tool. Combine it with coverage, unseen accuracy, timing, Paper A/B balance and official examination information.

Make every error earn its place

The value of a wrong-answer log is not how many mistakes it stores. It is how reliably it turns an exposed mental rule into a corrected, sourced model that survives new wording.

Copy the template, then Try 10 EDAIC questions free — no card required. Classify the first genuine gap, schedule one transfer prompt and build the habit from there.

Sources and official links

• ESAIC evidence-based study guide
• ESAIC Diploma Guide 2025
• ESAIC Part I paper examination regulations
• Maraver and colleagues: retrieval and corrective feedback
• Performance feedback and test-potentiated encoding
• Roediger and Butler: retrieval practice and long-term retention