Governance lifecycle
Defined phases, decision rights, ownership, approvals, and documentation expectations across the event lifecycle.
Institutional proof archive
The House That Kesha Built
An event governance and operations archive
Governance systems. Clause libraries. Vendor controls. Accessibility-forward architecture. Decision pathways. Operational safeguards. Case studies.
This is not the overview page and it is not the résumé. It is the deeper record of what was authored, structured, protected, and left behind so complex event work did not depend on memory or heroics.
What this archive contains
The archive documents systems, safeguards, operating logic, and selected case studies. It intentionally goes deeper than the public Proof of Work page without publishing confidential internal documents, names, or proprietary materials.
Governance and risk architecture
Relocation protections were authored and enforced during venue transitions where executive presence, program continuity, and event value were contractually vulnerable.
Resale mitigation language was structured to reduce six-figure attrition exposure during volatile booking cycles.
Master-account billing controls reduced ambiguity across multi-event settlements and protected the organization from unclear financial responsibility.
Approval thresholds and escalation pathways were codified so operational friction did not become public failure.
Total protected and negotiated event value: $260K+.
Execution under visible pressure
National convenings, executive-facing meetings, and digital programs were supported where reputational consequence was immediate and visible.
When key personnel were unexpectedly unavailable, run-of-show mapping, documentation, and escalation logic enabled substitution without collapsing the participant experience.
Manual operational burden was reduced by 40 percent through stronger systems, automation logic, documentation, and ownership clarity rather than increased staffing.
Redundancy was embedded where efficiency culture would have trimmed it.
The infrastructure held.
Systems that remain
Workflow architecture
Intake, routing, escalation, speaker logistics, attendee communication, supply tracking, and deadline visibility.
Financial controls
Budget visibility, meal coverage, reimbursement guidance, billing boundaries, concession tracking, and contract protections.
Accessibility infrastructure
Access integrated into registration, communication, room flow, seating, meals, transportation, digital participation, and onsite operations.
Cultural infrastructure
Cross-functional rhythm was formalized through structured planning and event operations governance.
Escalation logic replaced informal persuasion.
Policy language replaced recurring debate.
Documentation preserved institutional memory even when formal succession planning did not exist.
National event execution was sustained without relying on direct-report authority.
Created in spite of title. Built so the record could not be flattened into “she planned events.”
Contained proof library
Selected case studies
Each case study is collapsed by default so deeper evidence is available without turning the page into a wall of text.
National Leadership Convening
A multi-day event strategy and operations engagement for a national leadership membership organization.
Context
The organization needed a restructured annual convening that could support high-stakes decision-making, multiple stakeholder groups, accessibility, and evolving operational demands.
Role
Lead event and operations systems architect overseeing end-to-end planning, governance, risk mitigation, accessibility integration, vendor management, and onsite execution.
What was built
- A five-phase event governance lifecycle defining ownership, decision rights, and operating expectations.
- Cross-functional workflows for communications, accessibility, program development, travel, and vendor coordination.
- A classification model for event type, risk level, and approval requirements.
- A logistics playbook covering timelines, call sheets, escalation, accessibility needs, and onsite command flow.
- Contract protections addressing attrition, relocation, billing, accessibility, and vendor accountability.
Impact
- Reduced planning friction across multiple stakeholder groups.
- Created systems reused across later events.
- Improved executive visibility, cross-team communication, and operational consistency.
Governance and Systems Architecture
Designing decision rights, approval pathways, and cross-functional systems for a complex event portfolio.
Context
Unclear decision rights, overlapping responsibilities, inconsistent planning, and fragmented event requests created avoidable risk and staff strain.
What was built
- A five-phase governance lifecycle.
- A RACI model for ownership, communication, and accountability.
- Event classification by complexity, stakeholders, risk, and resource need.
- Standard planning artifacts including timelines, agendas, run of show, call sheets, escalation plans, and risk logs.
- Intake, approval, and routing systems that reduced surprise requests and uncontrolled work.
Impact
- Improved ownership clarity and cross-team coordination.
- Created shared language for decisions and risk.
- Increased executive confidence through better visibility.
Operations Playbook and Organizational SOPs
A repeatable operating foundation for planning, communication, risk, access, vendors, and escalation.
Context
Rapid growth and shifting priorities created inconsistent practices and made staff carry too much unwritten knowledge.
What was built
- A comprehensive operations playbook.
- Standard operating procedures for meetings, approvals, communications, and cross-team work.
- Decision protocols clarifying authority, pacing, and alignment.
- Templates that reduced guesswork and protected institutional memory.
- Capacity safeguards designed to reduce preventable overload.
Impact
- Improved onboarding and continuity.
- Reduced staff overwhelm created by unclear process.
- Established more consistent quality across staffing changes.
Event Portfolio Performance Analysis
Using data and systems analysis to reveal performance, capacity pressure, and recurring operational gaps.
Context
Leadership needed a clear view of event performance across virtual, hybrid, and in-person programs, but fragmented documentation obscured the full picture.
What was built
- An execution snapshot evaluating outputs, processes, decisions, and recurring gaps.
- Performance benchmarking for virtual programs.
- Cross-team dependency mapping.
- Recommendations for tools, templates, dashboards, and workflow changes.
Impact
- Improved leadership visibility into timelines, risk, and staffing needs.
- Supported more data-informed programming and resource decisions.
- Created a foundation for repeatable measurement and continuous improvement.
Data-Driven Virtual Event Performance
Audience insight, benchmarking, and operational redesign for stronger digital programs.
Context
Virtual programming was central to engagement, but performance varied and leadership needed evidence about what was working.
What was built
- Comparative analysis of attendance, retention, pacing, and engagement.
- Benchmarking against relevant industry performance.
- Audience behavior analysis identifying drop-off and participation signals.
- Recommendations for content delivery, accessibility, and experience design.
Impact
- Shifted planning from assumption to evidence.
- Improved understanding of audience needs and engagement patterns.
- Created a repeatable model for virtual program improvement.
Hotel Contracting and Risk Mitigation
Financial safeguards, accessibility expectations, and vendor accountability built into contracting.
Context
Existing agreements did not consistently protect budget, access, attendee experience, or organizational liability.
What was built
- A clause library covering accessibility, safety, attrition, resale, relocation, force majeure, staff housing, and billing.
- Standard redlines addressing unfavorable or ambiguous terms.
- Negotiation strategy for flexibility, savings, and equitable protections.
- A repeatable internal review and approval workflow.
Impact
- Reduced financial exposure and contract ambiguity.
- Established accessibility and safety expectations earlier.
- Strengthened the organization's negotiating position.
Why this record matters
High-stakes events do not hold through personality, overfunctioning, or last-minute heroics.
They hold when the operating structure is honest about risk, access, decision authority, vendor pressure, budget, and the people carrying the work.
This archive preserves the difference between “helped with events” and authored operational infrastructure.
Return to the buyer-facing overview
The Proof of Work page contains the shorter public summary and the path into Rolling With Keke™ services.