Part-time Distribution Center Dispatcher
Suburban Propane · Salt Lake City, UT · 1 mo ago
ManagementPart-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Must preserve all substantive info.
Let's parse the job description.
First paragraph: "Job Description We are currently looking for a Part-time Dispatcher (Distribution Center) to play a pivotal role in ensuring the efficient delivery of propane to our customers across diverse geographical areas and climates. As a Dispatcher, your primary responsibility will include assigning and scheduling Drivers for both daily and weekly propane deliveries. Identify and recommend customer specific routing and demand forecasting changes Assist Customer Service Centers (CSCs) with the resolution of delivery inquiries and issues from customers Assist with the delivery process by addressing and correcting skipped orders, inaccurate directions, propane tank obstructions, etc. Ensure timely, consistent and open lines of communication between the Distribution Center, CSCs, Drivers and customers Adapt to rapid and significant changes in workload due to weather, road conditions and other factors influencing the delivery fleet Provide general administrative support as required (i.e. drafting internal communications, filing and relaying processes/procedures) This is a part-time position offering approximately 29 hours per week."
So we have responsibilities list.
Then "Why join the Suburban Propane team? We value you as a part-time team member and will provide you with competitive pay and annual incentive potential, 401(k) Retirement Savings & Investment Plan with Company Match, paid time off including holidays, and generous employee discounts on products and services. For eligibility and a full list of our benefit offerings please visit https://jobs.suburbanpropane.com/benefits/"
So benefits: competitive pay and annual incentive potential, 401(k) with company match, paid time off including holidays, generous employee discounts on products and services. Also mention eligibility link.
Then "Minimum of 3 years of dispatching or related experience Minimum of a High School diploma or GED preferred Knowledge of fuel distribution concepts, practices and procedures including related government regulations Solid computer skills including Microsoft Office, data entry and the ability to run and analyze reports Ability to multi-task and prioritize assignments in a team environment"
These are requirements/qualifications/skills.
Then company description: Suburban Propane Partners, L.P. ... etc. That's about the company, maybe "About the role"? Actually "About the role" could be the introductory paragraph describing role. Could also be "About the company". But we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have schedule: part-time approx 29 hours per week. That's schedule.
Pay: "competitive pay and annual incentive potential". That's pay info.
Benefits: as above.
Requirements: Minimum of 3 years of dispatching or related experience; Minimum of a High School diploma or GED preferred.
Qualifications: maybe knowledge of fuel distribution concepts, practices and procedures including related government regulations; solid computer skills including Microsoft Office, data entry and ability to run and analyze reports; ability to multi-task and prioritize assignments in a team environment.
Skills: could be overlapping with qualifications. But we need to avoid duplication. We can separate: Requirements (experience, education), Qualifications (knowledge, computer skills), Skills (multi-task, prioritize). Or we could combine. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Requirements and Qualifications into one section? But they ask to use headings for those specific names if content exists. We need to decide.
We have content for:
- About the role: introductory paragraph describing role and purpose.
- Responsibilities: list of duties.
- Requirements: experience and education.
- Qualifications: knowledge of fuel distribution, computer skills.
- Skills: multi-task, prioritize.
- Benefits: list.
- Pay: competitive pay and annual incentive potential.
- Schedule: part-time approx 29 hours per week.
All have substantive content.
We must not include boilerplate like EEO, legal, application instructions, etc. Remove duplicated lines. Also remove navigation, cookie, etc. The description includes company description and pillars etc. That's likely boilerplate? It's substantive about company but maybe not needed for role? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The company description is substantive about the employer. Should we include it? Possibly under "About the role" or a separate "About the company" but not in list of allowed headings. The allowed headings are only those listed. We could incorporate company description into "About the role" maybe as context. But 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 says to use those for section headings. It might be okay to include other headings but they'd be non-standard. Safer to stick to those headings and put company info maybe in About the role or maybe omit? The instruction: "Prefer a few substantive sections over many thin ones." So we could combine company description into About the role.
Thus About the role: include the introductory paragraph plus company overview.
Responsibilities: bullet list.
Requirements: experience and education.
Qualifications: knowledge of fuel distribution, computer skills.
Skills: multi-task, prioritize.
Benefits: list.
Pay: competitive pay and annual incentive potential.
Schedule: part-time approx 29 hours per week.
Now format.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
.
Now Requirements:
- Minimum of 3 years of dispatching or related experience
- Minimum of a High School diploma or GED preferred
Now Qualifications:
- Knowledge of fuel distribution concepts, practices and procedures including related government regulations
- Solid computer skills including Microsoft Office, data entry and the ability to run and analyze reports
Now Skills:
- Ability to multi-task and prioritize assignments in a team environment
Now Benefits:
- competitive pay and annual incentive potential
- 401(k) Retirement Savings & Investment Plan with Company Match
- paid time off including holidays
- generous employee discounts on products and services
We could also mention eligibility link but that's maybe boilerplate; but it's part of benefits info. The instruction: remove duplicated lines, but eligibility link is not duplicated. It's a link to benefits. Might be considered navigation? It's a link to benefits page. Might be okay to keep? It's not boilerplate like EEO. It's a specific link. Could keep as part of benefits: "For eligibility and a full list of our benefit offerings please visit https://jobs.suburbanpropane.com/benefits/". That's substantive. We'll include as a
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 might be okay to include other headings but they'd be non-standard. Safer to stick to those headings and put company info maybe in About the role or maybe omit? The instruction: "Prefer a few substantive sections over many thin ones." So we could combine company description into About the role.
Thus About the role: include the introductory paragraph plus company overview.
Responsibilities: bullet list.
Requirements: experience and education.
Qualifications: knowledge of fuel distribution, computer skills.
Skills: multi-task, prioritize.
Benefits: list.
Pay: competitive pay and annual incentive potential.
Schedule: part-time approx 29 hours per week.
Now format.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
...
Responsibilities
- ... ...
maybe. Now Pay: - competitive pay and annual incentive potential But we already listed that under benefits. Actually benefits included competitive pay and annual incentive potential. So we might not need separate Pay section if it's already in benefits. However the instruction: include a section ONLY when the posting has real, specific content for it. Pay is mentioned as part of benefits. Could still have Pay section with that content. But to avoid duplication, we could put pay in Benefits section and not have separate Pay. However the instruction says "Prefer a few substantive sections over many thin ones." So maybe combine Pay into Benefits. But they listed Pay as a possible heading. If we omit Pay, we might