Imagine that the emperor appoints an officer, gives him a high rank and orders him to maintain cavalryโsoldiers who fight on horseback. The order creates status and an obligation. It does not by itself provide horses, pay soldiers or produce grain and money. For that, the officer needs a salary, and the state needs information about resources that can support it.
Most high officers received either cash or the right to collect a specified amount of revenue from an assigned area. That claim still had to pass through provincial officials, local records, zamindars with older landed, military or revenue claims, village headmen and cultivators. The amount written in an account might not be the amount actually collected. An imperial appointment therefore became working government only through a chain of people, information and enforcement.
The basic sequence was:
- the court appointed and ranked a servant;
- the rank carried pay and an expected service;
- pay came in cash or through an assigned revenue claim;
- officials assessed what an area was expected to provide;
- local actors tried to collect, record and transfer resources; and
- reports, inspection, audits, transfers, negotiation or resistance revealed what actually happened.
This chain is the key to the Mughal state. Its three essential separations are simple: rank was not land, assessment was not collection, and an imperial order did not implement itself.
Different records show intended order and actual results
The Mughal court produced an unusually detailed record of government. The Ain-i Akbari, compiled by Abu'l Fazl under Akbar, classified offices, ranks, regulations, provinces and assessed revenue. It shows what the court wanted to know and how it presented an orderly empire. Its detail is invaluable, but it gives strongest visibility to the imperial centre and Akbar's reign.
Even the Ain does not supply equally complete information for every province. Its totals often describe assessment or authorised strength, not money received or soldiers present. A number written in a court table is therefore evidence of an official claim before it is evidence of an achieved result.
Chronicles explain appointments, campaigns, conflicts and policy from particular court positions. Orders can establish that a ruler commanded an action. Account papers can show a specific assessment or payment. Regional records and episodes of negotiation or rebellion reveal how an arrangement worked away from the court.
These records answer different questions. A careful reader separates four levels: the rule that was announced, the mechanism intended to carry it, the people who implemented or resisted it, and the result that surviving evidence can demonstrate. That evidence rule prepares the first major institution: mansab, the ranking of imperial service.
A mansab ranked a servant without granting land
The Persian word mansab means position or rank. A person holding one was a mansabdar. The rank placed that person within the imperial service ladder, helped determine pay and signalled the level of service the court could demand.
A mansab did not make its holder the private owner of a territory. Nor did it mark a hereditary caste. The emperor could appoint, promote, reduce, transfer or dismiss a mansabdar. In practice, family influence and inherited connections mattered, but a son did not automatically inherit his father's exact rank as a legal right.
The same rank system covered both non-military government work and military command. A mansabdar might command troops, govern a province, manage finance, supervise a court task or lead a campaign. The numerical rank gave the court a common way to order servants whose actual jobs and political backgrounds differed.
Akbar regularised this system while widening imperial service. Central Asian and Iranian nobles, Indian Muslims, Rajput rulers and other regional elites could all hold rank. Their inclusion did not erase competition or make every group equally powerful, but it connected varied political networks to one court service ladder.
Rank also gave the emperor a way to compare servants who came from different political settings. Promotion could reward service, bind a regional ruler more closely to court or change the balance among noble groups. Reduction or removal could punish failure, but using that power still depended on the emperor's ability to enforce it.
Mansabdars did not form one uniform body of officials. They brought households, followers, kinship ties and regional connections into imperial service. The system ordered those relationships without dissolving them. A common rank scale could therefore strengthen court coordination while noble coalitions remained politically important.
Zat and sawar separated personal rank from cavalry obligation
Mansabs came to be expressed through two numbers. Zat indicated the holder's personal rank, status and pay position. Sawar indicated an authorised cavalry obligation and the payment attached to maintaining it.
Suppose an officer held a zat rank higher than his sawar rank. His place in the service ladder followed zat; sawar did not replace it. The two numbers allowed the court to change a servant's cavalry responsibility without always changing his personal rank.
The distinction also helped calculate salary. Personal pay followed zat, while the cavalry component had to support horses, riders, equipment and upkeep. Sawar money was therefore tied to an expensive service claim, not simply added wealth with no expected use.
The printed number was still an authorised claim, not a photograph of a camp. A mansabdar might be required to maintain a certain contingent, or troop group, but actual strength depended on recruitment, horse quality, pay, distance, campaign losses and inspection. Court service joined status to military capacity without making the two identical.
Inspection tried to connect paper numbers to real forces
At a muster, an inspection of troops, the court used dagh, the branding of horses, and chehra, a descriptive roll of soldiers, to check contingents. Officers responsible for military appointments examined men, animals and equipment. These procedures tried to prevent one horse from being presented repeatedly or a salary claim from resting on soldiers who did not exist.
Inspection did not eliminate evasion. Musters occurred at particular times, records could lag behind events and distant campaigns changed numbers quickly. The Mughal court nevertheless knew that a paper obligation needed checking and built repeated inspection into the service system.
The emperor relied on mansabdars, yet also tried to prevent any one service network from becoming permanently independent. Rank changes, transfers, divided offices and direct reporting were ways to manage that dependence. Mansab explained what a servant was owed and expected to do; the next question was how the servant would be paid.
A jagir paid service through revenue, not landownership
Some mansabdars received cash salaries. Many more received a jagir: an assignment authorising them to collect a specified amount of revenue from an area instead of drawing the same salary entirely from the treasury. The holder was a jagirdar, but the assignment did not give him ownership of all soil, houses or people there.
A jagir transferred a revenue claim. Cultivators retained their productive role and various rights in land. Zamindars and village communities could possess older local claims. Imperial regulations limited what the assignee was formally entitled to collect, even when power and distance made practice harsher.
Land whose revenue was reserved more directly for the imperial treasury was called khalisa. Khalisa did not mean empty land governed without local actors. It described where the principal revenue claim was directed. Cash salaries, khalisa receipts and jagir assignments formed different ways of connecting resources to court and service.
The proportion of revenue directed through khalisa or assignments changed over time. The treasury needed direct income for the household, cash salaries, war and other expenses, while mansabdars expected assignments matching their pay claims. Moving revenue between these channels was a political and financial choice, not a permanent division of the map.
Jagirdars normally used revenue agents to pursue authorised collections. Provincial finance officers were expected to inspect accounts and protect imperial rules, while military officers could help when collection met armed resistance. These checks did not remove coercion, but they show that a jagirdar was not formally sovereign inside his assignment.
Salary assignments and homeland interests were not the same
A transferable salary assignment is often called a tankhwah jagir. The court could move its holder from one assignment to another. Transfer was meant to stop a jagirdar from turning temporary revenue rights into an independent hereditary base.
A watan jagir had a different relationship. It was tied to the homeland interests of a ruling family or lineage, especially in the case of regional houses incorporated into imperial service. A Rajput ruler might hold recognised rights in his home territory while also receiving a transferable salary assignment elsewhere. Watan did not mean complete independence, but it could preserve a stronger lineage connection than an ordinary salary jagir.
By recognising a ruling family's hereditary home interests, the court could recruit that family without claiming that its older regional authority had disappeared. It could also make succession within a regional house an imperial concern. Court confirmation and lineage legitimacy could reinforce each other while still producing conflict over who would inherit local authority.
One person could therefore hold several relationships at once: mansab as imperial rank, a tankhwah jagir for salary and inherited authority in a watan. The terms must remain separate even when they met in the same career.
A paper salary could exceed real income
The court matched a salary claim to the recorded value of an assignment. Jama meant the assessed or expected revenue written in the accounts. Hasil meant the amount actually realised. A jagir with a high jama could still produce a lower hasil because of poor harvest, war, resistance, faulty records, collection costs or an assessment that was too optimistic.
This gap affected both state and servant. The mansabdar might not receive the income on which his rank and contingent rested. The court might then face weak military performance, requests for a better assignment or competition among nobles. Local society could face stronger short-term efforts to extract the missing amount.
Transfers created a real trade-off. They limited the chance that a jagirdar would build an unchallengeable local base. They could also discourage long-term care if the holder expected to leave soon and tried to maximise immediate collection. Neither outcome occurred everywhere, because assignment quality, tenure, local power and official supervision varied.
Jagir therefore linked the service ladder to farming resources, but it did not complete the chain. Before anyone could collect a demand, the state had to estimate what land and production could provide.
Revenue assessment turned production into a state demand
Land revenue supplied much of the money and produce that sustained the court, army and assignments. The state first needed information about cultivated area, crops, expected output and prices. It then converted that information into an assessed demand and tried to collect it.
Assessment and collection formed separate stages. Measurement could be incomplete. A crop could fail after a rate was fixed. A local power could block an official. A cultivator might pay in instalments, negotiate, borrow, flee or resist. The jamaโhasil gap was therefore part of the revenue system, not merely an accounting mistake.
Zabt used measurement and rates where records could support them
Zabt was an information-intensive arrangement that joined measurement of cultivated land to crop and value estimates and a scheduled revenue demand. It helped officials calculate a cash claim without physically dividing every harvested crop. This made records, survey work, price information and trained staff especially important.
Under Akbar, the dahsala arrangement used information averaged across a series of years to support more stable cash rates. It reduced dependence on the yield or price of one unusual season. Raja Todar Mal was an important finance official associated with this work, but the system grew through accumulated experiments, records and many officials; it was not invented instantly by one person.
Dahsala did not mean that one cultivator simply signed a ten-year lease at an unchanging amount. The multi-year information helped officials construct rates. Actual demand still depended on measured area, crop category and the conditions under which assessment and collection occurred.
Zabt did not cover the whole empire in one uniform way. It worked best where fields could be measured, crops and prices recorded, and cash schedules made practical. Floodplains, forests, hills, pastoral zones, frontiers and contested regions could present different problems.
The state also distinguished regularly cultivated land from land left fallow for shorter or longer periods. These categories connected productive history to demand because an assessment required a judgement about both area and likely capacity.
Officials also used estimation of a standing crop, often called kankut, or forms of crop sharing generally called batai. In crop sharing, state and cultivator divided produce or an agreed share after harvest. Each method required information and supervision, but the timing and risks differed.
Estimation could avoid measuring and dividing every harvested bundle, but it created disputes over predicted output. Crop sharing tied the claim more closely to an actual harvest, yet it required presence, storage and trusted supervision. Regional flexibility was therefore a response to different conditions, not proof that administration lacked rules.
Cash payment was often encouraged because the court and many assignments used money accounts. Payment in kind nevertheless remained possible. A cash rate did not prove that every village had easy access to markets or that all cultivators experienced the demand equally.
The revenue system tried to make production recorded and comparable. It could also impose severe pressure. High demand, poor harvest, official coercion and debt could reduce cultivators' ability to continue production. A revenue system that damaged its productive base also weakened the resources on which mansab and jagir depended.
Assessment still needed people to implement it. That takes the story from the method of calculation to the division of work between court, province and locality.
Government divided tasks so one officer did not control every link
The emperor stood at the head of appointment and policy, but he could not personally examine every account, horse or village. The court therefore divided major tasks. This division created expertise and also allowed one channel to check another.
The wakil could exercise broad authority on the emperor's behalf. Bairam Khan's regency showed how powerful that position could become. After ending the regency, Akbar reduced the chance that one wakil would again combine such wide control and strengthened more specialised lines of work.
The chief diwan supervised revenue and finance. The mir bakhshi handled military appointments, rank papers, pay claims and muster. Correspondence and news channels carried orders and reports. Other officials supervised justice, religious or charitable grants, and supplies for the imperial household.
The sadr oversaw charitable or revenue-free grants and religious matters, while qazis handled judicial functions in particular settings. The mir saman supervised supplies, storage and production for the imperial household. These tasks mattered because a court consumed goods, distributed patronage and judged disputes as well as collecting revenue and commanding troops.
Information had its own political value. News writers and postal channels could report provincial events without relying only on the governor's version. Multiple reports might conflict, arrive late or serve factions, but the court's demand for parallel information reveals the problem it was trying to solve.
These were not modern ministries with fixed boundaries for all reigns. Titles, influence and personal access changed. Finance, military service, information and household supply did not automatically belong to one all-powerful minister.
Provinces repeated the separation of command and finance
The large provincial unit was the suba. Its governor, often called the subadar, handled political command, security and military responsibilities. A provincial diwan supervised revenue and accounts through a separate line of appointment.
This separation tried to stop a governor from controlling both armed force and all provincial finance without scrutiny. A provincial bakhshi checked service and troops, while news reporters sent information towards the court. Their presence did not guarantee balance, but it created more than one route through which the emperor could learn about a province.
The governor and diwan could cooperate, compete or appeal against each other. Both depended on local knowledge and on support from people whose careers connected province to court. Divided authority offered a check, but it could also slow action or turn an administrative dispute into noble politics.
Subas were divided into smaller revenue and territorial settings, commonly sarkars and parganas, with villages below them. These units helped organise records and responsibility. They did not form a perfectly identical grid, because an officer's working area could cross a boundary and local arrangements differed.
Collection joined force, accounts and village knowledge
A faujdar supplied military force and helped maintain order across a regional area. An amil or amalguzar dealt with assessment and collection. When payment met refusal or armed opposition, revenue and military tasks could meet directly.
At the pargana level, the qanungo kept revenue records and local precedent. In a village, the muqaddam or headman connected officials to residents, while the patwari maintained village accounts. These actors possessed local knowledge that a distant court could not manufacture on demand.
Many local functions rested on existing social authority rather than on strangers sent from the capital. A village headman or zamindar might cooperate because collection confirmed status and provided a share. The same local position could support resistance when imperial demand threatened older interests.
Their jobs also created power. A record keeper could shape what became visible. A headman could distribute or conceal burdens. A collector could negotiate, threaten or take more than authorised. Formal position tells us who was supposed to act; particular evidence must show what that person did.
This layered arrangement explains why Mughal government could reach widely without becoming uniform. Court appointment, provincial checks and local knowledge worked together, but so did delay, bargaining and resistance. Zamindars stood at the centre of many of those local relationships.
Zamindars were local powers, not jagirdars by another name
The term zamindar covered a broad Mughal-period category, not one identical social class across India. It could refer to people with lineage authority, landed property, claims to collect revenue, armed followers or political influence over one village, several villages or a much wider territory.
A jagirdar received a salary assignment from the imperial system. A zamindar's local claims could be older, inherited, purchased, conquered or confirmed by the state. Some zamindars also entered imperial service and received mansab or jagir. Holding more than one role did not make the terms synonyms.
Zamindars could possess personal land called milkiyat, which they could sell, mortgage or pass to heirs. They might receive a share or fee for collecting revenue, maintain forts and armed retainers, help settle cultivators, extend cultivation and establish local markets. These activities gave them resources independent of a single court appointment.
Zamindari rights could grow through inheritance, purchase, state confirmation, conquest or the settlement of new land. Clan and caste networks sometimes helped lineages join small claims into a wider regional base. This history explains why a court could recognise a zamindar without having created that person's power from nothing.
The scale of power varied sharply. A village-level claimant and a regional ruling chief could both appear under the label. Clan connections, caste status, military force, control of records and imperial recognition all influenced their position. The category should begin a question about local power, not end it.
Zamindars could assist collection and provide troops. They could also delay payment, bargain for favourable terms, shelter resistance or lead rebellion. Imperial confirmation might strengthen a local lineage even while bringing it into a larger state network.
Their relationship with cultivators was not simply harmonious or hostile. Zamindars drew resources and could impose exploitation. Some also supplied credit, protection, settlement support or access to markets. Cultivators sometimes joined zamindars against state officials when their interests overlapped, while at other times they resisted local demands.
The state often needed a zamindar precisely because he could mobilise local people and resources. That capacity also made him dangerous when he withheld revenue or organised armed opposition. Service and rebellion were not permanent identities; the same lineage could move between negotiation, rank, conflict and renewed recognition.
Cultivators remained the indispensable producers behind every account. Officers and assignees could redistribute claims, but they could not collect crops that were not grown. The state therefore depended on people whose burden and local knowledge also gave them ways to negotiate, evade or withdraw.
The court extended its reach by ranking local and regional elites, confirming selected claims and placing them inside reporting and revenue relationships. Imperial reach could widen while local bargaining remained powerful.
The institutions changed as service and resources changed
Mansab and jagir were not fixed once under Akbar. Later rulers adjusted them because court politics, warfare, revenue and the number of claimants changed.
Nor did Akbar create every element from nothing. Earlier Sultanate and regional states had used ranked service, revenue assignments, measurement, records and local collectors. Mughal rule reorganised these practices on a larger scale and joined them to a distinctive numerical service ladder.
Jahangir used du-aspah sih-aspah for selected mansabdars. The device increased cavalry responsibility and payment without requiring the same increase in zat. It let the emperor strengthen chosen servants while preserving distinctions within the personal-rank ladder.
Under Shah Jahan, officials used month-based classifications to address the difference between an assignment's jama and its likely hasil. A jagir expected to yield only part of its paper assessment could not support the same real obligation as one whose revenue was fully realised. The adjustment recognised a problem the accounts could not solve merely by repeating the larger number.
Service requirements also became flexible in practice. The actual contingent demanded at a particular place could be lower than the fully authorised sawar rank, especially when distance, assignment yield and campaign conditions intervened. This did not make sawar meaningless; it shows why authorised obligation and verified performance must remain separate.
Aurangzeb's reign continued the system and added conditional cavalry obligations often called mashrut. At the same time, long warfare and wider territorial claims increased the number and cost of servants who expected payment. Recently conquered or contested regions did not instantly produce stable revenue.
โJagirdari crisisโ names a problem that still needs explanation
Historians use jagirdari crisis for late-seventeenth-century pressure within the assignment system. The phrase becomes useful only when its parts are stated. Salary and service claims increased; good assignments were unequal; jama could exceed hasil; transfers caused competition; war disrupted collection; and zamindars or regional powers could redirect resources.
An apparent shortage was therefore not only a shortage of acres on a map. The problem concerned assignments capable of producing usable revenue under current conditions. A recently conquered district with an impressive assessment but continuing warfare might be less valuable than its record suggested.
These pressures could encourage nobles to seek better assignments and jagirdars to intensify short-term collection. They could weaken military performance when expected income did not arrive. They could also shift greater burdens onto cultivators and deepen local resistance.
The problem did not look identical everywhere, and it did not by itself cause the Mughal Empire to collapse. Political succession, prolonged war, regional state formation, policy choices and local economies also mattered. The court's promise of rank and service remained durable only while real resources could be connected to it.
Judge the state by the whole chain
The Mughal state combined strong imperial claims with repeated dependence on other actors. The emperor appointed and ranked servants. Mansab joined status, pay and service. Jagir connected many salary claims to farming revenue. Assessment systems tried to turn changing production into comparable accounts. Provincial and local officers carried finance, force, records and information. Zamindars and cultivators supplied indispensable local power and production.
None of these links worked alone. A high mansab without income could not sustain service. A rich jama without hasil could not pay a contingent. A revenue schedule without local knowledge could not collect itself. A transfer order could limit one noble while strengthening another local broker. The court could supervise a wide empire only by working through provincial officers, zamindars, village headmen and cultivators who retained their own knowledge and bargaining power.
For any Mughal institution, ask six questions:
- Who appointed or ranked the actor?
- What service or payment was claimed?
- Which cash or assigned revenue source was expected?
- Who assessed, recorded, collected and enforced the demand locally?
- What evidence shows the intended rule became an actual result?
- What changed across region or reign?
This method prevents a title, regulation or court table from being mistaken for functioning government. Mughal power lay not in a perfect bureaucracy but in the repeated effort to connect rank, resources, information and local relationships across a very large and changing empire.