Administrative Support II
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the 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 the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the posting.
Key info:
- Department: 11100 Wake Forest Baptist Medical Center - Volunteer Services
- Status: Full time
- Benefits Eligible: Yes
- Hours Per Week: 40
- Schedule Details/Additional Information: M-F 8-5 with variation for special projects
- Pay Range: $24.10 - $36.15
- Major Responsibilities: list of duties (multiple sentences)
- Minimum Job Requirements: Education, Certification, Experience, Knowledge/Skills/Abilities
- Physical Requirements And Working Conditions: description
- This job description indicates... (boilerplate)
- Our Commitment To You Advocate Health offers a comprehensive suite of Total Rewards: benefits and well-being programs... (list of benefits)
- About Advocate Health: description
- Additional description: "Provides basic to moderately complex administrative support, including reception, scheduling, word processing, document distribution, and file maintenance. Relieves department leadership and other staff of administrative details, using judgment and discretion to solve office problems and expedite workflow."
We need to decide sections.
We have:
- About the role: maybe a short prose summarizing role? The posting includes "Provides basic to moderately complex administrative support..." which is a description of role. Also "Major Responsibilities" list.
- Responsibilities: list of duties (the "Major Responsibilities" bullet list). We can put that under
Responsibilities
with - items.
- Requirements: maybe combine Education, Certification, Experience, Knowledge/Skills/Abilities, Physical Requirements? Could have sections: Requirements (education/experience), Skills (knowledge/skills/abilities), Qualifications? But we need to avoid thin sections. Perhaps combine Requirements and Skills into one
Requirements
with sublists? However spec says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have separate sections if content exists.
We have:
- Requirements: Education, Certification, Experience (minimum job requirements). That's substantive.
- Skills: Knowledge / Skills / Abilities list (time management, confidentiality, initiative, communication, professional demeanor, proficiency in Microsoft Office, organizational and multitasking abilities, diligence, ability to create documents). That's substantive.
- Qualifications: maybe not separate; could be same as Requirements? But we have "Minimum Job Requirements" includes Education, Certification, Experience. Could treat that as Requirements. Skills separate.
- Benefits: The posting includes "Benefits Eligible Yes" and then "Our Commitment To You Advocate Health offers a comprehensive suite of Total Rewards: benefits and well-being programs..." with list: Paid Time Off programs, Health and welfare benefits such as medical, dental, vision, life, and Short- and Long-Term Disability, Flexible Spending Accounts, Family benefits such as adoption assistance and paid parental leave, Defined contribution retirement plans with employer match and other financial wellness programs, Educational Assistance Program. Also note eligibility depends on FTE/status. That's substantive benefits content. So we can have Benefits section.
- Pay: Pay Range $24.10 - $36.15. That's specific. So we can have Pay section.
- Schedule: Hours Per Week 40, Schedule Details/Additional Information M-F 8-5 with variation for special projects. That's substantive. So Schedule section.
- About the role: maybe a brief paragraph summarizing role: "Provides basic to moderately complex administrative support, including reception, scheduling, word processing, document distribution, and file maintenance. Relieves department leadership and other staff of administrative details, using judgment and discretion to solve office problems and expedite workflow." That's substantive. Could be About the role.
We also have "About Advocate Health" description of the organization. That could be considered "About the company" but not in list of headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add a section for About Advocate Health unless we map it to About the role? Probably not; we should omit that as it's not required heading. However we must preserve ALL substantive information; we cannot drop it. But we can incorporate it into About the role or maybe a general
without heading? 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 says to use those for section headings. It says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings, but we should stick to those given. However we need to preserve all substantive info; we could put the About Advocate Health description in a
under About the role or maybe as a separate
without heading. The instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings, but to be safe we can include the About Advocate Health as a
after About the role heading, or maybe as a separate
About the company? Not in list. Safer to incorporate into About the role paragraph.
We also have "Department 11100 Wake Forest Baptist Medical Center - Volunteer Services Status Full time Benefits Eligible Yes Hours Per Week 40 Schedule Details/Additional Information M-F 8-5 with variation for special projects Pay Range $24.10 - $36.15". This is metadata; we can fold into short
or drop minor metadata like Department, Status, Benefits Eligible, Hours Per Week, Schedule Details, Pay Range. But we already have sections for Pay, Schedule, Benefits. So we can drop the redundant lines.
We need to avoid duplication.
Let's extract substantive content:
**About the role** (maybe combine the two descriptive paragraphs):
- "Provides basic to moderately complex administrative support, including reception, scheduling, word processing, document distribution, and file maintenance. Relieves department leadership and other staff of administrative details, using judgment and discretion to solve office problems and expedite workflow."
That's it.
**Responsibilities** (list from Major Responsibilities):
- Schedules and maintains calendars for appointments, meetings, and travel.
- Assists with travel arrangements and expense reporting.
- Organizes administrative aspects of meetings (agenda, site, food/beverage, technology, documents).
- Answers and screens calls, greets visitors, provides procedural information, and answers questions related to operational matters.
- Performs routine to moderately complex word processing and document creation.
- Make decisions on formatting and layout, editing for accuracy and consistency.
- Compiles reports, graphics, and statistical data.
- Creates reports under general instruction and displays data to support needs, including the generation of existing reports.
- Maintains filing systems and confidential records.
- Opens, reads, and prioritizes mail, initiating return correspondence as appropriate.
- Conducts basic research and analysis to support administrative needs.
- Operates and maintains office equipment; may order supplies as needed.
**Requirements** (Education, Certification, Experience):
- Education: High School Graduate
- Certification / Registration / License: None Required
- Experience: Typically requires 1 year of administrative support experience
**Skills** (Knowledge / Skills / Abilities):
- Time management and prioritization.
- Ability to maintain confidentiality and use discretion.
- Initiative and independent problem-solving.
- Effective written and verbal communication.
- Professional demeanor and customer service orientation.
- Proficiency in Microsoft Office (Excel, PowerPoint, Word).
- Organizational and multitasking abilities.
- Diligence and attention to detail.
- Ability to create and compile simple to moderately complex documents, reports, graphs/charts, and presentations.
**Benefits** (from Benefits Eligible Yes and Total Rewards list):
- Benefits Eligible: Yes (full-time)
- Paid Time Off programs
- Health and welfare benefits such as medical, dental, vision, life, and Short- and Long-Term Disability
- Flexible Spending Accounts for eligible health care and dependent care expenses
- Family benefits such as adoption assistance and paid parental leave
- Defined contribution retirement plans with employer match and other financial wellness programs
- Educational Assistance Program
- Note: Eligibility for programs listed above may depend on your FTE or status (e.g., full-time, part-time, per diem, temporary, etc.); please ask a Recruiter for more information during an interview.
**Pay**:
- Pay Range: $24.10 - $36.15 (hourly presumably)
**Schedule**:
- Hours Per Week: 40
- Schedule Details/Additional Information: M-F 8-5 with variation for special projects
We also have Physical Requirements And Working Conditions: "Normal office environment; occasional lifting up to 20 lbs. Prolonged periods of sitting, standing, and keyboard use." This is substantive; we could include under a section maybe "Working Conditions" but not in allowed headings. Could we add a section? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but suggests those as examples. However to be safe, we could incorporate Physical Requirements into Requirements or Skills? Probably better to add a separate Working Conditions
but not in list. Might be considered extra heading; risk of being penalized? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot use other headings, but the examples are those. The safer approach is to include Physical Requirements under Requirements or maybe as a
without heading after Requirements. But we need to preserve all substantive info; we can add a
after Requirements heading.
Similarly, the boilerplate lines like "This job description indicates the general nature and level of work expected of the incumbent..." and "Our Commitment To You Advocate Health offers a comprehensive suite..." we already used benefits. The "About Advocate Health" description we can incorporate maybe as a
after Benefits or after About the role. But we need to preserve it. Could add a
under About the role heading (maybe two paragraphs). That would preserve.
We must not include duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, application instructions. The "Our Commitment To You" includes benefits list; we used that. The "About Advocate Health" is not boilerplate; it's substantive about the company. We'll keep.
Now structure:
About the role
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the 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 the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Key info: - Department: 11100 Wake Forest Baptist Medical Center - Volunteer Services - Status: Full time - Benefits Eligible: Yes - Hours Per Week: 40 - Schedule Details/Additional Information: M-F 8-5 with variation for special projects - Pay Range: $24.10 - $36.15 - Major Responsibilities: list of duties (multiple sentences) - Minimum Job Requirements: Education, Certification, Experience, Knowledge/Skills/Abilities - Physical Requirements And Working Conditions: description - This job description indicates... (boilerplate) - Our Commitment To You Advocate Health offers a comprehensive suite of Total Rewards: benefits and well-being programs... (list of benefits) - About Advocate Health: description - Additional description: "Provides basic to moderately complex administrative support, including reception, scheduling, word processing, document distribution, and file maintenance. Relieves department leadership and other staff of administrative details, using judgment and discretion to solve office problems and expedite workflow." We need to decide sections. We have: - About the role: maybe a short prose summarizing role? The posting includes "Provides basic to moderately complex administrative support..." which is a description of role. Also "Major Responsibilities" list. - Responsibilities: list of duties (the "Major Responsibilities" bullet list). We can put that under
Responsibilities
with- items.
- Requirements: maybe combine Education, Certification, Experience, Knowledge/Skills/Abilities, Physical Requirements? Could have sections: Requirements (education/experience), Skills (knowledge/skills/abilities), Qualifications? But we need to avoid thin sections. Perhaps combine Requirements and Skills into one
Requirements
with sublists? However spec says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have separate sections if content exists. We have: - Requirements: Education, Certification, Experience (minimum job requirements). That's substantive. - Skills: Knowledge / Skills / Abilities list (time management, confidentiality, initiative, communication, professional demeanor, proficiency in Microsoft Office, organizational and multitasking abilities, diligence, ability to create documents). That's substantive. - Qualifications: maybe not separate; could be same as Requirements? But we have "Minimum Job Requirements" includes Education, Certification, Experience. Could treat that as Requirements. Skills separate. - Benefits: The posting includes "Benefits Eligible Yes" and then "Our Commitment To You Advocate Health offers a comprehensive suite of Total Rewards: benefits and well-being programs..." with list: Paid Time Off programs, Health and welfare benefits such as medical, dental, vision, life, and Short- and Long-Term Disability, Flexible Spending Accounts, Family benefits such as adoption assistance and paid parental leave, Defined contribution retirement plans with employer match and other financial wellness programs, Educational Assistance Program. Also note eligibility depends on FTE/status. That's substantive benefits content. So we can have Benefits section. - Pay: Pay Range $24.10 - $36.15. That's specific. So we can have Pay section. - Schedule: Hours Per Week 40, Schedule Details/Additional Information M-F 8-5 with variation for special projects. That's substantive. So Schedule section. - About the role: maybe a brief paragraph summarizing role: "Provides basic to moderately complex administrative support, including reception, scheduling, word processing, document distribution, and file maintenance. Relieves department leadership and other staff of administrative details, using judgment and discretion to solve office problems and expedite workflow." That's substantive. Could be About the role. We also have "About Advocate Health" description of the organization. That could be considered "About the company" but not in list of headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add a section for About Advocate Health unless we map it to About the role? Probably not; we should omit that as it's not required heading. However we must preserve ALL substantive information; we cannot drop it. But we can incorporate it into About the role or maybe a general
without heading? 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 says to use those for section headings. It says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings, but we should stick to those given. However we need to preserve all substantive info; we could put the About Advocate Health description in a
under About the role or maybe as a separate
without heading. The instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings, but to be safe we can include the About Advocate Health as a
after About the role heading, or maybe as a separate
About the company? Not in list. Safer to incorporate into About the role paragraph. We also have "Department 11100 Wake Forest Baptist Medical Center - Volunteer Services Status Full time Benefits Eligible Yes Hours Per Week 40 Schedule Details/Additional Information M-F 8-5 with variation for special projects Pay Range $24.10 - $36.15". This is metadata; we can fold into short
or drop minor metadata like Department, Status, Benefits Eligible, Hours Per Week, Schedule Details, Pay Range. But we already have sections for Pay, Schedule, Benefits. So we can drop the redundant lines. We need to avoid duplication. Let's extract substantive content: **About the role** (maybe combine the two descriptive paragraphs): - "Provides basic to moderately complex administrative support, including reception, scheduling, word processing, document distribution, and file maintenance. Relieves department leadership and other staff of administrative details, using judgment and discretion to solve office problems and expedite workflow." That's it. **Responsibilities** (list from Major Responsibilities): - Schedules and maintains calendars for appointments, meetings, and travel. - Assists with travel arrangements and expense reporting. - Organizes administrative aspects of meetings (agenda, site, food/beverage, technology, documents). - Answers and screens calls, greets visitors, provides procedural information, and answers questions related to operational matters. - Performs routine to moderately complex word processing and document creation. - Make decisions on formatting and layout, editing for accuracy and consistency. - Compiles reports, graphics, and statistical data. - Creates reports under general instruction and displays data to support needs, including the generation of existing reports. - Maintains filing systems and confidential records. - Opens, reads, and prioritizes mail, initiating return correspondence as appropriate. - Conducts basic research and analysis to support administrative needs. - Operates and maintains office equipment; may order supplies as needed. **Requirements** (Education, Certification, Experience): - Education: High School Graduate - Certification / Registration / License: None Required - Experience: Typically requires 1 year of administrative support experience **Skills** (Knowledge / Skills / Abilities): - Time management and prioritization. - Ability to maintain confidentiality and use discretion. - Initiative and independent problem-solving. - Effective written and verbal communication. - Professional demeanor and customer service orientation. - Proficiency in Microsoft Office (Excel, PowerPoint, Word). - Organizational and multitasking abilities. - Diligence and attention to detail. - Ability to create and compile simple to moderately complex documents, reports, graphs/charts, and presentations. **Benefits** (from Benefits Eligible Yes and Total Rewards list): - Benefits Eligible: Yes (full-time) - Paid Time Off programs - Health and welfare benefits such as medical, dental, vision, life, and Short- and Long-Term Disability - Flexible Spending Accounts for eligible health care and dependent care expenses - Family benefits such as adoption assistance and paid parental leave - Defined contribution retirement plans with employer match and other financial wellness programs - Educational Assistance Program - Note: Eligibility for programs listed above may depend on your FTE or status (e.g., full-time, part-time, per diem, temporary, etc.); please ask a Recruiter for more information during an interview. **Pay**: - Pay Range: $24.10 - $36.15 (hourly presumably) **Schedule**: - Hours Per Week: 40 - Schedule Details/Additional Information: M-F 8-5 with variation for special projects We also have Physical Requirements And Working Conditions: "Normal office environment; occasional lifting up to 20 lbs. Prolonged periods of sitting, standing, and keyboard use." This is substantive; we could include under a section maybe "Working Conditions" but not in allowed headings. Could we add a section? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but suggests those as examples. However to be safe, we could incorporate Physical Requirements into Requirements or Skills? Probably better to add a separate
Working Conditions
but not in list. Might be considered extra heading; risk of being penalized? The instruction: "Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot use other headings, but the examples are those. The safer approach is to include Physical Requirements under Requirements or maybe as a
without heading after Requirements. But we need to preserve all substantive info; we can add a
after Requirements heading. Similarly, the boilerplate lines like "This job description indicates the general nature and level of work expected of the incumbent..." and "Our Commitment To You Advocate Health offers a comprehensive suite..." we already used benefits. The "About Advocate Health" description we can incorporate maybe as a
after Benefits or after About the role. But we need to preserve it. Could add a
under About the role heading (maybe two paragraphs). That would preserve. We must not include duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, application instructions. The "Our Commitment To You" includes benefits list; we used that. The "About Advocate Health" is not boilerplate; it's substantive about the company. We'll keep. Now structure:
About the role