Travel Nurse RN - ICU - Intensive Care Unit - $2,063 per week

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. Let's parse the posting. Content: - Job title: ICU RN travel nurse (but we don't repeat as heading) - Location: Cleveland, Ohio (maybe part of About the role) - Specialty: ICU - Intensive Care Unit - Discipline: RN - Start Date: 11/02/2026 - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, days - Employment Type: Travel - Description: As an ICU RN, you'll provide hands-on care for critically ill patients. Intensive Care nurses must be able to assess, plan, and implement care strategies for patients who may suffer from a variety of complex health conditions, but all of whom need round-the-clock attention. - Trustaff Job ID #1677120 (metadata) - Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. - Posted job title: ICU (duplicate) - About Trustaff: description of company, benefits etc. - Benefits list: Weekly pay, Guaranteed Hours, Wellness and fitness programs, Referral bonus, Medical benefits, Dental benefits, Vision benefits, 401k with employer match, Assistance with travel, compliance, and housing, Great bonuses for completions, referring friends, and more. We need to produce sections: About the role (maybe includes description of role, location, specialty, start date, duration, hours, shift, employment type). Responsibilities: maybe the description of duties: provide hands-on care, assess, plan, implement care strategies, round-the-clock attention. Requirements/Qualifications/Skills: Not explicitly listed; maybe we can infer from description? But we must not invent. If no explicit requirements, we should not create those sections. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we should only include sections where there is actual content. We have content for About the role (description, location, start date, duration, hours, shift, employment type). We have Responsibilities (the description of duties). We have Benefits (list). We have Pay (mention of pay package based on 12 hour shifts and 36 hours per week, tax-free stipend amount to be determined). That's somewhat vague but it's specific: pay package based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. It's not a specific number but it's still content. The instruction says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here we have "tax-free stipend amount to be determined" which is TBD-like. Might be considered placeholder. However the phrase "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation)" is specific about basis. Might be okay to include Pay section with that sentence. But we need to avoid filler. The phrase "tax-free stipend amount to be determined" is TBD. Might be considered placeholder. Safer to omit Pay section if it's too vague. However we could include Pay section with the sentence we have, but it includes TBD. The instruction says never emit a heading followed by filler/placeholder text. If we include the sentence, it's not purely filler; it's some info. I'd include Pay section. Schedule: we have shift: 12 hours, days; 36 hours per week. That's schedule info. So we can include Schedule section. We should not include Requirements/Qualifications/Skills because no explicit list. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. Not include Job ID as heading; fold minor metadata into short

  or drop it. We can include Job ID in a paragraph maybe under About the role or separate minor metadata paragraph. We must remove boilerplate like cookie/navigation/legal/EEO etc. Not present. We must preserve all substantive information. Let's craft: not needed; just output HTML fragment. We'll have:

  About the role

  Trustaff is seeking a travel nurse RN ICU - Intensive Care Unit for a travel nursing job in Cleveland, Ohio. Specialty: ICU - Intensive Care Unit. Discipline: RN. Start Date: 11/02/2026. Duration: 13 weeks. 36 hours per week. Shift: 12 hours, days. Employment Type: Travel. Trustaff Job ID #1677120.

  Responsibilities

  As an ICU RN, you'll provide hands-on care for critically ill patients. Intensive Care nurses must be able to assess, plan, and implement care strategies for patients who may suffer from a variety of complex health conditions, but all of whom need round-the-clock attention.

  Benefits

  • Weekly pay
  • Guaranteed Hours
  • Wellness and fitness programs
  • Referral bonus
  • Medical benefits
  • Dental benefits
  • Vision benefits
  • 401k with employer match
  • Assistance with travel, compliance, and housing
  • Great bonuses for completions, referring friends, and more

  Pay

  Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined.

  Schedule

  Shift: 12 hours, days. 36 hours per week.

  Check if any content duplicated: we included Job ID in About the role paragraph. Good. We didn't include Requirements/Qualifications/Skills. We preserved all substantive info: location, specialty, discipline, start date, duration, hours, shift, employment type, responsibilities, benefits, pay, schedule. We omitted the duplicated lines like "Posted job title: ICU" and "About Trustaff" description? Wait we omitted the About Trustaff paragraph describing the company. That is substantive information about the company, maybe should be included? The instruction: Preserve ALL substantive information. The About Trustaff section describes the company, benefits, etc. Some of that is already captured in Benefits list, but there is also descriptive prose about Trustaff's nurse-first attitude, recruiter support, etc. That is substantive. Should we include it? Possibly under a section like "About Trustaff" but we only allowed headings from the list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction says: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should not add a heading like "About Trustaff". However we could fold that content into About the role or Benefits? The About Trustaff paragraph includes info about the company, not directly about the role. But we could incorporate some of it into About the role as extra description? The instruction: "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." It doesn't forbid adding other headings not in list, but the examples suggest those are the expected sections. Safer to stick to those headings only. However we must preserve ALL substantive information. If we omit the About Trustaff description, we lose substantive info. But maybe that is considered boilerplate? It's not cookie/navigation/legal/EEO; it's marketing copy about the agency. Might be considered substantive. The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should include it. Where to put? Could be part of About the role as a paragraph describing the employer. That seems reasonable: About the role can include info about the employer and the role. So we can add a paragraph after the role details describing Trustaff. Thus About the role paragraph will be longer: include location, specialty, etc., plus description of Trustaff. Let's craft:

  About the role

  Trustaff is seeking a travel nurse RN ICU - Intensive Care Unit for a travel nursing job in Cleveland, Ohio. Specialty: ICU - Intensive Care Unit. Discipline: RN. Start Date: 11/02/2026. Duration: 13 weeks. 36 hours per week. Shift: 12 hours, days. Employment Type: Travel. Trustaff Job ID #1677120. About Trustaff: Our nurse-first attitude has set us apart from other travel nursing agencies. When you join the Trustaff family, you’re more than just a body filling a role—you're a vibrant individual with dreams and aspirations. As one of the nation's leading travel nursing companies, your recruiter will work with you one-on-one to guide your career and help you achieve your goals. You decide when and where you want to work. Enjoy industry-leading pay, benefits, and bonuses. Experience new people and places. Grow your clinical skills and expand your experience. Travel nursing lets you take your professional career to the next level while maintaining your flexibility and freedom. At Trustaff, we put you first, so you never have to compromise your work or pay. We are proud to have one of the highest nurse retention rates in the country. Some of the other reasons people choose us include: priority access to thousands of travel nursing jobs, industry-leading pay, guaranteed weekly hours, experienced recruiters, comprehensive benefits, including medical, dental, and vision, 401k with employer match, assistance with travel, compliance, and housing, great bonuses for completions, referring friends, and more.

  That preserves the Trustaff description. Now we still have Benefits list separate; but note that the Trustaff description already mentions benefits; we still have Benefits section with list. That's okay; not duplicate exactly. Now we need to ensure we didn't include any filler like "commensurate with experience". Not present. Check Pay section: "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." Contains "tax-free stipend amount to be determined" which is TBD. Might be considered placeholder. But it's still some info. The instruction says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The phrase "tax-free stipend amount to be determined" is essentially TBD. So maybe we should omit Pay section entirely to avoid violating rule. However we still have some info about basis: based on 12 hour shifts and 36.0 hours per week (subject to confirmation). That's not filler. But the sentence includes TBD. Could we rephrase to only include the definite part? We must not invent or summarize away detail. If we drop the TBD part, we are summarizing away detail (the stipend amount). But we could keep the sentence as is; it's not purely filler; it's a mix. The rule says "never emit a heading followed by filler/