ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

The Mauryan Administration

Updated on December 23, 2012

As contrasted with the earlier smaller kingdoms, the Mauryas ruled over an empire. By now, the powers of the king had also increased rapidly. A study of the Arthashastra in conjunction with the edicts provides information regarding the administrative structure. At the centre of the structure was the king who had the power to enact laws. According to Indian thought, the chief function of the king was to maintain social order. There was a council of ministers or mantri-parishad to advise the king and at times this may have acted as a political check. But the powers of the council were limited owing to the fact that it was the king who appointed the ministers in the first instance. Three qualities of a minister that the Arthashastra stresses are those of birth, integrity and intelligence. It is likely that the ministers may have belonged to the two higher castes.

Two of the key offices in the central administration were those of the Treasurer and Chief Collector. The Treasurer was responsible for the storage of the royal treasure and of the state income both in cash and kind. The Chief Collector, on the other hand was responsible for the collection of revenue from various parts of the kingdom. The Arthashastra provides a detailed list of the sources of revenue. These include revenue from cities, land mines, forests, roads, tolls, fines, licences, manufactured products, merchandise of various kinds and precious stones. Expenditure from the treasury was on two major counts; salaries of officials and public works. Here again we do have some idea of the relative salaries as the Arthashastra includes a break-up of the wages paid to officials. Expenditure on public works would have been largely in the construction and maintenance of roads, wells and rest-houses, as well as major irrigation works such as the dam on the Sudarshana lake. The other major expenditure was on maintaining a standing army.

Apart from the metropolitan areas which were directly governed, the empire was divided into four provinces, each under a prince or a member of the royal family. The terms used in the inscription are kumara and aryaputra. Under Ashoka, there were four provinces; the northern province with the capital at Taxila, western province with the headquarters at Ujjain, eastern province with the centre at Tosali and the southern province referred to as Suvarnagiri. The viceroy had the power to appoint some of his officials such as the mahamattas who went on tour every five years. As several officials are referred to by the term mahamatta, their precise function remains uncertain. A new type of mahamatta frequently mentioned as the Dhamma-mahamatta was the service started by Ashoka in his fourteenth regional year.

Provinces were subdivided into districts for purposes of administration and groups of officials were in charge of a district. One of these was the rajuka responsible for surveying and assessing land In fact, the IV Pillar Edict of Ashoka is entirely addressed to the rajukas. They are advised on their behaviour towards the people and the rules guiding reward and punishment. A further smaller unit of administration was the village and two important officials concerned with the administration of the village were the gopa and the sthanika. It seems that these officials were directly responsible for the collection of revenue and were recruited from the local populace. The names of the gopa and the sthanika do not appear in the list of salaried employees and it has been suggested that they were perhaps permitted to keep a part of the revenue collected in lieu of salary. The evidence from the peripheral regions, especially the southern district, indicates that it was the clan chiefs who acted as intermediaries with the Mauryan state. After the decline of the Mauryas, these chiefs asserted their independent status and adopted the title of Mahabhojas and Maharathis. In this system of administration, there was greater uniformity at the upper levels, whereas the system was more decentralised at the local level.

An important tenet of the Arthashastra is that the king should be accessible to his subjects at all times. In addition, it lays down that the king should maintain an elaborate network of spies to inform him regarding the functioning of his officers. Ashoka's edicts suggest that he did follow this advice, though his espionage system was not as complex as envisaged by Kautilya. In the Girnar Rock Edict, he states that his reporters are to have access to him no matter where he is; whether eating or relaxing or in the park. It would seem that the reporters were an important means through which the ruler learnt about public opinion.

Among the other officials' mentioned in Ashokan inscriptions are those connected with the administration of the city and those who worked among the frontier peoples. The Arthashastra mentions the nagaraka or city superintendent who was responsible for the maintenance of law and order in the city. Megasthenes, on the other hand, describes a more elaborate system with the officials divided into various committees. Such a system may have worked for the capital city of Patliputra, but is unlikely to have been in existence in other parts. The fact that Ashoka had a separate set of officials for the administration of the frontier peoples indicates the importance that he attached to building up loyalty and mutual trust among the people inhabiting the border areas. Elsewhere in his edicts, Ashoka states that he established centres of medical treatment for men and animals in neighbouring countries. In addition, there were the officials referred to as Dhamma mahamattas. One of their functions was to record gifts and donafions made to religious establishments. But we shall discuss this in greater detail in a subsequent section. The expansion of the empire under the early Maurya rulers meant that due importance had to be paid to the army. Both Kautilya and Megasthenes describe the administration of the army at great length. The state maintained a large standing army which by all accounts, was well paid and well looked after.

Finally, the distinction between the upper and lower levels of Mauryan administrative organisation should be stressed. In its upper levels it was centralized and uniform. The upper ranks were chosen directly by the king and paid high salaries. At the lower level, the picture was very different and control was far more decentralised. There was a substantial drop in salaries of the lower levels and many of these would have been local appointees.

working

This website uses cookies

As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://corp.maven.io/privacy-policy

Show Details
Necessary
HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
LoginThis is necessary to sign in to the HubPages Service.
Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
AkismetThis is used to detect comment spam. (Privacy Policy)
HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
Features
Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
MavenThis supports the Maven widget and search functionality. (Privacy Policy)
Marketing
Google AdSenseThis is an ad network. (Privacy Policy)
Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
Index ExchangeThis is an ad network. (Privacy Policy)
SovrnThis is an ad network. (Privacy Policy)
Facebook AdsThis is an ad network. (Privacy Policy)
Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
AppNexusThis is an ad network. (Privacy Policy)
OpenxThis is an ad network. (Privacy Policy)
Rubicon ProjectThis is an ad network. (Privacy Policy)
TripleLiftThis is an ad network. (Privacy Policy)
Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
Statistics
Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)
ClickscoThis is a data management platform studying reader behavior (Privacy Policy)