To define conversation turns without speech bias, include Yosef's person-authored contributions through speech, AAC, sign, text, gesture, movement, media, shared action, or intentional silence. Specify turn onset and end, overlap, continuation, acknowledgment, pass, pause, repair, partner turn, and topic relation. Preserve authorship and device-composition time. Spoken speed and one-message-per-turn conventions are design choices, rather than universal measures of communicative value.

Protect authorship across modes

A turn belongs to Yosef when he selects, produces, or directs the recognizable message or action. A partner can support access without choosing the content.

Define turn boundaries by mode

Speech may use utterance completion; AAC may use a finished signal or composition state; text may use send; a sketch may use presentation; shared action may use a task boundary. Document each rule.

Code overlap descriptively

Record whether a partner speaks, acknowledges, interrupts, completes, or changes topic while Yosef communicates. Overlap can be cooperative, neutral, or disruptive depending on the exchange.

Include pass and pause

A pass, wait request, private topic boundary, or intentional pause is a valid communicative event. Follow the governing consent and assent process rather than forcing a replacement turn.

Use this sequence to define turns

List modes, preserve authorship, define onset and completion for each, add pause and pass, classify overlaps, test boundary examples, and revise rules with Yosef.

Build Yosef's multimodal conversation-turn specification

Create one versioned multimodal conversation-turn specification for the makerspace design discussion. Include Yosef's priority, partners, activity, modes, person-authored turns, topic and timing rules, latency, overlap, initiation, response, repair, script and prompt status, partner behavior, context, health, privacy, client experience, passes, invalidity, missingness, withdrawal, evidence limits, qualified owner, correction, and reassessment trigger. Store only decision-relevant information with role-limited access.

Validate Yosef's evidence

Reproduce 20 exchanges, eight AAC, five sketch or photo, three speech, two shared actions, two passes, and four AAC turns with acknowledgment overlap. Verify authorship, onset, completion, pause, pass, overlap, continuation, repair, partner turn, topic relation, and device state.

Connect Yosef's evidence to a decision

The specification lets observers measure participation across modes and helps partners know when to wait, acknowledge, ask, act, or repair. It can expose interaction rules that favor speech without serving the project.

Work through Yosef's example

Yosef participates in 20 design exchanges. He uses eight AAC turns, five sketches or photos, three spoken turns, two shared actions, and two passes. Four AAC contributions span a partner acknowledgment while Yosef continues composing; the specification scores one extended turn with an overlap marker rather than splitting it into errors. Preserve every planned and valid exchange, partner and setting version, communication mode, authored contribution, topic, timing, prompt, script, repair, partner action, access and health state, pass, withdrawal, invalid event, correction, and unresolved item. This fictional example demonstrates one assessment control. It supplies no diagnosis, universal conversation hierarchy, treatment effect, legal conclusion, coverage decision, payment promise, or outcome guarantee for Yosef.

Address Yosef's main interpretation risk

A speech-only transcript could erase 15 nonspeech contributions and both passes if it captures only Yosef's three spoken turns. Even when audible AAC output is transcribed and attributed correctly, it would still erase five visual-media contributions and two shared-action contributions. Using silence as the end of every turn can let partners take over while he composes. Treating a sketch as a prompt-free artifact instead of authored communication can also remove Yosef from the exchange. Review communication access, message authorship, turn rules, topics, timing, partner questions and waits, prompts, scripts, task cues, partner familiarity, context, health, fatigue, privacy, preference, direct experience, and design strength separately. A convincing sequence cannot make an unsafe, inaccessible, unwanted, unauthorized, or irrelevant conversation goal clinically appropriate.

Keep scope and authority clear for Yosef

For Yosef's multimodal conversation-turn specification, 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 individualized conversation norm, language diagnosis, legal authority, or requirement that Yosef speak, answer, or converse in a typical style.

Treat timing as dyadic and contextual for Yosef

The automated latency study analyzed recordings from 210 child-adult pairs and derived non-speech intervals between turns. It also measured adult-partner latency and linked change to a particular intervention dataset. A later turn-taking context study found that latency and overlap varied with activity and partner familiarity in its child samples. These studies support measuring both partners and context for Yosef. They supply no universal optimal speed, diagnostic cutoff, or reason to shorten AAC composition time.

Use topic categories descriptively for Yosef

The recent topic-shift study distinguished contingent responses, associated and non-associated shifts, reintroductions, explicit and implicit markers, and immediate partner prompts. Its coding system illustrates how one off-topic category can erase meaningful distinctions. It does not establish that topic continuation is better than change for Yosef or that a laboratory exchange captures everyday conversational fit.

Keep AAC, repair, and partner findings bounded for Yosef

An AAC intervention study involved four minimally speaking autistic children ages six to nine and targeted turn requests, question answers, and comments with peers. A longitudinal repair study compared several neurodevelopmental groups and defined repair as responding to a clarification request. These studies support explicit message, partner, repair, and context records. Their populations and procedures do not create one conversation curriculum, mastery rule, or expected outcome for Yosef.

Preserve assent and communication access for Yosef

Breaux and Smith propose individualized assent and withdrawal practices while describing an evolving evidence base. Their paper is practice guidance rather than a separate BACB mandate. ASHA's AAC portal says AAC users should always have access to their tools or devices. Give Yosef an accessible way to contribute, compose, pass, ask, repair, pause, end, or withdraw. Do not require speech, speed, eye contact, topic conformity, or social endurance as the price of participation.

Choose Yosef's next bounded action

Yosef selects a composing indicator and a finished signal on his device. Partners can acknowledge partial information while leaving the turn open until he signals completion or passes. Record the qualified owner, source evidence, effective date, current partner, activity, mode, and context version, ordinary supports, communication and health state, implementation check, accessible explanation, disagreement route, and reassessment trigger. Preserve the earlier record when partners, vocabulary, devices, modes, topics, settings, outcomes, health, or priorities change. A repaired arrangement creates a dated phase rather than an error in Yosef's prior communication.

Close Yosef's assessment

Review the multimodal conversation-turn specification with Yosef, the qualified behavior analyst, relevant partners, access owners, and specialists named in the manifest. Confirm that person-authored turns, partner turns, timing, topic relation, repair, scripts, prompts, question load, context, and client experience remain separate; every denominator is reproducible; AAC, privacy, and basic access remain protected; urgent needs received action; and conclusions stay bounded to sampled exchanges. Keep this page draft and noindex until every required review is complete.

Related resources

Sources