Campaign and Volunteer Engagement Manager (Adjunct) - Institutional Advancement

We need to output HTML fragment with sections: About the role? The posting includes Position Summary, Salary & Benefits, Primary Duties, Required Knowledge, Skills And Abilities, Preferred Knowledge, Skills And Abilities, Working Conditions. Also maybe "How To Apply" etc but we must remove application instructions. Also remove boilerplate like EEO etc. We must not repeat job title as heading. Use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. The posting has Salary & Benefits: "Minimum starting salary of $60,000, commensurate with experience. Limited benefits package including medical, life insurance, wellness resources and tuition waiver effective on date of hire." This includes "commensurate with experience" which is filler? The instruction says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. It says we should not create Pay/Schedule/Benefits sections unless posting actually states them. It does state them: salary and benefits. However the phrase "commensurate with experience" is considered filler? The instruction says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. It seems they want us to avoid sections that only contain filler like "commensurate with experience". But we have actual salary figure and benefits list. So we can include a Benefits section? They said "Prefer a few substantive sections over many thin ones." We could combine Salary & Benefits into one section maybe titled "Salary & Benefits". That's allowed because posting actually states them. The filler phrase "commensurate with experience" is part of the sentence but not the whole content. It's okay. We also have Working Conditions: "Normal office environment. Some travel and evening/weekend work may be required." That's substantive. We have Position Summary (prose). Primary Duties (list). Required Knowledge, Skills And Abilities (list). Preferred Knowledge, Skills And Abilities (list). Possibly also "How To Apply" but we must remove application instructions. So we omit that. We also need to remove duplicated lines, boilerplate like EEO etc. At the end there is a lot of EEO statement, we must drop that. Thus final HTML: sections: Position Summary (maybe as

  ), Salary & Benefits (maybe as

  • ?), Primary Duties (
    ), Required Knowledge, Skills And Abilities (
    ), Preferred Knowledge, Skills And Abilities (
    ), Working Conditions (

    or

    ? It's prose). Use

    for each section heading. We need to decide heading names: Use exactly the headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can also use other headings? The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, not mandatory. We can use appropriate headings like "Position Summary", "Salary & Benefits", "Primary Duties", "Required Knowledge, Skills and Abilities", "Preferred Knowledge, Skills and Abilities", "Working Conditions". Those are not in the list but likely acceptable as they are descriptive. However they said use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It might be expecting us to map content to those headings. But we can also use other headings as long as they are

    . Safer to use those example headings where appropriate: About the role (for Position Summary), Responsibilities (for Primary Duties), Requirements (for Required Knowledge, Skills And Abilities), Skills (for Preferred Knowledge, Skills And Abilities), Benefits (for Salary & Benefits), maybe Schedule? Not present. Pay? Not separate. Could combine Pay and Benefits? But we have salary and benefits. Could use "Benefits" heading for salary+benefits. Or we could have "Pay" heading for salary and "Benefits" heading for benefits. But they said never create Pay/Schedule/Benefits sections unless posting actually states them. It does state both salary and benefits, so we could have Pay and Benefits separate. However they also said prefer a few substantive sections over many thin ones. So maybe combine into one Benefits section. Let's decide: Use headings: About the role, Responsibilities, Requirements, Skills, Benefits, Working Conditions. That seems reasonable. Now content: About the role: Position Summary paragraph. Responsibilities: Primary Duties list items. Requirements: Required Knowledge, Skills And Abilities list. Skills: Preferred Knowledge, Skills And Abilities list. Benefits: Salary & Benefits: Minimum starting salary of $60,000, commensurate with experience. Limited benefits package including medical, life insurance, wellness resources and tuition waiver effective on date of hire. We need to use

    • for any list of duties/requirements/benefits. For Benefits, it's not a list but we could still make a
      with two items: salary and benefits. Or we could keep as

      . The instruction: Use

      • for any list of duties/requirements/benefits, and

        for prose. Benefits is not a list but could be considered a list? It says "any list of duties/requirements/benefits". So if we treat benefits as a list, we should use

        • . But we have also salary. Could make two
        • items: one for salary, one for benefits. Working Conditions: prose, use

          . Now ensure we remove boilerplate: The EEO statement at end, also "How To Apply", "Application Deadline", etc. Also remove lines like "Must have the physical stamina to work long hours and/or more than 5 days per week." That is part of Working Conditions? Actually that appears after EEO. It's a requirement about physical stamina. Might be considered part of Working Conditions or Requirements. It's substantive: "Must have the physical stamina to work long hours and/or more than 5 days per week." Should we keep? It's not boilerplate; it's a job requirement. It appears after the EEO statement but before the accommodation statement. It's a requirement. We should keep it. Where to place? Could be under Requirements or Working Conditions. Since it's about physical stamina, maybe under Working Conditions. We'll add as a sentence in Working Conditions

          . Also "To perform this job successfully, an individual must be able to perform each essential duty satisfactorily." That's generic boilerplate; maybe remove as it's filler. Also "The requirements listed are representative of the knowledge, skill and/or ability required." That's also boilerplate. Also "Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions." That's EEO boilerplate; remove. Also "The information contained in this job description is for compliance with the Americans with Disabilities Act..." remove. Also "GVSU will provide reasonable accommodations..." remove. Also "See www.gvsu.edu/equalopportunity." remove. Also "TDD Callers..." remove. Also "Grand Valley State University is an Antidiscrimination/Equal Opportunity Employer..." remove. Also "University policy extends protections to additional identities." remove. Also "Application review begins October 1, 2026. This posting may be closed at any time at the discretion of the University." That's application instruction/boilerplate; remove. Also "If you have questions about the position or the posting, please contact Institutional Advancement at advancement@gvsu.edu." remove. Also "If you need technical assistance, please contact Human Resources at hro@gvsu.edu." remove. Also "Applicants must be legally authorized to work in the United States and must not require sponsorship now or in the future." That's a requirement; maybe keep under Requirements? It's a legal requirement. Could be considered a requirement. We'll keep as a requirement item. Also "Attach your cover letter and resume. The system will allow you to attach these documents electronically." remove. Now compile content. Position Summary paragraph: "This position leads the day-to-day coordination of campaign related activities and campaign volunteer engagement, serving as a key partner to campaign leadership, volunteers, fundraisers, and University partners. This role advances campaign fundraising efforts by coordinating and tracking activity, progress, and follow-through toward campaign goals. This position oversees volunteer communications and meetings, develops materials and resources to equip volunteers for success, coordinates campaign visits and solicitations, and facilitates collaboration across teams. This position anticipates needs, identifies opportunities to strengthen engagement, and ensures campaign priorities are effectively organized and advanced in support of the Comprehensive Campaign." Now Primary Duties list: each sentence starting with a verb. Let's extract: - Serve as a primary point of contact for campaign volunteer engagement and support, providing guidance, resources, and information; monitoring engagement; and escalating complex matters to campaign leadership. - In collaboration with colleagues in prospect research and management and frontline fundraisers, coordinate and track campaign prospects, assignments, cultivation activities, solicitations, and follow-up actions. - Manage the preparation and execution of campaign volunteer meetings, positioning campaign leadership for successful engagement with campaign volunteers. - Partner with professional support staff on scheduling, materials, communications, and follow-up to facilitate effective implementation. - Facilitate cross-functional communication and workflow among campaign leadership, Institutional Advancement teams, volunteers, and University partners. - Ensure prospect research and management needs, requests, assignments, timelines, and relevant information are effectively communicated, routed, and advanced through completion. - Drive the prospect visit and solicitation process forward by coordinating with frontline fundraisers and professional support staff to ensure timely completion of briefing materials, proposals, solicitation tracking, and follow-up communications. - Develop and maintain organized campaign resources and systems, including virtual and hardcopy volunteer resources, prospect materials, assignment information, campaign communications, meeting outcomes, and other documentation essential to effective campaign execution. - Track and communicate campaign progress and activity through regular review of volunteer engagement, prospect assignments, solicitation activity, outstanding action items, and key deadlines. Identify gaps and opportunities for follow-up and prepare reports, updates, and materials for campaign leadership. - Advance campaign-related processes and special projects, including collaboration with colleagues in gift processing to support accurate recordkeeping and timely processing of campaign gifts. - Contribute to volunteer engagement initiatives, campaign events, communications, data collection, and other priorities supporting successful implementation of the Comprehensive Campaign. - Perform other duties as required/assigned by leadership. Now Required Knowledge, Skills And Abilities list: - Bachelor’s degree or equivalent combination of education and relevant experience in an appropriate field such as communications, marketing, business, nonprofit management, or a related discipline. - Two to five (2-5) years of volunteer management and project management experience, with the ability to develop and maintain effective systems, manage multiple priorities and deadlines, track assignments and commitments, and ensure timely follow-through. - Excellent interpersonal skills and communication skills, with demonstrated ability to build effective, collaborative relationships that advance work and achieve shared goals with volunteers, senior leaders, staff, internal and external partners. - Proven ability to work proactively and collaboratively across multiple teams