Fleet Coordinator

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse job description. Content: - Job Description: "Responsible for overseeing the Comdata fuel card program and the Diesel fuel management programs including the Bulk fuel supplier contracts." - Essential Duties/Responsibilities: list of bullet-like statements. We need to extract duties/responsibilities. List: - Provides guidance to internal and external clients in relations to our Onsite and offsite Fuel programs - Manages the addition of all new Units and drivers to the Comdata program as needed - Supports all locations with their Bulk fuel programs and works directly with our bulk fuel suppliers - Provides internal and external clients with IFTA fuel Tax reporting data from our fuel suppliers - Works with Corporate Fleet Technology group on projects related to Fuel needs, Fuel Master and any other programs in place. - Works with Corporate Fleet Management Team to insure company fleet standards are (looks incomplete: "are" maybe missing word; but we keep as is) - Provides internal client support as an integral fleet team member - Report and escalate all non-compliant fleet fuel concerns - Supports internal Fleet Compliance Coordinators in a backup role when needed - Other duties as assigned Also there is a line: "Nothing in this job description restricts management's right to assign or reassign duties and responsibilities to this job at any time." That's boilerplate? It's a generic statement; maybe we should drop as it's not substantive? It's a disclaimer; but it's not a duty. Could be considered boilerplate; but it's not cookie/navigation/legal/EEO etc. It's a generic statement about management rights. Might be considered boilerplate but not explicitly listed to remove. However we can keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This line is not exactly those categories, but it's a generic disclaimer. Might be considered boilerplate but not sure. Safer to keep? It's not a duty. Might be considered filler. I'd drop it as it's not substantive duty. Minimum Qualifications: "High School diploma or equivalent", "2+ years of experience in an administrative role within a Fleet Company" Preferred Qualifications: list: - Demonstrates high ethical practices with exceptional decision making - Ability to measure and report operational (incomplete) - Must be able to work in a fast-paced, demanding environment, managing multiple (incomplete) - Excellent written and verbal communication - Functional use of various computer based programs, to include Microsoft Office, specifically Outlook, Excel, Word and Teams, and other related fleet - Ability to prioritize work to meet Fleet (incomplete) - Ability to travel when (incomplete) These are poorly phrased but we must preserve ALL substantive information; do not invent or summarize away detail. So we keep them as is, even if incomplete. Working Conditions and Physical Demands: includes a table-like text with categories. This is substantive; we need to include maybe under a section? There's no specific heading for Working Conditions; we could put under Requirements? But we have headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The physical demands could go under Requirements or maybe Skills? Probably Requirements (minimum qualifications) but it's about working conditions. Could create a section "Working Conditions" but not in allowed headings list. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we should only use those headings? It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely we should restrict to those headings. So we need to map content to those headings. We have: - About the role: could be the introductory sentence: "Responsible for overseeing the Comdata fuel card program and the Diesel fuel management programs including the Bulk fuel supplier contracts." - Responsibilities: the list of duties. - Requirements: Minimum Qualifications. - Qualifications: Preferred Qualifications. - Skills: maybe the skills like communication, computer programs, etc. But those are already in Preferred Qualifications. Could split: Skills section for abilities like communication, computer use, prioritize, travel, etc. But we must not invent sections if no real specific content. We have content for skills: "Excellent written and verbal communication", "Functional use of various computer based programs, to include Microsoft Office, specifically Outlook, Excel, Word and Teams, and other related fleet", "Ability to prioritize work to meet Fleet", "Ability to travel when". Those are skills. So we can create Skills section. - Benefits, Pay, Schedule: not present, so omit. We also have Working Conditions and Physical Demands: not covered by allowed headings. Could we put under Requirements? Might be considered part of Requirements (job requirements). But it's not exactly qualifications; it's work environment. However we could include under Requirements as additional details. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Working Conditions into Requirements or Skills? Probably Requirements is appropriate: includes minimum qualifications and also working conditions. But we already have Minimum Qualifications separate. Could combine both under Requirements. Let's structure:

About the role

Responsible for overseeing the Comdata fuel card program and the Diesel fuel management programs including the Bulk fuel supplier contracts.

Responsibilities

• Provides guidance to internal and external clients in relations to our Onsite and offsite Fuel programs
• Manages the addition of all new Units and drivers to the Comdata program as needed
• Supports all locations with their Bulk fuel programs and works directly with our bulk fuel suppliers
• Provides internal and external clients with IFTA fuel Tax reporting data from our fuel suppliers
• Works with Corporate Fleet Technology group on projects related to Fuel needs, Fuel Master and any other programs in place.
• Works with Corporate Fleet Management Team to insure company fleet standards are
• Provides internal client support as an integral fleet team member
• Report and escalate all non-compliant fleet fuel concerns
• Supports internal Fleet Compliance Coordinators in a backup role when needed
• Other duties as assigned

Requirements

• High School diploma or equivalent
• 2+ years of experience in an administrative role within a Fleet Company

Qualifications

• Demonstrates high ethical practices with exceptional decision making
• Ability to measure and report operational
• Must be able to work in a fast-paced, demanding environment, managing multiple
• Excellent written and verbal communication
• Functional use of various computer based programs, to include Microsoft Office, specifically Outlook, Excel, Word and Teams, and other related fleet
• Ability to prioritize work to meet Fleet
• Ability to travel when

We could also add a Skills section splitting out communication, computer use, prioritize, travel. But we already have those in Qualifications. Might be redundant. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we keep Qualifications as is and not create Skills. We also have Working Conditions and Physical Demands: we haven't included. Should we include them somewhere? They are substantive. Could add under Requirements as additional bullet points. Let's add them under Requirements after the minimum qualifications. So Requirements ul includes: - High School diploma or equivalent - 2+ years of experience in an administrative role within a Fleet Company - Working Environment: Constantly - Exposed to unpleasant or disagreeable physical environments such as high noise level, strong odors, and/or exposure to heat and cold - Constantly - Exposed to bio hazardous conditions - Frequently - Exposed to toxic or caustic chemicals which mandate attention to safety considerations - Frequently - Exposed to Electrical hazards; risk of electrical shock - Constantly - Handles or works with potentially dangerous equipment - Constantly - Travels to offsite locations - Physical Demands: Constantly - Must be able to remain in a stationary position (Sit) - Constantly - Must be able to move about inside/outside office or work location (Walk) - Constantly - Operates a computer and other office machinery (Use hands to finger, handle or feel) - Constantly - Must be able to position one's self to maintain computers in the lab, including under desks and in the server closet (Stoop, kneel, crouch, or crawl) - Constantly - Must be able to ascend/descend on a ladder (Climb or balance) - Constantly - Must be able to use senses to; effectively communicate with co-workers and clients and detect hazardous conditions (Talk, hear, taste, smell) - Weight and Force Demands: Constantly - Up to 10 pounds - Constantly - Up to 25 pounds - Occasionally - Up to 50 pounds - Occasionally - Up to 100 pounds - N/A- More than 100 pounds We need to preserve the exact phrasing. The original had lines like "Working Conditions and Physical Demands N/A | Occasionally = up to 20% | Frequently = 21% to 50% | Constantly = at least 51%". That seems like a legend. Then each condition line. We should include the legend? It's part of the description. Might be considered boilerplate? It's explaining the frequency scale. Could be considered part of Working Conditions. I'd include it as a paragraph before the list. Thus Requirements section could have a

for the legend, then

for each condition. But we must not create empty sections. We'll have content. Now we need to ensure we don't repeat job title as heading (not present). No Job ID. We also have "About Us" and "About The Team" and EEO statement. Those are boilerplate; we should remove. Thus final HTML:

About the role

Responsible for overseeing the Comdata fuel card program and the Diesel fuel management programs including the Bulk fuel supplier contracts.

Responsibilities

...

Requirements

Working Conditions and Physical Demands N/A | Occasionally = up to 20% | Frequently = 21% to 50% | Constantly = at least 51%

• Constantly - Exposed to unpleasant or disagreeable physical environments such as high noise level, strong odors, and/or exposure to heat and cold
• Constantly - Exposed to bio hazardous conditions
• Frequently - Exposed to toxic or caustic chemicals which mandate attention to safety considerations
• Frequently - Exposed to Electrical hazards; risk of electrical shock
• Constantly - Handles or works with potentially dangerous equipment
• Constantly - Travels to offsite locations
• Constantly - Must be able to remain in a stationary position (Sit)
• Constantly - Must be able to move about inside/outside office or work location (Walk)
• Constantly - Operates a computer and other office machinery (Use hands to finger, handle or feel)
• Constantly - Must be able to position one's self to maintain computers in the lab, including under desks and in the server closet (Stoop, kneel, crouch