Property Coordinator

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the job description. Key content: - Job description: coordinate property management functions, off-site shipping approvals, review contracts, assign property categorizations, maintain property records, interface with federal agencies, point of contact for property loans/exchanges, ensure audit trails. - Essential Job Functions and Responsibilities: list many duties. - Required Level 3/4: education, experience, driver's license, experience with Asset Suite, Excel, etc. - Preferred Experience: regulatory requirements, leadership experience, customer service mindset. - Ideal Candidate: certifications, experience with inventories, government property management, procurement, subcontracts. - Physical Requirements: standing, walking, etc. - Working Conditions: office and field environment, exposure, equipment, noise, etc. - Job Information: pay range for Level 3 ($26.36 - $43.48) / Level 4 ($30.84 - $50.87). So we have Pay info. - About Us Benefits and Relocation: list benefits: Medical, Dental, Vision, Flexible Spending Accounts; 401(k) with employer contribution; Paid time off; Employee Education Program; Comprehensive Relocation Package; Benefit eligibility subject to factors; BEA will not sponsor H1-B visas. - About Us: description of INL mission, vision, etc. Could be "About the role" maybe? Actually "About Us" is about the organization. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - About the role: maybe a brief summary of the role (first paragraph). Could be "Job Description At Idaho National Laboratory, you'll coordinate property management functions..." That's about the role. - Responsibilities: list of essential job functions and responsibilities. - Requirements: required qualifications (education, experience, driver's license, software experience). Could be "Required Level 3/4..." etc. - Qualifications: maybe preferred qualifications? Or we could combine Requirements and Qualifications. But we need to decide. - Skills: maybe specific skills like Excel, Asset Suite, regulatory knowledge, leadership, customer service. - Benefits: benefits and relocation info. - Pay: pay range. - Schedule: not explicitly mentioned; maybe working conditions mention may work >8 hours/day, but schedule not given. Should we include Schedule? Only if posting actually states them. There's no explicit schedule like "full-time", "shift work". It mentions may work alone and for more than 8 hours/day. That's somewhat schedule info but not explicit. Probably we should not include Schedule unless clear. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Pay is stated. Benefits is stated. Schedule is not explicitly stated; we have working conditions but not schedule. So omit Schedule. We need to preserve all substantive information, not invent or summarize away detail. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove EEO statement, Selective Service Requirements, Equal Employment Opportunity, Reasonable Accommodation, Other Information about applying, etc. Also remove "About Us Benefits and Relocation" heading? We'll keep benefits content but not the heading "About Us Benefits and Relocation". We'll put benefits under

  Benefits

  . We need to keep all substantive info: job description, responsibilities, requirements, qualifications, skills, benefits, pay. We need to avoid repeating job title as heading. Not include Job ID. We need to output only HTML fragment. Let's structure:

  About the role

  At Idaho National Laboratory, you'll coordinate property management functions including off-site shipping approvals for radioactive and hazardous materials, review contracts for high-risk property, assign correct property categorizations including export regulation and proliferation-sensitive determinations, and maintain property records in compliance with company policies. You'll interface with federal agencies and external customers, act as the point of contact for property loans and exchanges and ensure that documented audit trails are available for all property transactions processed.

  Responsibilities

  • Coordinate and perform various property management functions, including property acknowledgments.
  • Complete approval reviews of INL off-site shipping documents, including radioactive and hazardous materials, to ensure property management procedures are followed.
  • Initiate property category determinations, including fieldwork across the site.
  • Represent the department across INL, including interfacing with federal agencies and other external customers.
  • Pull reports from property management systems and review contracts to check for high-risk property to appropriately categorize materials and equipment received into INL.
  • Review contract property clauses (focusing on both federal and nonfederal WFO, federal agreements, CRADAs, and subcontract clauses) for determination of both LTI and disposal.
  • Properly identify incoming (or internally fabricated) property, materials, and equipment to assign the correct property categorization. This includes reviewing for high-risk category determinations, proliferation-sensitive and export regulation guidelines, hazardous property determinations, and reviewing and applying federal, state, and international regulations and directives pertaining to property management.
  • Document property category analysis determinations and present recommendations to Property Services management.
  • Categorize and tag property received into INL and DOE-ID according to required guidelines (e.g., CFR, FSC, ECCN, Asset Type, Asset Flag, Real vs. Personal Property, ME vs. MEC).
  • Create and maintain property records and execute specific property management transactions, processes, and procedures to ensure compliance with company policies and plans for managing company and government assets. Update records in databases as necessary.
  • Provide support to ensure continual accountability for government-owned property.
  • Implement and maintain the INL property system procedures, processes, and tools as directed. May make recommendations for improvements and/or modifications.
  • Act as the point of contact for property loans/borrows/exchange sales/warranty replacements/abandonments. Prepare and transmit internal and external correspondence for the document completion of property and logistics-related CDRLs (contract deliverables).
  • Coordinate with others across the INL and interface with external customers on specific property transactions and processes. Provide property services customer service.
  • Ensure proliferation reviews occur as required, for off-site shipments, and ensure a documented audit trail is available for all property transactions processed.
  • May research issues and provide written recommendations to management on solutions.

  Requirements

  • High school diploma or equivalent and 4 years of experience (Level 3) OR high school diploma or equivalent and 6 years of experience (Level 4).
  • Valid driver's license.
  • Experience utilizing enterprise software systems such as Asset Suite.
  • Experience using Microsoft Excel, specifically sorting, manipulating, and notating data using tools such as conditional formatting.

  Qualifications

  • Preferred experience with various regulatory requirements, such as standards, laws, regulations, and policies at a state or federal level.
  • Leadership experience (even in a volunteer capacity) within safety teams, community service, etc.
  • Customer service mindset.
  • Ideal candidate will possess certifications such as Certified Professional Property Specialist, CPPA Administrator, CCPM Manager, CFFS Fleet Specialist, etc.
  • Experience with inventories, government property management, procurement, subcontracts.

  Skills

  • Knowledge of federal, state, and international regulations pertaining to property management.
  • Proficiency with Asset Suite and Microsoft Excel (sorting, manipulating, conditional formatting).
  • Ability to conduct fieldwork and property categorization.
  • Strong communication and customer service skills.
  • Organizational and record‑keeping abilities.
  But we need to ensure we don't invent details not in posting. The Skills section we created may be inferring. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we cannot create a Skills section that adds info not explicitly stated. However we can list skills that are explicitly mentioned: experience with Asset Suite, Excel, regulatory requirements, leadership, customer service, certifications, inventories, government property management, procurement, subcontracts. Those are more qualifications/experience. Perhaps better to combine Qualifications and Skills into one section "Qualifications" that includes both required and preferred. But we already have Requirements (required) and Qualifications (preferred). The instruction says use headings like Requirements, Qualifications, Skills. We can have Requirements (mandatory), Qualifications (preferred), Skills (specific abilities). But we must not invent. Let's see what is explicitly stated as skills: "Experience utilizing enterprise software systems such as Asset Suite." "Experience using Microsoft Excel, specifically sorting, manipulating, and notating data using tools such as conditional formatting." "Preferred Experience with various regulatory requirements, such as standards, laws, regulations, and policies at a state or federal level." "Leadership experience (even in a volunteer capacity) within safety teams, community service, etc." "Customer service mindset." "The Ideal Candidate Will Possess Certified Professional Property Specialist, CPPA Administrator, CCPM Manager, CFFS Fleet Specialist, etc." "Experience with inventories, government property management, procurement, subcontracts." These are more like qualifications/experience, not necessarily skills. But we could treat them as qualifications. The Skills section could be left out if we don't have explicit skill statements beyond those. However we have "Experience utilizing enterprise software systems such as Asset Suite." That's a skill/experience. "Experience using Microsoft Excel..." also skill. Could be placed under Skills. But we need to avoid inventing. It's okay to list those as skills because they are explicitly mentioned as experience/skills. So we can have Skills section with those items. But we also have "Experience with inventories, government property management, procurement, subcontracts." That's also experience. Thus we could have: - Requirements: education, experience, driver's license. - Qualifications: preferred experience with regulatory requirements, leadership experience, customer service mindset, certifications, experience with inventories, government property management, procurement, subcontracts. - Skills: experience with Asset Suite, Microsoft Excel (sorting, manipulating, conditional formatting). Possibly also knowledge of federal, state, international regulations (but that's covered under preferred experience). Might be redundant. We need to avoid duplication. Let's think: The posting includes both required and preferred. We can capture required under Requirements, and preferred under Qualifications. Skills could be a subset of Qualifications but we can still separate if we have explicit skill statements. However to avoid duplication, we could put the software experience under Qualifications as well. But the instruction says we can have Skills section; it's not mandatory. We could omit Skills and put those under Qualifications. But we have already a Qualifications section with preferred items; we can add the software experience there. That would avoid duplication. Thus:

  Requirements

  • High school diploma or equivalent and 4 years of experience (Level 3) OR high school diploma or equivalent and 6 years of experience (Level 4).
  • Valid driver's license.
  • Experience utilizing enterprise software systems such as Asset Suite.
  • Experience using Microsoft Excel, specifically sorting, manipulating, and notating data using tools such as conditional formatting.

  Qualifications

  • Preferred experience with various regulatory requirements, such as standards, laws,