Valet Driver - Cleveland Clinic/Holiday Inn
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a 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.
We need to decide which sections to include based on content.
We have:
- About Towne (company description) – could be "About the role"? Actually "About the role" is generic; but we have company description. Could use "About the role" heading for description of role? The posting includes "Summary The Guest Service Associate is responsible for providing exceptional hospitality services..." That's a summary of role. Could put under "About the role". Or we could have "Responsibilities" for duties.
We have "Compensation: Towne Park is committed to offering competitive, fair, and commensurate compensation. Actual compensation will be based on a candidate’s job-related skills, experience, education or training, and location. The hourly base pay range for this position is $15-$17 per hour DAILY CASH TIPS."
That's pay info. So we can include a Pay section with that content.
We have "Work Schedule: The work schedule for this position is: 10:30PM - 7:00AM - MUST BE AVAILABLE TO WORK WEEKENDS, AS NEEDED". So Schedule section.
We have "Benefits: Employees are eligible to enroll in accident insurance, critical illness insurance, hospital indemnity insurance, and telemedicine benefits. Employees are also able to enroll in the company’s 401k retirement savings plan. Eligibility requirements depend on your job classification, length of employment and number of hours worked. Benefits are subject to change and may be subject to a specific plan or program terms. Seasonal and temporary roles are not eligible for benefits outlined above."
Thus Benefits section.
We have "Summary" which is a prose description of role. Could be under "About the role" or "Responsibilities". The "Essential Functions" with descriptive statements and percentages is essentially responsibilities/duties. Could be under "Responsibilities". The "Qualifications" section includes Education, Licensure, Work Experience, Knowledge, Skills. Could be under "Qualifications" and maybe "Skills". The instruction says we can use headings like Qualifications, Skills. We could combine Qualifications and Skills into one Qualifications section, but better to separate if content distinct.
We have "SCOPE Authority To Act", "Budget Responsibility", "WORKING CONDITIONS & PHYSICAL DEMANDS", "Physical Requirements", "Lifting Requirements", "Working Environment", "Travel". Those could be under "Working Conditions" or similar but not in the list of allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we can use those headings, but not required to use only those? It says use those as examples. Probably we should stick to those headings for simplicity. So we need to map content to those headings.
We have:
- About the role: could include company description and summary of role.
- Responsibilities: essential functions with percentages.
- Requirements: maybe qualifications (education, licensure, experience). Could be "Requirements".
- Qualifications: maybe education, licensure, experience.
- Skills: knowledge, skills, abilities.
But we have overlapping. To avoid thin sections, we can combine.
We need to output only HTML fragment, no extra markup.
We must preserve all substantive information. So we need to include all details from the posting, but we can reorganize under headings.
We must not repeat job title as heading. Not present.
We must not include boilerplate like "Click here for important notices", privacy policy, etc. Remove those.
We must not include duplicated lines.
We must not include application instructions.
We need to include Pay, Schedule, Benefits sections as they have specific content.
We need to include About the role (company description + summary). Responsibilities (essential functions). Requirements/Qualifications/Skills (maybe combine into Qualifications and Skills). Let's decide:
- About the role: company description (Towne is an exceptional arrival...), plus maybe the summary paragraph.
- Responsibilities: essential functions with percentages (the descriptive statements). Could be a list.
- Requirements: maybe education, licensure, work experience (the qualifications). Could be a list.
- Skills: knowledge, skills, abilities (the Knowledge and Skills bullet points). Could be a list.
- Pay: compensation details.
- Schedule: work schedule.
- Benefits: benefits details.
We must avoid filler like "commensurate with experience" but we can include the actual statement about compensation being competitive, fair, and commensurate compensation. That's not filler; it's substantive. However the instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). That seems to refer to headings with only filler text. If we have a Pay section, we have actual numbers, so fine.
We need to ensure we don't create sections with only placeholder text. All sections will have real content.
Now we need to format.
Use for each section heading.
Inside sections, use
for prose,
- for lists.
We need to preserve all substantive information. Let's extract.
Company description paragraph:
"About Towne Towne is an exceptional arrival through departure experience company. With its best-in-class parking and hospitality solutions and its fully integrated technology platform, we deliver seamless parking and mobility experiences in the places where people live, learn, work, play, rejuvenate, and recover. Towne’s 14,000 team members create smiles by delivering exceptional experiences for the millions of people we proudly serve each year. For nearly 40 years, Towne has been committed to providing the best experience, delivered by the best team, powered by innovative technology, enhancing lives and communities. For more information, visit www.towne.com and follow us on LinkedIn."
We should remove the "For more information, visit www.towne.com and follow us on LinkedIn." as that's like a link? It's not boilerplate but maybe considered navigation? It's not explicitly prohibited, but it's like a call to action. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those, but it's a promotional link. Might be okay to keep? It's not essential job info. Could be considered navigation? Safer to remove it. We'll keep the core description but drop the "For more information, visit www.towne.com and follow us on LinkedIn." Also drop "Click here for important notices that may be applicable to you. For more information about our privacy policy, please click here." That's definitely boilerplate.
Now the Summary paragraph:
"Summary The Guest Service Associate is responsible for providing exceptional hospitality services to guests in an attentive, friendly and efficient manner. The Guest Service Associate is responsible for parking and retrieving guest vehicles in a prompt yet safe manner and assisting guests with luggage, including delivery and pick up of guest luggage (where applicable) during arrival and departure."
We can keep that as prose.
Now Essential Functions with percentages:
We have a list of descriptive statements with percentages. We need to preserve all. Let's extract each bullet:
- Maintains pleasant, friendly and professional demeanor with all guests, co-workers, and clients. Acknowledges and greets guests within five feet with a professional and friendly demeanor. Uses guest last names during interactions. - 25%
- Uses salutation of the day and welcomes guests to the location. Practices proper Towne Park phone etiquette. Posts up in designated areas when not completing tasks. - 10%
- Parks and retrieves vehicles while driving slowly and cautiously. Assists guests with bell services and luggage storage as needed. Opens all vehicle and hotel doors for guests. - 20%
- Assists guests with directions, taxis, reservations and other inquiries. Provides guests with information about outlets, meeting rooms and/or amenities of the facility as well as main attractions in the area. Delivers messages, items and/or guest amenities as requested. Shuttles guests to appropriate places that are approved by the location. - 10%
- Explains parking rates and retrieval procedures to guests upon arrival. Issues claim checks only after receiving vehicle keys and collects claim checks from all guests prior to issuing keys. Consistently completes and maintains all ticket information including key tag, guest folio, location of vehicle, damage survey and claim check receipt from all vehicles taken into the valet system. Consistently completes location on all key tags after parking vehicle. Calculates and collects revenue for vehicles when needed. - 35%
- The total amount of time for all functions of the job - 100%
We could present as a list with each item including the percentage.
Now Qualifications section:
Education: High school diploma or general education degree (GED) Required
Licensure, Certification, Etc. Must hold a valid driver’s license for the state you are applying to work, or within a commutable distance from the state you are applying to work (as applicable)
Work Experience One (1) month related experience and/or training; OR equivalent combination of education and experience
Knowledge Knowledge of principles and processes for providing customer and personal services.
Skills Ability to read and write standard English languageAbility to read and comprehend simple instructions, short correspondence and memosAbility to write simple correspondenceAbility to effectively present information in one-on-one and small group situations to guests, clients and other employees of the organizationAbility to add and subtract three digit numbers and to multiply and divide with 10’s and 100’s; ability to perform these operations using units of American moneyAbility to understand 24 hour and military time systemsAbility to understand rates applicable to time passedAbility to operate a manual transmission is highly desirablePerform parallel parking
We need to split Skills into separate items for readability.
Now SCOPE Authority To Act etc. Those could be considered "Requirements" maybe? But we already have Requirements for education/experience. The SCOPE etc are more about job level. Could be omitted? The instruction says preserve ALL substantive information. So we need to include them somewhere. Could be under "Requirements" as additional notes. But we have limited headings. Could add a "Requirements" section that includes education, licensure, experience, SCOPE, Budget Responsibility, Working Conditions, Physical Demands, etc. However that may become a long list but okay.
But we also have separate "Skills" heading allowed. We could put knowledge and skills under Skills.
We need to decide structure:
Option: Use sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule.
Under Requirements we put education, licensure, work experience, knowledge, SCOPE, Budget Responsibility, Working Conditions & Physical Demands, etc. But that may mix knowledge with
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a 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. We need to decide which sections to include based on content. We have: - About Towne (company description) – could be "About the role"? Actually "About the role" is generic; but we have company description. Could use "About the role" heading for description of role? The posting includes "Summary The Guest Service Associate is responsible for providing exceptional hospitality services..." That's a summary of role. Could put under "About the role". Or we could have "Responsibilities" for duties. We have "Compensation: Towne Park is committed to offering competitive, fair, and commensurate compensation. Actual compensation will be based on a candidate’s job-related skills, experience, education or training, and location. The hourly base pay range for this position is $15-$17 per hour DAILY CASH TIPS." That's pay info. So we can include a Pay section with that content. We have "Work Schedule: The work schedule for this position is: 10:30PM - 7:00AM - MUST BE AVAILABLE TO WORK WEEKENDS, AS NEEDED". So Schedule section. We have "Benefits: Employees are eligible to enroll in accident insurance, critical illness insurance, hospital indemnity insurance, and telemedicine benefits. Employees are also able to enroll in the company’s 401k retirement savings plan. Eligibility requirements depend on your job classification, length of employment and number of hours worked. Benefits are subject to change and may be subject to a specific plan or program terms. Seasonal and temporary roles are not eligible for benefits outlined above." Thus Benefits section. We have "Summary" which is a prose description of role. Could be under "About the role" or "Responsibilities". The "Essential Functions" with descriptive statements and percentages is essentially responsibilities/duties. Could be under "Responsibilities". The "Qualifications" section includes Education, Licensure, Work Experience, Knowledge, Skills. Could be under "Qualifications" and maybe "Skills". The instruction says we can use headings like Qualifications, Skills. We could combine Qualifications and Skills into one Qualifications section, but better to separate if content distinct. We have "SCOPE Authority To Act", "Budget Responsibility", "WORKING CONDITIONS & PHYSICAL DEMANDS", "Physical Requirements", "Lifting Requirements", "Working Environment", "Travel". Those could be under "Working Conditions" or similar but not in the list of allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we can use those headings, but not required to use only those? It says use those as examples. Probably we should stick to those headings for simplicity. So we need to map content to those headings.
We have:
- About the role: could include company description and summary of role.
- Responsibilities: essential functions with percentages.
- Requirements: maybe qualifications (education, licensure, experience). Could be "Requirements".
- Qualifications: maybe education, licensure, experience.
- Skills: knowledge, skills, abilities.
But we have overlapping. To avoid thin sections, we can combine.
We need to output only HTML fragment, no extra markup.
We must preserve all substantive information. So we need to include all details from the posting, but we can reorganize under headings.
We must not repeat job title as heading. Not present.
We must not include boilerplate like "Click here for important notices", privacy policy, etc. Remove those.
We must not include duplicated lines.
We must not include application instructions.
We need to include Pay, Schedule, Benefits sections as they have specific content.
We need to include About the role (company description + summary). Responsibilities (essential functions). Requirements/Qualifications/Skills (maybe combine into Qualifications and Skills). Let's decide:
- About the role: company description (Towne is an exceptional arrival...), plus maybe the summary paragraph.
- Responsibilities: essential functions with percentages (the descriptive statements). Could be a list.
- Requirements: maybe education, licensure, work experience (the qualifications). Could be a list.
- Skills: knowledge, skills, abilities (the Knowledge and Skills bullet points). Could be a list.
- Pay: compensation details.
- Schedule: work schedule.
- Benefits: benefits details.
We must avoid filler like "commensurate with experience" but we can include the actual statement about compensation being competitive, fair, and commensurate compensation. That's not filler; it's substantive. However the instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). That seems to refer to headings with only filler text. If we have a Pay section, we have actual numbers, so fine.
We need to ensure we don't create sections with only placeholder text. All sections will have real content.
Now we need to format.
Use for each section heading.
Inside sections, use
for prose,
- for lists. We need to preserve all substantive information. Let's extract. Company description paragraph: "About Towne Towne is an exceptional arrival through departure experience company. With its best-in-class parking and hospitality solutions and its fully integrated technology platform, we deliver seamless parking and mobility experiences in the places where people live, learn, work, play, rejuvenate, and recover. Towne’s 14,000 team members create smiles by delivering exceptional experiences for the millions of people we proudly serve each year. For nearly 40 years, Towne has been committed to providing the best experience, delivered by the best team, powered by innovative technology, enhancing lives and communities. For more information, visit www.towne.com and follow us on LinkedIn." We should remove the "For more information, visit www.towne.com and follow us on LinkedIn." as that's like a link? It's not boilerplate but maybe considered navigation? It's not explicitly prohibited, but it's like a call to action. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those, but it's a promotional link. Might be okay to keep? It's not essential job info. Could be considered navigation? Safer to remove it. We'll keep the core description but drop the "For more information, visit www.towne.com and follow us on LinkedIn." Also drop "Click here for important notices that may be applicable to you. For more information about our privacy policy, please click here." That's definitely boilerplate. Now the Summary paragraph: "Summary The Guest Service Associate is responsible for providing exceptional hospitality services to guests in an attentive, friendly and efficient manner. The Guest Service Associate is responsible for parking and retrieving guest vehicles in a prompt yet safe manner and assisting guests with luggage, including delivery and pick up of guest luggage (where applicable) during arrival and departure." We can keep that as prose. Now Essential Functions with percentages: We have a list of descriptive statements with percentages. We need to preserve all. Let's extract each bullet: - Maintains pleasant, friendly and professional demeanor with all guests, co-workers, and clients. Acknowledges and greets guests within five feet with a professional and friendly demeanor. Uses guest last names during interactions. - 25% - Uses salutation of the day and welcomes guests to the location. Practices proper Towne Park phone etiquette. Posts up in designated areas when not completing tasks. - 10% - Parks and retrieves vehicles while driving slowly and cautiously. Assists guests with bell services and luggage storage as needed. Opens all vehicle and hotel doors for guests. - 20% - Assists guests with directions, taxis, reservations and other inquiries. Provides guests with information about outlets, meeting rooms and/or amenities of the facility as well as main attractions in the area. Delivers messages, items and/or guest amenities as requested. Shuttles guests to appropriate places that are approved by the location. - 10% - Explains parking rates and retrieval procedures to guests upon arrival. Issues claim checks only after receiving vehicle keys and collects claim checks from all guests prior to issuing keys. Consistently completes and maintains all ticket information including key tag, guest folio, location of vehicle, damage survey and claim check receipt from all vehicles taken into the valet system. Consistently completes location on all key tags after parking vehicle. Calculates and collects revenue for vehicles when needed. - 35% - The total amount of time for all functions of the job - 100% We could present as a list with each item including the percentage. Now Qualifications section: Education: High school diploma or general education degree (GED) Required Licensure, Certification, Etc. Must hold a valid driver’s license for the state you are applying to work, or within a commutable distance from the state you are applying to work (as applicable) Work Experience One (1) month related experience and/or training; OR equivalent combination of education and experience Knowledge Knowledge of principles and processes for providing customer and personal services. Skills Ability to read and write standard English languageAbility to read and comprehend simple instructions, short correspondence and memosAbility to write simple correspondenceAbility to effectively present information in one-on-one and small group situations to guests, clients and other employees of the organizationAbility to add and subtract three digit numbers and to multiply and divide with 10’s and 100’s; ability to perform these operations using units of American moneyAbility to understand 24 hour and military time systemsAbility to understand rates applicable to time passedAbility to operate a manual transmission is highly desirablePerform parallel parking We need to split Skills into separate items for readability. Now SCOPE Authority To Act etc. Those could be considered "Requirements" maybe? But we already have Requirements for education/experience. The SCOPE etc are more about job level. Could be omitted? The instruction says preserve ALL substantive information. So we need to include them somewhere. Could be under "Requirements" as additional notes. But we have limited headings. Could add a "Requirements" section that includes education, licensure, experience, SCOPE, Budget Responsibility, Working Conditions, Physical Demands, etc. However that may become a long list but okay. But we also have separate "Skills" heading allowed. We could put knowledge and skills under Skills. We need to decide structure: Option: Use sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Under Requirements we put education, licensure, work experience, knowledge, SCOPE, Budget Responsibility, Working Conditions & Physical Demands, etc. But that may mix knowledge with