How Indian Universities Should Evidence SDG 17 Partnerships Without Counting an MoU as Impact

Indian campuses can produce a thick folder of memoranda of understanding in a single academic year. A district college signs with a local bank. A state university signs with a foreign faculty it has never hosted. A private institute signs with an industry association whose only shared artefact is a photograph. SDG 17 — partnerships for the goals — is then claimed as the count of those signatures. The count is real. The partnership is not. This briefing is a playbook for registrars, IQAC cells, and commerce or management faculties that must evidence collaboration without treating a scanned MoU as impact.

The setting is India after NAAC’s emphasis on extension and collaboration, the spread of impact-ranking submissions, and the quieter pressure from state higher-education councils that now ask for “SDG mapping” in annual quality reports. The same discipline travels to affiliating universities reviewing a college’s self-study and to a department that wants one honest international link rather than twelve dormant ones. SDG 17 is not a public-relations target. It is a means: relationships that move teaching, research, finance, or public capacity toward the other goals.

1. Why an MoU folder is not an SDG 17 claim

Target language under SDG 17 is about mobilising resources, sharing knowledge, building statistical and institutional capacity, and making partnerships coherent. A university is not a finance ministry, and it should not pretend its MoU register is a development compact. It is, however, an institution that signs agreements, hosts scholars, runs joint credit, places students, and occasionally moves money. The error is to collapse all of that into one integer: number of MoUs.

Three failures follow. First, the denominator is undefined. Is a renewal a new partnership? Is a departmental letter the same as a university seal? Is an expired document still “active” because nobody filed the lapse? Second, the numerator has no activity test. A document signed in a convocation tent and never opened again scores the same as a joint degree that actually enrolled students. Third, the claim migrates. The prospectus says “global partnerships.” The ranking form says “SDG 17.” The peer team asks for one beneficiary and the room goes quiet.

A foreign logo is scarce, so it is displayed. A local panchayat or MSME cluster is abundant, so it is under-counted. SDG 17 does not rank a partner by flight distance. It asks whether the relationship added capacity the institution did not already have. A district skill centre that co-teaches GST returns to women traders can be a stronger file than a dormant European MoU.

Further reading on DrDPKlass: how campuses can map programmes to SDGs without SDG-washing and how universities should evidence SDG 13 climate action. Partnership claims sit next to both files. A climate MoU that never produced an inventory is the same error as a solar photograph counted as a strategy.

2. Separate the partnership types before anyone counts them

A single “collaborations” column hides unlike objects. Split the register before you write the narrative. The split is administrative, not rhetorical. Different partners create different evidence, different risks, and different SDG links.

Write the type on the register before you write the SDG code. A partnership can serve more than one goal, but it must serve one primary goal with a sentence a stranger can test. “Supports all 17 SDGs” is a refusal to choose. A commerce department’s tie with a regional rural bank might primarily serve SDG 8 or SDG 1, and only secondarily SDG 17 as the means. Say that. Means and ends are not the same row.

Expiry is part of the type. Indian MoUs often say three or five years and then linger in the prospectus. The live file should carry a status: signed and active, signed and dormant, expired, or terminated. Dormant means no activity in the reporting year. Expired means the date has passed and nobody renewed. Both can be listed in an annex. Neither belongs in the headline count.

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

Partnership evidence has three rungs. Activity is something that happened: a joint class, a data-sharing protocol, a faculty visit, a co-supervised dissertation, a training day. Output is an artefact: a curriculum module, a working paper, a tool handed to a cooperative, a placement process with a named employer. Outcome is a change you can describe without inventing a development miracle: students who completed the module, staff who can now run a method, a partner office that uses the tool. Most campus files stop at activity and call it outcome. The honest file labels the rung.

Take a familiar commerce example. A college signs with a district industries centre to help MSME owners read a GST notice. Activity is four Saturday clinics, with attendance. Output is a one-page notice checklist in Odia or Hindi, filed with the centre. Outcome, if you have it, is the number of owners who returned with a revised reply, counted by the centre, not estimated by the department. If the centre will not share that count, stop at output. The SDG 17 sentence is then: we built a repeatable clinic with a public partner and left a tool. That is a partnership. It is not a poverty-eradication claim.

Research partnerships need the same ladder. A joint paper is an output. It is not, by itself, capacity building in the partner institution unless the partner’s staff or students are authors or the method is now taught there. Citation counts borrowed from a foreign co-author’s profile are not evidence that the Indian campus’s students gained a method. List the work package: who cleaned data, who had ethics clearance, who holds the file after the project ends.

If the only shared object is a signature and a photograph, you have a ceremony. Ceremonies can open doors. They are not the partnership.

4. Treat South–South and industry links without brochure geography

Impact-ranking narratives reward international diversity. Indian public colleges often have almost none, and then either omit SDG 17 or invent it. A better file describes the partnership geography you actually have. South–South links — a Nepali campus, a Bangladeshi research group, an African management institute met through a funded network — are partnerships if activity exists. So is a tie with a state skill university two hundred kilometres away. Distance is not quality. Relevance and repeat interaction are.

Industry links fail in the opposite direction. They are over-counted because placement season produces many visiting cards. A single pre-placement talk is not a partnership. A three-year relationship in which the firm co-designs a lab elective, shares a redacted dataset, and takes interns under a written learning plan is a partnership. Write the learning plan into the evidence pack. Internship offer letters alone show recruitment. They do not show that the university contributed anything but a list of names.

Local government is the under-used partner in aspirational districts and in colleges far from a metro. A commerce department that helps a municipality read its own property-tax arrears, or that places students with a cooperative bank for a supervised audit of member passbooks, is doing SDG 17 work tied to SDG 11 or SDG 8. The risk is extraction: students collect data, the department publishes a brochure, and the office 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 belongs in the geography note. If students and local partners work in a regional language and the partnership operates only in English, do not claim community reach you did not resource. If materials were translated, file the translation.

5. Show money, credit, and conflict before the ranking form does

SDG 17 is partly about means of implementation: finance, technology, and capacity. A university partnership that moves money must show the path. Sponsored projects already have a sanction letter, a utilisation certificate, and an overhead policy. Use those. Do not create a parallel “SDG budget” that reclassifies the same grant three ways. If industry paid for a lab and also recruits from the lab, disclose both facts. The partnership can still be genuine. Hidden recruitment tied to a credited course is the conflict a peer team will find if you do not write it down.

Credit is the other currency. Joint degrees, twinning, and credit-transfer MoUs often promise mobility that visa rules, fee gaps, and academic calendars then block. The evidence file should report seats offered, seats filled, and credits actually recognised by the board of studies. A pathway with zero movement in three years is a dormant academic product. Keep it in the prospectus only if you are still willing to operate it, and do not feed it to SDG 17 as if students had crossed a border.

5.1 Who may sign

Indian public institutions usually restrict who can bind the university. A head of department who signs a “MoU” without registrar or syndicate authority has created a departmental letter, not an institutional partnership. The register should record the signing authority. Letters of intent can be listed separately. Counting them as MoUs inflates the number and creates a legal fog when a partner later asks for a certificate the university never authorised.

Data partnerships need a shorter rule. If student or respondent data move to a partner, the file needs a purpose, a retention date, and a statement that consent covers that sharing. A ranking narrative that boasts of “data collaboration” without that sentence is an ethics incident waiting for a complaint. Commerce faculties running field surveys with an NGO are especially exposed. The partnership is real only if both sides can say where the micro-data sit.

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

Different readers punish different inflations. A NAAC peer team will ask to see collaboration in the criterion on extension and best practice, and will sample files. They are rarely impressed by a count. They are often persuaded by one partnership a department can walk them through: the agreement, the activity register, the output, and a partner who answers a phone. Build three such walk-throughs a year, not thirty thin rows.

Impact-ranking submissions ask for evidence against partnership indicators and for narrative on working with government, NGOs, and other universities. The form will accept a URL. A URL that opens a prospectus page of logos is weak. A URL that opens a short evidence note — partner, goal, activity in the year, output, limit — is what a reviewer can score without guessing. If you cannot publish the note, do not claim the partnership in a public ranking. Internal quality files and public claims should match.

State councils and affiliating universities increasingly ask colleges for SDG tables inside the annual quality assurance report. The table should be generated from the register, not typed afresh by whoever holds the IQAC login that week. A second table that disagrees with the first is how a small college gets a large credibility problem. One owner of the register — typically IQAC, with departmental rows submitted by a date — stops the drift.

Scholars citing their own campus as an SDG 17 case should say, in the method, how partnerships were defined and that dormant MoUs were excluded. An Indian case that shows the exclusion rule is more usable than one that reports a logo count.

7. Field checklist and closing brief

SDG 17 is the goal most easily faked and most useful when it is narrow. A campus that retires dormant MoUs, types its live partners, and attaches one activity and one output to each live row will look smaller in a brochure and stronger in a peer visit. That is the correct trade.

1. Open the MoU folder and mark each document active, dormant, or expired against the reporting year.
2. Record signing authority. Departmental letters are not university partnerships.
3. Type each live row: academic, industry, government, research, or community. Drop intra-university rows unless resources moved.
4. Attach one primary SDG the partnership serves, and treat SDG 17 as the means unless the partnership itself builds partner capacity.
5. File activity (date, people, place) separately from output (artefact) and outcome (change against a baseline you hold).
6. For international rows, record who funded travel, who was selected, and what returned to the curriculum.
7. For local and industry rows, file a handover or learning plan. A photograph is not a handover.
8. Reconcile money to the existing grant file. Do not invent a parallel SDG budget.
9. State data-sharing limits where micro-data move. Logo use needs an output review.
10. Generate the NAAC, ranking, and annual-report tables from the same register. Sample three headline rows before you submit.

A registrar can run this in a month if departments are given a single template and a refusal rule: no activity, no row. The first year will shrink the number. The second year will show which partnerships are worth renewing. That shrinkage is the evidence. It is also how a college in a small city can report SDG 17 without borrowing a foreign logo it cannot operate.

Partnerships are a means of implementation. They are not a substitute for the goal they claim to serve. An MoU that never produced a class, a tool, a paper, or a handover did not implement anything. Leave it in the annex. Put the live work on the page.