Most early-career Indian scholars do not fail because they lack ideas. They fail because every idea sits in the same state: “I will finish this after internals.” A research pipeline is not a list of titles. It is a small set of manuscripts that occupy different states at the same time, so that a teaching week, a desk rejection, or a delayed data licence cannot stop all output at once.
This Research Series briefing is for assistant professors, post-docs converting a thesis, and doctoral candidates who already teach or invigilate more hours than their offer letter implied. It assumes an Indian commerce or management department: sixteen to eighteen contact hours in a heavy semester, a mid-semester test that eats two weekends, a committee that discovers NAAC evidence in March, and a data vendor that renews licences on a fiscal calendar. The method is operational. Three papers. Three states. One board you can read on Monday morning.
1. Why three papers, not seven ideas
Seven ideas feel like a pipeline. They are a wish list. An idea has no desk date, no coauthor agreement, and no file that a coauthor can open while you are on invigilation duty. A paper in a pipeline has a claim sentence, a conversation of six to twelve articles, a data vintage, and a next action that can be completed in a defined block of time.
Three is not a magic number borrowed from US research-track folklore. It is the largest number most Indian teaching loads can keep warm without lying. One paper in revise-and-resubmit, one paper in first-submission or late draft, and one paper in design or data construction is a working stack. A fourth paper is allowed only if it is parked: a one-page note, not an open file that steals Monday mornings.
The temptation on Indian campuses is to start a new paper every time a circular, a Budget annex, or a SEBI amendment looks “timely.” Timeliness is not a pipeline. A circular can become a citation in an existing identification section. It should become a new paper only when it creates identifying variation you do not already have.
2. Name the three slots by state, not by topic
Topic labels hide stall. “ESG paper,” “audit paper,” and “disclosure paper” can all be stuck at the same point: literature review unfinished. State labels force honesty.
| Slot | State | What “done this week” looks like |
|---|---|---|
| A | Under review or R&R | Response paragraph drafted, table rebuilt, or referee clock logged |
| B | Submission-ready draft | Contribution paragraph rewritten, journal shortlist frozen, files packaged |
| C | Design or data | Sample framed, licence confirmed, coding rule written, or pilot table produced |
When Slot A is empty because a paper was accepted or abandoned, promote Slot B. When Slot B is empty because you submitted, promote the most identified project from Slot C. Do not invent a fourth live project to fill a feeling of emptiness. Emptiness after a submission is the system working.
2.1 The one-page board
Keep a single page—paper, not a project-management theatre—with four columns: slot, twelve-word claim, next action, blocker. The blocker column is the point of the board. Typical Indian blockers are not “need motivation.” They are “CMIE vintage ends FY2023,” “IRB letter names thesis only,” “coauthor on NAAC visit until 12 October,” and “journal requires a data-availability statement we cannot sign.”
3. Build a calendar that respects mid-semester and NAAC weeks
A pipeline that assumes August and January are “research months” will die in September and February. Map the institutional calendar first, then place research blocks in the gaps that actually exist.
Mark, at the start of each semester, the weeks that cannot host deep work: internal-test setting and marking, end-semester evaluation, admission counselling if you are assigned it, NAAC or NIRF evidence weeks, and any statutory workshop the department cannot skip. Those weeks are not moral failures. They are constraints. Slot C work that needs four uninterrupted hours should not be scheduled inside them. Slot A work that is a two-hour response paragraph can be.
Use the light weeks for design and identification writing. Use the heavy weeks for mechanical tasks that survive interruption: checking a citation against the instrument, updating a sample-construction note, or writing the data-availability sentence you will need later.
Do not wait for a sabbatical you have not been granted. Wait for the next unmarked Saturday only if the board already names the Saturday’s task.
Doctoral candidates who also teach tutorials should treat the two weeks after a viva or a synopsis meeting as Slot B weeks. Committees create a false sense that the thesis is the only file. The article that will be read in a faculty shortlist is often the converted chapter sitting in Slot B, not Chapter 5.
Public universities and many private campuses also lose weeks to election duty, evaluation camps off site, and statutory training that arrives with three days’ notice. Put a “movable deep block” on the board: a reserved Saturday that can slide by one week without guilt. What you must not do is delete the block. A pipeline dies when the reserved hour is treated as optional the first time a notice arrives.
If your department still runs a research seminar, use it as a Slot B gate rather than as a performance. Present only the paper whose claim and kernel table exist. A seminar that restates the thesis chapter delays conversion. Ask for two comments you can act on in a week: one on the conversation, one on the identifying threat. Ignore advice to “add India as a contribution.” India is a setting. The contribution is the claim the setting lets you test.
Further reading on DrDPKlass: How to Convert an Indian PhD Chapter into a Journal Article Without Diluting the Contribution and How to Write an R-and-R Response Letter That Recovers the Paper Without Surrendering It.
4. Protect hours that can actually move a file
Advice to “write every day” is not false. It is incomplete. A 25-minute block can fix a paragraph. It cannot rebuild a stacked-difference table or reread an identification threat. Classify hours by what they can buy.
Deep blocks
Two to four hours. Identification, contribution paragraph, response-letter architecture, sample construction. Protect two of these a week in a light teaching month; one in a heavy month.Shallow blocks
Thirty to forty-five minutes. Citation sweep, licence email, coauthor ping, journal-fit skim of last year’s accepted titles, board update.Place deep blocks where the campus will not find you. For many colleagues that is 6:00–8:00 before the first lecture, or a library floor that is not the staff room. Do not place a deep block immediately after a three-hour case session. The cognitive residue is real. Use that afternoon for shallow work or for teaching files.
Count only blocks that produce an artefact: a rewritten page, a table, a letter paragraph, a licence confirmation. Time spent “reading around the topic” is Slot C only if it ends in a conversation list of six to twelve papers, not a highlighted PDF graveyard.
5. Use coauthors as capacity, not as decoration
On a teaching load, a coauthor is either capacity or risk. Capacity means they own a state you cannot occupy this month: the data build while you mark scripts, or the literature conversation while you run admissions. Risk means their name is on the paper and their next action is blank.
Agree three things in writing before a paper enters Slot B: who drafts which section, who holds the data licence, and who will answer a referee clock within ten days. Courtesy authorship for a head of department is a career decision, not a pipeline decision. If you accept it, treat it as a constraint and keep the technical files in hands that can defend them.
Doctoral coauthors need a different contract. Give them Slot C tasks with a definition of done: a coding memo, a sample log, a table that can be rebuilt from a script. Do not give them “please improve the literature review.” That instruction produces a chapter, not an article conversation.
When a coauthor disappears into NAAC or a family event, do not freeze the pipeline. Move that paper’s next action to something you can do alone—an appendix, a journal-fit note, a contribution rewrite—or park the paper and promote another Slot C project that does not depend on them.
6. Keep data, ethics and licences on the same board as drafts
Indian empirical work dies in silence when a draft is ready and the licence is not. CMIE extracts, bank files, ministry dumps, and interview protocols cleared for a degree are not automatically cleared for a journal data statement. Put licence expiry, IRB scope, and anonymisation status on the same board as the claim sentence.
Slot C is not “collect more variables.” Slot C is: frame who is in the sample, write the coding rule a coauthor could apply, confirm the vintage you may publish, and produce one table that a sceptic could attempt to rebuild. Extra variables are how seven-idea lists are born.
If the licence ends before the journal’s expected review cycle, write that fact in the data section now. Editors prefer a bounded sample to a promised package that will vanish. If interviews were consented for a thesis, tighten anonymisation before the manuscript leaves campus. A committee that knew the field site is not the same audience as an international referee.
7. Sequence outlets so one rejection does not empty the year
A pipeline that aims every paper at the same “Q1” list will stall together. Journal fit is a conversation test: has this outlet hosted the debate you joined in the last two years? Read accepted titles, not the aims-and-scope paragraph and not a quartile screenshot from last year’s API form.
Give each live paper a shortlist of three outlets in descending fit, not descending prestige. After a desk reject, the next action is not a month of mourning. It is a 48-hour fit rewrite: contribution paragraph retargeted, identification threats restated in that journal’s dialect, references that journal’s associate editors have handled. Then submit. Dead time after a desk reject is how teaching loads swallow a year.
Predatory outlets will clear Slot B instantly. That is not pipeline progress. It is a deposit that cannot be cited in the shortlist you actually want. A tough field journal that returns the file in three weeks has given you information. Use it on the same board.
Keep one paper—usually Slot A—aimed at the conversation you want your name attached to. Let Slot B be the paper that can land in a respectable field journal this calendar year. Slot C can be ambitious. Ambition belongs in design, not in simultaneous first submissions to six editorial offices.
8. Field checklist and closing brief
Run this list on paper every Monday that is not an evaluation week.
- Exactly three live papers; extras parked as one-page notes.
- Each paper has a twelve-word claim that can be false.
- Each paper has one next action that fits this week’s actual calendar.
- Blockers are named (licence, IRB, coauthor, journal statement), not vibes.
- Deep blocks are booked against light weeks; heavy weeks get shallow work only.
- Coauthor contracts exist for any paper in Slot A or B.
- Data vintage and consent scope are written where a referee will find them.
- Each paper has a three-outlet shortlist based on recent accepted conversations.
- A desk reject has a 48-hour retarget rule, not an open-ended rewrite.
- No new paper is started because a circular looked timely unless it creates new identifying variation.
A living pipeline looks slightly boring from the outside. The titles do not change every fortnight. The states do. That is the point. Indian teaching loads will not become American research loads because a productivity thread said so. They become survivable when three files occupy three different states, when Monday names the next action, and when a mid-semester week is allowed to be a mid-semester week. Keep the board short. Keep the claims sharp. Submit the paper that is ready. Start the next design only when a slot is actually empty.
Research Series · Daily Briefing · 28 September 2026