Editorial standards

What we publish

Educational research grounded in primary sources: statutes, court opinions, agency interpretive guidance (DOL opinion letters, IRS revenue rulings, state DLSE / DIR / L&I letters), and official institutional reports. Each article covers a specific area of US wage-and-hour law — overtime, breaks, sick leave, vacation payout, off-the-clock work, pay stubs, the OBBB tax deduction — with federal baseline + state-by-state coverage + named cases + the operational traps that drive litigation.

The audience is one person: an HR manager, business owner, payroll administrator, or employee searching for “rule in state” or “what's the penalty for X?” The reader landed from search with a real question and a tab full of other open results. Each article's job is to answer that question more usefully than the next tab.

What we don't publish

• Legal advice for a particular situation. Articles document the law as it stands; they don't apply it to a specific employee or employer. For case-specific decisions, employment counsel is the right resource.
• Generic explainers without primary citations. A claim about a statute without the section number, a claim about a court holding without the case citation — neither gets published. Load-bearing claims that only have a secondary source say so inline.
• Promotional content disguised as research. Articles cross-link to Clockspot's product where the topic genuinely connects (time-record capture, premium-pay tracking, multi-rate workers) but don't sell the product mid-paragraph. The article footer is the one place product positioning is allowed.

Citation density

Every load-bearing claim cites a primary source. In practice:

• Statutes cited to the section number. Not “California labor law” — California Labor Code §226(a)(9). Not “the FLSA” — 29 USC §207(a). Not “DOL regulations” — 29 CFR §785.48(b). Specific statute citations let readers verify the claim directly against the source.
• Named cases with full citations. Naranjo v. Spectrum Security Services, 13 Cal.5th 93 (2022). Magadia v. Wal-Mart Associates, Inc., 999 F.3d 668 (9th Cir. 2021). Donohue v. AMN Services, 11 Cal.5th 58 (2021). Reporter citations either match the source or they don't; fakes get exposed immediately.
• Procedural posture made explicit. When a widely-quoted dollar figure is a trial-court judgment that got reversed on appeal, the article says so. The Magadia“$172M wage-statement settlement” figure that circulates in popular coverage is wrong on two counts: the actual district-court judgment was ~$102M, and the 9th Circuit reversed the §226 portion entirely. Repeating the popular number would be the bug; explicit posture is the fix.
• Settlement amounts with lineage. Jury verdict, FLSA liquidated damages, affirmed-on-appeal figure, and final settlement amount are four different numbers and routinely get confused. Articles trace each amount back to the specific event that produced it.

Dense, specific claims are quotable. Generic prose isn't. The trade is intentional.

Editorial voice

The articles take positions. “Federal law does not require employers to give employees a pay stub” is a specific factual stance; “Employers should be aware of federal pay-stub requirements” is generic and uncite-able. We always pick the first shape.

• Direct address. Articles speak to the reader, not about a hypothetical employer.
• Stakes-first. Sections open with cost or risk, then explain the rule.
• Specific over generic. “Walmart was hit with a roughly $102M judgment in Magadiabefore winning on appeal” beats “Pay-stub violations can be expensive.”
• No encyclopedia tone. Sentences carry voice and opinion. Generic prose that could have been written about any state gets rewritten with a specific take.

A typical article covers 10–15 states with statute citations, names 3–10 cases with full reporter citations, includes a 6–8-question FAQ, and ends with a remediation playbook for employers who discover they've been out of compliance. The voice is consistent across the collection; each article reads like the same author wrote all of them.

Currency

Every article displays a “Last updated” date at the top. The date reflects when the article last received a substantive edit, so readers can see how recent the underlying review was.

We bump the date on substantive edits: a new section, a new named case, a statute amendment, a 2024–2026 development. We don't bump it for typo fixes or CTA tweaks. The date should mean the law changed and we updated for it — not that we touched the page.

Verification

Verification runs in two stages, in this order:

1. Pre-publication research-verification. Before any prose, the research file backing the article is walked claim-by-claim against the fact-check methodology. Every named case, statute citation, settlement amount, and recent change is verified against a Tier 1 primary source. Claims that can't be verified are softened to match the available evidence or removed. This catches procedural-posture errors, settlement-amount lineage errors, and stale legislation citations at the research stage, before voice and structure get layered on top.
2. Post-publication fact-check. Each article ships with a per-article fact-check report at /articles/<slug>/fact-check. The report applies the same methodology to the published article, claim by claim, with verification dates and source URLs. The summary at the top of each report (“32 verified / 3 partial / 0 flagged”) is computed from the claim list below, so the headline counts always match the detail.

Readers verify by clicking sources. Every claim has at least one URL; if a claim doesn't match its cited source, that's a single click to flag.

Corrections

Spot a factual error? The fact-check report at /articles/<slug>/fact-check lists every checked claim with its source URL and verification date. Clicking through to the source either confirms the claim still holds or surfaces the discrepancy. We re-check what's flagged and update the article + report, advancing the verification date.

We don't promise a re-verification cadence — that would create maintenance debt that doesn't improve trust. The date on each report is the reader's information; clickable sources let readers audit currency themselves.

Authorship

Articles are written by Clockspot's team, drawing on internal research, primary sources, and 18 years of operating experience with US employers — cleaning companies, construction crews, restaurants, healthcare facilities, retail. Clockspot has been building time-tracking software since 2007; the editorial choices reflect what we've watched happen across thousands of customer payroll periods.

Articles are not bylined to individual employees because the editorial voice and standards are collective, the fact-check methodology + source URLs are the citation surface, and a personal byline doesn't add information a reader can act on. Institutional authorship is the byline.