Field Clerical
Utility Lines Construction Services · United States · 1 mo ago
RemoteRemoteAdministrativePart-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Important Information for Applicants" etc? That's EEO etc. Should be removed. Also remove "We partner with the Department of Homeland Security..." etc. Also remove "Unsolicited resumes..." etc. Also remove "Compensation determination is based on market data..." maybe that's about pay but not specific numbers. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. The posting says "Pay: Competitive/Hourly". That's a statement about pay, albeit vague. It says "Competitive/Hourly". That's a statement about pay type. Should we include Pay section? It says "Competitive/Hourly". That's not a specific number but it's still pay info. The rule says: 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. "Competitive/Hourly" is somewhat vague but it's still stating pay type. Might be considered filler? It's not a specific number but it's still info. The instruction: "Prefer a few substantive sections over many thin ones." Might be better to include Pay section with that line. Benefits: posting says "We offer a competitive total rewards package inclusive of health and welfare and retirement benefits, as well as paid time off and holiday pay benefits." That's benefits info. So we can include Benefits section. Schedule: not mentioned. So no Schedule section.
We need sections: About the role (maybe from description?), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Let's parse.
Description Field Clerical Pay: Competitive/Hourly Essential Functions & Responsibilities: ... So "Description Field Clerical" maybe the role description. Could treat as About the role. Then "Essential Functions & Responsibilities:" list. Then "Minimum Qualifications:" then "Education & Experience". Then "Travel Requirements:" then "License & Certifications:" then "Pre-Screen ..." then "Physical Requirements:" then ADA etc (boilerplate). Then "We partner with..." (boilerplate). Then "Important Information for Applicants:" (EEO). Then "Employment offers are contingent..." (boilerplate). Then "Compensation determination is based on market data..." (maybe part of Pay but vague). Then "We offer a competitive total rewards package..." (Benefits). Then "Unsolicited resumes..." (boilerplate). So we need to extract substantive info.
Let's gather:
About the role: maybe "Description Field Clerical" is not descriptive. Could combine with "Supports Regional Office Manager and other management staff in daily clerical needs". That's part of responsibilities. Perhaps About the role could be a brief summary: "Field Clerical position supporting Regional Office Manager and management staff with clerical tasks." But we must not invent or summarize away detail. We can keep the sentence "Supports Regional Office Manager and other management staff in daily clerical needs" as part of About the role? But that's also a responsibility. However we can treat the first sentence as role description. It's not invented; it's present. So we can put that in About the role.
Responsibilities: list all duties after "Essential Functions & Responsibilities:" up to before "Minimum Qualifications:".
Let's extract that paragraph:
"Supports Regional Office Manager and other management staff in daily clerical needsOrganizes meetings, appointments, and travel arrangements. Sending reminders on a needed basis. Will handle inquires, work requests and at times employee personnel information. Project administration – ensures deadlines and requirements are met. Assist management with weekly production reports (i.e. Supervisor Reports). Perform secretarial duties for region management team; including but not limited to typing documents, data entry, photocopying, mailing, scanning, and faxing. Maintain office supply inventory and orders monthly basis. Answer, direct and make phone calls for the region. Receives sorts and distributes incoming Mail, Email, FedEx and Fax. Download/Upload necessary documents for proposals/bids to clients and prepare bid packages. Maintain a professional work area. (Conference room, front desk, waiting area and supply areas). Provides support and assistance to help the facility and personnel function as a team environment. Complete all other duties assigned by management."
We need to split into list items. Each sentence separated by period. We'll create
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Important Information for Applicants" etc? That's EEO etc. Should be removed. Also remove "We partner with the Department of Homeland Security..." etc. Also remove "Unsolicited resumes..." etc. Also remove "Compensation determination is based on market data..." maybe that's about pay but not specific numbers. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. The posting says "Pay: Competitive/Hourly". That's a statement about pay, albeit vague. It says "Competitive/Hourly". That's a statement about pay type. Should we include Pay section? It says "Competitive/Hourly". That's not a specific number but it's still pay info. The rule says: 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. "Competitive/Hourly" is somewhat vague but it's still stating pay type. Might be considered filler? It's not a specific number but it's still info. The instruction: "Prefer a few substantive sections over many thin ones." Might be better to include Pay section with that line. Benefits: posting says "We offer a competitive total rewards package inclusive of health and welfare and retirement benefits, as well as paid time off and holiday pay benefits." That's benefits info. So we can include Benefits section. Schedule: not mentioned. So no Schedule section.
We need sections: About the role (maybe from description?), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Let's parse.
Description Field Clerical Pay: Competitive/Hourly Essential Functions & Responsibilities: ... So "Description Field Clerical" maybe the role description. Could treat as About the role. Then "Essential Functions & Responsibilities:" list. Then "Minimum Qualifications:" then "Education & Experience". Then "Travel Requirements:" then "License & Certifications:" then "Pre-Screen ..." then "Physical Requirements:" then ADA etc (boilerplate). Then "We partner with..." (boilerplate). Then "Important Information for Applicants:" (EEO). Then "Employment offers are contingent..." (boilerplate). Then "Compensation determination is based on market data..." (maybe part of Pay but vague). Then "We offer a competitive total rewards package..." (Benefits). Then "Unsolicited resumes..." (boilerplate). So we need to extract substantive info.
Let's gather:
About the role: maybe "Description Field Clerical" is not descriptive. Could combine with "Supports Regional Office Manager and other management staff in daily clerical needs". That's part of responsibilities. Perhaps About the role could be a brief summary: "Field Clerical position supporting Regional Office Manager and management staff with clerical tasks." But we must not invent or summarize away detail. We can keep the sentence "Supports Regional Office Manager and other management staff in daily clerical needs" as part of About the role? But that's also a responsibility. However we can treat the first sentence as role description. It's not invented; it's present. So we can put that in About the role.
Responsibilities: list all duties after "Essential Functions & Responsibilities:" up to before "Minimum Qualifications:".
Let's extract that paragraph:
"Supports Regional Office Manager and other management staff in daily clerical needsOrganizes meetings, appointments, and travel arrangements. Sending reminders on a needed basis. Will handle inquires, work requests and at times employee personnel information. Project administration – ensures deadlines and requirements are met. Assist management with weekly production reports (i.e. Supervisor Reports). Perform secretarial duties for region management team; including but not limited to typing documents, data entry, photocopying, mailing, scanning, and faxing. Maintain office supply inventory and orders monthly basis. Answer, direct and make phone calls for the region. Receives sorts and distributes incoming Mail, Email, FedEx and Fax. Download/Upload necessary documents for proposals/bids to clients and prepare bid packages. Maintain a professional work area. (Conference room, front desk, waiting area and supply areas). Provides support and assistance to help the facility and personnel function as a team environment. Complete all other duties assigned by management."
We need to split into list items. Each sentence separated by period. We'll create - for each.
Requirements: maybe "Minimum Qualifications:" includes bullet-like statements. We'll treat as Requirements section.
Minimum Qualifications text:
"Must be 18 years of age or older. Excellent Adobe, Microsoft Word, Excel, PowerPoint, and Outlook skills. Knowledge of office and business practices, equipment, and procedures. Must possess good planning, analysis, and organizing skills. Able to react to change productively and capable of meeting short deadlines. Able to pay close attention to details and identify/correct mistakes. Good and consistent attendance. Ability to keep confidential information private. Able to effectively manage competing priorities."
We'll list each as
- .
Education & Experience: "High school diploma or equivalent." Could be part of Qualifications? But we have Qualifications section maybe separate. The instruction includes Qualifications as a possible heading. We could put Education & Experience under Qualifications. But we already have Requirements (maybe same as Minimum Qualifications). Actually we have both Requirements and Qualifications headings possible. We need to decide. The posting has "Minimum Qualifications:" and then "Education & Experience". Could treat Minimum Qualifications as Requirements, and Education & Experience as Qualifications. Or combine. Let's follow headings: Requirements (maybe for minimum qualifications) and Qualifications (for education/experience). We'll output both.
Skills: Could be extracted from "Excellent Adobe, Microsoft Word, Excel, PowerPoint, and Outlook skills." plus maybe "good planning, analysis, organizing skills", etc. But those are already in Requirements. Might be redundant. Better to have Skills section separate for technical skills: Adobe, MS Office suite. But we must not invent. We'll extract the explicit skills list: "Excellent Adobe, Microsoft Word, Excel, PowerPoint, and Outlook skills." Also maybe "Knowledge of office and business practices, equipment, and procedures." That's knowledge not skill. We'll put Skills section with that line.
Benefits: "We offer a competitive total rewards package inclusive of health and welfare and retirement benefits, as well as paid time off and holiday pay benefits."
Pay: "Compensation determination is based on market data, job scope and individual qualifications." plus earlier "Description Field Clerical Pay: Competitive/Hourly". So we have two statements about pay. We'll combine: "Competitive/Hourly pay. Compensation determination is based on market data, job scope and individual qualifications."
We must not create Pay section if it's just vague? It does state Competitive/Hourly and that compensation determination based on market data etc. That's still vague but it's info. We'll include.
Schedule: none.
Now we need to output HTML fragment with
headings and
or
- . Ensure we don't include boilerplate like EEO, ADA contact numbers, etc. Also remove "Pre-Screen Upon offer..." etc. Also remove "Physical Requirements:" etc. Also remove "Travel Requirements:" maybe that's substantive? It says "Must have transportation to and from the show up location. Willing to travel out of state for emergency storm work." That's substantive travel requirement. Should we include that? It's not under any heading but it's info. Could be part of Requirements or Qualifications. We'll include under Requirements maybe as separate bullet. Similarly "License & Certifications: Driver License Required." That's substantive. Also "Pre-Screen Upon offer, employees may be required to complete and pass a pre-employment drug screen, background, and/or MVR check." That's also substantive but maybe considered boilerplate? It's about pre-employment checks. Might be considered relevant. However the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Pre-screen drug test is not exactly boilerplate but could be considered standard. Might keep? It's substantive info about hiring process. But the instruction also says remove duplicated lines and application instructions. This is not application instructions but pre-employment requirements. Might be okay to keep. However we already have a lot. To be safe, we could include under Requirements or Qualifications. But we must not invent headings. We'll add bullet under Requirements for travel requirements, license, pre-screen.
Let's extract travel requirements: "Travel Requirements: Must have transportation to and from the show up location. Willing to travel out of state for emergency storm work."
License & Certifications: "Driver License Required."
Pre-Screen: "Upon offer, employees may be required to complete and pass a pre-employment drug screen, background, and/or MVR check."
Physical Requirements: lots of detail; that's substantive but maybe too detailed. Could be included under Requirements? It's about physical demands. Might be relevant. However the instruction says prefer few substantive sections over many thin ones. Including Physical Requirements would add another section maybe. Could include under Requirements as bullet list. But it's long. Might be okay.
But we need to decide what to include. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep Physical Requirements info. However we must not create a section unless there is real specific content. Physical Requirements is specific content. So we could add a section for Physical Requirements. But we only have allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Physical Requirements is not in that list. So we cannot create a heading not in list. We must fold it into one of the allowed headings. Likely under Requirements or Qualifications. We'll put under Requirements.
Similarly Travel Requirements and License & Certifications can be under Requirements.
Pre-Screen maybe also under Requirements.
Thus Requirements section will have many bullets: minimum qualifications, education & experience? Actually education & experience we might put under Qualifications. Let's split:
Requirements: Minimum Qualifications (the bullet list of skills, abilities, etc.) plus Travel Requirements, License & Certifications, Pre-Screen, Physical Requirements.
Qualifications: Education & Experience (High school diploma or equivalent). Could also include any other qualifications like "Must be 18 years of age or older" but that's already in Minimum Qualifications. We'll keep 18+ in Requirements.
Skills: Technical skills: Adobe, MS Word, Excel, PowerPoint, Outlook.
Now let's craft.
We'll produce:
About the role
Supports Regional Office Manager and other management staff in daily clerical needs.
Responsibilities
- Organizes meetings, appointments, and travel arrangements.
- Sending reminders on a needed basis.
- Will handle inquires, work requests and at times employee personnel information.
- Project administration – ensures deadlines and requirements are met.
- Assist management with weekly production reports (i.e. Supervisor Reports).
- Perform secretarial duties for region management team; including but not limited to typing documents, data entry, photocopying, mailing, scanning, and faxing.
- Maintain office supply inventory and orders monthly basis.
- Answer, direct and make phone calls for the region.
- Receives sorts and distributes incoming Mail, Email, FedEx and Fax.
- Download/Upload necessary documents for proposals/bids to clients and prepare bid packages.
headings and
or
- . Ensure we don't include boilerplate like EEO, ADA contact numbers, etc. Also remove "Pre-Screen Upon offer..." etc. Also remove "Physical Requirements:" etc. Also remove "Travel Requirements:" maybe that's substantive? It says "Must have transportation to and from the show up location. Willing to travel out of state for emergency storm work." That's substantive travel requirement. Should we include that? It's not under any heading but it's info. Could be part of Requirements or Qualifications. We'll include under Requirements maybe as separate bullet. Similarly "License & Certifications: Driver License Required." That's substantive. Also "Pre-Screen Upon offer, employees may be required to complete and pass a pre-employment drug screen, background, and/or MVR check." That's also substantive but maybe considered boilerplate? It's about pre-employment checks. Might be considered relevant. However the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Pre-screen drug test is not exactly boilerplate but could be considered standard. Might keep? It's substantive info about hiring process. But the instruction also says remove duplicated lines and application instructions. This is not application instructions but pre-employment requirements. Might be okay to keep. However we already have a lot. To be safe, we could include under Requirements or Qualifications. But we must not invent headings. We'll add bullet under Requirements for travel requirements, license, pre-screen.
Let's extract travel requirements: "Travel Requirements: Must have transportation to and from the show up location. Willing to travel out of state for emergency storm work."
License & Certifications: "Driver License Required."
Pre-Screen: "Upon offer, employees may be required to complete and pass a pre-employment drug screen, background, and/or MVR check."
Physical Requirements: lots of detail; that's substantive but maybe too detailed. Could be included under Requirements? It's about physical demands. Might be relevant. However the instruction says prefer few substantive sections over many thin ones. Including Physical Requirements would add another section maybe. Could include under Requirements as bullet list. But it's long. Might be okay.
But we need to decide what to include. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep Physical Requirements info. However we must not create a section unless there is real specific content. Physical Requirements is specific content. So we could add a section for Physical Requirements. But we only have allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Physical Requirements is not in that list. So we cannot create a heading not in list. We must fold it into one of the allowed headings. Likely under Requirements or Qualifications. We'll put under Requirements.
Similarly Travel Requirements and License & Certifications can be under Requirements.
Pre-Screen maybe also under Requirements.
Thus Requirements section will have many bullets: minimum qualifications, education & experience? Actually education & experience we might put under Qualifications. Let's split:
Requirements: Minimum Qualifications (the bullet list of skills, abilities, etc.) plus Travel Requirements, License & Certifications, Pre-Screen, Physical Requirements.
Qualifications: Education & Experience (High school diploma or equivalent). Could also include any other qualifications like "Must be 18 years of age or older" but that's already in Minimum Qualifications. We'll keep 18+ in Requirements.
Skills: Technical skills: Adobe, MS Word, Excel, PowerPoint, Outlook.
Now let's craft.
We'll produce:
About the role
Supports Regional Office Manager and other management staff in daily clerical needs.
Responsibilities
- Organizes meetings, appointments, and travel arrangements.
- Sending reminders on a needed basis.
- Will handle inquires, work requests and at times employee personnel information.
- Project administration – ensures deadlines and requirements are met.
- Assist management with weekly production reports (i.e. Supervisor Reports).
- Perform secretarial duties for region management team; including but not limited to typing documents, data entry, photocopying, mailing, scanning, and faxing.
- Maintain office supply inventory and orders monthly basis.
- Answer, direct and make phone calls for the region.
- Receives sorts and distributes incoming Mail, Email, FedEx and Fax.
- Download/Upload necessary documents for proposals/bids to clients and prepare bid packages.