Early-career commerce faculty in Indian colleges and universities routinely spend hours each week on informal mentoring: answering exam-preparation questions after class, reviewing project drafts outside office hours, guiding first-generation students through online application portals, or talking a final-year student through a job-interview rejection. These interactions are real work. They also vanish from the Academic Performance Indicator (API) file and from the promotion dossier unless the faculty member creates a contemporaneous record that maps onto the categories the institution and the UGC framework actually recognise. This briefing sets out a practical system for turning that invisible labour into evidence that a selection or promotion committee can open, evaluate, and credit.
The disappearance is structural. Most institutional API formats and the UGC categories that underlie them privilege activities that generate an external artefact: a published paper, a certificate of attendance at a seminar, a letter from an external body, or a formal appointment as a programme coordinator. Informal mentoring produces none of these by default. A conversation that takes place in the corridor after the last period, or a sequence of WhatsApp messages that help a student rewrite a statement of purpose, leaves no automatic trace in the departmental file.
Two features of Indian commerce departments amplify the problem. First, the volume of such requests is high because of large class sizes and limited counselling infrastructure. Second, the culture often treats responsiveness as a personal virtue rather than as departmental work. A senior colleague who says “just help them, it is part of the job” is expressing a genuine expectation; the same colleague, when asked later to certify the activity, may have no recollection and no form on which to record it.
When the early-career faculty member prepares the API score sheet or the CAS application years later, the mentoring hours have already been spent. Reconstructing them from memory produces claims that are either too vague to score or that invite challenge. Faculty who have kept no record therefore either omit the work or submit unsupported assertions. Both outcomes understate the contribution.
Not every helpful conversation will score. Committees look for activity that can be placed under one of the recognised heads and supported by evidence the institution accepts. Under the UGC regulations and local adaptations used by most universities and affiliated colleges, mentoring-related work most often maps onto three areas.
The first is student-related co-curricular or extension activity. Guidance given for project work, competitive examinations, placements, or higher-study applications can be claimed when the faculty member can show that the guidance was systematic rather than incidental and that it involved a defined set of students over a defined period. The second is involvement in departmental or institutional student-support functions. Even if the faculty member does not hold a formal coordinator title, documented participation in placement drives, remedial classes, or orientation programmes can be recorded under the appropriate activity head. The third, less frequently used but available in some institutions, is contribution to the personal and professional development of students beyond the classroom, provided the contribution is evidenced and endorsed by the head of department or by the students themselves through a simple feedback mechanism.
What does not score is purely social conversation, one-off answers to routine syllabus queries, or mentoring indistinguishable from ordinary classroom follow-up. Committees distinguish activity that is additional, structured, and evidenced from activity that is part of normal teaching. The documentation system must capture the additional character of the work.
Local rules vary. Some universities require the head of department to countersign every claim; others accept a self-certified log supported by student acknowledgements. Before building a personal system, the faculty member should read the current API or CAS guidelines of the affiliating university and, if possible, examine one recent successful file. The personal log should be designed so that it can be copied, with minimal editing, into the institutional format.
The log does not need to be elaborate. A single spreadsheet or a dedicated notebook, updated on the same day as the interaction, is sufficient. Each entry should contain six fields that allow a later reader to understand what was done, for whom, and why it was more than ordinary teaching.
The fields are: date; student identifier (roll number or name, kept confidential if the log is later shared); nature of the request (project draft, placement interview preparation, higher-study application, competitive-examination strategy, or other); duration or number of interactions; concrete outcome or next step agreed; and any artefact produced (annotated draft returned, list of resources supplied, mock-interview notes). A seventh optional field records whether the student later provided a short written acknowledgement.
An example entry might read: “12 September 2026; Roll 2023COM045; review of two-page statement of purpose for an M.Com application; 40 minutes in person plus follow-up comments the next day; student submitted the application on 18 September; student sent a one-line acknowledgement.” The entry is short, factual, and time-stamped. It records the work that was done.
Two practices keep the log credible. First, update it the same day; entries written weeks later are easy to challenge. Second, retain the supporting artefact when one exists—an annotated draft, a screenshot, or a short student note—in a dated folder. The log can then point to the folder. When the API season arrives, extract the relevant rows and attach a sample of the supporting material.
Once the log exists, map clusters of entries onto the categories the institution uses. Most API formats contain a section for “student-related co-curricular, extension and field-based activities” or an equivalent head. Under that head, a faculty member can typically claim a fixed score for systematic guidance provided to a stated number of students over a semester or year, provided the claim is supported.
Sort the log by type of request. Group entries that concern final-year project supervision beyond the formal allocation, or placement and higher-study counselling. Count distinct students and total interactions. Then prepare a one-page summary: “During 2026–27 I provided documented mentoring support to 28 students on project writing, placement preparation, and higher-study applications (46 interactions). A sample of acknowledgements and annotated drafts is attached.” The summary is what the committee reads; the log and sample artefacts can be inspected if needed.
Evidence requirements differ. Some institutions accept the self-certified summary with the head of department’s counter-signature; others ask for student feedback. A practical approach is to request, at the end of each semester, a short acknowledgement from students who received substantial help: “I received guidance from [Faculty Name] on my project draft / placement preparation / higher-study application during [month].” These notes, stored with the log, supply the corroboration committees prefer. Do not pressure students; a simple request is usually enough.
Where the institution has a formal mentoring coordinator, inform that person of the volume of work and, if possible, have the activity noted in the coordinator’s report. An institutional note carries more weight. Even without such a structure, a brief email to the head of department at the end of each semester creates a contemporaneous institutional trace.
The request is common and usually well-intentioned. The early-career faculty member who responds only with compliance continues to accumulate unrecorded hours. The faculty member who responds with a request for formal recognition risks being seen as unwilling. A middle path exists.
When the request is made, the faculty member can accept the work and, in the same conversation, state the documentation practice already in use. “I am happy to review the drafts. I keep a short log of these interactions so that I can include them properly in the API file at the end of the year. Would you be willing to countersign a one-page summary in April?” Most senior colleagues, once the administrative implication is made explicit and limited, will agree. The request for a countersignature is concrete, time-bound, and does not require the senior colleague to remember individual students.
If the colleague is reluctant to countersign, the faculty member can still maintain the personal log and the student acknowledgements. Those two elements are usually sufficient for a self-certified claim, and the refusal itself can be noted privately so that the faculty member does not later over-estimate the institutional support that will be available. In either case, the conversation has converted an open-ended expectation into a bounded, documented activity.
A second useful practice is to batch the work where possible. Instead of accepting every individual request for an immediate meeting, the faculty member can announce a fixed mentoring hour each week and ask students to bring written drafts or specific questions. The fixed hour is easier to log, easier to defend as systematic, and easier for the head of department to recognise as a departmental contribution rather than as ad-hoc personal assistance. Students who need urgent help can still be seen; the existence of the scheduled hour simply reduces the number of purely informal encounters that never enter the record.
When the promotion or confirmation file is prepared, the mentoring log should appear as one element in a broader narrative of contribution, not as a stand-alone claim that the faculty member “mentored many students.” Overclaiming is easy to detect and damages credibility. Underclaiming wastes the record that has been carefully kept.
A restrained narrative paragraph might read: “In addition to the formal teaching allocation, I maintained a documented mentoring practice that supported 25–30 students each year on project writing, placement preparation, and applications for further study. The practice was recorded in a contemporaneous log, corroborated by student acknowledgements, and summarised for the departmental record at the end of each semester. Sample materials are available for inspection.” The paragraph states what was done, how it was recorded, and where the evidence sits. It does not assert that the mentoring produced placements or admissions; those outcomes depend on many factors outside the faculty member’s control.
The same paragraph can be adapted for a teaching statement or for an interview in which the candidate is asked about contribution to the department. In an interview the candidate can offer to show the one-page semester summary if the committee wishes. Most committees will not ask to see it; the offer itself signals that the claim rests on a record rather than on recollection.
Two cautions apply. First, do not inflate the numbers. If the log shows 22 distinct students, claim 22. Committees that sample the underlying material will notice discrepancies. Second, do not present mentoring as a substitute for research or for formal teaching innovation. In most Indian commerce promotion exercises the research score remains decisive. Mentoring evidence strengthens the teaching and extension components; it does not compensate for an empty research folder. The faculty member who has both a credible research pipeline and a documented mentoring record presents a more complete file than the faculty member who has only one of the two.
Finally, the log has a forward-looking use. Patterns visible in the entries—repeated difficulties with a particular type of assignment, or clusters of students seeking help with the same competitive examination—can inform the design of a short remedial module or a departmental workshop. When that module is later offered, the earlier log supplies evidence that the module responded to an observed need. The documentation system therefore serves both the individual API file and the department’s capacity to improve student support.
Informal mentoring will continue to be part of the work of early-career commerce faculty in Indian institutions. The difference between work that strengthens a promotion file and work that disappears is the existence of a light, contemporaneous record that can be mapped onto the categories committees already recognise. The system described here requires only a few minutes a day and a short summary each semester. Those minutes convert otherwise invisible labour into evidence that can be opened, evaluated, and credited.