Manager of Community Engagement and Events
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content.
Job Overview: we can put under About the role.
Responsibilities: list duties.
Requirements: maybe Minimum Qualifications.
Qualifications: maybe Preferred Qualifications.
Skills: maybe combine some skill statements.
Benefits: Benefits Information.
Pay: Salary Information.
Schedule: Department Name, Job Status, Shift etc.
We must not repeat job title as heading. No Job ID etc.
We must not include boilerplate like EEO, legal, application instructions.
We must preserve all substantive info.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We must not create sections with filler like "commensurate with experience". Pay and Schedule sections only if posting actually states them. Pay is stated: Annual Salary Range $70,200 to $95,500. So include Pay section.
Schedule: The posting includes Department Name, Job Status, Shift: Monday to Friday, 8am-5pm - Hybrid. So we can include Schedule section with that info.
Benefits: there is Benefits Information paragraph.
Now we need to decide what goes into each section.
About the role: Job Overview paragraph.
Responsibilities: list of duties from "Duties & Responsibilities". Many bullet-like sentences. We'll turn into
- .
Requirements: Minimum Qualifications (Degrees, Area of Study, Experience). We'll list.
Qualifications: Preferred Qualifications.
Skills: maybe combine skill statements from Experience section? Actually the Experience section includes many skill statements. Could treat as Skills. But we already have Requirements and Qualifications; maybe Skills separate for skill-based bullet list. However we must not create thin sections. Could combine skill statements into Requirements or Qualifications. But the instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can include Skills if we have substantive content. The Experience section includes many skill statements; we could put them under Skills.
But we also have Minimum Qualifications (education, experience) and Preferred Qualifications. So we could have Requirements = Minimum Qualifications, Qualifications = Preferred Qualifications, Skills = the skill statements (like project management, communication, data analysis, etc). That seems reasonable.
We must not repeat content. Ensure we capture all substantive info.
Let's extract:
Job Overview paragraph: "The Manager of Community Engagement and Events (CEE) at Children’s Hospital Colorado Foundation (Foundation) is responsible for managing community fundraising partnerships, donor engagement, and event-based fundraising initiatives that advance organizational revenue and engagement goals. The role oversees assigned Community Partner Program relationships, manages a portfolio of approximately 50-75 donors and prospects, and will cultivate, steward, and expand community partner support. The position leads fundraising activations for Signature Events, manages event technology and donor data processes. The role works across multiple Foundation departments and will engage hospital stakeholders, community partners, volunteers, on a regular basis in their scope of work. Reports to the Director of Community Engagement and Events."
That's About the role.
Responsibilities: list from "Duties & Responsibilities". Let's parse each bullet:
- Manage key functions with Community Partner Program with a focus on Tier 2 & 3 partnerships
- Demonstrate commitment to and success in managing the implementation of Community Partner Program (CPP) towards achieving annual revenue and operational goals for Community Engagement and Events team, and the Foundation as a whole.
- Communicates efficiently and effectively with annually registered event partners to ensure parameters and standards are met
- Partners with the Director, CEE in support of more complex events, as assigned
- Leads event support for Tier 2 and Tier 3 partner activity,
- Responsible for post-event coordinates post-event collection and donor payment follow-up
- Partners with Director, CEE to track, analyze, and evaluate CPP data to make strategic decisions about future engagement, support, and stewardship.
- Manage a portfolio of prospects and donors
- Manage a portfolio of 50-75 relationships
- Identify, qualify, cultivate and steward assigned prospects and donors
- Proactively identify new Community Partner prospects and donors to qualify for portfolio assignment
- Follow up on all leads identified by Prospect Development, volunteers, hospital and Foundation partners to further qualify for portfolio assignment
- Travel within Colorado and nationally to meet with prospects, donors, and other key stakeholders, as necessary
- Maintain complete and accurate donor records, plans, and opportunities in CRM
- Collaboratively manage the overall process and execution of onsite fundraising activations for Foundation Signature Events.
- Design and execute effective at-event fundraising activations for Signature Events which meet/exceed expectations for both the donor and Foundation revenue goals
- Execution and implementation of event technology (GiveSmart) at both Signature and qualified CPP Events
- Works with Gift Processing team to ensure timely and accurate reporting for all receipt/CRM management post event
- Works with Director, CEE on Signature Event guest collection and pre-event data management
- Courage Classic – Serve as project lead for the Courage Cruise
- Partner with Director, Courage Classic to design and execute the Courage Cruise event as part of the Courage Classic program
- Manage all logistical and operational elements required to efficiently execute the Courage Cruise (timelines, contractors, run of show and volunteer positions)
- Create and implement fundraising strategies that enhance donor pipeline, drive engagement and boost fundraising revenue
- Collaborates with Marketing Business Partner on promotional strategies
- Determine GIK needs and partner with CP and other departments to secure required elements
- Special Projects as requested
- Support Sr. Director, CEE and other colleagues with special projects, such as:
- Ancillary activities related to the 50th Anniversary Gala
- Courage Classic Team Program needs related to engagement, retention and growth
- Community Partner work related to Courage Classic team fundraising
- Organizational projects involving hospital partnerships, grateful families and Community Partnerships team at the hospital
We need to keep all these as list items. Some are sub-bullets under Special Projects; we can keep them as separate list items or nested? Probably just list items.
Now Requirements (Minimum Qualifications):
- Degrees: BA/BS undergraduate degree is required from an accredited college or university. No equivalency.
- Area of Study: Please insert details here for AREA STUDY (this is placeholder; we should not include filler? The instruction says do NOT emit a heading followed by filler/placeholder text. But this is content inside a section; it's placeholder text "Please insert details here for AREA STUDY". That's basically filler. Should we include it? It's part of the posting but it's placeholder. The instruction: "Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences." Also: "Do NOT repeat the job title as a heading ... and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." For content, we should preserve ALL substantive information; do NOT invent or summarize away detail. However placeholder like "Please insert details here for AREA STUDY" is not substantive; it's basically a note to fill in. Should we include it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't explicitly say to drop placeholders, but earlier: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". That's about headings. For content inside sections, maybe we should keep it? It's not a heading. It's a line under Requirements. It's basically a placeholder that says "Please insert details here for AREA STUDY". That's not substantive; but it's part of the posting. I'd lean to keep it as it's part of the Minimum Qualifications. However it's not meaningful; but we could drop it as it's not substantive. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. This is not substantive, it's a placeholder. I'd drop it.
Experience: Four to six years of progressively responsible experience in nonprofit fundraising, community engagement, donor relations, special events, sponsorship management, corporate event management, or related fields.
Then list of required knowledge and skills (these could go under Skills). Let's extract:
- Demonstrated experience managing fundraising events, community partnerships, and donor cultivation.
- Experience independently managing a portfolio of donors, prospects, sponsors, or key community stakeholders.
- Proven success meeting fundraising, engagement, revenue, and partnership goals.
- Experience with peer-to-peer fundraising platforms and event technology solutions such as GiveSmart.
- Experience managing volunteers, contractors, vendors, sponsors, and event committees.
- Experience coordinating multiple projects simultaneously while managing competing priorities and deadlines.
- Experience utilizing CRM systems (such as Blackbaud CRM, Raiser’s Edge, Salesforce, or comparable platforms) for donor management, reporting, and pipeline tracking.
- Strong project management skills with demonstrated ability to lead complex initiatives from planning through execution.
- Excellent verbal, written, and presentation communication skills.
- Ability to analyze fundraising and engagement data to inform recommendations and decision-making.
- Strong organizational skills with exceptional attention to detail and follow-through.
- Ability to build collaborative relationships across departments, volunteers, donors, community partners, and hospital stakeholders.
- Demonstrated sound judgment, discretion, and professionalism with confidential information.
- Ability to work evenings, weekends, and travel as required for events and donor engagement activities.
These are skill/experience statements. Could go under Skills.
Preferred Qualifications:
- Experience in healthcare, higher education, or mission-driven nonprofit organizations.
- Project Management experience or certification, desired.
Now Benefits: paragraph.
Pay: Annual Salary Range (Based on 40 hours worked per week): $70,200.00 to $95,500.00 plus description about starting pay etc. We need to preserve all substantive info. So include that paragraph.
Schedule: Department Name: CHCHS Foundation; Job Status: Exempt- Full time, 40 hours per week; Shift: Monday to Friday, 8am-5pm - Hybrid.
We can put these in a
or list.
Now we need to output HTML fragment with headings
and content.
We must not include any markdown fences.
Let's structure:
About the role
Job Overview paragraph.
Responsibilities
- ...
...
Requirements
- BA/BS undergraduate degree required from an accredited college or university (no equivalency).
- Four to six years of progressively responsible experience in nonprofit fundraising, community engagement, donor relations, special events, sponsorship management, corporate event management, or related fields.
We omitted Area of Study placeholder.
Qualifications
- Experience in healthcare, higher education, or mission-driven nonprofit organizations.
- Project Management experience or certification desired.
Skills
- Demonstrated experience managing fundraising events, community partnerships, and donor cultivation.
- Experience independently managing a portfolio of donors, prospects, sponsors, or key community stakeholders.
- Proven success meeting fundraising, engagement, revenue, and partnership goals.
- Experience with peer-to-peer fundraising platforms and event technology solutions such as GiveSmart.
- Experience managing volunteers, contractors, vendors, sponsors, and event committees.
- Experience coordinating multiple projects simultaneously while managing competing priorities and deadlines.
- Experience utilizing CRM systems (such as Blackbaud CRM, Raiser’s Edge, Salesforce, or comparable platforms) for donor management, reporting, and pipeline tracking.
- Strong project management skills with demonstrated ability to lead complex initiatives from planning through execution.
- Excellent verbal, written, and presentation communication skills.
for prose. We must not create sections with filler like "commensurate with experience". Pay and Schedule sections only if posting actually states them. Pay is stated: Annual Salary Range $70,200 to $95,500. So include Pay section. Schedule: The posting includes Department Name, Job Status, Shift: Monday to Friday, 8am-5pm - Hybrid. So we can include Schedule section with that info. Benefits: there is Benefits Information paragraph. Now we need to decide what goes into each section. About the role: Job Overview paragraph. Responsibilities: list of duties from "Duties & Responsibilities". Many bullet-like sentences. We'll turn into
- .
Requirements: Minimum Qualifications (Degrees, Area of Study, Experience). We'll list.
Qualifications: Preferred Qualifications.
Skills: maybe combine skill statements from Experience section? Actually the Experience section includes many skill statements. Could treat as Skills. But we already have Requirements and Qualifications; maybe Skills separate for skill-based bullet list. However we must not create thin sections. Could combine skill statements into Requirements or Qualifications. But the instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can include Skills if we have substantive content. The Experience section includes many skill statements; we could put them under Skills.
But we also have Minimum Qualifications (education, experience) and Preferred Qualifications. So we could have Requirements = Minimum Qualifications, Qualifications = Preferred Qualifications, Skills = the skill statements (like project management, communication, data analysis, etc). That seems reasonable.
We must not repeat content. Ensure we capture all substantive info.
Let's extract:
Job Overview paragraph: "The Manager of Community Engagement and Events (CEE) at Children’s Hospital Colorado Foundation (Foundation) is responsible for managing community fundraising partnerships, donor engagement, and event-based fundraising initiatives that advance organizational revenue and engagement goals. The role oversees assigned Community Partner Program relationships, manages a portfolio of approximately 50-75 donors and prospects, and will cultivate, steward, and expand community partner support. The position leads fundraising activations for Signature Events, manages event technology and donor data processes. The role works across multiple Foundation departments and will engage hospital stakeholders, community partners, volunteers, on a regular basis in their scope of work. Reports to the Director of Community Engagement and Events."
That's About the role.
Responsibilities: list from "Duties & Responsibilities". Let's parse each bullet:
- Manage key functions with Community Partner Program with a focus on Tier 2 & 3 partnerships
- Demonstrate commitment to and success in managing the implementation of Community Partner Program (CPP) towards achieving annual revenue and operational goals for Community Engagement and Events team, and the Foundation as a whole.
- Communicates efficiently and effectively with annually registered event partners to ensure parameters and standards are met
- Partners with the Director, CEE in support of more complex events, as assigned
- Leads event support for Tier 2 and Tier 3 partner activity,
- Responsible for post-event coordinates post-event collection and donor payment follow-up
- Partners with Director, CEE to track, analyze, and evaluate CPP data to make strategic decisions about future engagement, support, and stewardship.
- Manage a portfolio of prospects and donors
- Manage a portfolio of 50-75 relationships
- Identify, qualify, cultivate and steward assigned prospects and donors
- Proactively identify new Community Partner prospects and donors to qualify for portfolio assignment
- Follow up on all leads identified by Prospect Development, volunteers, hospital and Foundation partners to further qualify for portfolio assignment
- Travel within Colorado and nationally to meet with prospects, donors, and other key stakeholders, as necessary
- Maintain complete and accurate donor records, plans, and opportunities in CRM
- Collaboratively manage the overall process and execution of onsite fundraising activations for Foundation Signature Events.
- Design and execute effective at-event fundraising activations for Signature Events which meet/exceed expectations for both the donor and Foundation revenue goals
- Execution and implementation of event technology (GiveSmart) at both Signature and qualified CPP Events
- Works with Gift Processing team to ensure timely and accurate reporting for all receipt/CRM management post event
- Works with Director, CEE on Signature Event guest collection and pre-event data management
- Courage Classic – Serve as project lead for the Courage Cruise
- Partner with Director, Courage Classic to design and execute the Courage Cruise event as part of the Courage Classic program
- Manage all logistical and operational elements required to efficiently execute the Courage Cruise (timelines, contractors, run of show and volunteer positions)
- Create and implement fundraising strategies that enhance donor pipeline, drive engagement and boost fundraising revenue
- Collaborates with Marketing Business Partner on promotional strategies
- Determine GIK needs and partner with CP and other departments to secure required elements
- Special Projects as requested
- Support Sr. Director, CEE and other colleagues with special projects, such as:
- Ancillary activities related to the 50th Anniversary Gala
- Courage Classic Team Program needs related to engagement, retention and growth
- Community Partner work related to Courage Classic team fundraising
- Organizational projects involving hospital partnerships, grateful families and Community Partnerships team at the hospital
We need to keep all these as list items. Some are sub-bullets under Special Projects; we can keep them as separate list items or nested? Probably just list items.
Now Requirements (Minimum Qualifications):
- Degrees: BA/BS undergraduate degree is required from an accredited college or university. No equivalency.
- Area of Study: Please insert details here for AREA STUDY (this is placeholder; we should not include filler? The instruction says do NOT emit a heading followed by filler/placeholder text. But this is content inside a section; it's placeholder text "Please insert details here for AREA STUDY". That's basically filler. Should we include it? It's part of the posting but it's placeholder. The instruction: "Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences." Also: "Do NOT repeat the job title as a heading ... and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." For content, we should preserve ALL substantive information; do NOT invent or summarize away detail. However placeholder like "Please insert details here for AREA STUDY" is not substantive; it's basically a note to fill in. Should we include it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't explicitly say to drop placeholders, but earlier: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". That's about headings. For content inside sections, maybe we should keep it? It's not a heading. It's a line under Requirements. It's basically a placeholder that says "Please insert details here for AREA STUDY". That's not substantive; but it's part of the posting. I'd lean to keep it as it's part of the Minimum Qualifications. However it's not meaningful; but we could drop it as it's not substantive. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. This is not substantive, it's a placeholder. I'd drop it. Experience: Four to six years of progressively responsible experience in nonprofit fundraising, community engagement, donor relations, special events, sponsorship management, corporate event management, or related fields. Then list of required knowledge and skills (these could go under Skills). Let's extract: - Demonstrated experience managing fundraising events, community partnerships, and donor cultivation. - Experience independently managing a portfolio of donors, prospects, sponsors, or key community stakeholders. - Proven success meeting fundraising, engagement, revenue, and partnership goals. - Experience with peer-to-peer fundraising platforms and event technology solutions such as GiveSmart. - Experience managing volunteers, contractors, vendors, sponsors, and event committees. - Experience coordinating multiple projects simultaneously while managing competing priorities and deadlines. - Experience utilizing CRM systems (such as Blackbaud CRM, Raiser’s Edge, Salesforce, or comparable platforms) for donor management, reporting, and pipeline tracking. - Strong project management skills with demonstrated ability to lead complex initiatives from planning through execution. - Excellent verbal, written, and presentation communication skills. - Ability to analyze fundraising and engagement data to inform recommendations and decision-making. - Strong organizational skills with exceptional attention to detail and follow-through. - Ability to build collaborative relationships across departments, volunteers, donors, community partners, and hospital stakeholders. - Demonstrated sound judgment, discretion, and professionalism with confidential information. - Ability to work evenings, weekends, and travel as required for events and donor engagement activities. These are skill/experience statements. Could go under Skills. Preferred Qualifications: - Experience in healthcare, higher education, or mission-driven nonprofit organizations. - Project Management experience or certification, desired. Now Benefits: paragraph. Pay: Annual Salary Range (Based on 40 hours worked per week): $70,200.00 to $95,500.00 plus description about starting pay etc. We need to preserve all substantive info. So include that paragraph. Schedule: Department Name: CHCHS Foundation; Job Status: Exempt- Full time, 40 hours per week; Shift: Monday to Friday, 8am-5pm - Hybrid. We can put these in a
or list. Now we need to output HTML fragment with headings
and content. We must not include any markdown fences. Let's structure:
About the role
Job Overview paragraph.
Responsibilities
- ... ...
Requirements
- BA/BS undergraduate degree required from an accredited college or university (no equivalency).
- Four to six years of progressively responsible experience in nonprofit fundraising, community engagement, donor relations, special events, sponsorship management, corporate event management, or related fields.
Qualifications
- Experience in healthcare, higher education, or mission-driven nonprofit organizations.
- Project Management experience or certification desired.
Skills
- Demonstrated experience managing fundraising events, community partnerships, and donor cultivation.
- Experience independently managing a portfolio of donors, prospects, sponsors, or key community stakeholders.
- Proven success meeting fundraising, engagement, revenue, and partnership goals.
- Experience with peer-to-peer fundraising platforms and event technology solutions such as GiveSmart.
- Experience managing volunteers, contractors, vendors, sponsors, and event committees.
- Experience coordinating multiple projects simultaneously while managing competing priorities and deadlines.
- Experience utilizing CRM systems (such as Blackbaud CRM, Raiser’s Edge, Salesforce, or comparable platforms) for donor management, reporting, and pipeline tracking.
- Strong project management skills with demonstrated ability to lead complex initiatives from planning through execution.
- Excellent verbal, written, and presentation communication skills.