Non-Exempt Hourly Offer Letter Framework

This framework is for non-exempt hourly roles where the employee is paid a default compensation rate by the hour and may earn overtime. It fits frontline, operational, clerical, warehouse, retail, and other hourly positions that are not salaried exempt roles. If the role is salaried exempt, use a different offer letter template. If the role crosses state lines or is remote, narrow the letter with the correct country and state_province fields.

Yes. It is designed to state overtime eligibility clearly so the candidate understands that hours worked beyond the applicable threshold are paid according to law and company policy. That matters for FLSA compliance and for avoiding confusion after the offer is accepted. The template should not imply a fixed weekly paycheck if the role is hourly.

Recruiters or hiring managers usually prepare the draft, but HR or compensation should verify the hourly rate, default benefits, and any approval rules before it goes out. If the pay rate crosses a salary_threshold or triggers executive_approval_required in your workflow, that approval should happen before the candidate sees the offer. For hourly roles, the approval path should be lighter than executive sign-off for every offer.

It helps you document non-exempt status, hourly pay, overtime eligibility, and the acceptance terms in a way that aligns with wage-and-hour expectations. For U.S. offers, it should also reflect the correct state-specific language where needed, such as at-will employment carve-outs by state and any required wage-theft prevention notices in NY, CA, or DC. If the offer is for an EU worker, add the GDPR data-handling clause that applies to the offer process.

A common mistake is using salaried language for an hourly role, which can create confusion about overtime and pay calculations. Another is leaving out the acceptance deadline or the signature anchors, which makes e-signature routing harder. Teams also sometimes forget to localize the letter with country and state_province, or they use a free-text benefits paragraph instead of a structured default_benefits block.

Yes. You can customize the default_compensation range, the hourly rate, the default_benefits structure, and the jurisdiction fields for each location. If you hire across multiple states, keep the core framework the same and swap in state-specific clauses where required. That makes it easier to maintain one template while still matching local rules.

An ad-hoc email often misses key details like overtime eligibility, acceptance timing, or the correct legal language for the worker’s location. This framework gives you a repeatable structure so every hourly offer includes the same core terms and approval checkpoints. It also makes it easier to reuse the letter across recruiters, locations, and job families without rewriting from scratch.

At minimum, confirm the role title, start date, hourly rate, overtime eligibility, accept-by date, country, state_province, and signature anchors. You should also verify the default benefits, any approval rules, and whether the role needs at-will language or a regional notice. If the role includes equity, make sure the timing and approval language are reviewed separately.