The two included synchronous sessions are the capstone of a short arc: align on evidence, train on the exact moves in your materials, then verify transfer with lightweight data your site already owns. Below is representative of how a district engagement is structured; Sample ISD is fictional and for illustration only.
Before live PD
Discovery + lock-ins
- Objective: Reduce rework — agree what “good implementation” looks like on your bell schedule.
- Formats: 60–90 min leadership sync; artifact review (async, 5 business days).
- Time box: Complete before Session A is scheduled.
Live PD (×2)
Train + practice
- Objective: Teachers execute two prioritized moves from the new unit kit (e.g., oral language launch + formative checkpoint).
- Formats: Virtual synchronous (Zoom/Teams) · 90 min each · bilingual support materials as agreed.
- Time box: Hard stop at 90 min; parking lot captured for async follow-up.
Between + after
Async bridge + evidence
- Objective: Close the gap between “understood in the room” and “happening in classrooms.”
- Formats: Recorded walkthrough of slides/unit pages; implementation checklist; 30-day pulse survey.
- Time box: Async clips ≤20 min; post-PD window = 30 instructional days unless otherwise contracted.
Stakeholder pre-meeting — needs sensing
A structured pre-PD step aligns session design to your real constraints (coverage, tech, language access) so synchronous minutes are not spent renegotiating scope.
Who attends: program lead + 2 teacher leads + optional tech liaison
What we review: 2 lesson plans or short video clips they select; recent EL roster/ML data they already use; master schedule constraints
What gets locked: priority standards strand, pilot cohort, language for family-facing pages, success criteria for Session A/B
Sample artifacts (illustrative excerpts)
Redacted fictional district — not a live client file.
Sample document
One-page PD scope summary · Sample ISD · Internal draft
PD Scope — English Acquisition Pilot
Goal: By Day 30 post–Session B, 80% of pilot teachers score ≥ proficient on walkthrough items EL-1…EL-3.
Sessions: (A) Unit launch protocols · (B) Formative toolkit calibration
Async: Checklist + 12 min module between A and B
Owner: Director of EL (implementation); Camino (design + facilitation + survey instrument)
Sample document
Stakeholder intake — excerpt
Q4. Where does instruction currently break down for newcomers in Period 1–3?
→ “Academic oral output — they stay in single words during turn-and-talk.”
Q7. What data may we reference in PD (no new collection)?
→ “WIDA ACCESS roster export (Spring) + building walkthrough notes from March.”
Sample document
Session A agenda — fragment (first 45 min)
0:00–0:10 Outcome + look-for tied to Sample ISD rubric EL-2
0:10–0:25 Model: launch moves from Unit 3.2 slides (teacher-facing)
0:25–0:45 Paired rehearsal + public commitment (one shift each)
Metrics — pre, during, post
Measurement stays lean: reuse instruments the client already has where possible; add only what makes accept/reject decisions obvious. Cadence and ownership are explicit so nothing depends on “someone remembering to follow up.”
Pre-PD
Baseline: three walkthrough look-fors (EL oral language, scaffolded output, formative use) scored once by site coaches; optional anonymized student language sample set agreed in writing.
During PD
Exit slip: 5-point competency self-rating on the two prioritized moves; implementation checklist started (yes/partial/no) before teachers leave the synchronous block.
Post-PD (30 days)
Short pulse survey: recommend score (0–10) + three self-ratings; repeat walkthrough on the same three look-fors; count of student tasks collected that match the new formative protocol.
Delivery contingencies — compact playbook
Practical if/then defaults keep the engagement moving without burning synchronous budget.
If primary platform fails mid-session
Switch to phone bridge for voice + screen-shared PDF pack within 10 minutes; async recording + slide deck posted within 24 hours.
If live attendance < 60% of invited pilot cohort
Record core model segment (≤25 min); assign async homework + optional 20-minute office-hours block; reschedule make-up only if listed in scope.
If substitute coverage cannot be secured
Reschedule synchronous block within 5 business days of written notice, or convert to shortened sync (45 min) + expanded async checklist — client picks one path at kickoff.
If tech equity gaps (bandwidth/devices)
PDF-first handouts, captioned recordings, Spanish companion summaries for family-facing lines; low-interactivity mode (chat-based checks instead of breakout rooms).
