A strong NPTE error log answers three questions: Why did I miss this, what rule should change, and when will I retrieve it again? It should not become a second textbook or a collection of copied question stems.

The simpler the log, the more likely you are to use it.

The six fields to record

Use one row per meaningful error:

| Field | Example | |---|---| | Date and content area | Aug 28 — cardiopulmonary | | Confidence | Confident / unsure / guess | | Error type | Knowledge / interpretation / priority / assumption / pacing | | Missed rule | Check stability and safety before progression | | Corrected reasoning | Explain in your own words | | Revisit date | Aug 30 and Sep 5 |

Do not copy protected NPTE or PEAT items. For independent practice, follow the product’s terms and record concepts rather than reproducing proprietary questions.

Start with confidence

Confidence changes the meaning of an answer:

• Wrong and confident: likely misconception; highest priority.
• Wrong and unsure: gap or poor discrimination; teach the distinction.
• Correct but unsure: fragile knowledge; review and retrieve again.
• Correct and confident: maintain through mixed practice.

If you record only wrong answers, you miss correct guesses that may fail next time.

Choose one error type

Knowledge

You did not know or could not retrieve a relevant concept. Correct it with a narrow source, then close the source and explain it.

Interpretation

You misunderstood the task word, setting, phase of care, or key finding. Write the question’s actual task in plain language.

Prioritization

Several options were reasonable, but you chose the wrong sequence or level of urgency. Write the rule that separates “reasonable” from “best now.”

Assumption

You added a detail that was not stated. Record which invented assumption drove the choice.

Pacing

Time pressure, rushing, or overthinking changed the answer. Add a timing action, not a content chapter.

Use one primary label. Too many labels make trends hard to see.

Write a transferable rule

Weak note:

I missed question 42 about a patient with several details.

Stronger note:

When the task asks for the first action, resolve immediate safety and stability before choosing a later intervention.

The second note can guide a future case even when every clinical detail is different.

Schedule retrieval

Learning happens when you must produce the corrected idea again. Add a revisit date as soon as the entry is created.

A practical pattern:

• First revisit in two days
• Second revisit about one week later
• Later test in a mixed set

Research on retrieval practice has found benefits from relearning across separated sessions. Treat the schedule as a flexible principle rather than a guarantee or one required interval.

Run a weekly pattern review

Once a week, count only the error types and content areas. Look for patterns:

• Three confident errors in the same concept
• Strong knowledge but repeated “first” versus “best” mistakes
• More pacing errors in late sections
• One smaller content area appearing across several cases

Choose one change for the next week. For example: “Before looking at options, I will identify the task word and setting.”

Keep the log small

Use a rule such as:

• Log all confident errors.
• Log repeated uncertain errors.
• Log any pacing pattern.
• Skip isolated details that are unlikely to transfer after the rationale is understood.

If the log grows faster than you can revisit it, tighten the criteria.

What to do with resolved entries

Mark an entry resolved only after you retrieve the corrected reasoning and apply it successfully in a new context. Do not delete it immediately; archive it so you can see progress without cluttering the active list.

Use three states:

• Active
• Revisit scheduled
• Resolved

Pair the log with official preparation

FSBPT recommends reviewing the content outline and offers PEAT with rationales and references. An error log can organize what you learn from practice, but it does not replace official exam information or create an official readiness score.

A five-minute setup

1. Create a table with the six fields above.
2. Add the last five meaningful practice errors.
3. Assign one error type to each.
4. Write one transferable rule.
5. Schedule two short revisits.

That is enough. The system becomes valuable through reuse, not visual complexity.

PTverse records practice performance and lets you return to missed and flagged questions. Use the error-log method to turn that review into a change in reasoning.