Praxis 5412 study materials
Praxis 5412 study resources

41% New Staff, a Fire Citation, and No Common Planning

Praxis 5412 · Put your knowledge to work in context.

All case studies

41% New Staff, a Fire Citation, and No Common Planning

Riverside High School enrolls 1,150 students on a seven-period day. This year 41% of the teaching staff is new to the building, including nine first-year teachers. In October a fight in an unsupervised stairwell led to a suspension and a public complaint; in November the fire marshal cited blocked exits because furniture was stored in a corridor. On the fall climate survey, 38% of staff said they do not feel safe, and only 22% agreed that adults in the building share consistent expectations. The master schedule leaves most teachers without a common planning period, and first-period tardies run at 17%. The district has offered one paid release day for planning, and the union contract caps any added duty at one period per week.

1. You cannot fix culture before you fix the corridor. Rank what you address first, and explain why the order matters.

Read the worked answer

Order by clock, not by feeling

The tempting move is to start with staff morale, because 38% is the loudest number. But morale is a lagging indicator of conditions I have not yet fixed.

  1. Fire citation. This is a corrective order with a re-inspection date. It is the only item with an external enforcement clock, and it is cheap and fast to close. Leaving it open signals that compliance is optional.
  2. Supervision coverage. The stairwell fight and the blocked corridor share one cause: no named adult accountable for a specific place at a specific time. Until posts are assigned and checked, every other improvement sits on an unsafe base.
  3. Shared expectations. 22% agreement with 41% new staff is not a culture problem, it is an onboarding vacuum. New teachers are each inventing their own script because nobody handed them one.
  4. Common planning time. Real, but slowest and most expensive. It depends on trust built in steps 1–3, and a planning period in a building with inconsistent hallways gets spent on discipline.

The principle

Sequence by legal exposure and by what makes the next step possible. A release day about collaboration will be wasted if the first ten minutes of it are complaints about the stairwell.

2. Design a 90-day operational plan that respects the contract's one-period cap on added duty, and identify what you will measure.

Read the worked answer

The constraint drives the design

The cap means I cannot add duty; I can only reallocate it. So the plan trades supervision from low-incidence times to high-incidence times rather than stacking new obligations on tired people.

Days 1–30

  • Clear corridors; photograph and log weekly; schedule re-inspection.
  • Rewrite the duty map: move two assignments from low-traffic periods to the stairwell at the two highest-density transition minutes, identified from incident reports by time and location.
  • Publish a one-page expectation matrix: three expectations, not twelve.

Days 31–60

  • Weekly 15-minute expectation practice in the new-teacher meeting; one expectation per month, modeled and rehearsed.
  • Use the paid release day for a product, not a speaker: a shared first-six-weeks calendar and a common entry routine per hallway.
  • Restructure first-period entry-staggered doors, posted passes-if the tardy data show the bottleneck is procedural rather than motivational.

Days 61–90

  • Pulse survey re-run; adult-post spot-checks; begin a common-planning pilot for one department using existing early-release time.

Measures and decision rules

Incidents by location and time; tardy rate; percentage of posts filled at spot-check; staff safety item. Rule: if first-period tardies are not under 10% in six weeks, change the entry procedure, not the messaging. If spot-checks show posts unfilled above 20%, the duty map is wrong, not the staff.

3. Half the staff believes 'we've tried this before and nothing changed.' How do you handle that skepticism and the contract constraint without overpromising?

Read the worked answer

Treat skepticism as evidence, not resistance

If a majority of a staff believes initiatives die, they have watched initiatives die. Arguing with that memory is the fastest way to confirm it.

  • Name the history specifically. 'The 2022 plan had nine priorities and we stopped reporting on them in November.' Vagueness is what makes people cynical; precision is what makes them listen.
  • Pick two visible wins in 30 days-cleared corridors, a posted duty map, a re-inspection passed-and publish them. Early wins are not morale decoration; they are the proof of concept that buys the slower work.
  • Say what I will not do. Not nine priorities. Not a binder. Not a survey I never report back.

Working inside the cap honestly

I will say plainly that I cannot add a period, so anything new must displace something. That means asking staff what to stop-and actually stopping it. If I cannot name what I am removing, they are right to assume the plan is more work for the same result.

What I would not do

Promise that this time will be different, or trade on my own credibility as the guarantee. Credibility is spent, not asserted; the 30-day wins are the only honest currency I have.