To assess working memory demands in multistep tasks, map what Wren must hold, update, reorder, ignore, retrieve, or record at each step. Define the task, time gap, interruptions, language, response mode, and ordinary tools. Compare performance with accessible checklists, models, AAC, repetition, or reduced load. An error pattern can guide support; it does not reveal a pure memory capacity by itself.

Map the information load

For every step, list the information Wren must encode, keep active, update, transform, ignore, retrieve, or place in an external record. Mark how many elements compete and how long they must remain available.

Treat external tools as ordinary supports

Checklists, calendars, labels, written models, timers, AAC, calculators, notes, and reminders can be part of successful performance. Assess whether a tool is accessible, accurate, current, portable, acceptable, and under Wren's control.

Separate memory from other task demands

Audit hearing, vision, language, reading, motor action, navigation, attention, interruption, anxiety, time pressure, unfamiliar vocabulary, and the response requirement. Use control items only when they answer a stated alternative.

Score scenarios and error locations

Preserve the number of scenarios, opportunities within each, correct updates, repetitions, requests, external checks, corrections, and incomplete records. Avoid treating correlated errors inside one scenario as independent evidence.

Use this sequence to assess working-memory demand

Map Wren's load, preserve ordinary tools, audit access, define scenario outcomes, compare one useful support, ask about effort, inspect remaining errors, and choose or close the next action.

Build Wren's working-memory demand map

Create one versioned working-memory demand map for the community event-booking desk. Include Wren's priority, exact task, executive-demand hypothesis, ordinary supports, instructions, access, eligible opportunities, observable outcomes, latency or sequence when relevant, direct experience, informants, measurement methods, privacy, health, invalidity, missingness, withdrawal, alternatives, design limits, qualified owner, correction, decision rule, and reassessment trigger. Store only decision-relevant information with role-limited access. To assess working memory demands in multistep tasks fairly, preserve the outcome and information load across support conditions. Record any wording or timing difference that remains.

Validate Wren's evidence

Reproduce 18 scenarios, spoken-only 5/9, checklist 8/9, and recognition 9/9. Verify item load, update points, delay, interference, language, response form, vision, AAC, practice, order, prompts, errors, corrections, experience, and scenario-level denominators.

Connect Wren's evidence to a decision

Wren chooses the visible checklist as the default booking interface. The team studies whether the remaining error reflects an unclear field, interruption, or another access issue instead of withdrawing the tool for testing.

Work through Wren's example

Wren completes nine booking scenarios from spoken instructions alone and nine matched scenarios with an accessible visible checklist. Five of nine spoken-only scenarios retain every changing detail; eight of nine checklist scenarios do. A separate recognition check is 9/9. The conditions differ in external memory support and order, so the 5/9 and 8/9 pattern guides support without isolating one cause. Preserve every planned and eligible event, task and support version, access and health state, direct report, method, informant, prompt, invalid record, correction, unresolved item, and outcome. This fictional example demonstrates one assessment control. It supplies no diagnosis, global executive-function score, treatment effect, legal conclusion, coverage decision, or outcome guarantee for Wren.

Address Wren's main interpretation risk

Counting each forgotten detail as a separate participant failure inflates the denominator and ignores clustered errors within scenarios. Calling checklist use dependence frames an ordinary tool as a weakness. Practice, order, wording, anxiety, and visual access remain possible contributors. Review language, memory, inhibition, planning, sensory and motor access, health, sleep, stress, medication, anxiety, interest, workload, task familiarity, practice, partner behavior, observer effects, source bias, client priorities, and design strength separately. A convincing task result cannot make an unsafe, inaccessible, unwanted, unauthorized, surveillance-based, or compliance-centered goal clinically appropriate.

Keep scope and authority clear for Wren

For Wren's working-memory demand map, the CASP public summary supplies high-level ABA behavioral-health-treatment scope for autistic people, with licensed detail outside this page. The current BACB Ethics Code addresses competence, client involvement, consent and assent when applicable, assessment, medical needs, risk, data, documentation, and evaluation for covered people. The BACB outline is examination content. These sources supply no global executive-function diagnosis, neuropsychological interpretation, legal authority, payer approval, or requirement that Wren perform without ordinary supports.

Use executive-function components as hypotheses for Wren

Diamond's review describes inhibition, working memory, and cognitive flexibility as core executive functions and discusses higher-order processes such as reasoning, problem solving, and planning. It also describes links with stress, sleep, social conditions, and physical health. This framework can help name a task demand. It cannot show which process explains Wren's result or turn a task score into a diagnosis.

Keep measurement methods separate for Wren

Kofler and colleagues examine weak correspondence between executive-function rating scales and performance tests and warn about construct, task-specific, informant, and shared-method problems. The review supports a multi-method record that preserves disagreement. It supplies no rule that either a rating or a performance task is the true measure of Wren.

Interpret autism research cautiously for Wren

Kenworthy and colleagues review mixed laboratory and real-world executive-control findings in autism. A meta-analysis of 235 studies and 14,081 participants reported heterogeneous results, method differences, and limited clinical sensitivity for many measures. Group findings can inform design and uncertainty. They cannot diagnose Wren, predict daily performance, or justify removing supports.

Include lived experience and access for Wren

Kenny, Remington, and Pellicano interviewed 12 autistic adolescents without intellectual disability and seven mothers. Participants described executive performance as context-dependent and affected by factors such as demand, anxiety, motivation, language, and other conditions. The narrow qualitative sample supports asking Wren directly, not generalizing its themes to every autistic person. Breaux and Smith propose individualized assent and withdrawal practices in an evolving literature. ASHA's AAC portal says AAC users should always have access to their tools or devices.

Choose Wren's next bounded action

The desk makes the checklist editable and marks updates as they occur. A short follow-up uses new matched scenarios with order balanced when feasible. Record the qualified owner, source evidence, effective date, current task and support version, ordinary tools, communication and health state, implementation check, accessible explanation, disagreement route, and reassessment trigger. Preserve the earlier record when tasks, tools, contexts, people, health, or priorities change.

Close Wren's assessment

Review the working-memory demand map with Wren, the qualified behavior analyst, relevant partners, access owners, and specialists named in the manifest. Confirm that initiation, working memory, inhibition, flexibility, planning, self-monitoring, task performance, experience, and informant report remain separate; every denominator is reproducible; useful supports, AAC, privacy, and basic access remain protected; urgent needs received action; and conclusions stay bounded to sampled tasks. Keep this page draft and noindex until every required review is complete.

Related resources

Sources