How Indian Commerce Faculties Should Evidence SDG 9 Innovation Claims Without Treating a Startup Cell Poster as Infrastructure

Indian commerce and management faculties can point to a startup cell, a one-day hackathon, a wall of posters, and a list of “industry partners” and call the package SDG 9. The posters are real. The claim is not. SDG 9 — industry, innovation and infrastructure — asks whether the campus built or improved productive capacity, research-to-practice pathways, or shared infrastructure that others can use. A photograph of students holding certificates does not answer that question. This briefing is a playbook for IQAC cells, commerce heads, and entrepreneurship cells that must evidence innovation work without treating a poster or a placement offer as infrastructure.

The setting is Indian higher education after the proliferation of startup cells, the NIRF innovation ranking, NAAC’s emphasis on extension and industry interface, and the quieter pressure of impact-ranking forms that now invite an SDG 9 paragraph. The same discipline applies to an affiliating university reviewing a college’s self-study and to a department that wants one honest industry linkage rather than twelve dormant ones. SDG 9 is not a public-relations target. It is a means: relationships and assets that move teaching, research, or local productive capacity toward the other goals.

1. Why a startup-cell poster is not an SDG 9 claim

Target language under SDG 9 is about resilient infrastructure, inclusive and sustainable industrialisation, and fostering innovation. A commerce faculty is not a ministry of industry, and it should not pretend its startup-cell register is an industrial policy. It is, however, an institution that runs courses, hosts projects, places students, and occasionally builds labs or tools. The error is to collapse all of that into one integer: number of events, number of posters, or number of “startups incubated.”

Three failures follow. First, the denominator is undefined. Is a one-day idea pitch the same as a multi-month mentoring relationship? Is a departmental poster the same as a university-recognised incubation slot with space, mentor hours, and a signed agreement? Is an expired MoU still “active” because the logo remains on the website? Second, the numerator has no activity test. A hackathon that produced no working prototype or follow-up scores the same as a tool handed to a cluster of small firms. Third, the claim migrates. The prospectus says “innovation ecosystem.” The ranking form says “SDG 9.” The peer team asks for one beneficiary outside the campus and the room goes quiet.

A foreign accelerator logo is scarce, so it is displayed. A local industrial cluster or MSME association is abundant, so it is under-counted. SDG 9 does not rank a partner by brand prestige. It asks whether the relationship or the asset added productive capacity the campus or its partners did not already have. A commerce department that co-designs a simple inventory tool with a cluster of small retailers, trains the owners, and leaves the tool in their hands can be a stronger file than a dormant national-level incubator logo.

Further reading on DrDPKlass: how campuses can map programmes to SDGs without SDG-washing and how universities should evidence SDG 17 partnerships. Innovation claims sit next to both files. An industry MoU that never produced a shared tool or a curriculum change is the same error as a startup-cell poster counted as infrastructure.

2. Separate the three objects SDG 9 actually names

A single “innovation” column hides unlike objects. Split the register before you write the narrative. The split is administrative, not rhetorical. Different objects create different evidence, different risks, and different links to the rest of the SDGs.

Write the object on the register before you write the SDG code. A single activity can serve more than one goal, but it must serve one primary goal with a sentence a stranger can test. “Supports innovation and all SDGs” is a refusal to choose. A commerce faculty’s work with a regional MSME cluster on digital bookkeeping might primarily serve SDG 8 or SDG 9, and only secondarily SDG 17 as the means. Say that. Means and ends are not the same row.

Expiry and dormancy belong in the register. Indian startup-cell “partners” often appear on a website for years after the single event. The live file should carry a status: active with activity this year, dormant, or ceremonial. Ceremonial means the logo and the poster exist; the activity does not. Both can be listed in an annex. Neither belongs in the headline count.

3. Build an activity–output–outcome ladder the file can defend

Innovation and infrastructure evidence has three rungs. Activity is something that happened: a mentoring session, a lab booking, a joint workshop, a data-cleaning exercise with a partner. Output is an artefact: a working prototype, a curriculum module approved by the board of studies, a simple tool or checklist handed to firms, a usage protocol for a shared lab. Outcome is a change you can describe without inventing an industrial miracle: students who can demonstrate the skill, firms that used the tool for a stated period, or external users who booked the facility. Most campus files stop at activity and call it outcome. The honest file labels the rung.

Take a familiar commerce example. A department runs a three-Saturday clinic with a local traders’ association on simple digital invoicing and inventory tracking. Activity is the three sessions, with attendance and a partner confirmation. Output is a one-page checklist and a shared Google Sheet template, filed with the association and translated into the local language. Outcome, if you have it, is the number of traders who continued to use the template after the clinic, counted by the association, not estimated by the department. If the association will not share that count, stop at output. The SDG 9 sentence is then: we built a short, repeatable pathway that left a usable tool with local firms. That is an innovation linkage. It is not an industrial-policy claim.

Research or project work needs the same ladder. A student dissertation that analyses a firm’s data is an activity and, if finished, an output for the student. It is not, by itself, an innovation pathway unless the firm received a usable summary or the method entered the curriculum. List the work package: who cleaned data, who had permission, who holds the file after the semester ends. Citation of the dissertation in the department newsletter is not evidence that the firm gained a tool.

If the only shared object is a poster, a certificate, and a photograph, you have a ceremony. Ceremonies can open doors. They are not the innovation claim.

4. Treat industry linkages without counting placement offers as innovation

Placement season produces many visiting cards and offer letters. A single pre-placement talk or a list of companies that visited is not an industry linkage for SDG 9. A multi-year relationship in which the firm co-designs an applied module, shares a redacted dataset under a written agreement, hosts supervised projects with a learning plan, and receives a usable output is a linkage. Write the learning plan and the output into the evidence pack. Offer letters show recruitment. They do not show that the faculty contributed anything but a list of names.

Industrial visits fail in the same direction. A one-day bus trip to a plant can be excellent exposure. It becomes SDG 9 evidence only when it is part of a sequence: pre-visit briefing, structured observation task, post-visit analysis that feeds a course or a partner report, and a record that the partner received the analysis. Without the sequence, the visit is teaching. Teaching can be excellent. It is not automatically infrastructure or innovation.

Local industry is the under-used partner in colleges far from a metro and in districts with MSME clusters. A commerce faculty that helps a small-manufacturing association read its own working-capital cycles, or that places students with a cooperative for a supervised review of member accounts under a written protocol, is doing SDG 9 work tied to SDG 8 or SDG 1. The risk is extraction: students collect data, the department publishes a brochure, and the association never receives the analysis. The evidence standard is a handover note signed by the partner, with the campus copy filed. No handover, no outcome claim.

Language and accessibility belong in the note. If the work with local firms operates only in English while the owners work in a regional language, do not claim reach you did not resource. If materials were translated or explained in the local language, file the translation or the session plan.

5. Show the infrastructure you actually built, maintained, or shared

SDG 9 infrastructure claims on a campus are usually modest and should stay modest. A computer lab, a licensed statistical package, a shared repository of redacted firm data, or a simple maker corner can be infrastructure if it is used, maintained, and preferably open to users beyond the single course that justified the purchase. A room that exists on the floor plan but is locked except on inspection day is not shared infrastructure. A software licence that sits unused is not innovation capacity.

The evidence standard is a usage log or a booking record for the reporting year, plus a short note on who maintains it and how external or cross-department users are admitted. If the only users are the students of one elective, say so and claim it as teaching infrastructure, not as a campus-wide SDG 9 asset. If other departments, a neighbouring college, or local firms used it under a protocol, that is the stronger claim. File the protocol.

Physical and digital infrastructure both need maintenance evidence. Indian campuses often photograph the inauguration and then lose the log. The peer team that asks “who used this last month and who fixes it when it breaks” will not be satisfied by the ribbon-cutting picture. Keep a simple monthly or semester log. It does not have to be elaborate. It has to exist before the inspection.

Shared research infrastructure follows the same logic. A dataset the faculty cleaned and documented, with a data dictionary and a clear access rule, can be infrastructure if other researchers or students can request it. A private folder on a faculty member’s laptop is not. Write the access rule. If the data are restricted, say so and stop at the internal-use claim.

6. What NAAC, NIRF, THE Impact and a peer team will actually ask

Peer teams and ranking forms ask concrete questions. They do not ask for the number of posters. They ask for one or two examples they can open. Prepare the file so that any of the following can be answered in under five minutes with a document, not a speech.

• Name one industry or community partner with whom the faculty had repeat activity this year. Show the dates, the artefact, and the partner’s confirmation.
• Show one student or faculty project that left the classroom. What was handed over, to whom, and on what date?
• Open the usage or booking log for the lab, licence, or shared tool you claim as infrastructure. Who used it last month?
• Show the curriculum change, if any, that resulted from the industry or innovation work. Board-of-studies minutes or the revised syllabus page are the evidence.
• Explain the status of every logo on the startup-cell wall or website. Active, dormant, or ceremonial?

NIRF innovation metrics and THE Impact SDG 9 indicators reward documented activity, outputs, and external engagement more than event counts. NAAC peer teams increasingly ask for the beneficiary or the artefact rather than the photograph. An honest, thinner file survives better than a thick ceremonial one. If the only evidence is the poster and the group photograph, do not claim the row. Move it to the annex of aspirations or teaching activities.

Conflict and credit belong in the note as well. If a firm sponsored the event, say so. If faculty or students hold equity or a consultancy interest in a claimed “startup,” disclose it. An undisclosed interest that surfaces later damages the entire SDG file.

7. Field checklist and closing brief

SDG 9 on an Indian commerce campus is usually modest, local, and practical. That is a strength, not a weakness. A short series of clinics that leave a usable tool with local firms, a lab that is actually booked and maintained, or a curriculum module co-designed with a partner and assessed for skill — these are defensible claims. A wall of posters and a list of companies that once visited are not. Build the register, label the rungs, and keep the ceremonial material in the annex. The peer team, the ranking form, and the next academic year will all be easier to face.

The same discipline that prevents SDG-washing on other goals applies here. Do not retrofit keywords onto ordinary teaching and call it innovation infrastructure. Do the smaller, documented thing. File the artefact. Then write the paragraph.