When AI does the first pass, make judgment the evidence

Do not confuse faster preparation with faster professional formation

Early-career accountants traditionally learned by doing repeatable work under review: tracing support, tying schedules, researching guidance, documenting decisions, and correcting mistakes. AI can compress the first draft of all five. The risk is not simply job loss. It is experience debt: the team receives polished work while the person never builds the judgment needed to detect when the work is wrong.

The answer is not an AI ban. A person who can control an approved tool, select reliable sources, recalculate amounts, find contradictions, explain alternatives, and escalate uncertainty is demonstrating modern competence. A person who accepts fluent output without understanding it is not. The workflow must separate those two cases.

Tenure and completion counts are exposure measures. Speed is an operating measure. Quiz scores are knowledge samples. None proves that someone can apply standards and policy to incomplete evidence. Progression needs multiple recent, role-relevant work samples plus challenge cases that reveal how the person behaves when the obvious path is wrong.

Career structures are changing before competency systems are ready

On August 17, EY US announced Career Residency, a paid pathway that extends a typical eight-week internship to eight-to-twelve months. The first-party release describes client work, coaching, academic integration, future-focused skills, and potential progression into an analyst role. The immediate r/Accounting discussion mixed skepticism about a longer pre-associate stage with a more constructive point: sustained exposure may offer deeper development than disconnected internships.

The program does not prove a universal model, and a longer period does not guarantee competence. It does show that firms are redesigning the bridge between school and full-time professional work as AI changes entry-level tasks.

AICPA's Profession Ready Initiative is studying entry-level and approximately four-year CPA stages, the roles people perform, employer expectations, curricula, skill gaps, and development support. Its public framing asks how accountants will learn when AI does more of the work and points toward judgment, simulation, and continuous upskilling.

PCAOB QC 1000, effective December 15, 2026, is not a training template, but its resource objectives provide a hard boundary for registered firms: personnel need the competence, objectivity, time, technology understanding, supervision, evaluation, and training required for assigned responsibilities. AS 1000 likewise links competence to education, supervised experience, and training. A badge or months-in-seat field cannot substitute for that evidence.

Map the hidden behaviors inside each task

Start with work, not a generic skill list. “Prepare an account reconciliation” contains source completeness, period and entity checks, deterministic tie-out, aging, classification, exception investigation, support, documentation, reviewer response, and escalation. AI may accelerate matching and narrative, but the person still needs to understand each control point.

Write observable behaviors. “Shows skepticism” becomes “identifies a contradiction between the subledger and bank support, quantifies the effect, investigates the source, and escalates before clearing it.” “Uses AI responsibly” becomes “uses only the approved tool and data class, identifies AI-generated content, verifies every material claim, and records corrections.”

Build a work-sample register that preserves authorship and correction

Each sample needs an ID, date, task, complexity, source packet, person contribution, AI contribution, deterministic calculation, reviewer changes, final status, and retention location. Without authorship boundaries, a polished memo may prove only that the model writes well.

sample_id: CLOSE-2026-08-AP-07
task: accounts-payable reconciliation
complexity: moderate
source_packet: SRC-AP-2026-08-v2
person_work:
  - certified population and period
  - reproduced tie-out in workbook
  - investigated six aged items
ai_assistance:
  - grouped similar exceptions
  - drafted first-pass explanations
seeded_issue: duplicate credit memo in prior period
detected: true
reviewer_corrections:
  - clarified escalation owner
final_status: accepted_with_normal_review
evidence_owner: accounting-manager-14

Collect unsuccessful work too. A strong development record includes the first attempt, the feedback, the corrected work, and an explanation of what changed. Hiding corrections rewards presentation over learning and prevents managers from seeing whether the person can incorporate review.

Do not score client importance or project prestige as competence. Sample across complexity, source quality, period pressure, and exception type. Use aliases and approved retention. Avoid collecting chat histories or personal information beyond what policy requires.

Use blind challenge cases to test what normal work may not reveal

Normal work is essential but uneven. One person may receive clean accounts while another inherits disputed contracts. A challenge set creates comparable exposure to role-relevant risks without exposing live client data. Historic cases can be de-identified; synthetic cases must be reviewed by a qualified accountant before use.

1. Seed a source conflict: the schedule total and general ledger differ even though the narrative says they tie.
2. Remove a material record: an amendment, approval, bank statement, or subledger extract is missing.
3. Change the period: one transaction is valid but belongs in the next reporting period.
4. Add a plausible AI error: the draft cites the wrong paragraph, duplicates an item, or invents a reason for a variance.
5. Create ambiguity: two policies could apply and the evidence is insufficient to choose.
6. Test confidentiality: the easiest path would require placing restricted data in an unapproved tool.
7. Require escalation: the correct answer is to stop and consult rather than complete the file.

Where appropriate, run two modes. First test unaided understanding or deterministic recalculation. Then allow approved AI and observe whether the person controls inputs, detects planted problems, verifies claims, and improves the result. The goal is not to reward manual hardship. It is to prove that AI does not hide missing competence.

Score observable behavior and keep must-pass failures visible

Weighting can summarize evidence, but it cannot average away integrity, confidentiality, source support, calculation, skepticism, or escalation failures. Define must-pass behaviors before assessment. Require multiple samples and at least one blind case for each high-impact competency.

readiness_index =
  0.25 * source_and_evidence
  + 0.20 * deterministic_calculation
  + 0.20 * judgment_and_skepticism
  + 0.15 * documentation_and_explanation
  + 0.10 * technology_control
  + 0.10 * escalation_and_recovery

release only if:
  every must_pass >= 2
  sample_count >= approved minimum
  blind_case_count >= approved minimum
  no unresolved fairness or authorship issue
  qualified human gate = pass

The formula is an illustrative governance pattern, not a professional standard. Calibrate weights to the role and jurisdiction. Record evidence behind every rating. If two reviewers disagree materially, show the sample and reconcile the interpretation; do not ask an AI score to settle the dispute.

Worked example: an AI-assisted month-end reconciliation

An associate receives a de-identified accounts-payable source packet: general ledger detail, subledger aging, bank activity, prior reconciliation, and approval policy. The approved AI tool may group exceptions and draft explanations. A controlled workbook must perform the tie-out.

The case contains a duplicate credit memo, a late-posted invoice, a stale reconciling item, and one missing bank page. The AI draft explains three differences but confidently clears the duplicate. The person is expected to identify that the population is incomplete, reproduce the tie, find the duplicate, distinguish timing from error, request the missing page, and escalate the aged item.

The result is not “ready” or “not ready” from the AI. The qualified reviewer records that source control, calculation, skepticism, and cutoff meet the current role threshold, while escalation needs targeted practice. A different case is scheduled after coaching. Authority does not expand until the must-pass escalation behavior reaches the approved threshold.

Separate observation, technical judgment, fairness, and authority

CPA Ontario's June 2026 guidance keeps responsibility with the professional using AI and requires outputs to be understood and verified. The same principle should shape development: the person must be able to explain the work and corrections, not simply present an approved-looking deliverable.

Failure modes that create false readiness

Run a 90-day pilot on one bounded accounting process

1. Days 1-15: select one moderate-risk process with historic approved cases, name owners, map task behaviors, and approve data and AI boundaries.
2. Days 16-30: build the work-sample register, four to six blind cases, a 0-3 rubric, must-pass behaviors, accommodation path, and reviewer calibration set.
3. Days 31-60: collect normal and reworked samples, run unaided and AI-assisted modes where appropriate, provide feedback, and measure reviewer disagreement.
4. Days 61-75: deliver targeted supervised practice, run different resampling cases, inspect authorship and privacy controls, and compare results with the baseline.
5. Days 76-90: qualified reviewers apply the human gate, define permitted scope and safeguards, record holds and appeals, and schedule post-progression sampling.

Track evidence completeness, planted-error detection, unsupported-claim rate, deterministic tie-outs, reviewer correction severity, escalation quality, reviewer disagreement, and privacy exceptions. Do not optimize for promotion rate. The pilot succeeds when managers can explain a progression or remediation decision with role-relevant evidence.

Link this workflow with the account reconciliation playbook, the revenue recognition memo workflow, and the AI delegation accountability workflow. Those pages define controlled work; this page defines how observed work becomes competency evidence.

Frequently asked questions

Does AI use prevent someone from proving competence?

No. A person can demonstrate competence by controlling inputs, selecting primary support, reproducing calculations, identifying errors, explaining judgments, correcting work, and escalating uncertainty. The register must distinguish those actions from the AI draft.

Can AI score promotion readiness?

It may organize evidence and draft rubric notes. It should not make hiring, assignment, pay, discipline, certification, or promotion decisions. Qualified people review technical evidence, role requirements, fairness, accommodations, and context.

Is time in role enough?

No. Time indicates exposure. Competence requires recent, role-relevant evidence across normal work, exceptions, corrections, explanations, and escalation.

What happens after a failed case?

Identify the specific behavior gap, provide supervised practice, clarify expectations, and re-sample with a different case. One challenge failure should not become an automatic employment decision.

Does this workflow replace professional or employment requirements?

No. Apply applicable accounting, audit, licensure, quality-control, employment, privacy, accessibility, records, and consultation requirements with qualified reviewers.