A landscaping contractor can win a public-project package and still lose money before the first invoice if the payroll record is not designed around the contract’s wage requirements. Prevailing-wage work is not simply a higher hourly rate. It can require the contractor to identify the governing wage determination, classify each worker’s work, account for cash wages and qualifying fringe benefits, preserve supporting records, and produce a certified payroll or equivalent report when the awarding authority requires one.
The first question is scope. The Davis-Bacon Act and related federal requirements apply to covered federal or federally assisted contracts, while states, cities, and public authorities may impose their own prevailing-wage rules on covered public work. A landscaping company should read the contract and the wage decision issued by the responsible agency rather than assume that a rule for one project follows the crew to every private account. The U.S. Department of Labor’s Davis-Bacon and Related Acts guidance is a starting point, not a substitute for the contract administrator or the applicable state or local labor agency.
StockPoint can give a contractor one operational record for worker identity, building or project assignment, photo and PIN verification, honest-accuracy location evidence, payroll preparation, and correction history. It cannot determine which wage determination governs, certify compliance on the employer’s behalf, or file a certified payroll report. Those boundaries matter: software should organize the evidence while the employer validates the legal inputs.
How to identify the governing wage requirements
Before scheduling the crew, save the wage determination and the contract language that incorporates it. Record the project, contracting agency, effective date, covered classifications, base rates, fringe requirements, apprentice conditions if any, and the person responsible for reviewing changes. If an addendum replaces the wage decision or changes the scope, preserve both versions and the date the team began using the new one.
A wage determination is useful only when it is translated into the work actually performed. “Landscaper” may not be the right classification for every task on a public site; planting, mowing, irrigation, tree work, laboring, equipment operation, and construction-related work can be described differently by a governing schedule. Do not invent a classification from a familiar job title. Compare the contract’s scope with the agency’s definitions and ask the agency or counsel when the work does not fit cleanly.
Keep the lookup decision separate from the worker’s pay calculation. A supervisor may know that a worker trimmed a site, but payroll needs the project, date, hours, classification, base rate, fringe treatment, and any approved correction. That separation makes review possible when the same employee works on both prevailing-wage and ordinary commercial accounts in one week.
How to classify landscaping work without guessing
Worker classification should follow the duties performed on the covered project, not a title copied from the general payroll system. A crew member who spends part of a day operating equipment and part of a day doing manual landscaping may need a documented allocation if the wage schedule treats those duties differently. When the record cannot distinguish the work, payroll may be forced into a conservative treatment or a later reconstruction.
A practical assignment record states the project, location, date, crew member, supervisor, task description, classification used, and the evidence supporting the classification. A photo of a completed planting bed can support what happened at a site, but it does not by itself prove every hour or the correct wage category. StockPoint’s per-building or per-project punch can connect the field event to the payroll record while leaving the classification review visible to an authorized reviewer.
If a worker changes tasks mid-shift, record the change at the time rather than asking payroll to guess at week’s end. The record can remain simple: the supervisor selects the project task, the worker confirms the time, and a reviewer resolves an exception. A correction should retain the original event, the reason, the reviewer, and the final approved value.
How to document base wages and fringe benefits
Prevailing wage usually requires attention to fringe benefits as well as cash wages. The wage decision or contract may state a combined rate, a base wage plus fringe amount, or a permitted way to credit certain bona fide benefits. The employer should not treat an ordinary perk, an unverified reimbursement, or a payroll deduction as a fringe credit merely because it has a dollar value. Confirm the agency’s rules and retain the plan, payment, or contribution records that support the credit.
A worked example shows the control needed. Suppose a project schedule requires a base wage of $24 per hour and a fringe amount of $8 per hour, and a worker records 32 approved project hours. The gross prevailing-wage package is $1,024 before considering any lawful payroll deductions or the employer’s chosen fringe method. If the company pays $5 per hour toward an eligible benefit and pays the remaining $3 per hour as cash wages, payroll must preserve both the contribution evidence and the calculation; it should not simply label the entire $8 as “benefits.” The figures are illustrative, and the governing schedule controls.
If the worker also has hours on private work, keep the project totals distinct. Blending the week into one rate makes it difficult to show that the public-project requirement was met and difficult to explain the calculation to the employee. Per-worker payroll locking can stop an approved correction from being posted twice, but it does not validate whether the benefit was creditable.
Building certified-payroll inputs
Certified payroll is a reporting process, not a decorative PDF. When the contract requires a Davis-Bacon or state equivalent report, the contractor must be able to trace the report’s worker names, classifications, hours, rates, deductions, and statement of compliance to underlying records. The DOL’s Davis-Bacon guidance explains the federal framework, while the awarding agency may prescribe a particular form, portal, deadline, and retention period.
Build the report from reviewed records rather than from a last-minute spreadsheet. The source should identify each covered project, each worker, the days and hours worked, the classification, the wage and fringe calculation, and any deductions. The reviewer should compare the project roster with payroll, investigate missing punches, and confirm that a worker who moved between sites is allocated correctly. A client portal photo can support the service narrative, but the payroll report needs the wage fields required by the governing program.
StockPoint can calculate or prepare payroll data and can preserve the same verified punch used for cost-plus support. The employer remains responsible for reviewing, signing, filing, and responding to agency questions. StockPoint can calculate or prepare 941, NYS-45, and W-2 data, while the employer files; bank-feed reconciliation is on the roadmap, not shipped.
Correcting payroll records without erasing history
Corrections should be ordinary workflow, not evidence destruction. If a worker forgot to punch out, the supervisor should record the source of the correction, the actual work performed, the project, the classification, and the person who approved it. If payroll discovers that a fringe contribution was not credited correctly, preserve the original calculation and the replacement calculation, then determine whether the contract requires notice or a supplemental report.
The contractor should never make a record look cleaner by deleting a disputed event. An audit log that shows a failed location check, a worker explanation, and a supervisor disposition is more credible than a perfect dataset with no exceptions. GPS is context, not exact proof; indoor or signal-limited work may produce an estimate. Photo and PIN evidence can corroborate attendance, but neither changes the applicable wage decision.
A correction also needs a worker-facing path. Provide a bilingual explanation of the pay change where the workforce needs it, show the covered project and hours, and give the worker a way to dispute an error. A wage complaint should be investigated without retaliation. The record should show the correction, not imply that asking a question was misconduct.
The audit trail should be useful to more than the auditor
The most useful project file joins contract scope, wage determination, worker classification, time, payroll, fringe support, certified reports, and correspondence. It does not give every client access to every worker detail. A facility or public agency may need the report fields required by the contract, while a worker needs an understandable pay record and the company needs the underlying audit trail.
Separate project evidence from personal information wherever possible. Limit client portal views to the proof of work and status the contract calls for, and define retention and deletion rules before the first photo is uploaded. The employer’s recordkeeping duty may outlast a client’s operational interest in a live location feed. A privacy-conscious system can show that a checkpoint was reviewed without exposing a worker’s full route history.
Use a short review at the end of each payroll period: reconcile the project roster, approved punches, pay register, fringe support, and report submission. A rough internal estimate that a coordinator spends three hours rebuilding one week of mixed-site records is not a compliance fact, but it illustrates why a connected record is an operating control rather than an administrative luxury.
Make responsibility visible before the first payroll
A contractor should decide in advance who owns each prevailing-wage control. The estimator confirms the contract and wage schedule. The operations lead assigns workers and tasks. The supervisor reviews the daily record. Payroll applies the approved wage and fringe treatment. The owner or designated compliance reviewer signs the report and keeps the submission evidence. If one person performs all five roles, the company still needs the steps to be visible.
Train supervisors to report facts, not legal conclusions. They should record that a worker operated the mower, installed irrigation, or loaded debris at a project, not select a rate because it “seems close.” Training should be understandable to the bilingual workforce and should explain how to report missed punches, changed duties, and unsafe conditions without fear of losing pay.
StockPoint helps put that process near the work: assigned project, verified punch, photo or PIN, client status, bilingual pay surface, locked payroll approval, and an audit log. The product is strongest when the company configures the governing rules with an adviser and uses the platform to make execution consistent.
What to do before the crew starts
Before mobilizing a landscaping crew, save the governing wage source, map the classifications, document the base-and-fringe treatment, test the project punch flow, and agree on the correction path. Confirm whether the awarding agency requires a certified report, an electronic portal, a particular statement, or a special retention period. If the scope or wage decision changes, reopen the review instead of carrying forward a familiar assumption.
The field-service payroll records guide is useful for the broader record architecture, while StockPoint’s features show how per-project punches, client proof, payroll preparation, and audit history fit together. The correct result is not a prettier report; it is a report that can be traced back to work the crew actually performed.
Sign up at getstockpoint.com to give your landscaping operation a shared, bilingual record for verified work, payroll inputs, client status, and corrections. You get an operating layer that helps your team prepare defensible records while leaving legal classification, employer filing, and agency certification where they belong: with the employer and its advisers.