Development Program Manager, Central Programs (Prospect Development and Stewardship & Donor Experience)
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content. We have:
- About the role: maybe we can combine the introductory paragraph about mission, structure, focus. Could be "About the role" or "Focus". The instructions say we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content.
We have:
- Focus: description of role as strategic partner, supporting teams.
- Specific Duties: list of duties.
- Requirements: bullet list of qualifications.
- What We Offer: includes pay range, benefits description.
- Physical Demands: description.
- Work Environment: description.
- Pre-Hire Requirements: background check, drug test, education verification.
We should not include boilerplate like EEO etc. Already removed.
We need to decide which headings to use. We have content for:
- About the role (maybe include mission statement and structure). Could be "About the role".
- Responsibilities (Specific Duties).
- Requirements (maybe combine Requirements and Qualifications). The posting has "Requirements" bullet list. Could use "Requirements" heading.
- Benefits (What We Offer includes benefits). Also Pay range.
- Pay (we have hourly rate range). Could have separate Pay section.
- Schedule? Not explicitly given, but mentions ability to work non-traditional flexible hours, evenings, weekends, travel. That's schedule info. Could include Schedule section.
- Physical Demands and Work Environment maybe could be under "Working Conditions" but not in allowed headings. Since only allowed headings list includes those specific ones; we should not create other headings. So we may need to omit Physical Demands and Work Environment if they don't fit allowed headings. However we must preserve ALL substantive information; cannot drop info. But we can incorporate that info into existing sections like Responsibilities or Benefits? Not appropriate. 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 exclusive? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect we use those headings where appropriate; we could also use other headings if needed? But they gave examples; maybe we should stick to those. However we have info like Physical Demands and Work Environment and Pre-Hire Requirements. Could we fit them under "Responsibilities"? No. Could we create a "Qualifications" heading for requirements? Already have Requirements. Could we put Physical Demands under "Benefits"? No.
Maybe we can create a section "Working Conditions" but not in list; risk of violating instruction. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those. Safer to use only those headings and incorporate other info into appropriate sections. For Physical Demands and Work Environment, maybe we can put under "Responsibilities" as part of job demands? Not ideal but could be considered part of role. Pre-Hire Requirements could be under "Requirements". Actually Pre-Hire Requirements are about background check etc., which could be considered part of Requirements (pre-employment). So we can add those to Requirements section.
Physical Demands and Work Environment could be added to "Responsibilities" as part of job demands, but maybe better to create a "Skills" heading? Not appropriate.
Alternatively, we could create a section "About the role" that includes mission, structure, focus, physical demands, work environment? Might be too broad.
Given the instruction to preserve ALL substantive information, we need to include them somewhere. Let's try to incorporate Physical Demands and Work Environment into a "Responsibilities" section as bullet points under a subheading? But we cannot add extra headings besides h3. We could add a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect we use those headings where appropriate; we could also use other headings if needed? But they gave examples; maybe we should stick to those. However we have info like Physical Demands and Work Environment and Pre-Hire Requirements. Could we fit them under "Responsibilities"? No. Could we create a "Qualifications" heading for requirements? Already have Requirements. Could we put Physical Demands under "Benefits"? No.
Maybe we can create a section "Working Conditions" but not in list; risk of violating instruction. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those. Safer to use only those headings and incorporate other info into appropriate sections. For Physical Demands and Work Environment, maybe we can put under "Responsibilities" as part of job demands? Not ideal but could be considered part of role. Pre-Hire Requirements could be under "Requirements". Actually Pre-Hire Requirements are about background check etc., which could be considered part of Requirements (pre-employment). So we can add those to Requirements section.
Physical Demands and Work Environment could be added to "Responsibilities" as part of job demands, but maybe better to create a "Skills" heading? Not appropriate.
Alternatively, we could create a section "About the role" that includes mission, structure, focus, physical demands, work environment? Might be too broad.
Given the instruction to preserve ALL substantive information, we need to include them somewhere. Let's try to incorporate Physical Demands and Work Environment into a "Responsibilities" section as bullet points under a subheading? But we cannot add extra headings besides h3. We could add a
inside Responsibilities describing physical demands and work environment. That would preserve info. Similarly, Pre-Hire Requirements can be added to Requirements section as bullet. Thus sections: - About the role: includes introductory paragraph about mission, structure, focus. - Responsibilities: includes specific duties list plus physical demands and work environment description. - Requirements: includes bullet list of qualifications plus pre-hire requirements. - Benefits: includes benefits description (total rewards package). - Pay: includes hourly rate range. - Schedule: includes note about flexible hours, evenings, weekends, travel. We must not repeat job title as heading. We must not include Job ID etc. We must not include boilerplate like EEO etc. We must output only HTML fragment. Let's craft. First, About the role: combine mission statement and structure and focus. Paragraph: "At the University of Cincinnati Foundation, we commit ourselves to providing a place where everyone belongs. We care deeply about those in our community, while also taking care to nurture new relationships. We have the courage to dream big, drive excellence and uphold integrity in our work. The Development Program Manager, Central Programs, is a non-exempt (hourly) position employed by the University of Cincinnati Foundation (UCF) and reports to the Senior Director of Operations, Central Programs. Serving as a strategic partner, the role provides programmatic, operational, and project support to the Prospect Development and Stewardship & Donor Experience teams." That seems good. Next Responsibilities: Provide administrative support etc. We'll list bullet list of specific duties. Then add a paragraph about physical demands and work environment. We need to preserve all duties exactly as given. Let's list them: - Provide administrative support, including calendar management, travel planning, submitting support tickets and expense reports for the Prospect Development and Stewardship & Donor Experience teams. - Support donor recognition efforts including mailings, generating lists for invitations and honor rolls, parking, responding to donor emails and calls; run reports, as needed. - Provide support for and attend strategy sessions and team meetings for Prospect Development and Stewardship & Donor Experience; prepare and file meeting materials. - Assist with paper document management, including mailing and printing documents. - In coordination with Central Programs’ administrative support team members, create, maintain and distribute Central Programs’ newsletter and HUB content. - Maintain a central file structure for the Central Programs team, coordinating with other Central Programs’ administrative support team members to ensure paper and electronic files and important documents are organized and maintained in a consistent manner. - Assist the Senior Director of Operations in budget management, including tracking and processing purchase orders, invoices, and monitoring other essential financial processes. - Special projects, as assigned by the Senior Director of Operations. - Handle confidential information and correspondence. - Other duties, as assigned. Now physical demands: "This Position Is Considered To Have Medium Work. Exerting Up To 50lbs. Of Force Occasionally, And/or Up To 30 Lbs. Of Force Frequently, And/or Up To 10 Lbs. Of Force Constantly To Move Objects. This Position Requires The Operation Of a Motor Vehicle. This Position Also Requires ClimbingStandingWalkingPushingPullingReachingLiftingFinger useTalkingHearingRepetitive motion of the wrist, hands, and/or fingers" We need to preserve exactly but maybe format nicely. We'll put as a paragraph. Work Environment: "While performing the duties of this job, this position is subject to outside environmental conditions and indoor conditions." We'll add after physical demands. Now Requirements: bullet list: - Bachelor’s degree preferred and 1-3 years of administrative support experience or the equivalent combination of education and related experience. - Proven ability to handle, update, and maintain sensitive information in a confidential, timely, and professional manner. - High level of accuracy and attention to detail; excellent oral, written, and interpersonal communication skills. - Ability to interact in a courteous, positive, professional, and timely manner with diverse internal and external constituents and foster strong, productive relationships. - Proficiency in Adobe, Microsoft Office (e.g. Word, Office, Excel, PowerPoint) and information systems databases. - Ability to prioritize effectively to meet multiple competing deadlines. - Able to work non-traditional, flexible hours, as needed for events, including evenings, weekends and travel when needed. - Valid driver’s license and access to a vehicle required for travel. - A commitment to and passion for the role of development in advancing the mission of the University of Cincinnati. Pre-Hire Requirements: "All offers of full-time employment are contingent upon passing a criminal background check and drug test. Positions requiring a degree are also contingent upon education verification." We'll add as bullet points under Requirements. Now Benefits: paragraph: "At the UC Foundation, we understand the importance of providing both a desirable work environment as well as benefits that provide our employee’s peace of mind and work/life balance. We offer a total rewards package inclusive of performance based bonus, as well as, competitive health and wellness benefits, tuition remission, retirement with employer match, paid parental leave, and paid vacation, sick time and holidays, including calendar year-end closing." Also mention "To learn more, visit our careers page." That's like application instruction? It's not exactly instruction but maybe considered boilerplate? It's a link to careers page; might be considered navigation? Probably we should drop it as it's not substantive about the job. The instruction says remove application instructions. This is not exactly application instruction but maybe considered a link to learn more; could be considered boilerplate. Safer to drop. Now Pay: "The anticipated starting hourly rate range for the Development Program Manager, Central Programs role is $24.00 to $27.50 . When determining final offer amount the UC Foundation considers factors such as (but not limited to) scope and responsibilities of the position, candidate’s work experience, education/training, key skills, internal peer equity, external market data, as well as, market and business considerations when making compensation decisions." We'll keep that. Now Schedule: we have info about ability to work non-traditional flexible hours, evenings, weekends, travel when needed. Already included in Requirements but we can also put in Schedule section. However we must not duplicate content? The instruction says preserve ALL substantive information; duplication is okay if it's already present elsewhere? It says remove duplicated lines. So we should not duplicate same sentence. We have that sentence already in Requirements. If we also put in Schedule, that would be duplication. Better to move that sentence to Schedule and remove from Requirements? But the requirement list includes that as a requirement; it's both a requirement and schedule info. We could keep it under Requirements and not have a separate Schedule section. However we need to include Schedule section only if posting has real specific content for it. The posting does mention flexible hours etc. So we could have Schedule section with that content, and we could remove it from Requirements to avoid duplication. But then we would lose that requirement info. However the requirement list includes many items; we could keep the requirement about flexible hours as part of Requirements but also mention in Schedule? That would be duplication. The instruction says remove duplicated lines. So we should avoid duplication. We need to decide where to place it. The requirement list includes "Able to work non-traditional, flexible hours, as needed for events, including evenings, weekends and travel when needed." That's definitely a requirement. The schedule info is essentially the same. So we could keep it under Requirements and not have a Schedule section. But then we would not have a Schedule section, which is okay if we don't have specific schedule content beyond that. However the instruction says "include a section ONLY when the posting has real, specific content for it". If we treat the flexible hours as schedule content, we could have a Schedule section with that content, and we could remove it from Requirements to avoid duplication. But then we would lose that