Process / pipelineSocial WorkSingle-case evaluationPipeline

Single-System Design

Also known as: Single-Subject Design, Single-Case Design, N-of-1 Design, Single-System Evaluation

OriginatorMartin Bloom, Joel Fischer & John G. Orme (codification in social work)Year2009Sources2Related methods20

A single-system design is a time-series approach to evaluating practice in which a single client system — an individual, family, group, or organization — is measured repeatedly on a clearly defined target before and during (and sometimes after) an intervention. By tracking the same system over time rather than comparing a treatment group to a control group, it lets a practitioner judge whether their own intervention is associated with change in the people they actually serve. It is the methodological backbone of the 'accountable professional' tradition codified by Bloom, Fischer, and Orme.

Key highlights

  • Integrates evaluation directly into ongoing practice, so the practitioner gets continuous feedback on whether the current client is improving.
  • Requires only one client system, making rigorous outcome evaluation feasible in everyday casework where randomized groups are impossible.
  • Each client serves as their own comparison, removing between-person confounds such as differing histories or severity.
  • Repeated measurement reveals the timing and trajectory of change, not just a before-after snapshot, supporting timely adjustment of the intervention.

Intuition

This section is available to Pro members. Upgrade to Pro

How it works

This section is available to Pro members. Upgrade to Pro

When to use it

Use a single-system design when you need to evaluate whether a specific intervention is helping a specific client system and a group comparison is impossible, unethical, or irrelevant — the typical situation in direct clinical and community social work practice. It fits targets that can be measured repeatedly and frequently with the same instrument. It is poorly suited to outcomes that can only be measured once, to problems with no stable baseline (acute crises requiring immediate action), or to questions about average effects across a population, where group designs are appropriate. Carryover, history, and maturation threats must be considered when interpreting any single case.

Strengths & limitations

Strengths
  • Integrates evaluation directly into ongoing practice, so the practitioner gets continuous feedback on whether the current client is improving.
  • Requires only one client system, making rigorous outcome evaluation feasible in everyday casework where randomized groups are impossible.
  • Each client serves as their own comparison, removing between-person confounds such as differing histories or severity.
  • Repeated measurement reveals the timing and trajectory of change, not just a before-after snapshot, supporting timely adjustment of the intervention.
Limitations
  • Findings apply to the single system studied; external validity (generalization to other clients) rests on replication across cases, not on a single design.
  • A basic AB design cannot rule out history or maturation as alternative explanations; stronger logic requires withdrawal (ABAB) or multiple-baseline structures.
  • An unstable or trending baseline can make any later change uninterpretable, yet ethically a baseline cannot always be extended.
  • Autocorrelation in time-series data violates the assumptions of many ordinary statistical tests, so naive significance testing can mislead.

Common pitfalls

This section is available to Pro members. Upgrade to Pro

Applications

This section is available to Pro members. Upgrade to Pro

Frequently asked

How many baseline data points do I need?

There is no universal number, but three is a common practical minimum and more is better when the data are variable. What matters is not the count but stability: the baseline should show a flat level or a trend opposite to the desired change, so that subsequent improvement cannot be explained as a continuation of the baseline pattern. In crisis situations where withholding intervention is unethical, a retrospective or concurrent baseline from records may substitute.

What is the difference between an AB design and an ABAB design?

An AB design has one baseline phase (A) followed by one intervention phase (B); it documents change but cannot strongly rule out coincidental causes. An ABAB (withdrawal/reversal) design removes and reintroduces the intervention, so if the target improves under B, worsens when B is withdrawn, and improves again when B returns, the repeated correspondence is much stronger evidence that the intervention — not history or maturation — drove the change.

Can I use ordinary statistics on single-system data?

With caution. Time-series data from one system are typically autocorrelated, meaning consecutive observations are not independent, which violates the assumptions of standard t-tests and regression and tends to inflate significance. Practitioners more often rely on visual analysis supplemented by tools designed for the setting — the two-standard-deviation band, celeration lines, and non-overlap effect sizes — or on methods that explicitly model serial dependence.

Sources

  1. 1.
    Bloom, M., Fischer, J., & Orme, J. G. (2009). Evaluating Practice: Guidelines for the Accountable Professional (6th ed.). Pearson/Allyn & Bacon.
    ISBN 9780205458066
  2. 2.
    Kazdin, A. E. (2011). Single-Case Research Designs: Methods for Clinical and Applied Settings (2nd ed.). Oxford University Press.
    ISBN 9780195341881

You have read it. What now?

Cite this page

ScholarGate. (2026, June 22). Single-System Design. ScholarGate. https://scholargate.app/social-work/single-system-design