IEP goal bank: measurable sample goals by domain

This is a goal bank with the warning label printed first: a bank goal is a scaffold, not a goal. IDEA requires annual goals designed to meet the child’s needs that result from the child’s disability (34 CFR §300.320(a)(2)) — which no bank can know. What a good bank can give you is the anatomy: a condition, an observable behavior, a criterion, and a measurement method, assembled correctly so you can swap in your student’s baseline and numbers. Below: one labeled sample per domain, and a link to the full guide for each — every guide covers measurement methods, common write-ups, and more samples.

The anatomy every goal below follows

Given [condition] , [student] will [observable behavior] at/with [criterion] as measured by [method and schedule]. If any of the four parts is missing, data collection fails before it starts. The full breakdown — with weak-vs-strong rewrites — is in how to write measurable IEP goals, and every criterion below implies a matching data collection sheet.

Why copy-paste fails an audit

File reviewers read goals against the present levels. A goal whose baseline doesn’t appear in the PLAAFP, whose criterion jumps from nowhere, or whose wording matches three other students’ IEPs word-for-word reads as non-individualized — the exact thing §300.320(a)(2) exists to prevent. The fix is a four-step adaptation, not a rewrite from scratch: (1) replace the baseline with the student’s own from collected baseline data; (2) keep the verb only if it matches what the student actually needs to do; (3) set the criterion one realistic year from the baseline, not at the bank’s default; (4) name a measurement method someone on your team will actually run weekly. Ten minutes per goal, and the bank did its job without leaving fingerprints.

FAQ