Chief Operating 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. The posting includes many details about role, responsibilities, etc. Need to extract relevant content. We must not repeat job title as heading. No Job ID. Remove boilerplate. Provide only HTML. We need to decide which sections have content. From posting: - About Mentor A Promise (description) – could be "About the role"? Actually "About the role" could be overview of role. The posting includes "Role Overview" and "About Mentor A Promise". We'll put role overview under "About the role". - Responsibilities: many bullet points under "Enterprise Operations Strategy", "Strategy Into Execution", "Organizational Operating Model", "Operational Systems", "Cross-Divisional Operations", "PromiseOperations Leadership", "Senior Director of Operations", "Organizational Rhythm", "Process Improvement", "Internal Operational Services", "Documentation & Institutional Knowledge", "Operational Performance", "Risk, Continuity & Organizational Readiness", "Governance & Operations", "Legal, Risk & Compliance", "Privacy, Cybersecurity & Safeguarding". Those are responsibilities. - Requirements/Qualifications: Not explicit list of qualifications, but maybe "Chief Operating Officer (Volunteer)" with commitment 5-10 hrs/week, minimum 6 months, reports to CEO, etc. Could be under "Requirements". Also "Volunteer Executive Leadership". Might include "Experience in nonprofit operations, systems building, etc." Not explicit. We'll need to see if any explicit qualifications listed. The posting includes "About PromiseOperations" and "Role Overview". Not explicit qualifications like degree, years experience. Might be omitted. If no specific qualifications, we should not create a Qualifications section with placeholder. So we may omit Qualifications if no concrete content. - Skills: maybe implied but not explicit. Could omit. - Benefits: Not mentioned (volunteer). No benefits listed. So omit Benefits. - Pay: Volunteer, no pay. Not mention pay. Omit Pay. - Schedule: "Approximately 5–10 hours per week", "Minimum Commitment 6 months; 12 months preferred". That's schedule/commitment. So we can include Schedule section with that info. Thus sections: About the role, Responsibilities, Schedule. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. For About the role, we can use

  prose. For Responsibilities, we need to list duties; we can create

  with many items. Should we break into subcategories? Probably just list each responsibility as
  • . Could be many; but okay. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all responsibilities listed. That's a lot; we need to capture each bullet point. Let's extract responsibilities from the text: Under "Enterprise Operations Strategy": list items: - Develop and lead MAP's enterprise operations strategy. - Establish priorities involving: - Organizational systems - Operational infrastructure - Cross-divisional coordination - Workflow design - Administrative operations - Process improvement - Organizational readiness - Internal service delivery - Documentation - Business continuity - Operational performance - Execution discipline - Organizational scalability That's a list. Under "Strategy Into Execution": description: "Help translate CEO and Executive Team priorities into coordinated organizational action. Use a clear execution framework Decision → Owner → Action → Deadline → Follow-Up → Completion → Documentation Ensure major operational priorities have Clear ownership Defined responsibilities Appropriate contributors Timelines Dependencies Decision authority Escalation pathways Completion criteria Follow-through". That's prose but we can break into bullet points maybe. Under "Organizational Operating Model": description: "Help define how MAP operates across divisions. Clarify Who owns the work? Who contributes? Who decides? Who approves? Who executes? Who monitors? When does something need to be escalated? Support an enterprise framework Own → Recommend → Review → Approve → Execute → Monitor → Escalate". Could be bullet. Under "Operational Systems": list: "Build and strengthen systems supporting MAP's work. This may include Project management Workflows Request processes Internal service systems Operational calendars Documentation Records management Organizational trackers Approval pathways Escalation procedures Cross-functional coordination Operational dashboards Standard operating procedures Knowledge management Organizational planning Administrative infrastructure". Could be bullet list. Under "Cross-Divisional Operations": description: "The COO ensures those divisions can work together effectively without PromiseOperations absorbing their authority. For significant cross-functional initiatives, establish Owner → Contributors → Dependencies → Decision Authority → Timeline → Escalation → Completion The COO should be especially attentive to work that falls between divisions. When everyone is involved but no one owns the outcome, execution becomes fragile." Could be bullet. Under "PromiseOperations Leadership": list responsibilities: "Establish division strategy. Set annual and quarterly priorities. Define operating standards. Build the leadership structure. Recruit and develop Operations leaders. Delegate appropriately. Establish accountability. Review performance. Resolve operational barriers. Improve systems. Build succession and continuity." Also note: "The COO should not become MAP's most overworked Operations Manager. The COO should build an operations organization capable of functioning exceptionally well without depending on one person to hold everything together." That's more guidance. Under "Senior Director of Operations": description: "Provide strategic leadership and direction to the Senior Director of Operations. The relationship should remain clear The Chief Operating Officer determines where PromiseOperations is going. The Senior Director of Operations makes sure PromiseOperations gets there. The COO establishes enterprise operational strategy, priorities, architecture, and expectations. The Senior Director drives implementation, department coordination, operational follow-through, and execution across PromiseOperations. This distinction allows the COO to lead the function rather than becoming consumed by every operational detail." That's more about relationship. Under "Organizational Rhythm": list: "Help establish predictable operating rhythms across MAP. Support systems for Annual planning Quarterly priorities Monthly reviews Weekly execution Leadership reporting Project reviews Operational check-ins Performance monitoring Risk escalation Cross-divisional coordination Follow-up". Could be bullet. Under "Process Improvement": description: "Identify processes that are Unclear Duplicative Manual Inconsistent Slow Unnecessarily complicated Dependent on one person Poorly documented Difficult to scale Use a disciplined improvement process Understand → Map → Diagnose → Simplify → Redesign → Implement → Measure → Improve Do not automate a broken process simply because technology makes automation possible. First determine whether the process should exist in its current form." Could be bullet. Under "Internal Operational Services": description: "Strengthen how internal teams receive operational support. Develop clear processes for requests, ownership, timelines, escalation, and completion. Internal teams should not need personal relationships with the right person to receive routine operational support. A strong organization makes ordinary work easier to accomplish." Could be bullet. Under "Documentation & Institutional Knowledge": description: "Ensure important operational knowledge remains with MAP. Develop standards for SOPs Playbooks Process maps Templates Organizational records Decision documentation Operating procedures Administrative documentation Ownership records Version control Archives People will change. The organization should not have to relearn how it works every time they do." Could be bullet. Under "Operational Performance": list: "Develop practical indicators for understanding organizational execution. These may include Priority completion Project status Turnaround times Missed deadlines Operational bottlenecks Request completion Cross-functional dependencies Process reliability Documentation completeness Recurring operational failures Escalations Team capacity Operational measurement should help leaders identify problems before those problems become emergencies." Could be bullet. Under "Risk, Continuity & Organizational Readiness": description: "Work with PromiseTrust, PromiseShield, PromiseFinance, PromisePeople, and other responsible teams to strengthen organizational preparedness. Support operational planning for Business continuity Critical process coverage Leadership transitions Technology disruptions Vendor disruptions Program interruptions Emergency operations Records availability Key-person dependencies Operational incidents PromiseOperations coordinates operational readiness. It does not replace the specialized legal, privacy, cybersecurity, financial, safeguarding, or governance authority of other divisions." Could be bullet. Under "Governance & Operations": description: "Maintain a clear distinction between PromiseOperations and PromiseGovernance. PromiseGovernance establishes and protects the frameworks within which MAP operates, including appropriate governance structures, authority, oversight, accountability, and institutional responsibilities. PromiseOperations builds and runs the systems that allow MAP to operate effectively within those frameworks. Governance establishes the guardrails and appropriate oversight. Operations builds the systems and processes that allow the organization to move effectively within them. Governance should not become Operations. Operations should not become Governance." Could be bullet. Under "Legal, Risk & Compliance": description: "Partner closely with PromiseTrust while maintaining functional boundaries. PromiseTrust owns legal affairs, legal risk, compliance, and related institutional responsibilities. PromiseOperations may implement processes required by legal or compliance standards but should not independently determine the legal standard. The distinction is important PromiseTrust determines what MAP must do. PromiseOperations helps build reliable systems for doing it." Could be bullet. Under "Privacy, Cybersecurity & Safeguarding": description: "Partner with PromiseShield on operational processes involving privacy, cybersecurity, data protection, safeguarding, and related protective requirements. PromiseShield establishes specialized protective requirements and standards within its authority. PromiseOperations helps ensure those requirements can function". (cut off). Could be bullet. We need to include all these as list items. That's huge but doable. We also need About the role: we can combine "Role Overview" and "About Mentor A Promise". Provide prose. Schedule: include commitment details. Now produce HTML fragment. We must not include any extra text outside HTML. No markdown fences. Let's craft. Structure:

    About the role

    ...

    Responsibilities

    • ...
    ...

    Schedule

    Approximately 5–10 hours per week; minimum commitment 6 months (12 months preferred).

    We need to ensure we don't include any placeholder like "commensurate with experience". Not present. Now craft the About the role paragraph: combine role overview and about MAP. Role Overview: "MAP is seeking a Chief Operating Officer to serve as the organization's senior executive leader for enterprise operations and organizational execution. The COO will translate organizational strategy into operating systems capable of supporting MAP's programs, people, divisions, initiatives, and continued growth. This is not simply an administrative role. The COO must understand how an organization actually works how decisions move, how responsibilities are assigned, how teams coordinate, where processes fail, why commitments stall, what information leaders need, and how systems can make execution more reliable. The COO owns the strategic direction of PromiseOperations. The Senior Director of Operations serves as the principal execution leader beneath the COO, helping translate that direction into day-to-day operational practice. The central question is How do we build an organization capable of reliably executing what it says it will do?" About Mentor A Promise: "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." We can combine. Now responsibilities list: need to include each bullet as separate
  • . Might be long but okay. Let's enumerate