What requesting help involves
- Noticing they are stuck and using a help signal
- Making a request specific enough that the helper knows what to do
- Asking promptly instead of waiting a long time
- Asking peers as well as adults
- Requesting help with functional tasks using AAC, sign, or a help card
- Contacting teachers in writing about missing or unclear work
Baseline and measurement considerations
- Write a shared definition of "stuck" (for example, no progress on the same item for 30 seconds) before collecting data.
- Use opportunities when the question is whether the student asks; use latency when the student asks eventually but too late.
- Make sure the work is at the student's instructional level so help is needed occasionally, not on every item.
- Record the student's exact request when the goal is specificity.
- Respond quickly to requests while the skill is new.
Progress-monitoring methods used in these templates
- Opportunity (trial) recording: Each planned or naturally occurring opportunity is recorded as correct/independent, prompted, or not demonstrated.
- Latency recording: The time between a cue (such as a direction) and the start of the response is timed.
- Frequency (event) recording: Each occurrence of a clearly defined behavior is tallied during a fixed observation period.
Matching data sheets
Each template links to a blank sheet built for its measure. You can also download these sheets on their own:
- Opportunity tracker: Records each opportunity as independent, prompted, or not demonstrated.
- Latency tracker: Times the gap between a cue and the start of the response.
- Frequency & rate tracker: Counts a defined behavior during a fixed observation period. Calculates rate when time is recorded.
Common mistakes when writing requesting help goals
- Writing "will ask for help when needed" with no definition of when help is needed.
- Counting requests without counting opportunities, so a drop in requests could mean progress or regression.
- Placing the student in work that is too hard, which makes the goal measure task difficulty.
- Requiring hand-raising when the student uses a card, sign, or device.
- Forgetting to plan for adult response time, so requests go unanswered.
Frequently asked questions
Opportunities or frequency: which should I use for requesting help?
Opportunities is usually better, because the right number of requests depends on how often the student actually needs help. Frequency fits when the opportunities are hard to define but the activity is consistent, such as asking peers questions during group work of a set length.
What if the student asks for help on everything?
Check whether the work matches the student's instructional level first. If it does, a goal for asking specific questions (naming the part they're stuck on) or trying one strategy before asking may fit better than a goal for asking more often.
How do I write a help-request goal for a student who uses AAC?
Make HELP easy to reach on the device, model it throughout the day, and create natural reasons to ask, such as a container the student can't open. Score requests in any mode and develop the goal with the SLP.
Do these goals need short-term objectives or benchmarks?
Federal regulations require short-term objectives or benchmarks only for students who take alternate assessments aligned to alternate academic achievement standards (34 CFR §300.320(a)(2)(ii)). Many states and districts require them more broadly, so check local policy. The builder can generate objectives from a template's progression steps or from intermediate targets.
References
- American Speech-Language-Hearing Association — ASHA
- CASEL — Social and emotional learning — CASEL
- Progress Monitoring: Data & Goal Setting — National Center on Intensive Intervention
IEP Atlas is a drafting aid. Every goal is a starting point that needs to be individualized from assessment data and reviewed by the IEP team. It does not determine compliance or appropriateness for any student.