Ohio Tax Residency: The Bright-Line Contact Period Test & the Affidavit Trap

If you're relocating out of Ohio — or spending significant time there while claiming residency elsewhere — you need to understand something up front: Ohio does not use a day-count test. It uses a "contact period" test, and the difference is not just semantic. It changes how you should be tracking your time in the state.

Most of the residency guides you'll find online describe Ohio the same way they describe New York or Connecticut — "just count your days, stay under 183, you're fine." That's wrong. Ohio's rule is built around something called a contact period, governed by Ohio Revised Code (R.C.) § 5747.24, and it's stricter, more mechanical, and more procedurally unforgiving than a simple day count.

What Is a "Contact Period"?

Under R.C. § 5747.24(A), a contact period is created any time an individual spends any portion, however minimal, of two consecutive days in Ohio while away overnight from an abode located outside the state.

The cleanest way to think about this: a contact period is generated by being in Ohio through a midnight — the overnight straddle — not by however many daylight hours you spent there. If you were in Ohio on the evening before midnight and still in Ohio (or arrived there) on the morning after midnight, that overnight straddle is one contact period.

Three Concrete Examples

The pattern to take away: contact periods accumulate per overnight straddle, not per calendar day of physical presence. Consider ten separate two-day overnight trips spread across the tax year: in a traditional day-count state (like New York or New Jersey) where any portion of a day counts as a day, those trips would go down on your log as 20 days. In Ohio, they generate exactly 10 contact periods — meaning you've only consumed 10 of your 212 safe-harbor slots. This overnight-straddle math actually makes the safe harbor significantly easier to meet for frequent short-stay travelers than a traditional day count.

The Bright-Line Thresholds

Ohio's statute creates two presumptions, based on your total contact periods for the tax year:

• 212 or fewer contact periods: Combined with maintaining an abode outside Ohio for the entire year and timely filing the required affidavit, this gives you an irrebuttable presumption of non-residency (subject to the five exceptions discussed below).
• 213 or more contact periods: This creates a presumption that you are domiciled in Ohio, which you can only overcome with "clear and convincing" evidence under the traditional common-law domicile factors — a much harder standard to meet.

Historical Note: This threshold has changed over time. It was originally 182 contact periods, was raised to 213 in 2015, and the safe-harbor threshold sits at 212 or fewer today. If you are reading older articles or forum posts that cite "182 days," they are describing a prior version of the law.

The Affidavit Is Mandatory — and the Law Behind It Has an Important History

Filing is not optional. To claim the bright-line safe harbor, you must timely file the Affidavit of Non-Ohio Residency/Domicile (Form IT DA) with the Ohio Department of Taxation by October 15 following the tax year in question. Miss that deadline, and you lose access to the bright-line test entirely — you're thrown back into the much more fact-intensive common-law domicile analysis, regardless of how few contact periods you actually had.

Why the rule looks the way it does today: Cunningham v. Testa

In 2015, the Ohio Supreme Court decided Cunningham v. Testa, 2015-Ohio-2744. Kent Cunningham had 182 or fewer contact periods (the threshold at the time), maintained an abode in Tennessee, and timely filed his affidavit claiming non-Ohio domicile — satisfying every mechanical requirement the statute asked of him. He still lost. The Court found that despite meeting the contact-period and abode tests, Cunningham had also claimed an Ohio homestead exemption, held an Ohio driver's license, and was registered to vote in Ohio — all traditional common-law domicile factors — and held that these facts made his affidavit's "non-Ohio domicile" statement false. In effect, Cunningham opened the door for the Tax Commissioner to reach into the full, open-ended common-law domicile test — everything from where you bank to where your doctor is located — to challenge an otherwise-compliant affidavit.

The Legislative Correction: House Bill 292

That door has since been closed. Ohio's legislature responded directly to Cunningham with House Bill 292, signed into law June 14, 2018, and effective for tax years beginning in 2018. HB 292 amended R.C. § 5747.24 to specify that the open-ended common-law domicile factors are no longer relevant to a bright-line claim. In their place, the statute now limits the Tax Commissioner to a closed, enumerated list: your contact-period count, whether you maintained a qualifying out-of-state abode, and five specific disqualifying conditions. Nothing outside that list — no bank location, no place of worship, no political contributions, none of the "dozens of common-law factors" that made Cunningham so unpredictable — can be used to attack an affidavit today.

Practical takeaway: Cunningham is important background — it explains why the current five-condition checklist exists and why the 2018 amendment was necessary — but it is no longer the operative legal test. For someone with 212 or fewer contact periods today, the real question isn't "would a court find common-law domicile," it's simply "does this person satisfy all five enumerated conditions below, yes or no." That's a closed, mechanical checklist now, not an open-ended factual inquiry.

The Five Enumerated Conditions

To qualify for the Ohio bright-line safe harbor today, an individual must be able to say, truthfully, that during the entire tax year they did NOT:

These conditions were added specifically to close the gap exposed by Cunningham. If you can check off all five (no Ohio license, no homestead exemption, no in-state tuition benefit, no depreciation deduction on an Ohio home, and you meet the abode and contact-period rules), your bright-line claim is secure.

Why This Matters for Remote and Hybrid Workers

Because a contact period is only triggered by an overnight stay, frequent short trips to Ohio that do not involve staying overnight generate zero contact periods, while two-day overnight trips only count as one. For remote and hybrid workers who commute to the state for single-day meetings, this test is highly favorable. A worker who commutes to a Columbus office for 40 day-trips (returning home the same day) accumulates exactly zero contact periods. In a traditional day-count state like New York, those same 40 commutes would count as 40 days of presence, pushing the taxpayer much closer to residency thresholds.

Even when overnight stays are required, the contact-period math makes it easier to stay within the 212 safe-harbor threshold. For example, monthly two-day overnight trips to Ohio only generate 12 contact periods over the course of the year. In a day-count state, those same trips would represent 24 days. For individuals managing hybrid work schedules, Ohio's test provides a significantly wider safety margin than states utilizing standard day counts.

How Domicile365 Handles Contact Periods

Because "contact period" is a fundamentally different unit of measurement than "day," a generic day-counting tool can silently misclassify your Ohio presence — either under-counting overnight trips that don't look like "full days," or failing to flag the specific two-consecutive-day trigger that Ohio's statute cares about.

Domicile365's overnight presence detection is built around exactly this mechanic: rather than asking "was the person present at some point during this calendar day," it checks for recorded locations in a window before midnight and a window after midnight, and attributes a count only when both are present — meaning a count is generated once per midnight actually crossed, not once per trip and not once per day of physical presence. That's the same underlying logic Ohio's contact period test uses. A short overnight stopover, a run of consecutive nights, or a multi-week continuous stay are all measured the same way: one count per midnight straddled, which lines up directly with how Ohio counts contact periods, without requiring a separate Ohio-specific calculation.

What this means in practice: the location log Domicile365 already produces for you is structured in the unit Ohio's statute actually uses, not in the "days visited" framing that trips up most manual trackers and generic apps. That log — exportable, date-stamped, and tied to your recorded locations — is exactly the kind of record that supports getting your contact-period count right when it comes time to file the Affidavit of Non-Ohio Residency/Domicile.