If you have used the OT Wizard Plan of Care generator, you have probably noticed that it does not always suggest the goals you expected. Sometimes it surfaces fewer goals than you would write yourself. Sometimes it skips a domain entirely. The question we hear most often is about pencil grasp. A child walks in with an obvious grasp issue, the evaluation reflects that, and yet the suggested goals are about postural endurance and bilateral coordination instead. No grasp goal in sight.

This is not a glitch. It is the engine doing what it was built to do. Here is what is happening underneath, and why developmental sequencing drives every recommendation the system makes.

Goals are sequenced, not just listed

Pediatric OTP's  have known for a long time that skill development is layered. Postural control comes before distal fine motor control. Bilateral integration and motor planning come before efficient tool use. Visual motor integration comes before legible handwriting. Underneath all of it sits sensory regulation. None of this is controversial. It is the proximal to distal progression that Jane Case-Smith and her colleagues established decades ago, and that follow-up research on preterm infants has reinforced again and again. Children with delayed postural control show downstream fine motor delays. The pattern is consistent.

So when OT Wizard analyzes an evaluation, it is not just scanning for low scores. It is looking at how the low scores relate to each other developmentally. The goal that gets suggested is the one that gives the child the best chance of meaningful progress, not the one that mirrors the parent or teacher complaint most directly.

Why pencil grasp often does not appear

Grasp is the example everyone asks about, and it is a good one to work through because it shows the logic clearly.

An immature or inefficient grasp is almost never a standalone problem. It usually reflects something further upstream. Postural fatigue that drives a child to brace through the hand instead of stabilizing through the trunk. Shoulder instability that creates compensatory grip tension. Bilateral coordination issues that disrupt the stabilizer and manipulator hand relationship. In hand manipulation limitations that make finger isolation harder than it should be. Motor planning challenges that affect how the child organizes the tool in space.

If the evaluation shows deficits in any of those upstream areas, the engine will surface goals targeting them first. Not because pencil grasp is unimportant, but because resolving the upstream skill is what shifts the grasp pattern. Anyone who has tried to remediate a hooked grasp by reminding a kid to hold the pencil differently knows how that goes. The grasp does not change until the foundations support a different pattern.

Writing a pencil grasp goal in isolation, when the foundations are still shaky, sets up a goal that is hard to achieve and harder to defend to a reviewer asking why progress has stalled. The engine is trying to keep you out of that situation.

What the engine is actually weighing

Several inputs feed into a goal suggestion. The score data across all evaluated domains, with attention to how the deficits cluster. Developmental priority, which puts safety and access concerns at the top, regulation second, foundational motor and sensory motor building blocks ahead of task specific performance, and enrichment goals at the bottom. Foundational dependencies, where a lower tier domain is driving deficits in a higher tier domain. Setting, since medical Plans of Care emphasize functional independence, health, and safety, while school Plans of Care emphasize educational access and IDEA aligned PLAAFP framing. Skilled intervention scope, because every goal needs to reflect work that requires occupational therapy expertise. And domain specific clinical rules. Motor planning goals always use completion as their measurement, not accuracy. Trunk stability goals use duration. Visual memory goals use frequency. Each domain has its own conventions and the engine respects them.

You are still the clinician in the room

This is the part that matters most. The goal engine is decision support. It is not making clinical decisions for you, and it does not have the context you have when you sat across from the child and the parent and watched what happened.

Every suggested goal is editable. Every suggestion can be removed. Every Plan of Care has space for you to add goals the engine did not surface. If you believe a pencil grasp goal is the right call for your kid, because the foundations are intact and grasp efficiency is genuinely the highest priority, write it. What it will not do is generate the grasp goal automatically when the clinical evidence points to foundational work first, because doing so quietly would undermine the developmental logic that makes pediatric OT work in the first place.

An example to make this concrete

Take an eight year old referred for handwriting concerns. The evaluation shows postural endurance below age expectations, bilateral coordination deficits, oculomotor inefficiency, and below threshold scores in fine motor and handwriting. A traditional goal list might be five handwriting and fine motor goals, all targeting the surface complaint.

OT Wizard, working from the same data, will more likely suggest something like a postural endurance goal for sustained tabletop work, a bilateral coordination goal addressing midline crossing, an oculomotor goal supporting visual tracking during near point work, a fine motor goal for in hand manipulation, and a functional handwriting goal targeting the actual writing outcome.

Notice the sequence. Each goal builds on the one before it. When the child progresses, gains compound. When you take this Plan of Care to a payer or an IEP team, the rationale is visible in the structure of the goals themselves.

If a goal you expected does not show up

Look at the foundational domains. Most of the time, the goals it did surface are the ones that will move the child further, faster, than the goal you were anticipating. OT Wizard is telling you something about the developmental picture, and it is usually worth a second look before you override it.

And if you still want to write the goal you had in mind, you can. OT Wizard supports clinical reasoning. It does not replace it.