Triggers: What Actually Sets a Clawback Off

A clawback does nothing until something trips it. That something is the trigger, and the quality of a clawback is decided first at the trigger, because a penalty that never fires is no penalty at all. Let us catalog the triggers a practitioner looks for, in rough order of how commonly they appear and how easily they are gamed.

The job-shortfall trigger is the archetype. The agreement sets a minimum headcount by a compliance date, and if the company employs fewer, recovery is due. Simple in principle, but the details decide everything. What counts as a job? A full-time equivalent, a headcount including part-timers, a contractor, a temp from a staffing agency? Agreements that fail to define this invite the company to meet its number with positions that were never the point of the subsidy. And when is the count taken? If it is a single-day snapshot, a firm can borrow bodies for the audit. Sound agreements require the jobs to be full-time-equivalent, held by employees rather than contractors, and sustained across a maintenance period measured in years, verified by payroll records rather than the company's own attestation.

The wage-floor trigger addresses a subtler evasion. A company can hit its job count while paying poverty wages, which defeats the public purpose of the subsidy — the whole justification for spending public money on private employment is that the employment is supposed to be good. So better agreements condition the incentive not just on the number of jobs but on those jobs clearing a wage threshold, often pegged to a county or regional average so it rises with the local economy. A job-count trigger without a wage floor is half a safeguard.

The capital-investment trigger requires the company to actually spend what it said it would spend on the facility — the building, the equipment, the fit-out. This matters because much of a subsidy's justification rests on the durable physical asset left behind, the thing that keeps generating property tax after the incentive expires. A shortfall here signals a project that shrank after the ink dried.

Then come the triggers that address bad faith directly. The relocation trigger fires if the company moves the operation — sometimes even within the same state — defeating the local government that paid for it. The closure or cessation trigger fires if the facility shuts before the agreed term. And the maintenance trigger, the most important and most often omitted, fires if the company hits its targets and then lets them erode. Without a maintenance trigger, an agreement rewards a single good photograph rather than a decade of sustained employment.

The recurring theme across all of these is gameability. A trigger is only as strong as the definition beneath it and the verification behind it. Ask, of every trigger: is the triggering event measured by a neutral, documentary source, or by the company's own say-so? Payroll filings, unemployment-insurance records, and building permits are hard to fake. Self-reported surveys are not. A watchdog like Good Jobs First built its Violation Tracker precisely because the gap between what companies report and what they do is wide enough to catalog. When you evaluate a deal, do not ask merely whether it has a clawback. Ask what, specifically, sets it off — and whether the setting-off depends on a number the beneficiary controls. If it does, the trigger is a courtesy, not a control.

One more discipline. Read the trigger for what it excludes as much as what it includes. Force-majeure carve-outs, economic-downturn exceptions, and "good faith effort" escape hatches can hollow out an otherwise sturdy trigger. A clause that suspends the clawback whenever the company can plead adverse market conditions has quietly moved the risk of the deal back onto the public — which was supposed to be the point of the clawback in the first place. The trigger is where optimism meets the meter. Everything downstream depends on whether the meter can actually be read.