Back to blog

Administration & Coaching Integration | District Implementation

What Schools Should Analyze Before Planning Fall PD

Many professional development programs fail not because teachers do not care, but because schools are often designing PD around incomplete or poorly aligned data. This post explores why schools need better systems, clearer goals, and stronger feedback loops to make PD more meaningful and effective.

5/28/2026 | Instructional Partner

What Schools Should Analyze Before Planning Fall PD

Why PD Often Misses the Mark

See if this sounds familiar.

You spend the summer looking over results from the prior year. You review school goals, district goals, teacher needs, and student performance data. You meet with your leadership team and try to identify what support teachers need going into the next school year.

Then you design a series of fall PD days.

You may even bring in an outside consultant because they have ideas that seem like they could help teachers, support students, and move the school closer to its goals.

The plan looks good.

The sessions make sense.

Everyone is trying to do the right thing.

But then the year goes by and it feels like the goals were not really reached. Teachers are not very excited about the PD that was shared, and there is not much evidence that the training actually changed outcomes.

That frustration is real.

And it is felt by the whole team.

Administrators want PD that actually helps. Teachers want support that fits the reality of their classrooms. Everyone wants to improve what matters most, which is helping students.

The problem is that PD often misses the mark because it is built before the school fully understands the system driving the problem.

It is not always a teacher effort problem.

It is not always a training problem.

Sometimes it is a data problem.

Sometimes it is a workflow problem.

And sometimes the school is trying to solve the wrong part of the system.


More Data Does Not Automatically Lead to Better PD

Schools are constantly told to make data-driven decisions.

That sounds good, and I agree with the idea.

But the problem is that many schools already have more data than they know what to do with.

They may have:

  • attendance data
  • behavior data
  • gradebook data
  • state testing data
  • benchmark data
  • student survey data
  • teacher evaluation data
  • PLC data
  • intervention data
  • MTSS data
  • student engagement or belonging data

The issue is not usually that there is no data.

The issue is that the data is often scattered across different systems, collected in different formats, and not connected to a clear question.

So schools end up with dashboards, reports, surveys, and spreadsheets, but they still do not have a clear picture of what is actually driving the problem.

That makes PD planning harder.

Because if the data is incomplete, misaligned, or too broad, the PD built from that data will probably be incomplete, misaligned, or too broad as well.


Start With the Goal

The first step should not be picking a PD topic.

The first step should be identifying the goal.

Not a vague goal like:

We want to improve student achievement.

That is too broad.

A better goal would be something more specific and measurable, such as:

We want to improve student attendance by 10% over the next quarter.

or:

We want to improve student performance on informational text across grades 6–8.

or:

We want to reduce the number of students failing two or more core classes by the end of the semester.

Once the goal is clear, then the school can start asking better questions.

What is contributing to the problem?

What data do we already have?

What data are we missing?

What parts of the system might be affecting the outcome?

That is when data becomes useful.

Not because there is more of it, but because it is connected to a real question.


What Data Should Schools Look At?

Once the goal is established, schools need to identify as many possible data points as they can that might influence that goal.

For example, say the district wants to improve student attendance by 10% over the next quarter.

The school might need to look at:

  • grade level
  • attendance by period
  • course performance
  • teacher or course patterns
  • behavior data
  • intervention history
  • transportation issues
  • student belonging data
  • safety data
  • subgroup data
  • participation in activities or CTSOs
  • PLC notes
  • family communication
  • MTSS supports already in place

That list can get long quickly.

And that is the point.

Most school problems are not caused by one thing.

They are usually connected to a larger system.

If a school only looks at attendance totals, they may know there is a problem, but they may not know what is causing it.

That leaves administrators guessing.

And when administrators are guessing, teachers often end up receiving broad PD that may or may not address the actual need.


The Analysis Is Where the Work Begins

This is where many schools get stuck.

They collect data.

They review data.

They get a report.

Then they pick a PD topic.

But that should not be the end of the process.

That is where the real work begins.

Once the data is collected, it needs to be organized, cleaned, and aligned to the goal. Then the school can start looking for patterns.

For example:

  • Are absences higher during certain periods?
  • Are they connected to specific grade levels?
  • Are students with low belonging scores missing more school?
  • Are students with prior behavior concerns also showing attendance risk?
  • Are certain interventions helping?
  • Are some student groups responding differently than others?

Those questions matter because they help the school move from a general problem to a more specific one.

Instead of saying:

Attendance is low.

The school might discover:

Attendance is dropping most among 9th grade students who are failing two or more classes and report low belonging.

That is a very different problem.

And it would likely require very different PD.


PD Should Be Connected to a Testable Model

Once the school has a clearer picture, then it can build a model.

Not a perfect model.

Not something that explains every student or every situation.

But a practical model that gives the school a starting point.

For example:

If students with low belonging and multiple failing grades are showing higher absenteeism, then we need to test whether stronger advisory supports, targeted teacher check-ins, or earlier intervention meetings improve attendance.

Now the PD has a purpose.

Teachers are not just being asked to sit through another training.

They are being asked to participate in a focused support system tied to a measurable goal.

That makes a big difference.

The school can then continue collecting data to see whether the intervention is working.

If it works, they can expand it.

If it does not work, they can adjust it.

Either way, they are no longer just shooting in the dark.


Teachers Need Support That Fits the School Day

This is one of the biggest missing pieces in PD planning.

Even when the data points to a real need, the solution still has to fit into the actual school day.

Teachers already have limited time, limited planning space, and a long list of responsibilities.

So any PD or intervention needs to come with a realistic tradeoff.

If teachers are being asked to do something new, something else may need to be reduced, removed, or simplified.

Otherwise, even a good idea can become another unsustainable task.

That is why PD cannot just be about giving teachers more information.

It has to be connected to workflow.

A good PD system should help teachers:

  • understand the goal
  • know what problem is being addressed
  • see how the strategy fits into their classroom
  • understand what data will be used
  • know what support they will receive
  • and see what will be adjusted if the plan is not working

That is very different from one-time training.

That is a feedback loop.


What Schools Should Do Before Planning Fall PD

Before planning fall PD, I think schools should ask:

  1. What goal are we actually trying to reach?
  2. What data helps us understand that goal?
  3. What data are we missing?
  4. What patterns are showing up across students, classrooms, or systems?
  5. What part of the problem can teachers actually influence?
  6. What support do teachers need to act on that part?
  7. What will we measure to know if the PD is working?
  8. What will we adjust if the data does not move?

Those questions matter because they keep PD from becoming disconnected from the real problem.

They also help protect teachers from being handed another initiative that sounds good but does not fit the reality of their classroom.


Final Thought

One of the biggest mistakes schools make with PD is assuming the training is the solution.

Sometimes it is.

But many times, the training is only one piece of a much larger system.

If the goal is unclear, the data is incomplete, or the workflow is unrealistic, then even good PD can miss the mark.

The goal should not be to plan more professional development.

The goal should be to build a better system for identifying what support is actually needed, testing whether that support works, and adjusting based on what the data shows.

When all the data starts talking to the same goal, schools can make better decisions.

And even when they miss the target, they are no longer guessing.

They can adjust their aim.

Most AI tools don't fail because they are bad. They fail because they are used in the wrong workflow.

Want to see responsible AI workflow tools in action?

Instructional Partner AI helps teachers connect assessments, unit planning, assignments, and reusable instructional context while keeping teacher control.