Iqta vs Jagir vs Mansabdar vs Zamindari: The Complete 700-Year Story (UGC NET History Deep Dive)

If you’ve sat with these four terms long enough, you know the specific kind of frustration they cause. You read Iqta, feel confident, move to Jagir, and by the time Mansabdar and Zamindari show up in the same paragraph, everything’s blurred into one indistinct “medieval land revenue thing.” Then a PYQ asks you to distinguish Jagirdar from Zamindar specifically — or worse, throws in Zabt or Dahsala as a fifth term you weren’t expecting — and the blur costs you a mark you actually knew.

Here’s what almost no source gets around to telling you plainly: you’re not looking at four unrelated systems. You’re looking at one system evolving, across seven centuries — the Sultanate builds it, the Mughals refine and split it, the British bend it into something new. And buried inside that story is a distinction most notes blur completely: the difference between who gets the revenue (Iqta, Jagir, Zamindar) and how much revenue there actually is to collect (Zabt, Dahsala) — two different questions medieval administrators had to solve separately. Once both pieces click, you stop memorising four flashcards and start recognising one connected mechanism.

First, separate two questions that keep getting merged

Every term in this guide is really answering one of two different questions, and conflating them is where most confusion starts:

• “Who has the right to collect this land’s revenue, and on what terms?” — this is the assignment question. Iqta, Jagir, and Zamindar all live here.
• “How much revenue is this land actually supposed to yield?” — this is the assessment question, and it’s a completely separate administrative problem. Zabt and Dahsala live here.

You can have a jagir (an assignment) whose revenue is calculated using the zabt method (an assessment) — the two systems operate side by side, not as alternatives to each other. Most comparison guides online only cover the assignment question and never mention this second axis exists at all, which is exactly why it’s worth getting right here.

Act One: the Sultanate invents the Iqta (13th–14th century)

Picture the actual problem the early Delhi Sultans faced. They’d conquered a vast, newly-won territory and needed to pay a large standing military and administrative class — but medieval treasuries didn’t hold enough coined money to pay everyone in cash, reliably, every month. The Iqta was the elegant fix: instead of a cash salary, the Sultan assigned an officer a territory and let him collect its revenue directly, in exchange for military and administrative service — governing the area, keeping order, and supplying troops on demand.

The officer holding this assignment went by two names you’ll see used interchangeably in sources and PYQs alike: Iqtadar and Muqti. They’re the same role — don’t let the exam trip you up by treating them as two different offices. His military counterpart at the centre sat in the Diwan-i-Arz (the department of military affairs, created under Balban), headed by the Ariz-i-Mumalik — the minister who mustered troops, inspected arms, and fixed pay. That department mattered precisely because it was the centre’s check on iqtadars scattered across the empire: someone still had to verify a muqti’s claimed troop numbers were real.

The genuinely important design detail — the one PYQs love to test — is that an iqta was meant to be transferable and non-hereditary. The Sultan could, in principle, move an iqtadar from one territory to another, or reclaim it outright. This wasn’t incidental; it was the whole point. A transferable assignment meant an iqtadar could never put down roots deep enough to become a rival power centre. Historians studying Sultanate administration do debate how consistently this was actually enforced in practice — powerful iqtadars sometimes entrenched themselves anyway — but the design intention is unambiguous, and it’s what you’re being tested on: mobility as a deliberate control mechanism.

Hold onto that idea. It reappears, almost word for word, three centuries later.

Act Two: the Mughals split the Iqta into two separate ideas

Most explanations rush past the most interesting part of this whole story. The Mughals didn’t just rename “iqta” to “jagir.” They took the single Sultanate-era iqta system and split it into two distinct components — because Akbar needed something the Sultanate never had: a precise, standardised way to rank an enormous, ethnically and religiously mixed nobility.

That standardisation was the Mansabdari system — every noble held a numerical mansab (rank), graded on a dual zat-and-sawar scale fixing both personal status and the exact size of military contingent he owed. This was Akbar’s genuine institutional innovation: one unified number that worked for a Rajput raja, a Persian émigré, and an Afghan general alike, regardless of background. A mansabdar is simply the title for someone holding one of these ranks — notice it tells you nothing about land at all. That’s the single fact that resolves half the confusion in this whole topic: mansabdar is a rank, not a landholding.

So how did a mansabdar actually get paid? Almost always, through a jagir — a territorial revenue assignment, structurally the direct descendant of the Sultanate’s iqta. The system administering these assignments was called jagirdari. And here’s the detail worth sitting with: the Mughals kept the exact same transferability logic the Sultanate had built a century earlier. Most jagirs — called tankha jagirs — were deliberately reassigned every few years specifically so a mansabdar could never build entrenched, hereditary regional power. Same design instinct as the transferable iqta, just refined with a name and a schedule.

But — and exam-setters love this exception precisely because it’s an exception to a rule you’ve just learned — the Mughals permitted two deliberate departures. A watan jagir was hereditary and non-transferable, retained by regional chiefs (especially Rajput rulers) within their own ancestral territory: a pragmatic compromise that let the Mughal state absorb powerful regional elites without stripping them of authority they already held. An altamgha jagir was rarer still — a permanent, hereditary grant given directly by the emperor to specific favoured nobles or family lines, a deliberate signal of unusual imperial trust. Both exist precisely because they break the transferability rule — which is exactly why they’re worth knowing by name, not filing away as a vague “some jagirs were hereditary” footnote.

If you remember nothing else from this section: Mansabdar is a rank. Jagir is the land that pays for that rank. Jagirdari is the system connecting the two. Almost every confusion between these three terms comes from treating them as three parallel things instead of three parts of one mechanism.

The other half nobody mentions: how was the revenue even calculated?

Here’s where this guide goes somewhere most comparison articles don’t. Assigning a jagir to a mansabdar only solves half the problem — someone still had to work out how much revenue that land was actually expected to produce, because that figure decided the mansabdar’s real income. Akbar tackled this with two assessment methods, and knowing they exist (and that they’re a different kind of system from jagir/iqta) is exactly the sort of connected understanding a PYQ rewards.

The Zabt System physically measured land (using a unit called the jarib) and applied fixed cash revenue rates based on crop yields. The Dahsala System, introduced in 1580 CE, went further — it calculated tax rates from a ten-year average of yields and prices, smoothing out the effect of any single unusually good or bad year. On the ground, the actual collection at district level was the job of the Amilguzar, the chief revenue official at the sarkar (district) level, who assessed and collected what Zabt or Dahsala said was owed.

The relationship to keep straight: Zabt and Dahsala decide how much revenue a piece of land yields. Iqta and Jagir decide who has the right to collect it. A single jagir’s income was very often calculated using exactly this Zabt/Dahsala machinery — the two systems worked together, not as competing alternatives. Treating them as one blurred category is precisely the mistake that costs marks on an assertion-reason question built to test whether you actually know the difference.

Act Three: the Zamindar was never part of this system at all

This is the reframe that trips up the most students, so let’s be direct: the zamindar predates and sits outside the entire Sultanate-Mughal iqta/jagir lineage. A zamindar wasn’t a state-appointed officer the way an iqtadar or mansabdar was. A zamindar was a member of the landed rural elite who already possessed hereditary rights to collect revenue from agrarian land, under Mughal sovereign oversight — but not as a state-assigned salary mechanism.

The category was genuinely broad — everyone from powerful, semi-autonomous regional rajas down to comparatively modest local landholders, all bundled under one administrative label. That internal diversity isn’t just trivia: when the British designed the Permanent Settlement, they took this deliberately broad, locally varied category and flattened it into a single, uniform, hereditary, revenue-collecting landlord class — a colonial simplification of something that had never actually been simple. Knowing the zamindar category existed in this form well before the British arrived, and that the British reshaped rather than invented it, is exactly the nuance that separates a strong answer from a merely adequate one.

The one table you actually need

How this actually shows up in the exam

UGC NET History rarely asks “define jagir” in isolation — that’s too easy to be worth a mark. What it tests is your ability to spot the exception or the relationship: a question naming a specific hereditary jagir and asking you to identify it correctly as watan rather than tankha; an assertion-reason question testing whether you know mansabdar names a rank while jagir names land, not two words for the same thing; a question that expects you to recognise Zabt or Dahsala as an assessment system when everything around it is talking about assignments, and not lump it in with Iqta and Jagir out of habit. Every one of these becomes straightforward once you’re holding the whole arc — assignment systems AND assessment systems — in your head at once, instead of four (or six) disconnected definitions.

Quick recap, in one breath

• Sultanate pays officers with land instead of cash → Iqta, held by an Iqtadar (also called Muqti).
• Mughals split this into a rank (Mansabdar) and the land that pays for it (Jagir, under the Jagirdari system).
• Most jagirs were transferable (Tankha); a few, by exception, were hereditary (Watan, Altamgha).
• Separately, Zabt and Dahsala decided how much revenue any of this land was even worth — a different question entirely.
• Zamindars sat outside this whole state-assignment system, holding hereditary local rights the British later reshaped into the Permanent Settlement.

The next time these terms show up together in a passage, you won’t be reaching for six separate memorised definitions. You’ll already know the shape of the story they’re telling — and which of two very different questions each one is actually answering.