Senior Event Program Manager

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: About Crawford Group (but not "About the role"? Actually there is "About Crawford Group." but not "About the role". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings if present. The posting includes: "About Crawford Group." That's about the company, not role. Could treat as "About the role"? Not exactly. There's no explicit "About the role" heading. However we could still include an "About the role" section summarizing the role description? The instruction: "Prefer a few substantive sections over many thin ones." Also "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we need to see if there is content for each heading. We have: - Responsibilities: yes, there is a big block labeled "Responsibilities:" with many bullet-like sentences. - Requirements: yes, there is a block labeled "Requirements:" with bullet-like sentences. - Qualifications: there is "Preferred Qualifications:" block. - Skills: not explicitly a heading, but many skills are listed within Requirements and Preferred Qualifications. Could we create a Skills section? The instruction says use those headings if content exists. There's no explicit "Skills" heading, but we could extract skills from the text. However we must not invent or summarize away detail; we must preserve ALL substantive information. If we create a Skills section, we would be extracting content from elsewhere, potentially duplicating or summarizing. Better to not create a Skills section unless there is explicit "Skills" heading. The posting does not have a "Skills" heading. So we omit Skills. - Benefits: The posting mentions "benefits available." under Rate line: "Rate: $2,400 Per Wk. salary as a W-2 consultant of Crawford Group; benefits available." That's a mention of benefits but not detailed. It's not specific content; it's just "benefits available." That's vague; could be considered filler? The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "benefits available." is vague but still a statement that benefits are available. Is that considered specific? It's not detailed. Might be considered placeholder. Safer to omit Benefits section unless we have specific benefits listed. We don't. - Pay: The posting includes "Rate: $2,400 Per Wk. salary as a W-2 consultant of Crawford Group; benefits available." That's specific pay rate. So we can include a Pay section with that sentence. - Schedule: The posting includes "Required onsite in the Seattle office three days per week." Also "Seattle-based position." "Some early morning calls..." "Travel may be required". That's schedule info. So we can include a Schedule section with those details. - About the role: Not explicit but we have an introductory paragraph describing the role: "Crawford Group ... is seeking a Sr. Event Program Manager, based in Seattle, WA. to join our embedded event team supporting a global enterprise technology client. This role will have primary ownership of the Workplace Events portfolio for the Seattle and New York sites, delivering events end-to-end including employee networking events, office gatherings, innovation and hackathon-style events, and other workplace experiences. As a senior member of the team, you will also partner closely with colleagues across the Americas and the broader global Workplace Events team, supporting additional sites and programs based on capacity, expertise, and business needs. You will work closely with our Workplace Events Lead based in Sydney and team members across multiple time zones, operating effectively in an asynchronous, follow-the-sun environment." That is substantive content about the role. So we can create an About the role section with that paragraph. - Also there is "About Crawford Group." which is about the company. Not requested heading; we could ignore or maybe incorporate into About the role? But we should not invent headings. The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow the pattern. Probably better to omit About Crawford Group as it's not requested; but we must preserve ALL substantive information. If we omit it, we lose info about the company. However the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep that info somewhere. Could we include it under About the role? That would be mixing company info with role info, but still preserving. Or we could add a separate section like "About Crawford Group" but that's not one of the suggested headings; but the instruction says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not an exhaustive list. So we could add other headings if needed. However they said "Prefer a few substantive sections over many thin ones." So maybe we can incorporate the company description into About the role or maybe a brief intro before sections. But we need to preserve it. I'd include it as a

before the sections, not as a heading. That preserves info without extra heading. Thus final HTML: start with a

containing the introductory paragraph about the role and maybe also the company description? Actually we have two paragraphs: first about seeking Sr. Event Program Manager... second about Crawford Group. We'll combine them into a single

or two

s. Use

for prose. Then

About the role

with the role description paragraph(s). But we already used the introductory paragraph for that; maybe we should not duplicate. Let's think: The introductory paragraph already describes the role. So we can use that as About the role content. Then we can omit the company description? But we need to preserve it. Could add a

after About the role section for company description without heading, or we could add a heading "About Crawford Group". Since it's substantive, we could add a heading but not in the list; but it's okay. However the instruction says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but to be safe we could incorporate company description into a

without heading. Thus:

Crawford Group (www.crawfordgroup.com) is seeking a Sr. Event Program Manager, based in Seattle, WA. to join our embedded event team supporting a global enterprise technology client. This role will have primary ownership of the Workplace Events portfolio for the Seattle and New York sites, delivering events end-to-end including employee networking events, office gatherings, innovation and hackathon-style events, and other workplace experiences. As a senior member of the team, you will also partner closely with colleagues across the Americas and the broader global Workplace Events team, supporting additional sites and programs based on capacity, expertise, and business needs. You will work closely with our Workplace Events Lead based in Sydney and team members across multiple time zones, operating effectively in an asynchronous, follow-the-sun environment. We are looking for a hands-on senior event professional with strong event production, event execution, project management, stakeholder management, vendor management, and cross-team collaboration skills who can quickly build trust with both client stakeholders and the Crawford team.

About Crawford Group.We are revolutionizing how marketing gets done! Crawford Group provides expert marketing, digital, creative, events, and communications talent solutions for marketers. Our customers want flexibility in their workforce solutions and need experts with the skills and capabilities to deliver on revenue and pipeline growth through marketing activities. At Crawford Group, we believe in developing collaborative customer relationships to create the best talent solution for their marketing organization's needs.

Then sections:

Responsibilities

with

• each bullet. The responsibilities block contains many sentences separated by periods. We need to turn each into
• . We must preserve all info. Let's extract bullet points from the responsibilities block: "Site Ownership & Program Support: Serve as the senior event manager accountable for the Seattle and New York Workplace Events portfolios, including planning, production, execution, vendors, budgets, stakeholder management, and reporting. Support additional AMER sites and event programs based on capacity, expertise, and program needs. Provide asynchronous program support and continuity when global team members are offline or unavailable. Ensure follow-the-sun coverage and seamless handoffs between AMER and APAC/EMEA time zones. Support strategic planning, workflow intake, prioritization, and coordination for Seattle and New York events. Ensure consistent quality and brand standards across Seattle and New York event delivery and contribute to consistency across the broader program. Contribute to Monthly Program Reviews and Quarterly Business Reviews. Support business continuity plans and incident response protocols." "Team Collaboration: Partner closely with the global Workplace Events Lead based in Sydney for cross-time-zone coverage, continuity, and escalation support. Support broader AMER and global events based on capacity, expertise, and program needs. Participate in regular team check-ins and maintain proactive communication across the distributed team. Support training and knowledge sharing related to event processes and event technology where appropriate. Foster cross-training and knowledge sharing to ensure business continuity. Work collaboratively across AMER, APAC, and EMEA to support seamless handoffs and consistent event delivery." "Client Relationship & Strategy: Serve as a senior event contact for Seattle and New York client stakeholders, building trusted relationships at all levels. Provide strategic oversight of the Seattle and New York event portfolios across in-person, hybrid, and virtual formats. Contribute to broader event strategy and roadmap development aligned with client priorities and objectives. Drive event strategy and creative ideation for assigned programs, bringing industry relevance and knowledge. Develop strong working partnerships with client Workplace teams and cross-functional partners. Coordinate planning meetings with client Workplace teams supporting Seattle and New York. Support broader AMER and global program initiatives as needed. Support QBRs, monthly check-ins, and reporting on budget adherence, SLAs, and KPIs." "Program Governance & Operations. Accountable for Seattle and New York program metrics, budgets, SLAs, KPIs, and quality standards. Support workflow and ticketing systems for event requests, approvals, and tracking. Identify gaps in processes and develop efficiencies. Ensure all events and vendor activities comply with client legal, privacy, security, operational processes, and established timelines. Maintain and update event documentation, SOPs, playbooks, and knowledge base." "Event Delivery & Production (Hands-On): Drive event production schedules and production meetings with cross-organizational teams. Actively manage VIP-level employee-facing events and liaise between internal partners and external vendors for flawless event execution. Deliver in-person employee events including venue management, catering, AV/technology coordination, production, and onsite execution. Manage hybrid and virtual event formats via Zoom Webinar or other client-approved platforms. Provide a white-glove experience with strong attention to detail, project management, production oversight, and communication. Manage event registration, attendee communications, and feedback collection through client event technology platforms. Create and contribute to event program playbooks, ensuring processes are documented, updated, and continuously improved. Drive continuous improvement through post-event retrospectives and lessons learned." "Financial & Vendor Management: Manage Seattle and New York event budgets and individual event budgets against established benchmarks, client processes, and timelines. Track actual expenses against forecasts and ensure effective cost controls. Manage sourcing of external venues and event vendors when required. Coordinate contracts, purchase orders, invoices, billing, and approvals according to client processes. Manage contracted external vendors from pre-production through onsite execution and