The Advisory Board Wants Three Weeks; the EOPA Calendar Allows Six Days

Decision: keep the nine-week calendar intact and embed a six-day client sprint rather than a three-week takeover. The EOPA is cumulative and secure; removing 15 instructional days from a nine-week block would force selling, economics, and channel management into review-only treatment, which is a poor bet for students who have not yet demonstrated mastery. The client work is not discarded-it becomes the context for teaching promotion, pricing, and customer relations. I would map each deliverable to a pathway standard, use the client's exported GA4 PDF/CSV because the filter blocks live access, and schedule the Tuesday-only client contact as a recorded Q&A. I accept a real tradeoff: students will do less advanced analytics than the advisory board imagined. To offset that, I would add one screencast annotation task and an individual analytics memo, and invite the agency owner to co-score presentations. I would also offer a summer externship or Saturday micro-internship for students who want depth. The principle is to protect guaranteed, assessed standards while still giving employers authentic work; business engagement should enrich the curriculum, not replace it.

I would use a common client brief with defined roles so that the project does not depend on live synchronous attendance. Students who work or compete receive the same brief, recorded client Q&A, and an asynchronous role such as copy editor, data interpreter, or presentation reviewer. A simulated-client version uses the same dataset for any student who misses the Tuesday contact. Individual accountability matters: each student submits an analytics memo interpreting two metrics and a draft ad claim tied to a pricing or promotion objective, so the group product cannot hide nonparticipation. Formative evidence includes a standards-to-deliverable map, exit tickets on markup and target-market language, and a midproject rubric check. Summative evidence is an individual memo, an individual ad draft, and a team presentation scored on a rubric aligned to promotion, pricing, and customer-relations standards. I would also keep a simple participation and accommodation log. The network block is handled by teacher-downloaded reports, not by letting students search for workarounds. DECA students are not exempted from the standards; their competition preparation becomes an additional context for the same skills.

I would respond promptly and without defensiveness: thank the chair, restate the shared goal-students who can use data and write persuasive copy-and explain the constraint with specifics. I would attach the six-day standards map, the client deliverables, and the assessment dates, then note that the EOPA is a graduation-related pathway assessment the principal will not waive. The counterproposal is a signed six-day commitment plus two optional Saturday work sessions or a summer paid micro-internship; those add depth without displacing guaranteed instruction. I would invite the chair to co-score final presentations and to help recruit internship slots. I would not sign a three-week commitment I cannot honor, because overpromising damages the partnership more than a clear boundary does. If the chair continues to push, I would ask the principal to clarify priorities in writing and document the decision. The reasoning is transparent: protect instructional time for assessed standards, preserve the relationship with a smaller but genuine commitment, and create a deeper optional pathway for students who want it.