Why a Single Percentage Rule Controls More of Your Semester Than You Think

Shah Noor — Tue, 04 Aug 2026 06:54:05 +0000

Most students treat attendance like a background task, something you deal with only when a warning shows up on the portal. I didn't think much about it either, until a research project on academic policy design pulled me into how Indian universities structure attendance rules, and how little most students understand the mechanics behind them.

I'm not affiliated with SRM. I study at a different university, and my interest here is academic policy design and the small tools students build to survive it. SRM Institute of Science and Technology turned out to be one of the clearest, best-documented cases I came across, so I'm using it to explain a pattern that shows up across most credit-based Indian universities, not just one campus.

The Logic Behind Mandatory Attendance Rules

Attendance thresholds exist for a reason that has nothing to do with punishing students. Practical, lab-heavy, cohort-based programs need a minimum floor of physical presence to justify awarding a grade. A 75% threshold, common across many AICTE-affiliated technical universities, isn't arbitrary. It roughly corresponds to missing no more than one class in four without losing continuity.

The problem isn't the logic, it's the execution. Most attendance portals show you a raw number and nothing else:

No warning before you cross the line
No forecast of how many classes you can still miss
No separation between what's recoverable and what isn't

You find out you're in trouble only after the fact, when a detention list is already published.

SRM's 75% Rule: A Closer Look

SRM's regulation is worth studying because it's unusually well documented. Under SRMIST's official regulation R7.5, falling below the attendance floor results in an 'I' grade, shorthand for registration cancelled for want of attendance. That isn't a soft warning. It means retaking the entire course from scratch, including re-registration and re-payment.

A few details make this rule stricter than students assume:

The threshold applies per subject, not as a semester-wide average. You can be comfortably above 75% overall and still get detained in one lab course sitting at 73%.
Lab and theory attendance are tracked as separate pools. A few missed lab sessions can tank your percentage far faster than the same number of missed theory classes, since the total session count is smaller.
There's no rounding in your favor. 74.9% is treated the same as 60%.

This per-subject, no-rounding structure is what catches most first-year students off guard. They mentally track one number, "my attendance," when the system tracks six or seven separate numbers at once.

The Condonation Process Most Students Misread

Almost every Indian university with a hard attendance floor has some form of condonation process, and almost every student misunderstands how limited it is.

Under SRM's framework, the ceiling on condonation is fixed at a 10% shortfall, no matter the reason. A departmental committee reviews documentation like medical certificates or proof of participation in approved events, and a senior academic authority makes the final call.

What this means in practice:

Somewhere in the 65–75% range, you may be eligible to apply, with proper documentation.
Below that range, condonation typically isn't on the table at all. Re-registration becomes the only route back.
Even within the eligible range, approval is discretionary, not guaranteed. Documentation improves your odds; it doesn't lock in an outcome. A condonation policy is a safety net with a maximum stretch, not an alternate attendance requirement. That distinction holds true well beyond SRM.

On-Duty vs Medical Leave: A Distinction That Trips People Up

One detail worth knowing, and one that generalizes well beyond SRM, is the practical difference between On-Duty (OD) status and Medical Leave (ML).

On-Duty, granted for things like inter-university events or approved interviews, counts as a day physically attended. Your percentage doesn't move.

Medical Leave does not add to your attendance count. What it can do is strengthen your case if you later apply for condonation. It's evidence for an appeal, not protection against the shortfall itself.

If a student has a genuine choice between securing an OD and taking medical leave for something non-urgent, the OD is structurally the safer option for protecting the percentage. This distinction is rarely explained clearly to first-year students, at SRM or anywhere else.

Why This Deserves More Attention Than It Gets

The deeper issue isn't SRM specifically. Attendance systems across Indian higher education are built around strict, per-subject, non-negotiable thresholds, but the tools students get to monitor them are usually just a raw percentage with no forecasting built in.

That gap is why dedicated tracking tools exist. While researching this, I came across a free SRM attendance calculator that does something SRM's own portal doesn't: it shows exactly how many classes you can still miss, or need to attend, before you
cross into shortage or detention territory. For a policy this
unforgiving, that forward-looking number matters more than the
raw one.

The Takeaway

Hard attendance cutoffs aren't going away, and for lab-heavy programs there's a reasonable case for them. But a policy this strict deserves to be understood, not guessed at. Know whether your university tracks attendance per subject or as an average. Know your condonation ceiling before you need it. And track your numbers before the portal decides to tell you, rather than after.

Building a CGPA Calculator Was Easy. Making It Useful Wasn't.

Shah Noor — Tue, 14 Jul 2026 08:46:42 +0000

Most people think a CGPA calculator is only about formulas.

I thought same.

Then I started building one.

Very quickly I realized students do not struggle with calculations. They struggle with everything around them.

Finding subject credits.

Checking semester details.

Making sure nothing is missed.

Entering same information again and again.

That is where most of time goes.

So I changed my approach.

Instead of building another calculator, I focused on removing unnecessary work.

I wanted students to spend a few seconds selecting their grades instead of several minutes searching through documents.

That meant organizing academic data first.

Not writing code.

I spent days reading official SRM curriculum documents and arranging subjects and credits into a format calculator could understand.

It was repetitive work.

Sometimes frustrating.

But I knew every hour spent behind scenes would save students time later.

One lesson stood out.

A good tool is not one with most features.

It is one that asks users to do less.

Today calculator automatically handles subjects and credits based on selected course and semester. Students only choose their grades and calculator does rest.

If you are curious to see how that idea turned into working tool, you can explore it here:

CGPA Calculator for SRM University

It also includes separate tools for GPA, CGPA and arrear calculations, all designed with same goal of reducing manual work instead of adding more steps.

Building this project changed how I think about software.

Sometimes biggest improvement is not adding another feature.

It is removing one unnecessary click.

Have you ever built something that looked simple on outside but took far more work behind scenes? I'd love to hear your experience.

DEV Community: Shah Noor