Chief Partnership Officer (Volunteer)

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate. We need to parse the posting: It's a volunteer Chief Partnerships Officer role. Content includes overview, responsibilities (list of duties), requirements/qualifications (maybe not explicit). There's mention of "Chief Partnerships Officer (Volunteer)" and details: Fully Remote — United States, with NYC-based collaboration as needed. Type Volunteer Executive Leadership Role. Commitment Approximately 5–10 hours per week Minimum Commitment 6 months; 12 months preferred. Reports To Chief Executive Officer. Directly Oversees Senior Director of Partnerships & External Affairs, Partnership Directors, Managers, Coordinators, and designated PromiseBridge initiatives. Works Closely With Executive Team, PromisePrograms, PromiseLearning, PromiseRise, PromiseGiving, PromisePublic, PromiseVoice, PromiseBrands, PromiseMeasure, PromiseOperations, PromiseTrust, and other MAP divisions. Also there is a lot about PromiseBridge, Partnership Strategy, Partnership Portfolio, Partnership Development, Opportunity Development, Youth Opportunity Partnerships, Corporate Partnerships, Academic & Educational Partnerships, Community Partnerships, Strategic Relationship Management, Partnership Design, Internal Partnership Readiness, Partnership Activation, Partnership Stewardship, Partnership Measurement, External Representation. We need to extract substantive content for sections: About the role (role overview), Responsibilities (list of duties), Requirements/Qualifications/Skills (maybe not explicit but we can infer from description: need strategic partnership experience, leadership, etc). However we must not invent detail. If not explicitly stated, we should not create sections with filler. The instruction: "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 are explicit Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Schedule: "Commitment Approximately 5–10 hours per week Minimum Commitment 6 months; 12 months preferred". That's schedule info. So we can include a Schedule section with that. Pay: Volunteer role, no pay. Should we include Pay? The posting says it's a volunteer role, no compensation. That is specific content: it's volunteer, no pay. Should we include Pay section? It says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state it's volunteer, so we can include Pay section stating "Volunteer position (unpaid)". That is specific. Benefits: Not mentioned. No benefits listed. So we should not include Benefits. Requirements/Qualifications/Skills: The posting does not have explicit bullet list of requirements. It describes role overview and responsibilities, but not explicit "Requirements". However we could infer that they expect experience in partnership strategy, leadership, etc. But that's not explicitly stated as a requirement; it's part of role overview. The instruction says do not invent or summarize away detail. We should not create sections unless there is real specific content. Since there is no explicit "Requirements" or "Qualifications" or "Skills" list, we should omit those sections. Thus we will have sections: About the role (role overview), Responsibilities (list of duties), Schedule, Pay. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. So About the role heading is fine. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include the details from the overview: Mentor A Promise is a NYC-based nonprofit serving children and youth experiencing housing instability, etc. Also mention PromiseBridge, etc. But we need to avoid duplication. The posting includes an "About Mentor A Promise" and "About PromiseBridge" sections earlier. We should incorporate that into About the role? The role overview includes description of MAP and PromiseBridge. We can combine. We need to ensure we don't include boilerplate like EEO, legal, etc. Not present. Let's extract role overview text: "MAP is seeking an exceptional Chief Partnerships Officer to lead PromiseBridge and serve as the organization's senior executive responsible for strategic partnerships, external relationships, and partnership-driven opportunity development. The Chief Partnerships Officer will establish MAP's partnership strategy, build and lead the PromiseBridge team, cultivate senior external relationships, develop institutional opportunities, strengthen partnership infrastructure, and ensure promising conversations become meaningful outcomes. This is not primarily a networking position. It is an enterprise leadership role requiring strategy, judgment, relationship-building, negotiation, organizational understanding, execution, and stewardship. The Chief must be able to move comfortably between a conversation with a corporate executive, university leader, nonprofit partner, community organization, prospective funder, program leader, and MAP's CEO—and understand that each relationship requires something different." Also earlier description of MAP and PromiseBridge: "Mentor A Promise is a New York City–based nonprofit serving children and youth (ages 5–18) experiencing housing instability, grounded in the belief that every child is a Promise—full of potential, dignity, and possibility. We deliver consistent, high-quality programming across mentorship, literacy, social-emotional learning, and creative expression in shelters, schools, and community spaces, creating structured environments where students can grow, be seen, and build lasting skills. Through signature experiences like The Imagination Studio, The Kitchen Table, The Sound Lab, and The Story Space, we nurture academic development, emotional well-being, and creative voice, all within a trauma-informed, culturally responsive, and accessibility-centered framework. Our work prioritizes dignity-protective storytelling, consent-driven engagement, and deep community partnership, ensuring that how we serve is as intentional as whom we serve. We are not only addressing immediate needs - we are building pathways to confidence, belonging, and long-term opportunity, so every child has the support and foundation to carry their promise forward." And "About PromiseBridge PromiseBridge is MAP's partnerships and external-relations division. The division identifies, develops, activates, and stewards relationships capable of expanding MAP's reach, strengthening programs, creating opportunities, increasing organizational capacity, and advancing our mission. PromiseBridge should not be measured by how many organizations appear on a partnership list. It should be measured by what those relationships make possible." We can include that in About the role. Responsibilities: We need to list duties. The posting has many sections: Partnership Strategy, Partnership Portfolio, Partnership Development, Opportunity Development, Youth Opportunity Partnerships, Corporate Partnerships, Academic & Educational Partnerships, Community Partnerships, Strategic Relationship Management, Partnership Design, Internal Partnership Readiness, Partnership Activation, Partnership Stewardship, Partnership Measurement, External Representation. Each has bullet-like paragraphs. We need to turn them into

  • items. We should preserve all substantive information, not invent or summarize away detail. So we need to extract each duty as a list item, preserving the detail. We must be careful not to create overly long list items that combine multiple duties; but we can break them into logical items. Let's parse each section and create list items. Partnership Strategy: - Develop and lead MAP's organization-wide partnership strategy. - Establish priorities based on organizational strategy, program needs, youth and family opportunities, educational priorities, career pathways, community needs, organizational capacity, geographic priorities, funding and resource opportunities, creative initiatives, research and knowledge opportunities, long-term institutional growth. - Continually ask: What does MAP need? Who could help make it possible? What could MAP contribute in return? Why would this relationship make sense for both organizations? What would success actually look like? - Ensure partnership begins with mutual value—not simply an introduction. Partnership Portfolio: - Build a diversified portfolio of relationships across sectors: corporations, small and local businesses, universities and colleges, schools, nonprofit organizations, community-based organizations, cultural institutions, professional associations, foundations, philanthropic institutions, healthcare organizations, financial institutions, technology organizations, media and creative organizations, workforce-development organizations, research institutions, government and public institutions (where appropriate). - Avoid building an external-relations strategy dependent on one organization, one sector, or one relationship. - Ensure a resilient partnership ecosystem that creates multiple pathways to opportunity. Partnership Development: - Lead the complete partnership lifecycle: Research → Qualification → Outreach → Conversation → Opportunity Design → Internal Review → Commitment → Activation → Stewardship → Evaluation → Renewal. - Ensure the organization distinguishes among a contact, a conversation, an opportunity, a commitment, an active partnership, a strategic relationship (these are not interchangeable). - Recognize that a promising conversation is not yet a partnership. Opportunity Development: - Translate external relationships into tangible opportunities. - Potential partnership outcomes may include: mentors, volunteers, career professionals, internships, career exposure, educational programming, workshops, employee engagement, pro bono expertise, technology support, creative collaboration, research partnerships, program locations, in-kind resources, professional services, community resources, event participation, sponsorship opportunities, financial support, institutional introductions, capacity-building assistance. - Continually move relationships from possibility toward responsible execution. Youth Opportunity Partnerships: - Work closely with PromisePrograms, PromiseLearning, and PromiseRise to build partnerships that directly expand opportunities available to young people. - Potential relationships may create: career days, workplace exposure, professional speakers, mentorship, internships, job-shadowing, skills workshops, college exposure, financial-literacy programming, technology learning, arts and creative experiences, entrepreneurship exposure, career pathways, educational resources. - Ensure a partnership becomes meaningful when it creates something young people can actually access. Corporate Partnerships: - Develop relationships with companies whose capabilities and interests align with MAP's mission. - Explore opportunities involving: employee volunteering, skills-based volunteering, corporate philanthropy, sponsorship, workplace experiences, career exposure, pro bono services, technology, product or service contributions, professional mentorship, employee-resource groups, cause-related collaborations. - Design corporate partnerships around mutual clarity rather than vague promises of collaboration. Academic & Educational Partnerships: - Develop relationships with colleges, universities, schools, faculty, researchers, internship programs, and academic centers. - Potential collaborations may include: student interns, fellows, faculty expertise, research, evaluation, educational programming, curriculum collaboration, service learning, career pathways, volunteer recruitment, professional development, campus partnerships. - Work across MAP to ensure academic partnerships have clear supervision, deliverables, responsibilities, and organizational value. Community Partnerships: - Build relationships with organizations rooted in the communities MAP serves. - Potential partners may include: community-based organizations, family-serving organizations, local businesses, libraries, cultural institutions, schools, youth organizations, community leaders, neighborhood networks, service providers. - Partnership strategy should not only look toward large institutions; some of MAP's most meaningful relationships may come from organizations that understand a community deeply because they are part of it. Strategic Relationship Management: - Serve as a senior relationship owner for priority institutional partners. - Responsibilities include: executive outreach, relationship cultivation, partnership meetings, opportunity development, negotiation, expectation setting, internal coordination, issue resolution, stewardship, renewal conversations. - Ensure partners know who owns the relationship and what happens next; no important relationship should depend entirely on someone's memory or personal inbox. Partnership Design: - Help structure collaborations before commitments are made. - For significant opportunities, clarify: purpose → mutual value → scope → owners → responsibilities → resources → decision authority → timeline → safeguarding / risk review → success measures → documentation → activation. - Be willing to slow down an opportunity long enough to determine whether MAP can responsibly deliver what is being discussed. Internal Partnership Readiness: - Before committing MAP to significant collaborations, ensure appropriate teams understand: what is being proposed, what MAP has committed to, who owns implementation, what resources are required, what deadlines exist, what the partner expects, what MAP expects, what approvals are required, how success will be evaluated. - Recognize that a strong external partnership can fail because of weak internal coordination. - PromiseBridge opens doors; the organization must be prepared to walk through them. Partnership Activation: - Work with the Senior Director of Partnerships & External Affairs and relevant divisions to ensure signed or agreed partnerships become active work. - Use a clear transition: agreement