• Twitter
  • Facebook
  • Google+
  • LinkedIn

Information Display Policy

 General Information

  1. Please inform about errors and omissions in the website content.  The email should be sent from an IITB email account.
  2. Each department or division should identify a Student/Staff and a Faculty, who will create and approve textual material for the News, Events, and Awards section (see Roles below for detailed information). These persons will be given special permission in the website to directly upload the content and initiate the approval chain online.

Types of Content

IIT Bombay Website has the following types of content, and its approval hierarchy for publication in the web.



Who can Submit Info?

Who Approves ?

Basic Page, Article

A static information page about the general activities of the Institute, organised within the Site Map

Deputy Registrars, HoDs, Deans

Registrar, Deputy Directors, Director as appropriate.

Breaking News

A short article or a press release of immediate relevance

Content Creators

Content Publishers


Upcoming Academic/Social event

Content Creators

Content Publishers


A detailed account of a recent News or Event

Content Creators

Content Publishers


Honorary Awards given to Faculty, Staff, and Students

Content Creators

Content Publishers

Job Vacancy

Faculty and Staff job advertisements

Admin-1, Admin-2 Staff

Pre-approved advertisement


Purchase tenders

Admin-2, MM Staff, Estate Office Staff

Pre-approved advertisement

Gallery Picture

Beautiful and representative photographs of IITB and related activities

Content Creators

Content Publishers

Annual Report

PDF copy of the Institute Annual Report

PRO office

Pre-approved Report

RTI Query

Soft copies of replies to RTI queries

Legal Cell

Pre-approved document

Hindi Content

Translation of the above content where applicable

Hindi Cell Staff

Hindi Officer

Content Creators, Editors, and Publishers

For generic variable content three categories (roles) of people will be identified, who will create and moderate the information that is published. The persons identified to act in each role need to be approved by the respective heads of department/division/section. The webmaster will then assign the roles against their LDAP ID. The following chart summarises the flow of the document through various states and who is authorised to change the states.



Who are they ?

What information can they Moderate ?

Content Creator

Students or staff identified by the respective heads of department, section, or division.  They need to have a reasonable command over the English language, and can express in it clearly.  They lookout for information related to a News worthy item, Event, or photographs. and upload it.

They cannot moderate, but only create fresh information either in a ‘Draft’ state or submit it for ‘Review’.

Content Editor

Permanent senior staff or faculty identified by the respective heads of department, section, or division.  They will need an excellent command in English and need to have a broad perspective of the appropriateness of the information being put up.

They have to ‘Review’ the contents, carry out minor edits if required and keep it in ‘Copy Edited’ state ready for publication.  They can also send it back to ‘Draft’ state if it requires major changes from the ‘Content Creator’

Content Publisher

PRO or the Webmaster or the Design Expert (as appropriate for the type of content)

They usually accept all ‘Copy Edited’ content, after ensuring general guidelines of publication and branding are followed.  On rare occasions, the articles can be sent back to the ‘Review’ stage for the ‘Content Editor’ to have a relook.

  1. An Editor can view the contents created by all Creators, not necessarily in their own department. Therefore the creators are requested to send a link by email to the Editor of their division requesting them to approve the ‘Review’.

  2. Similarly if at all an article is sent back to ‘Review’ by the Publisher, they need to send an email informing them of the requirement of a change.

  3. Since the extent of content transaction is likely to be small, unlike large volume OPS or Drona approvals, the backend logic is kept simple without identifying and linking the departments of the Creators and Editors.