Purpose
When the Lead Planner believes the Showbook is ready for the handoff call with the Lead Tech (Stage A5), this auditor runs the "Will It Work?" checklist against the actual data. It checks whether the plan is executable — whether crew matches scope, whether the schedule is physically possible, and whether the Lead Tech will have what they need.
Owner
Findings route to: Lead Planner
How to Run
python -m event_audit planning_readiness --event 1247
python -m event_audit planning_readiness --event 1247 --depth deep
What It Reads
From Odoo (x_events model)
All core event fields plus:
Planning & Showbook fields:
- x_studio_lead_show_tech, x_studio_lead_prep, x_studio_lead_deprep (many2one — lead assignments)
- x_studio_lead_tech_is_booked, x_studio_lead_prep_is_booked, x_studio_lead_deprep_is_booked (scorecard)
- x_studio_showbook_url, x_studio_showbook_short_url
- x_studio_system_ready_time, x_studio_doors_open_time
- x_studio_staffing_overview_notes
Scope flags (boolean):
- x_studio_has_audio_pa, x_studio_has_audio_corp, x_studio_has_video_main
- x_studio_has_lighting_stage, x_studio_has_lighting_decor
- x_studio_has_staging, x_studio_has_rigging
All scorecard fields, handoff fields, promise fields, and dates (same as Sales Readiness)
From Odoo (related models)
- planning.slot — Full crew schedule: employee name, role, start/end times, published/draft status
- helpdesk.ticket — All linked tickets (open tickets = unresolved scope questions)
- mail.activity — Open/overdue activities
- res.partner — Venue and room records (address, notes, past events)
Business Rules (compiled from KB)
| KB Article | Compiled Rules File | What It Covers |
|---|---|---|
| KB 1589 | audit_rules/showbook_handoff.md |
21-day rule, "Will It Work?" checklist, Lead Tech confirmation |
| KB 1202 | audit_rules/system_ready.md |
2-hour minimum before doors, Yellow/Red alert protocol |
| KB 1203 | audit_rules/contingency_planning.md |
Buffer multipliers for risk factors |
| KB 1218 | audit_rules/handoff_overview.md |
Handoff context and lifecycle position |
What It Checks
Quick Depth
| Check | Source |
|---|---|
| Showbook URL populated | x_studio_showbook_url |
| Lead Show Tech assigned | x_studio_lead_show_tech |
| Lead Prep assigned | x_studio_lead_prep |
| Lead Deprep assigned | x_studio_lead_deprep |
| Ship and return dates set | x_studio_ship_date, x_studio_return_date |
| Key positions scorecard Green | scorecard fields |
| System Ready and Doors times set | x_studio_system_ready_time, x_studio_doors_open_time |
Standard Depth (adds)
| Check | Source |
|---|---|
| Crew roles match active scope flags | planning.slot roles vs. has_* flags |
| System Ready buffer >= 2 hours before Doors | time field math |
| All planning slots assigned (not UNASSIGNED) | planning.slot employee_id |
| All shifts published (not draft) | planning.slot state |
| Venue advancing complete | scorecard |
| On-site contact populated | contact fields |
| Event risks documented | x_studio_event_risks |
| No unresolved helpdesk tickets | ticket stages |
| No overdue activities | mail.activity |
Deep Depth (adds)
| Check | Source |
|---|---|
| Setup time realistic for equipment scope | shift hours vs. scope complexity |
| Contingency buffer for risk factors (out of town, first-time venue, complex scope) | KB 1203 criteria |
| Ship date vs. crew start time consistency | date/time math |
| Past event history at venue leveraged | venue history |
| Overall "Will It Work?" assessment | AI reasoning |
Findings Output
Written to x_studio_audit_planning_readiness (text field on x_events).
Also creates structured records in x_audit_run and x_audit_finding. Visible in the Audit Findings tab on the event and in the Audit > Open Findings workbook.
Depth Levels
- Quick — Key positions, showbook URL, lead techs, ship/return dates
- Standard — Quick + crew-to-scope matching, system ready buffer, venue advancing, risks
- Deep — Full "Will It Work?" analysis including setup time realism and contingency assessment
Prompt
Full prompt at scripts/event_audit/prompts/planning_readiness.md. Key instructions:
- Think like the Lead Tech receiving this Showbook
- Cross-reference scope vs. crew (lighting-heavy show with no L1 is a problem)
- Check shift math (can the crew realistically set up in the time between arrival and system ready?)
- Flag events past the 21-day deadline that haven't been escalated
- A well-planned event with no findings is a valuable outcome
Learnings File
scripts/event_audit/learnings/planning_readiness.md
Configuration File
scripts/event_audit/auditors/planning_readiness.yaml