Candidate vs. confirmed requirements: a safer application workflow

Treat a starter checklist as a research queue

A generic checklist is useful for remembering what to investigate. It can suggest categories such as transcripts, tests, recommendations, writing, portfolios or financial documents. It cannot establish that every item applies to a particular applicant.

Common App's official first-year guide tells applicants to track each college's unique requirements and notes that colleges can make different choices about recommendations, testing and writing. EducationUSA's undergraduate application guidance states that U.S. application requirements can vary greatly and directs applicants to each institution's official information. Those sources support a cautious workflow: use general guidance to generate questions, then verify the answers for the exact destination.

The checklist should therefore begin as a research queue. Capturing an item means it deserves investigation, not that the applicant has already received an official instruction.

Use candidate, confirmed and superseded states

Three states preserve both speed and caution.

Only confirmed items should affect completion percentages, readiness indicators or warnings that an application is incomplete. Candidate items can remain visible in a research view. Superseded items should leave the active checklist while retaining enough context to explain why they no longer drive action.

Unresolved is not a fourth state. It is a review flag applied to a Candidate item when official evidence conflicts or is incomplete. The flag blocks promotion to Confirmed until the conflict is clarified, while the underlying state remains Candidate.

This model does not prove that the underlying information is correct forever. Confirmation is a documented state based on the source and time checked, which is why scope and review triggers matter.

• Candidate means a possible requirement discovered through general guidance, prior knowledge, a template or early research.
• Confirmed means the item was checked against an official source for the relevant institution, program, applicant type and entry cycle.
• Superseded means the item was once relevant or believed to be relevant but has been replaced, removed or made inapplicable by stronger current evidence.

Record the minimum evidence for confirmation

A requirement name alone is not enough. The verification record should answer what applies, to whom, where the instruction came from and when it was checked.

Avoid copying more personal information than the workflow needs. The evidence record is about the rule and its scope, not a place to duplicate sensitive academic, identity or financial documents.

• Institution and program or pathway.
• Applicant type, such as first-year, transfer, graduate or international where relevant.
• Entry term or application cycle.
• Exact requirement and any condition that changes whether it applies.
• Direct official source URL or named official portal.
• Date checked and the person responsible for the check.
• Deadline and time zone only when the official source supplies them.

Follow one hypothetical requirement through the states

Imagine a starter checklist proposes a standardized test score. At first the item is Candidate because it came from a reusable template. It appears in the research queue but does not reduce application readiness.

The applicant checks the institution's official page for the correct program and entry cycle. The page states that the score is optional for this applicant type. The record is updated with the source, cycle, date checked and condition. Depending on the applicant's decision, the item can become a confirmed optional choice rather than a required task.

Later, the institution updates its policy for a new cycle. The old record becomes Superseded and the new cycle receives its own candidate item for verification. The history explains why last year's workflow differs without allowing an old rule to remain active.

This example is hypothetical. It demonstrates the state change; it is not evidence about any real institution's current testing policy.

Define promotion and review rules

Promotion from Candidate to Confirmed should require the minimum evidence fields rather than a person merely changing the status. If the platform supports validation, prevent a confirmed state when the official source, scope or checked date is blank. If it does not, place incomplete confirmations in a review view.

Create review triggers for time-sensitive information. A new application cycle, revised institution page, changed program, different applicant type or conflicting portal instruction should reopen verification. Do not update the check date simply to make the record look current; perform the review and record what was found.

When two official sources appear to conflict, return the requirement to Candidate and apply the Unresolved review flag. Preserve both links, record the disagreement and contact the institution or relevant application service. Remove the flag and promote the item to Confirmed only after the conflict is clarified with sufficient official evidence. A dashboard should not manufacture certainty from contradictory evidence.

Keep official instructions in control

The workflow organises research; it does not replace an institution, program, government agency or official application platform. Applicants should follow the instructions for their own circumstances and seek clarification from the responsible organisation when the consequences of an error are significant.

Use the system to expose uncertainty early. Candidate items show what still needs research. Confirmed items show what currently has sufficient evidence to drive action. Superseded items preserve the reason an old instruction stopped applying.

That separation allows broad capture without confusing possibility with obligation, the key distinction a reusable application workspace must protect.