OPT Unemployment Days, Explained (2026): Orientation for Indian Students

What the counter actually is

Post-completion OPT is generally described as carrying a limited allowance of time during which you may be unemployed while remaining in that period of authorised training. It is an allowance, not a grace period and not a cushion at the end — it accrues day by day, from the start of your authorisation, for every day you are not employed in a qualifying way.

The specific numbers are exactly what this page will not state as fact. Our CPT vs OPT and STEM OPT pages describe the allowance as commonly around 90 days for post-completion OPT, with an additional allowance during a STEM extension bringing the combined figure to roughly 150 — and both pages say, correctly, to treat that as orientation and confirm the current figures with your DSO. Treat it that way here too. The arithmetic of your own case is a question for the person who administers your record, not for a page on the internet.

Three properties of the counter matter more than its size, and they are the ones students consistently get wrong. It starts earlier than people assume — generally from the start date on your authorisation, not from the day you began seriously applying. It is cumulative rather than consecutive, so a scattering of gaps between short roles adds up the same way one long stretch does. And exceeding the allowance is generally treated as a status problem rather than an administrative one, which puts it in the small category of things that are genuinely hard to undo.

None of that is meant to frighten you into a bad job. It is meant to make the counter visible while you still have the time to use the information.

The count lives on your record, not in your memory

Here is the gap that catches conscientious students, and it is the single most useful idea on this page. Your unemployment count is not derived from whether you had a job. It is derived from what your record shows about whether you had a job. Those are usually the same thing. When they are not, the record wins.

A student who started work on the first of the month and reported it six weeks later has, on paper, a six-week story that does not match the one they would tell you. Whether and how that resolves is a question for the DSO — sometimes it is straightforwardly corrected, sometimes it is more work — but the point is that it becomes a question at all, and it did not need to.

• The practical rule: report promptly, report through whatever channel your DSO tells you to use, and keep your own copy of what you submitted and when. A dated confirmation is worth more than a clear memory.
• Ask your DSO explicitly which channel applies to you — a student portal, a school process, or something they file on your behalf. Do not assume it is the same as a friend's at another university.
• Check what your record says rather than assuming. If your school gives you a way to see your reported employment, look at it, and look at it again after any change.
• Report changes as well as starts: a new employer, an end date, a change in hours or address. Ends matter as much as starts, because an unreported end date is what turns a short gap into a long one on paper.

What generally counts as employment

The broad shape of this is stable enough to be worth knowing, and the details are precisely where you must not rely on a page like this one. Every line below is a category to ask your DSO about, not a test to apply to yourself.

• Work must generally relate to your field of study. This is the condition students underweight: a job that pays the rent but has no connection to your programme is not the same thing, for this purpose, as employment. If the relationship is arguable, get the reasoning on record with your DSO before you rely on it.
• There is generally a minimum level of engagement expressed in hours per week, commonly described as at least twenty. Below-threshold work is the case people misjudge most often, because it feels like a job and may not count as one.
• Multiple employers, part-time roles combining to the threshold, and work through a staffing or agency arrangement are all generally recognised patterns — but each carries its own evidence and reporting expectations, and the agency case in particular is one to raise early.
• Self-employment and running your own business have historically been possible in principle and are hedged with conditions about the legitimacy of the business, the relationship to your field, and your ability to evidence it. This is not a fallback to improvise while the counter runs; it is a conversation to have in advance.
• Certain unpaid or volunteer positions in your field have historically counted under specific conditions, including an expectation about hours and about the nature of the role. Our CPT vs OPT page flags this as a confirm-in-writing question, and that is the right instinct — an unpaid arrangement you assumed counted, which did not, is a costly discovery.
• Whatever the category, expect to be able to evidence it: an offer letter, a description of duties showing the relationship to your field, dates, and hours. Assemble that as you go rather than reconstructing it later.

Tracking your own count

Nobody is going to do this for you, and the effort involved is about fifteen minutes once and two minutes per change after that. Students who track it make different decisions in month four than students who do not — not more anxious ones, better ones.

• Write down your authorisation start and end dates the day you receive your document, and put both in a calendar with reminders well ahead of them.
• Keep one simple sheet: every employment start date, every end date, the employer, hours per week, and the date you reported each of those. The reporting-date column is the one that turns out to matter.
• Count gaps deliberately rather than estimating them. A weekend between two roles is not a gap worth agonising over; six weeks between two roles is information you want in front of you in month three, not month seven.
• Re-read your sheet at fixed points — the end of every month is enough. The failure mode is not miscounting, it is not looking.
• Treat your own count as an estimate that informs when to ask, never as an authoritative figure. The authoritative version is the one your DSO can see, and the two should be reconciled rather than assumed identical.

As the count climbs: act on weeks, not days

The advice here is the same as on our grace periods page, for the same reason: in almost every version of this that goes badly, the damage was done less by the original circumstance than by the weeks that passed before anyone was told. Options in this area expire, and the ones that remain late are slower, more expensive and less certain than the ones available early.

So the trigger for a conversation is not "the counter is nearly out". It is "the search is running longer than I planned". Those are months apart, and the difference between them is most of what determines how this ends.

• Ask in writing, ask a specific question about your own situation, and keep the answer. "My authorisation began on [date], I have had these roles on these dates, my search is running longer than expected — what should I be considering now and what has deadlines attached?" gets a usable reply.
• Do not wait until you have good news to report. The reflex to go quiet until something is settled is understandable and it is exactly backwards: a DSO can do considerably more with four weeks of warning than with four days.
• Do not take a materially unsuitable job purely to stop the counter without understanding whether it qualifies at all. Work that does not meet the conditions may stop nothing while costing you the time you had left to search properly.
• Be wary of anybody who solves this for a fee. Arrangements that place you on a payroll you do not really work for, or that promise to keep your record clean in exchange for money, are among the more serious ways students damage their own position — and the pressure of a running counter is precisely what those arrangements are designed to exploit. Take anything of that shape to your DSO before you agree to it.

The mistakes that cost days nobody needed to lose

• Starting the count from the wrong date — usually from graduation, or from when the search got serious, rather than from the date on the authorisation.
• Assuming a gap is short because the jobs were close together, when one of them was reported weeks after it started or ended.
• Treating an employer's onboarding paperwork as the reporting step. It is not; your obligation is separate and generally runs through your school.
• Letting an unpaid, part-time or self-directed arrangement run on the assumption that it counts, without ever asking. This is the expensive one, because the days are gone by the time the assumption is tested.
• Travelling without checking what your situation requires while you are between jobs — a re-entry question that is better asked before booking than at a port of entry. Our travel and re-entry page covers the document side.
• Going quiet with the DSO during the hardest stretch of the search, which is the stretch when contact is worth the most.

The honest part

A slow search is not a character failure, and a counter that has been running is not evidence that you did something wrong. Hiring cycles are long, sponsorship narrows the field further, and plenty of strong candidates spend months on this. Our page on the sponsorship question covers why the rejections you are getting are often policy rather than performance.

What is in your control is small and genuinely effective: know your dates, report promptly and keep proof, check your record rather than trusting your memory of it, and start the conversation with your DSO on the timescale of weeks rather than days. None of that is dramatic, and together it is the difference between a search that ran long and a status problem.

And the last thing, which is the reason this page exists at all: the counter is not a secret being kept from you. It is simply a thing most students meet late. Meeting it early costs you one afternoon and removes most of the ways this goes wrong.

Frequently asked questions