To triage an ABA client-experience concern, receive it through an accessible route, preserve the client's exact report and communication, and protect immediate safety. Separate emergency, medical, protective, privacy, clinical, access, and routine pathways. Assign the authorized owner and applicable clock, explain the next step, and avoid diagnosing, investigating beyond the triage purpose, or dismissing the concern during intake.

Receive the concern accessibly

Offer speech, AAC, writing, symbols, interpreter support, private digital entry, and other effective modes. Keep the communication system available, allow correction or pause, and document who authored the report. A partner may support access without choosing Kira's content.

Protect immediate safety

When the report describes imminent danger, medical emergency, suspected abuse or neglect, or another current protective trigger, follow the applicable emergency or reporting route at once. Routine consent, payer, survey, or investigation steps never delay required immediate action.

Classify only enough to route

Use observable information needed to choose emergency, medical, protective, privacy, clinical, access, or routine ownership. Preserve uncertainty and choose a safer qualified escalation when facts are incomplete. Triage never establishes diagnosis, behavioral function, fault, credibility, or final disposition.

Preserve source and privacy

Record Kira's exact message, time, mode, setting, access support, people present, requested privacy, correction, and immediate response. Limit copied narrative and viewers. Explain any required disclosure and avoid promising confidentiality or anonymity the workflow cannot provide.

Assign clocks and handoffs

Record the receiving owner, acknowledgment target, protection already in place, next action, due date, handoff acceptance, and escalation route. The sender retains responsibility until the named receiver accepts the concern. Software can route evidence without deciding clinical meaning.

Check triage quality

Review correct pathway, timeliness, access, misroutes, duplicate entries, repeated transfers, client understanding, and unresolved protection. Sample every high-risk concern and a representative routine set. Repair the workflow without erasing the original state or blaming Kira for system delay.

Protect Kira while review proceeds

For Kira, preserve communication and AAC, basic access, privacy, immediate safety, needed medical or protective routes, and any authorized interim safeguard while review continues. Record who approved each temporary action, its scope, effective time, client explanation, evidence, and reassessment point. Keep routine investigation, payer, survey, and scheduling work from delaying an urgent response required by the actual event.

Maintain Kira's response timeline

Create a visible timeline for Kira from receipt through acknowledgment, triage, owner acceptance, protection, review, decision, implementation, update, confirmation, closure, and reopening. Give each stage a start event, due date, completion evidence, dependency, escalation, and accessible client update. Preserve corrections and superseded states. A changed due date needs a documented decision and cannot quietly remove overdue work.

Explain the current status to Kira

Use Kira's selected language and communication mode to explain what the practice heard, what is protected now, who owns the next step, what remains uncertain, when the next update is due, and how to correct, disagree, pause, or add information. Avoid promises about outcome or confidentiality that the process cannot support. Record meaningful receipt separately from agreement with the decision.

Build Kira's client-experience concern triage file

Create one versioned client-experience concern triage file for the multi-channel concern intake. Include the exact report, source, access method, author, context, time, consent and assent when applicable, privacy, route, urgency, owners, clocks, protection, evidence, decision, rationale, affected versions, implementation, communication, confirmation, disagreement, closure, reopening, retention, and next review. Restrict sensitive content to approved roles and systems.

Work through Kira's example

Kira's mature queue contains 14 concerns: two emergency, one protective, three privacy, four clinical, and four routine operational matters. Thirteen enter the correct pathway within its target; one privacy concern is initially misrouted. Report 13/14 correct timely triage and retain each pathway count. The misrouted concern remains open with protection, correction, and owner evidence. Preserve the frozen cohort, every stage, raw counts, denominators, missing states, source labels, owners, ages, corrections, actions, and open work. This fictional example demonstrates one response control. It supplies no universal threshold, legal conclusion, clinical validation, treatment effect, causal finding, or outcome guarantee.

Use Kira's evidence for a bounded decision

Identify the exact decision and authorized owner before gathering more evidence. For Kira, document what is known, what remains uncertain, current protection, options, client preference, further evidence, rationale, implementation test, accessible explanation, disagreement route, next review, and reopening rule. Software may route and display evidence; qualified people retain decisions within their actual authority.

Review Kira's results with fixed denominators

For Kira, report the full mature cohort and each due stage separately. Keep inaccessible, misrouted, unassigned, unaccepted, overdue, partial, unfavorable, unconfirmed, corrected, and reopened cases visible. Show counts beside percentages, define clocks, and state exclusions. Separate direct client experience, proxy report, clinical outcome, treatment integrity, attendance, authorization, and payment.

Address Kira's main response risk

A single urgent label could send every concern to emergency services, while a routine feedback queue could dangerously delay a true emergency. Kira's triage file uses observable pathway criteria and current authority. Review access, authorship, triage, authority, protection, evidence, clocks, decision, implementation, confirmation, and reopening separately. A closed ticket cannot repair a missing safeguard or wrong decision owner. A favorable group result cannot close a serious individual concern, and one critical report cannot describe every client.

Choose Kira's next action

Kira's privacy owner corrects the misroute, reviews exposure, communicates accessibly, and updates the triage example that caused the classification error. Record qualified owners, affected clients and artifacts, interim safeguards, corrected version, downstream recipients, due dates, validation evidence, accessible communication, current state, and next governance check. Preserve the original report, decisions, and closure history. Reopening adds a new auditable state and retains the prior conclusion.

Apply current professional sources to Kira's response workflow

For Kira, the BACB ethics hub identifies the current Ethics Code, which addresses understandable communication, client involvement, consent and assent when applicable, confidentiality, assessment, documentation, risk, and evaluation for covered people. BACB has no separate organizational jurisdiction. The BCBA outline is examination content and supplies no practice authority. The CASP public summary gives high-level context for ABA treatment of autistic people. An evidence-based ABA framework supports research evidence, clinical expertise, client values, and context.

Use measurement evidence carefully for Kira

For Kira's workflow, the treatment-integrity practitioner guide, Essig review, impact study, and reporting review support explicit units, representative evidence, observer controls, and cautious interpretation. They establish no universal feedback threshold, response clock, closure rule, or causal conclusion. Breaux and Smith offer assent-focused practice guidance in an evolving evidence base. ASHA supports continuous AAC access.

Close Kira's response review

Review the client-experience concern triage file with Kira, the responsible clinician, access and operational owners, privacy and safety roles, and the specialists named in the manifest. Verify that receipt, routing, protection, decisions, implementation, confirmation, and closure remain understandable and reproducible. Preserve disagreement and open concerns. Keep this page draft and noindex until all required reviews are complete.

Related resources

Sources