Construction Payroll Admin
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Also remove "About Actalent" etc. Also remove "Application Deadline" maybe? It's not a required heading but could be considered metadata; we can fold into a short
or drop it. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a short paragraph for location, contract duration, etc. But we need to preserve all substantive information. So we need to include details: company description, role summary, responsibilities (certified payroll & union compliance, accounts payable & invoice processing, subcontractor & contract compliance, project & administrative support), qualifications (requirements), nice-to-have qualifications, employee value proposition (benefits? Actually benefits are separate), pay, schedule, workplace type, contract duration, location, etc. Also benefits list. We must not create sections with filler like "commensurate with experience". We have actual pay range and schedule. We need to decide which sections to include: About the role (summary), Responsibilities, Requirements (maybe Qualifications), Skills (maybe nice-to-have), Benefits, Pay, Schedule. Could also include "Qualifications" as separate from Requirements? The instruction says use headings for those specific labels. We can combine similar content. We must not repeat the job title as heading. So no
Construction Payroll / Office Administrator.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract substantive content:
From job description:
- A reputable electrical construction contractor company in Tukwila, WA is hiring a detail-oriented Construction Payroll / Office Administrator to support the operations team on union construction projects. This role is critical to maintaining certified payroll, subcontract compliance, and overall project documentation. This position will work closely with leadership and the current office administrator and must be capable of stepping in to cover certified payroll and compliance responsibilities when needed.
- Title - Construction Payroll / Office Administrator (we ignore as heading)
- Pay - $25/hr. - $30/hr.
- Schedule - Standard Monday - Friday Morning Shift (40 hours a week)
- Location - Tukwila, WA (100% On-site)
- Contract Duration - 12 Month Contract-to-Hire
- Summary Of Key Responsibilities (headings inside):
(Certified Payroll & Union Compliance)
Prepare and submit certified payroll in compliance with government and union requirements
File certified payroll in LCPtracker, L&I, and distribute required reports
Support union payroll processes and compliance (including EVerify coverage when needed)
Coordinate unionrelated requirements such as drug testing and screenings
(Accounts Payable & Invoice Processing)
Process accounts payable on scheduled cycles (e.g., 10th and 25th)
Review and process vendor and subcontractor invoices
Ensure required documentation is received prior to payment, including lien waivers
Load invoices into Field Materials and export to Sage (experience preferred, not required)
(Subcontractor & Contract Compliance)
Manage subcontractor paperwork, ensuring all documentation is complete and up to date:
Signed subcontracts
Certificates of Insurance (COIs)
Certified payroll submissions
Lien waivers for each invoice
Support DCMS reporting and compliance for King County and other municipalities
Track and maintain subcontractor prequalifications
(Project & Administrative Support)
File and organize project documentation and compliance records
Sort and manage shared inbox communications related to projects and compliance
Support reconciliation of company accounts (e.g., Voyager, VISA, Banner Bank, Verizon)
General office administration as needed in coordination with the team
- Qualification Requirements
2+ years of experience in an administrative role supporting construction, engineering, or field operations with a Union Contractor.
Experience assisting with certified payroll on federal projects, in addition to subcontract billings, lien waivers, and accounts payable.
Exposure to compliance on federal projects - prequalifications, verifying insurance certificates, subcontract documentation compliance.
Experience with Accounts Payable, Invoice Processing, and Subcontract Billing Documentation.
Prior experience with a union contractor or union construction environment.
Hands-on experience with certified payroll and subcontract compliance.
Understanding of government contract requirements (DCMS, lien waivers, certified payroll, insurance tracking).
- Nice-To-Have Qualifications
Experience using LCPtracker.
Experience with Sage (not required).
Familiarity with Field Materials or similar invoice management systems.
- Employee Value Proposition
Family-owned and operated company with a long-standing reputation.
Smaller company environment, where employees can have greater visibility, impact, and access to leadership.
Opportunity to be part of a specialized union electrical contractor with a strong reputation in the municipal and industrial infrastructure market.
Company culture focused on craftsmanship, quality, and long-term customer partnerships.
Work alongside experienced professionals in a company that emphasizes building lasting relationships with both employees and clients.
- Job Type & Location: This is a Contract to Hire position based out of Tukwila, WA. (we already have location and contract duration)
- Pay And Benefits: The pay range for this position is $25.00 - $30.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors. Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms. If eligible, the benefits available for this temporary role may include the following:
Medical, dental & vision
Critical Illness, Accident, and Hospital
401(k) Retirement Plan
Pre-tax and Roth post-tax contributions available
Life Insurance (Voluntary Life & AD&D for the employee and dependents)
Short and long-term disability
Health Spending Account (HSA)
Transportation benefits
Employee Assistance Program
Time Off/Leave (PTO, Vacation or Sick Leave)
- Workplace Type: This is a fully onsite position in Tukwila,WA.
- Application Deadline: This position is anticipated to close on Oct 12, 2026. (metadata, can be short paragraph or dropped)
- About Actalent etc: boilerplate to remove.
- Also remove equal opportunity employer etc.
We need to preserve all substantive info, but we can drop the "About Actalent" and legal boilerplate.
We need to format using for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which sections to include:
- About the role: we can put the introductory paragraph(s) describing the role, company, etc.
- Responsibilities: we can list the bullet points under the four subcategories. Could combine into a single with items, or we could keep subheadings inside? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid additional headings inside, but we should follow the pattern. Probably better to keep responsibilities as a - list, maybe grouping by subcategory within
- text.
- Requirements: could be the Qualification Requirements (mandatory). Could also include "Qualifications" as separate? The instruction lists both Requirements and Qualifications as possible headings. We could put mandatory qualifications under Requirements, and nice-to-have under Skills or Qualifications? Actually they have separate headings: Requirements, Qualifications, Skills. We could map:
- Requirements: mandatory qualifications (2+ years experience, etc.)
- Qualifications: maybe the nice-to-have? Or we could treat Qualifications as the same as Requirements? But we need to avoid filler. Since we have both mandatory and nice-to-have, we could put mandatory under Requirements, nice-to-have under Skills (or Qualifications). The instruction says "Prefer a few substantive sections over many thin ones." So maybe we combine Requirements and Qualifications into one section? But they ask to use those headings if content exists. We have content for both mandatory and nice-to-have. Could make Requirements = mandatory, Qualifications = nice-to-have, Skills = maybe specific software skills (LCPtracker, Sage, Field Materials). But the nice-to-have already includes those. Could treat Skills as those specific software skills.
Let's decide:
- About the role: intro paragraph.
- Responsibilities: list of duties.
- Requirements: mandatory qualifications (the bullet list under Qualification Requirements).
- Skills: nice-to-have qualifications (experience with LCPtracker, Sage, Field Materials). Could also include "Experience using LCPtracker", "Experience with Sage (not required)", "Familiarity with Field Materials or similar invoice management systems". That's skills.
- Benefits: list of benefits.
- Pay: pay range.
- Schedule: schedule details.
We also need to include location, contract duration, workplace type maybe as a short paragraph under About the role or separate? Could add a short
after About the role: "Location: Tukwila, WA (100% on-site). Contract duration: 12-month contract-to-hire." That preserves info.
We must not repeat job title as heading.
We must not include application deadline? Could fold into short paragraph or drop. The instruction says "fold minor metadata into a short
or drop it." So we can include a short paragraph for application deadline maybe, but it's minor. I'd include it as a short
at end maybe.
We must not include boilerplate like About Actalent, EEO, etc.
Now craft HTML.
Structure:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Benefits
- ...
...
Pay
$25.00 - $30.00 per hour.
Schedule
Standard Monday‑Friday morning shift, 40 hours per week.
Optionally add a for location/contract duration/application deadline after About the role or at end.
Let's write About the role paragraph: combine the intro sentences plus location and contract duration maybe.
"A reputable electrical construction contractor company in Tukwila, WA is hiring a detail‑oriented Construction Payroll / Office Administrator to support the operations team on union construction projects. This role is critical to maintaining certified payroll, subcontract compliance, and overall project documentation. The position works closely with leadership and the current office administrator and must be capable of stepping in to cover certified payroll and compliance responsibilities when needed. The role is a 12‑month contract‑to‑hire position, fully on‑site in Tukwila, WA."
That covers location and contract duration.
Now Responsibilities: we need to list all duties from the four subcategories. We'll create
- items, maybe combine similar.
List:
- Prepare and submit certified payroll in compliance with government and union requirements.
- File certified payroll in LCPtracker, L&I, and distribute required reports.
- Support union payroll processes and compliance (including
- with items, or we could keep subheadings inside? The instruction says use
- list, maybe grouping by subcategory within
- text.
- Requirements: could be the Qualification Requirements (mandatory). Could also include "Qualifications" as separate? The instruction lists both Requirements and Qualifications as possible headings. We could put mandatory qualifications under Requirements, and nice-to-have under Skills or Qualifications? Actually they have separate headings: Requirements, Qualifications, Skills. We could map:
- Requirements: mandatory qualifications (2+ years experience, etc.)
- Qualifications: maybe the nice-to-have? Or we could treat Qualifications as the same as Requirements? But we need to avoid filler. Since we have both mandatory and nice-to-have, we could put mandatory under Requirements, nice-to-have under Skills (or Qualifications). The instruction says "Prefer a few substantive sections over many thin ones." So maybe we combine Requirements and Qualifications into one section? But they ask to use those headings if content exists. We have content for both mandatory and nice-to-have. Could make Requirements = mandatory, Qualifications = nice-to-have, Skills = maybe specific software skills (LCPtracker, Sage, Field Materials). But the nice-to-have already includes those. Could treat Skills as those specific software skills.
Let's decide:
- About the role: intro paragraph.
- Responsibilities: list of duties.
- Requirements: mandatory qualifications (the bullet list under Qualification Requirements).
- Skills: nice-to-have qualifications (experience with LCPtracker, Sage, Field Materials). Could also include "Experience using LCPtracker", "Experience with Sage (not required)", "Familiarity with Field Materials or similar invoice management systems". That's skills.
- Benefits: list of benefits.
- Pay: pay range.
- Schedule: schedule details.
We also need to include location, contract duration, workplace type maybe as a short paragraph under About the role or separate? Could add a short
after About the role: "Location: Tukwila, WA (100% on-site). Contract duration: 12-month contract-to-hire." That preserves info. We must not repeat job title as heading. We must not include application deadline? Could fold into short paragraph or drop. The instruction says "fold minor metadata into a short
or drop it." So we can include a short paragraph for application deadline maybe, but it's minor. I'd include it as a short
at end maybe. We must not include boilerplate like About Actalent, EEO, etc. Now craft HTML. Structure:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Benefits
- ... ...
Pay
$25.00 - $30.00 per hour.
Schedule
Standard Monday‑Friday morning shift, 40 hours per week.
Optionally add afor location/contract duration/application deadline after About the role or at end. Let's write About the role paragraph: combine the intro sentences plus location and contract duration maybe. "A reputable electrical construction contractor company in Tukwila, WA is hiring a detail‑oriented Construction Payroll / Office Administrator to support the operations team on union construction projects. This role is critical to maintaining certified payroll, subcontract compliance, and overall project documentation. The position works closely with leadership and the current office administrator and must be capable of stepping in to cover certified payroll and compliance responsibilities when needed. The role is a 12‑month contract‑to‑hire position, fully on‑site in Tukwila, WA." That covers location and contract duration. Now Responsibilities: we need to list all duties from the four subcategories. We'll create
- items, maybe combine similar. List: - Prepare and submit certified payroll in compliance with government and union requirements. - File certified payroll in LCPtracker, L&I, and distribute required reports. - Support union payroll processes and compliance (including