Manager, Turfgrass and Athletic Grounds
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for any list of duties/requirements/benefits, and
for prose
3. Do NOT repeat the job title as a heading (the page already shows it)
4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it
5. Preserve ALL substantive information; do NOT invent or summarize away detail
6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
6. 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
7. Prefer a few substantive sections over many thin ones
8. Output ONLY the HTML fragment — no /, no markdown code fences
Let me analyze the job posting content:
- Position Information: Posting Number, Job Title, Position Number, FTE, FLSA, Position Type, Union, Pay Grade Level, Pay Grade Range, Status, Department, Contact info, Physical Demands, Campus Location, Grant Funded, Extension Contingency Notes
- Job Description Summary: About URI (description of university)
- Position Summary: Overview of role
- Duties and Responsibilities: Key Duties And Responsibilities (long list), Other Duties And Responsibilities (another list)
- Licenses, Tools, And Equipment: List of requirements
- Qualifications: Required Qualifications (list), Preferred Qualifications (list)
- Environmental Conditions: Description
- Posting Date, Closing Date
- Special Instructions to Applicants: Application instructions (should be removed per rules)
- Quicklink for Posting: URL (should be removed)
I need to create sections only for substantive content. Let me map:
1. About the role / Position Summary - there's a Position Summary section with prose
2. Responsibilities - there are Key Duties and Other Duties (both lists)
3. Requirements / Qualifications - Required Qualifications and Preferred Qualifications (both lists)
4. Licenses, Tools, and Equipment - list
5. Environmental Conditions - prose
6. Pay - there is Pay Grade Range: Salary Hiring Range: $90,000 - $100,000. That's specific, so include Pay section.
7. Schedule - there is Status: Calendar Year, Full-time, Permanent. That's schedule info, include Schedule section.
8. Benefits - not explicitly mentioned, but there is Union info, maybe not. The posting doesn't list benefits. So no Benefits section.
9. About the organization - there's "About URI" section, could be "About the Organization" or "About the University". The rules mention "About the role" but not "About the organization". However, the example headings include "About the role". The posting has "About URI" which is about the university. I could include an "About the University" section with that prose.
But the rules: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says e.g., so we can have other headings. But we should only include sections with real content.
Let's decide on sections:
- About the University (from "About URI")
- Position Summary (from "Position Summary")
- Responsibilities (combine Key Duties and Other Duties)
- Licenses, Tools, and Equipment
- Qualifications (Required and Preferred)
- Environmental Conditions
- Pay (from Pay Grade Range)
- Schedule (from Status: Calendar Year, Full-time, Permanent)
Also, there is metadata like Posting Number, Position Number, FTE, FLSA, Union, Pay Grade Level, Department, Campus Location, Grant Funded. These are minor metadata. The rules: "fold minor metadata into a short
or drop it." I think we can include a brief paragraph at the top with key metadata: Posting Number, Position Number, FTE, FLSA, Union, Pay Grade, Department, Campus Location, Grant Funded. But not as headings.
Also, the posting has "Contact(s)" with note about applying online. That's application instructions, should be removed.
"Physical Demands" is mentioned but no details? It says "Physical Demands" then "Campus Location Kingston". Might be a heading with no content. Probably drop.
"Extension Contingency Notes" empty.
"Posting Date" and "Closing Date" could be included in metadata paragraph.
"Special Instructions to Applicants" and "Quicklink for Posting" are application instructions, remove.
Now, structure:
Start with a
for metadata: "Posting Number: SF02239 | Position Number: 108520 | FTE: 1.00 | FLSA: Exempt | Position Type: Professional Staff | Union: PSA/NEA - Professional Staff Assoc | Pay Grade: Level 12 | Salary Hiring Range: $90,000 - $100,000 | Status: Calendar Year, Full-time, Permanent | Department: Facilities Operations | Campus Location: Kingston | Grant Funded: No"
But the Pay and Schedule will be separate sections, so maybe not duplicate. However, the metadata paragraph can include the basics, and then Pay and Schedule sections can have more detail. But the Pay section will have the salary range. The Schedule section will have the status. It's okay to have both.
Better to include metadata in a paragraph, then sections.
Now, write HTML.
I'll create:
Posting Number: SF02239 | Position Number: 108520 | FTE: 1.00 | FLSA: Exempt | Position Type: Professional Staff | Union: PSA/NEA - Professional Staff Assoc | Pay Grade: Level 12 | Department: Facilities Operations | Campus Location: Kingston | Grant Funded: No | Posting Date: 10/19/2026 | Closing Date: 11/01/2026
Then sections:
About the University
...text from About URI...
Position Summary
...text from Position Summary...
Responsibilities
- ... each duty from Key Duties and Other Duties ...
But there are two lists: Key Duties And Responsibilities and Other Duties And Responsibilities. Could combine into one list, or separate with subheadings? The rules say use - for any list of duties. Could keep as one list, but maybe separate with a note? The rules don't forbid subheadings, but we only have
for section headings. Could use ? Not specified. Better to combine into one list, but preserve all items. I'll combine all bullet points into a single with all li items.
Similarly for Qualifications: Required and Preferred. Could make two sublists under Qualifications heading, but we can't use subheadings. Could do:
Qualifications
Required Qualifications:
...required items...
Preferred Qualifications:
...preferred items...
That's acceptable.
Licenses, Tools, and Equipment: list.
Environmental Conditions: prose.
Pay: include salary range.
Schedule: include status.
Now, ensure no filler. All content is substantive.
Let's extract text exactly.
From posting:
About URI: "The University of Rhode Island enrolls approximately 17,000 students across its graduate and undergraduate programs and is the State’s flagship public research university, as well as the land grant and sea grant university, for the state of Rhode Island. The main campus is located in the historic village of Kingston, and the Bay Campus is located in Narragansett. Both campuses are near major beaches in a beautiful coastal community. URI is just 30 minutes from Providence, RI and within easy reach of Newport, Boston, and New York City."
Position Summary: "Manage the daily operations of Athletics Lands and Ground workers. Oversee the University’s turf areas and other sports field surfaces, including campus landscapes and athletic/recreation fields. Design and execute maintenance plans to provide aesthetic and functional turf using best management practices. Communicate and coordinate varsity sports fields and recreation fields use with the Department of Athletics, Department of Recreation, and Special Events Staff. Develop maintenance operating standards and specifications for commercial equipment, landscape maintenance, turf maintenance, construction, and winter operations. Manage and verify hourly time entry and related records for department personnel."
Key Duties And Responsibilities (list):
- Develop and implement best management practices to achieve the highest possible standard for the University’s recreational and intercollegiate sports fields, including natural grass and synthetic turf surfaces in addition to other exterior sport facility surfaces.
- Collaborate with and make recommendations to University Facilities Operations and Athletics Departments to develop a systematic approach to turfgrass management with a goal of developing exceptional quality playing surfaces for the University’s student athletes, visitors, and external users.
- Supervise operations and assigned workers in the division of Athletics Grounds.
- Act as secondary supervisor for the Campus Grounds division operations and assigned workers.
- Manage, inspect, and document construction, renovation, and deferred maintenance projects.
- Manage construction and maintenance contracts for Facilities Operations and provide oversight for landscape projects for other University departments, including Campus Planning and Design and the office of Capital Program Design and Delivery.
- Manage the summer use of athletic and recreational sports fields and coordinate with external customers to optimize revenue opportunities and showcase campus facilities.
- Write specifications to procure equipment and materials.
- Develop written project specifications.
- Coordinate with the Procurement department for ordering of equipment, materials, and other required services.
- Directly supervise one small engine mechanic and oversee maintenance of all Turf and Landscape Equipment within Athletics Lands and Grounds.
- Assist with Campus Grounds Turf and Landscape Equipment maintenance when needed.
- Develop preventive maintenance schedules for vehicles and equipment.
- Coordinate with the Automotive department for repairs and maintenance to department fleet vehicles.
- Exercise knowledge of function and ability to operate and perform adjustments and maintenance on: reel mower cutting units, commercial sprayers, tractors, aerifiers, topdressers, fertilizer and seed application equipment, field painting equipment including robotic autonomous marking equipment, and paint removal equipment.
- Operate, maintain, and repair irrigation systems for sports fields and landscape areas.
- Provide oversight and recordkeeping for the application of turf chemicals and pesticides.
- Provide oversight for accurate field layout and installation, painting sports fields lines, logos, and other markings.
- Provide management oversight for grounds crews working Athletic department sports events.
- Manage snow removal operations to include state employees, students, and contractors.
Other Duties And Responsibilities:
- Coordinate and collaborate with university turfgrass experts on research and outreach activities.
- Coordinate with Athletics’ Operations and Coaching staffs to provide timely setup needs for field facilities and events.
- Develop and implement projects on the University’s sports turf areas, to include field resurfacing, drainage improvements, irrigation improvements and other construction as needed.
- Establish and cultivate collaborative relationships with university faculty/staff, strategic partners, turf industry representatives, and professional turf organizations in Rhode Island and the Northeast Region.
- Evaluate and provide recommendations on products, tools, and equipment used to cultivate, maintain, and use University turf areas.
- Train employees on equipment operation, pesticide application, and other department procedures and safety protocols.
- Manage and disseminate Personal Protective Equipment to Lands & Grounds
for prose 3. Do NOT repeat the job title as a heading (the page already shows it) 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 6. 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 7. Prefer a few substantive sections over many thin ones 8. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: - Position Information: Posting Number, Job Title, Position Number, FTE, FLSA, Position Type, Union, Pay Grade Level, Pay Grade Range, Status, Department, Contact info, Physical Demands, Campus Location, Grant Funded, Extension Contingency Notes - Job Description Summary: About URI (description of university) - Position Summary: Overview of role - Duties and Responsibilities: Key Duties And Responsibilities (long list), Other Duties And Responsibilities (another list) - Licenses, Tools, And Equipment: List of requirements - Qualifications: Required Qualifications (list), Preferred Qualifications (list) - Environmental Conditions: Description - Posting Date, Closing Date - Special Instructions to Applicants: Application instructions (should be removed per rules) - Quicklink for Posting: URL (should be removed) I need to create sections only for substantive content. Let me map: 1. About the role / Position Summary - there's a Position Summary section with prose 2. Responsibilities - there are Key Duties and Other Duties (both lists) 3. Requirements / Qualifications - Required Qualifications and Preferred Qualifications (both lists) 4. Licenses, Tools, and Equipment - list 5. Environmental Conditions - prose 6. Pay - there is Pay Grade Range: Salary Hiring Range: $90,000 - $100,000. That's specific, so include Pay section. 7. Schedule - there is Status: Calendar Year, Full-time, Permanent. That's schedule info, include Schedule section. 8. Benefits - not explicitly mentioned, but there is Union info, maybe not. The posting doesn't list benefits. So no Benefits section. 9. About the organization - there's "About URI" section, could be "About the Organization" or "About the University". The rules mention "About the role" but not "About the organization". However, the example headings include "About the role". The posting has "About URI" which is about the university. I could include an "About the University" section with that prose. But the rules: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says e.g., so we can have other headings. But we should only include sections with real content. Let's decide on sections: - About the University (from "About URI") - Position Summary (from "Position Summary") - Responsibilities (combine Key Duties and Other Duties) - Licenses, Tools, and Equipment - Qualifications (Required and Preferred) - Environmental Conditions - Pay (from Pay Grade Range) - Schedule (from Status: Calendar Year, Full-time, Permanent) Also, there is metadata like Posting Number, Position Number, FTE, FLSA, Union, Pay Grade Level, Department, Campus Location, Grant Funded. These are minor metadata. The rules: "fold minor metadata into a short
or drop it." I think we can include a brief paragraph at the top with key metadata: Posting Number, Position Number, FTE, FLSA, Union, Pay Grade, Department, Campus Location, Grant Funded. But not as headings. Also, the posting has "Contact(s)" with note about applying online. That's application instructions, should be removed. "Physical Demands" is mentioned but no details? It says "Physical Demands" then "Campus Location Kingston". Might be a heading with no content. Probably drop. "Extension Contingency Notes" empty. "Posting Date" and "Closing Date" could be included in metadata paragraph. "Special Instructions to Applicants" and "Quicklink for Posting" are application instructions, remove. Now, structure: Start with a
for metadata: "Posting Number: SF02239 | Position Number: 108520 | FTE: 1.00 | FLSA: Exempt | Position Type: Professional Staff | Union: PSA/NEA - Professional Staff Assoc | Pay Grade: Level 12 | Salary Hiring Range: $90,000 - $100,000 | Status: Calendar Year, Full-time, Permanent | Department: Facilities Operations | Campus Location: Kingston | Grant Funded: No" But the Pay and Schedule will be separate sections, so maybe not duplicate. However, the metadata paragraph can include the basics, and then Pay and Schedule sections can have more detail. But the Pay section will have the salary range. The Schedule section will have the status. It's okay to have both. Better to include metadata in a paragraph, then sections. Now, write HTML. I'll create:
Posting Number: SF02239 | Position Number: 108520 | FTE: 1.00 | FLSA: Exempt | Position Type: Professional Staff | Union: PSA/NEA - Professional Staff Assoc | Pay Grade: Level 12 | Department: Facilities Operations | Campus Location: Kingston | Grant Funded: No | Posting Date: 10/19/2026 | Closing Date: 11/01/2026
Then sections:About the University
...text from About URI...
Position Summary
...text from Position Summary...
Responsibilities
- ... each duty from Key Duties and Other Duties ...
- for any list of duties. Could keep as one list, but maybe separate with a note? The rules don't forbid subheadings, but we only have
for section headings. Could use
? Not specified. Better to combine into one list, but preserve all items. I'll combine all bullet points into a single
- with all li items.
Similarly for Qualifications: Required and Preferred. Could make two sublists under Qualifications heading, but we can't use subheadings. Could do:
Qualifications
Required Qualifications:
- ...required items...
Preferred Qualifications:
- ...preferred items...