An ABA contingency contract worksheet can make an agreed arrangement easier to understand, but the paper itself is not the intervention and a signature is not proof of ongoing participation. A useful record identifies the observable action, the promised outcome, each party's responsibility, what makes a review period valid, and how the agreement can be questioned, changed, paused, or ended.

This copyable worksheet separates co-design, contract wording, client performance, support-party delivery, implementation fidelity, and revision decisions. It is an educational clinical artifact, not informed consent, a legal contract, a behavior plan, or a device for compelling agreement. The fictional makerspace example tests the fields and denominators without recommending terms for a real person.

Clinicians & ABA Professionals / Assessment and Treatment Planning.

Clinical boundary: Use an accessible, authorized, individualized process. Protect communication, food, water, toileting, education, healthcare, safety, property, relationships, breaks, and other ordinary rights from becoming bargaining chips. A client may ask questions, decline, withdraw assent, or request another approach without losing basic access. Pause for confusion, coercion, material unavailability, implementation mismatch, distress, or another unwanted effect. The BACB ethics resources offer professional context; this form cannot establish consent, necessity, effectiveness, payer coverage, employment or school compliance, or legal enforceability.

What a contingency contract records

A contingency contract is a written description of an agreed relation between an observable action and a stated outcome. It can also identify when, where, how often, and by whom each part will occur. A contract is different from an operational definition, an informed-consent process, a treatment plan, a crisis or safety plan, a school behavior plan, an employment agreement, and a legal document. One record may refer to those documents without replacing them.

A meta-analysis of 18 single-case studies reported an overall moderate effect for behavior contracts across 58 children and youth, with effects varying across studies. The included work focused on academic and behavioral outcomes in educational contexts. That evidence cannot establish that a contract is appropriate or effective for every client, age, goal, service, or setting.

The current BCBA Test Content Outline includes observable goals, reinforcement, measurement, social validity, integrity, and data-based decisions. The BACB outline access page identifies the current outlines. These sources help anchor vocabulary but do not supply contract terms.

Participation comes before wording

The opening conversation should establish why the client might want the arrangement and how they can participate. Offer the document in a form the client can access. Record accepted communication forms, processing time, translation, visual or auditory supports, and whether a support person is requested. A copied signature line cannot substitute for comprehension or ongoing assent.

Blank participation card

FieldCase-specific entryClient-selected or agreed purposeWhat the client wants to be easier or differentPeople participating and their rolesAccessible language, format, translation, and processing supportsOrdinary AAC, sensory, motor, visual, hearing, and health supportsHow questions, choice, assent, dissent, help, break, change, and stop are communicatedAlternatives discussedRights and access that remain unconditionalConsent/authorization or other governing document referenced separatelyClinical owner, version, date, and next review

ASHA's AAC Practice Portal describes communication as multimodal and individualized. Keep familiar communication available. If the person can indicate “not now,” “different option,” or “I do not understand” through speech, sign, gesture, device, behavior, or another established form, the process should recognize that response.

Translate an idea into observable terms

“Have a good day” or “be responsible” cannot be scored consistently. Define the action, setting, opportunity start and end, accepted variations, time window, direct measure, and invalid conditions. Then define the promised outcome, when it becomes due, who provides it, and what happens if that person or item is unavailable.

Contract-term map

TermPlain-language entryObservable recordQuestion or exceptionMeaningful purposeClient actionContext and opportunityStart/end and time windowAccepted variations and ordinary supportsDirect measure and case-defined criterionPromised outcomeSupport party responsible for deliveryDelivery timing and locationInvalid or unavailable periodPause, stop, revision, and expiration rule

A small on-task study with three primary-age students used teacher-developed contracts while students selected consequences, and on-task behavior increased during contract conditions. The small ABABA study illustrates participant choice and direct observation; it does not show that teacher-authored wording or the same consequences should be used elsewhere.

Put both parties' obligations on the page

Many records closely track the client's action and barely mention the support party. That creates an asymmetrical account. If a clinician, caregiver, teacher, supervisor, or other person promises access to an outcome, the contract should identify their behavior, timing, substitutions, and repair process just as clearly.

PartyAgreed actionWhen dueAccess/support neededHow recordedIf unavailable or missedPerson who reviewsClientSupport partyAdditional party, if any

A study of a brief training manual evaluated staff contract-negotiation and writing behavior in simulations and generalization tests with four child-care workers. Its results show that writing and negotiation are implementer skills that can be observed. They do not validate a specific contract, population, setting, or staff-training package.

Versioned agreement record

Keep the client-facing agreement concise enough to use while retaining a fuller clinical record behind it. Each version should carry its effective date, review date, and links to the definitions or authorizations it relies on. When a target, outcome, timing rule, party, access support, exception, or criterion changes, create a new version rather than editing history in place.

VersionEffective datesClient-facing wordingAction definitionOutcome and delivery ruleInvalid-state ruleParticipation confirmed howAuthorized/reviewed byStatusdraft / active / held / expireddraft / active / held / expired

A signature may document one event, such as acknowledgment or agreement at a particular time. Such a signature does not prove comprehension, remove the right to dissent, or convert a clinical form into legally enforceable terms. Legal, employment, educational, and payer questions need their own qualified review.

Review-period ledger

The ledger keeps planned coverage and valid performance separate. A period may be invalid when the agreed opportunity did not occur, required materials were unavailable, a party changed the terms, the client could not access the wording, or the promised outcome could not be delivered. That period still matters, but it is not a client failure.

Date/timeContract versionPlanned contextOpportunity available and accessible?Initial client actionMeets definition?Support-party actionOutcome delivered within window?Prompt/reminderValid? reasonAssent/dissent or unwanted effectObserveryes / no / not scorableyes / no / not dueyes / no / not scorableyes / no / not dueyes / no / not scorableyes / no / not due

Record prompts or reminders after the initial response without erasing the initial score. Keep the final supported outcome too when it matters. If the client meets the action and the support party is late, client performance may be correct while contract implementation is not.

Implementation fidelity is its own outcome

Contract fidelity asks whether the current version was available, accessible, followed, and reviewed as planned. It is not evidence that the client benefited. Each component should be observable and scorable only when an opportunity occurred.

ObservationCorrect version availableTerms stated accessiblyOpportunity arranged as agreedInitial response capturedClient action scored correctlyOutcome delivered correctlyDissent/exception honoredRecord completedCorrect componentsOpportunitiesNotes

“Contract followed” is too broad if the reviewer cannot identify which party, term, or opportunity was observed. A mismatch can point to unclear wording, unavailable materials, insufficient training, competing responsibilities, or a version-control problem. It should not automatically be assigned to client motivation.

Denominator rules for a fair review

Review questionNumeratorDenominatorResultWhat it does not showValid-period coveragevalid review periodsplanned review periodsClient performance is separate. Keep availability visibleClient performance among valid periodsvalid periods meeting the action rulevalid review periodsPlanned coverage and causation are separate. Examine both independentlyPlanned-period yieldvalid periods meeting the action ruleall planned periodsInvalid-period reasons are separate. Preserve each reasonTimely support-party deliveryvalid periods with the promised outcome delivered on time when duevalid periods with delivery dueClient benefit is separate. Evaluate it directlyImplementation fidelitycorrectly implemented componentsobservable component opportunitiesEffectiveness and assent are separate. Ask about both

If two of 12 planned periods are invalid, eight of the remaining 10 meet the action definition, and the support party delivers on time in nine of 10 valid periods, the percentages answer different questions. The ABA contingency contract worksheet should preserve every raw count so another reviewer can recompute them.

Fictional community makerspace example

In this fictional example, the client helped define a makerspace arrival routine and selected an agreed outcome from accessible options. Twelve review periods were planned. In two periods the materials named by the contract were unavailable, so the agreed opportunity did not occur. Ten periods remained valid, and eight met the case-defined action.

  • valid-period coverage: 10 / 12 × 100 = 83.3%;
  • performance among valid periods: 8 / 10 × 100 = 80.0%; and
  • planned-period yield: 8 / 12 × 100 = 66.7%.

The support party's promised delivery was due in each of the 10 valid periods and occurred within the defined window in nine. Timely support-party delivery was 9 / 10 × 100 = 90.0%. The late delivery remains an implementation event; it does not change the client's action score.

Fidelity was separately observed across 18 events and eight components, creating 144 component opportunities. One hundred thirty-four were correct and 10 were mismatches, reconciling to 144. Implementation fidelity was 134 / 144 × 100 = 93.1%. That result does not establish effectiveness or fairness.

Fictional review table

Evidence layerFictional resultBounded interpretationPlanned coverage10 valid of 12 plannedTwo periods were unavailable. They were not client failuresClient performance8 of 10 validDescribes this definition. The result is limited to these periodsPlanned yield8 of 12 plannedRetains availability in the record. It does not explain missing periodsSupport-party delivery9 of 10 dueOne promised outcome was late. Client performance remains separateImplementation fidelity134 of 144 componentsTen mismatches require review. Effectiveness is not establishedClient responsefictional feedback variedA completed action is not ongoing assent. Feedback remains essentialGeneralization or maintenancenot establishedNo cross-setting claim follows. Durability was not tested

These results could prompt questions about material availability, the late delivery, clarity of the action, client feedback, burden, and whether both parties still want the agreement. They do not automatically justify continuing, revising, or ending it.

Social validity, revision, and ending

Ask separately whether the purpose matters, the terms are understandable, the effort and outcome feel acceptable, the process preserves dignity, and the client wants to continue. A recent practice-oriented review of contingency contracting describes varied uses and emphasizes accessible dissemination. It is not an endorsement of every contract or of this worksheet.

Review dateClient feedback and communication formPurpose still matters?Terms understood?Burden or unwanted effectsParty obligations met?Change requestedContinue / revise / hold / endDecision owner

Ending can be appropriate because the goal changed, the arrangement was ineffective, natural outcomes now support the action, the burden outweighs benefit, a party cannot fulfill the terms, the client declines, or another approach is preferred. The reason should be documented without treating withdrawal as noncompliance.

The CASP ABA Practice Guidelines access page provides current professional context for individualized care. That page cannot authorize a contract, determine a service plan, or establish that the procedure is suitable in a particular school, workplace, home, clinic, or community setting.

Decision and exception record

FieldReview entryContract versions and date range reviewedClient feedback, assent/dissent, comprehension, burden, and unwanted effectsPlanned coverage and client-performance patternSupport-party delivery and implementation mismatchesInvalid periods and alternative explanationsSocial-validity, generalization, or maintenance evidence still missingConsent, rights, safety, school, employment, payer, or legal issue for separate reviewHold / revise / continue / end / assess another option questionQualified decision owner and next review date

The Ethics Code for Behavior Analysts keeps competence, informed consent, assent when applicable, client rights, documentation, confidentiality, and data responsibilities with the responsible professional. The record should preserve disagreement and uncertainty instead of turning a percentage or signature into an automatic decision.

Related resources

Sources

The literature spans different ages, settings, actions, outcomes, contract authors, measures, and designs. It supports clear terms, direct observation, participation, and implementation review. It does not provide a universal contract, signer, consequence, duration, criterion, legal status, or prediction for a specific client.