Proposal Preparation Week
Session at a Glance
Intensive proposal writing week; synthesising Weeks 1–6 into a coherent research proposal document
Proposal drafting; structured peer review; individual supervisor consultations; proposal self-assessment against evaluation rubric
14 hrs Lab/Workshop + Individual Writing
Complete research proposal draft (2,500–3,500 words)
Learning Objectives
By the end of this session, you will be able to:
- Synthesise your work from Weeks 1–6 — problem statement, literature review, methodology outline, and ethics assessment — into a single, coherent research proposal document
- Structure a research proposal following a standard template that communicates the what, why, and how of your capstone project to a supervisor and evaluation committee
- Critique a research proposal against evaluation criteria, identifying strengths, weaknesses, and areas requiring revision — both in your own proposal and in peers' work
- Prepare for a productive supervisor consultation by identifying specific questions, articulating uncertainties, and presenting draft material in a structured format
- Plan your capstone execution roadmap, linking the proposal to the methodology design, data collection, and analysis phases that follow in Weeks 8–30
Week 7 Planner — Lab-Intensive Format
This week operates differently from Weeks 1–6. Instead of a lecture-driven session, it is structured around writing workshops, peer review, and individual consultations. The schedule below assumes a 2-hour opening workshop + 12 hours of structured independent work with consultation touchpoints.
| Time / Phase | Activity | Details | Mode |
|---|---|---|---|
| 0:00–0:20 | Opening Workshop | Proposal anatomy overview; evaluation criteria; common pitfalls; template walkthrough; week roadmap and deliverables | Whole class |
| 0:20–0:50 | Structured Writing Block 1 | Draft proposal Sections 1–3 (Title/Abstract, Introduction & Problem Statement, Research Questions & Objectives). Use provided templates. | Individual writing |
| 0:50–1:10 | Peer Exchange | Exchange Sections 1–3 with a partner. Apply structured feedback prompts: Is the problem clear? Are the RQs specific and researchable? Is the scope appropriate for a capstone? | Pairs |
| 1:10–1:25 | Mini-Clinic | Facilitator addresses common issues emerging from peer exchanges; Q&A on problem statements and RQs | Whole class |
| 1:25–1:40 | Break | — | — |
| 1:40–2:00 | Structured Writing Block 2 | Draft proposal Sections 4–5 (Literature Review summary, Conceptual/Theoretical Framework). Focus on synthesis, not annotated bibliography. | Individual writing |
| Day 2–3 (4 hrs) | Independent Writing | Complete Sections 6–8 (Proposed Methodology, Ethics, Timeline & Resources). Submit complete draft to supervisor by end of Day 3. | Individual |
| Day 4 (2 hrs) | Supervisor Consultation | Individual 20–30 min consultation with faculty supervisor. Discuss proposal draft; receive formative feedback; identify revision priorities. | 1-on-1 |
| Day 4–5 (3 hrs) | Revision & Refinement | Revise proposal based on supervisor feedback and peer review. Complete self-assessment against evaluation rubric. Strengthen weak sections. | Individual |
| Day 5 (1 hr) | Final Polish & Submission | Format check; proofread; ensure all sections complete; verify citations; submit final proposal draft. | Individual |
1. What a Research Proposal Is — and Why It Matters
A research proposal is a structured document that articulates what you plan to study, why it matters, and how you will study it. It is the bridge between your preparatory work (Weeks 1–6) and your execution phase (Weeks 8–30). Think of it as a contract — with your supervisor, your institution, and yourself — about what your capstone will deliver.
A research proposal is a coherent, evidence-based argument that a specific research question is worth investigating and that the proposed methodology is capable of answering it. It demonstrates: (a) that the problem is real and significant, (b) that the researcher understands the existing literature and has identified a genuine gap, (c) that the proposed research design is feasible, rigorous, and ethical, and (d) that the researcher has the competence and plan to execute it.
1.1 Three Audiences for Your Proposal
| Audience | What They Want to Know | What This Means for Your Writing |
|---|---|---|
| Your Supervisor | "Is this student ready to execute this project? Do I understand what they're doing well enough to guide them? Are there obvious problems I need to flag now?" | Be specific, not vague. A supervisor cannot guide "I want to study digital marketing." They can guide: "I will compare the effectiveness of micro-influencer vs. macro-influencer marketing on purchase conversion for beauty products among Gen Z consumers in Tier-2 Indian cities, using a 2×2 experimental design." |
| The Evaluation Committee | "Does this proposal meet the standards for a capstone? Is the problem significant, the literature review adequate, the methodology sound, and the scope feasible?" | Demonstrate competence explicitly. Show that you understand research design, not just that you have an interesting topic. Cite methodological literature. Justify your choices — don't just describe them. |
| Your Future Self | "What did I commit to? What was my rationale? What were my assumptions? What should I do when things don't go as planned?" | Write with enough detail that you can return to the proposal after 8 weeks of data collection and remember exactly what you intended and why. The proposal is your compass when the research gets messy — and it will get messy. |
The proposal is a plan, not the final product. Plans change — and that is expected. When your methodology encounters reality, you will adapt. When your literature review deepens, your theoretical framework may shift. The proposal documents your starting point and your rationale — it is the baseline against which changes are judged and justified. A proposal that is perfectly executed without modification is not a sign of good planning; it is a sign that you didn't learn anything during the research process. Proposals are revised; research questions are refined; methods are adapted. What matters is that you can explain why.
2. Anatomy of a Research Proposal — The Complete Template
Every institution and discipline has its own proposal format. The template below synthesises the common elements expected in BBA and BCA capstone proposals. Adapt it to your institution's specific requirements, but ensure every section is addressed.
2.1 The Standard Proposal Structure
A working title that communicates the topic, context, and (where possible) the methodology. The abstract summarises the entire proposal: problem, gap, RQs, proposed method, expected contribution. Write this LAST — after you've drafted everything else — but place it first.
Establish the domain and its significance. State the problem clearly and precisely. Provide evidence that the problem is real (cite data, prior research, industry reports). Explain why the problem matters — to whom, at what scale, with what consequences if unsolved. Close with a focused problem statement that the RQs will address. This section draws directly on your Week 3 work.
State your primary research question and 2–4 sub-questions. Ensure they are specific, researchable, and aligned with your paradigm (Week 2). Translate each question into a research objective (actionable statement of what the study will do). For BCA projects: include technical objectives (e.g., "To develop and evaluate a fine-tuned multilingual model for code-mixed sentiment classification").
This is NOT the full literature review chapter. It is a summary of your literature review that: (a) situates your study in the existing literature, (b) identifies 3–5 key themes from prior research, (c) demonstrates that you know the seminal and current work in your area, and (d) articulates the specific gap(s) your study will address. Draw on your Week 4 search results and Week 5 synthesis matrix. This section should convince the reader that your RQs emerge from the literature, not from thin air.
Identify the theory(ies) that ground your study. Explain the key constructs and their hypothesised relationships. Include a conceptual framework diagram (boxes and arrows showing how variables or concepts relate). For BBA: this is typically a theoretical model (e.g., TAM, UTAUT, Source Credibility Theory). For BCA: this may be a system architecture, algorithm design, or computational framework. This section should answer: "What is the lens through which this study makes sense of its data?"
This is the how of your proposal. Address: research paradigm and design (Week 2), population and sampling strategy (who/what, how many, how selected), data collection methods (survey, interview, experiment, system development, secondary data), data analysis plan (statistical tests, thematic analysis, model evaluation metrics), validity/reliability/trustworthiness strategies, and limitations. Be specific: "I will conduct semi-structured interviews with 15–20 middle managers in Indian manufacturing firms, selected through purposive sampling, and analyse transcripts using Braun and Clarke's (2006) thematic analysis procedure." NOT: "I will interview some managers and analyse the data."
Summarise the ethical dimensions of your study (Week 6). Address: informed consent procedures, confidentiality/anonymity measures, data security, vulnerable populations (if any), institutional ethics approval status, potential harms and mitigation strategies. For BCA: address algorithmic fairness, dual-use concerns, data provenance, and platform ToS compliance.
Provide a realistic timeline (Gantt chart or table) showing when each phase will be completed across Sem VII and VIII. Identify resources needed: software, lab access, datasets, survey platforms, participant incentives, travel (if any). Include a reference list of all cited sources in the proposal (not your full bibliography — just works actually cited).
2.2 Proposal Length Guidelines
| Component | Recommended Length | Proportion of Total |
|---|---|---|
| Title & Abstract | 150–250 words | ~7% |
| Introduction & Problem Statement | 400–600 words | ~18% |
| Research Questions & Objectives | 200–300 words | ~9% |
| Literature Review & Gap | 600–900 words | ~27% |
| Conceptual / Theoretical Framework | 300–400 words | ~12% |
| Proposed Methodology | 500–700 words | ~21% |
| Ethical Considerations | 200–300 words | ~9% |
| Timeline, Resources & References | 200–300 words + references | ~9% |
| Total | 2,550–3,750 words | 100% |
These are guidelines, not rigid rules. A quantitative study may need more methodology detail; a study grounded in a complex theory may need more theoretical framework space. What matters is that every section earns its word count — no padding, no placeholder text, no "this will be developed later."
3. Writing Strategies for a Strong Proposal
3.1 The Golden Thread — Coherence Across Sections
The most common weakness in student proposals is fragmentation — sections that were written in isolation and don't connect. A strong proposal has a "golden thread" running through it: the problem (Section 2) creates the need for the RQs (Section 3), which are justified by the gap in the literature (Section 4), which is explained by the theoretical framework (Section 5), which is investigated through the methodology (Section 6), which is conducted within ethical constraints (Section 7), all within a feasible timeline (Section 8). If any section could be swapped into a different proposal without the reader noticing, the golden thread is broken.
Problem: "Digital transformation is changing the banking sector."
RQs: "How does social media influence consumer trust?"
Method: "I will conduct a survey of 200 students."
These don't connect. The problem is about banking; the RQs are about social media; the sample is students (not banking customers). The reader cannot trace how the RQs emerge from the problem or how the method will answer the RQs.
Problem: "Despite high smartphone penetration, mobile banking adoption among rural Indian women remains below 15% (RBI, 2023)."
RQs: "What factors — cultural, technological, and institutional — inhibit mobile banking adoption among rural women in Uttar Pradesh?"
Method: "Semi-structured interviews with 25–30 rural women in three UP districts, selected through stratified purposive sampling, analysed using thematic analysis."
The problem (rural women, mobile banking, low adoption) directly generates the RQs (factors inhibiting adoption in this population), and the method (interviews with this population) is clearly capable of answering the RQs.
3.2 Proposal Writing Principles
Every sentence should survive the "So what?" test. "I will use a mixed-methods approach." So what? "I will use a sequential explanatory mixed-methods design: Phase 1 will survey 200 consumers to identify adoption patterns (quantitative), and Phase 2 will interview 15 survey respondents to explore the reasons behind those patterns (qualitative)." Every methodological choice is named, justified, and connected to the RQs.
Every claim needs backing. "This is an important problem" → cite the data that shows it. "There is a gap in the literature" → show the gap through your synthesis, don't just state it. "This method is appropriate" → cite methodological literature supporting your choice. A proposal is an argument, and arguments require evidence.
The best capstone proposal is not the most ambitious — it is the one that can actually be completed within the available time and resources. A proposal to "study the impact of AI on global employment" is not feasible. A proposal to "compare the adoption of AI-powered inventory management systems in three Delhi retail chains" is. Scope down until the project is achievable — you can always extend later.
Acknowledge limitations, uncertainties, and assumptions. A proposal that admits "This study is limited to a single organisation and findings may not generalise" is stronger than one that ignores this obvious limitation. Intellectual honesty signals maturity as a researcher. The evaluation committee will spot the limitations whether you acknowledge them or not — acknowledging them shows you understand your study's boundaries.
3.3 Common Proposal Pitfalls — and How to Avoid Them
| Pitfall | What It Looks Like | How to Fix It |
|---|---|---|
| The Floating RQ | Research questions that appear without justification — the reader doesn't understand where they came from or why these specific questions matter | Your RQs should emerge visibly from the gap identified in your literature review. The reader should think "Given that gap, these questions make sense" — not "Where did these come from?" |
| The Kitchen Sink Method | "I will use surveys, interviews, focus groups, experiments, secondary data analysis, and machine learning." Too many methods, none justified. | Choose the MINIMUM set of methods needed to answer your RQs. For each method, justify: "Why this method? Why not an alternative? What will it produce that answers which RQ?" |
| The Missing Sample | "I will survey consumers." Which consumers? How many? Where? Selected how? Why this group and not another? | Specify: population, sampling frame, sampling technique (probability or non-probability, which specific type), sample size, and justification for each choice. Cite sampling literature if using a specific technique. |
| The Phantom Analysis | "The data will be analysed using appropriate statistical techniques." Which techniques? Applied to which RQs? What assumptions must be met? | Name the specific analyses: "RQ1 will be tested using independent samples t-test comparing treatment and control group means. Assumptions of normality (Shapiro-Wilk) and homogeneity of variance (Levene's test) will be checked." |
| The Vanishing Ethics | "Ethical guidelines will be followed." One paragraph that says nothing specific. No consent form, no data security plan, no risk assessment. | Apply your Week 6 work. Include: consent procedures, data anonymisation plan, storage and destruction timeline, risk mitigation strategies, ethics approval status. Be specific to YOUR study, not generic. |
| The Hopeful Timeline | "Week 8–10: Literature review. Week 11–13: Data collection. Week 14–16: Analysis. Week 17–20: Writing." — No detail, no buffer, no contingencies. | Break each phase into specific tasks with estimated hours. Include buffer time (20–30%). Identify dependencies (what must finish before what can start?). Show the timeline as a Gantt chart or detailed table. |
| The Ghost References | In-text citations that don't appear in the reference list, or vice versa. Inconsistent formatting. Reliance on blogs and grey literature without acknowledging their limitations. | Use reference management software (Zotero/Mendeley — Week 4). Check every in-text citation against the reference list before submission. Use a consistent style (APA 7th recommended). |
4. Making the Most of Supervisor Consultations
The supervisor consultation is not a meeting where your supervisor tells you what to do. It is a structured conversation where you present your thinking, receive expert feedback, and collaboratively identify the strongest path forward. The quality of the consultation depends largely on how well you prepare.
4.1 Before the Consultation — Preparation Checklist
- Send your draft proposal at least 48 hours before the meeting. Supervisors need time to read and think. A proposal sent the night before will get superficial feedback.
- Identify 3–5 specific questions you want answered. Not "Is my proposal okay?" but "I'm unsure whether purposive or snowball sampling is more appropriate for my population — can we discuss the trade-offs?" or "My conceptual framework has five constructs — is this too many for a capstone, or is it justified given the literature?"
- Flag the sections you're least confident about. "Section 6 (Methodology) is where I feel weakest — could we focus most of our time there?" This helps the supervisor prioritise.
- Bring your proposal document — annotated. Mark sections where you had doubts, alternatives you considered but rejected, and places where you made assumptions you want to check. These annotations are valuable discussion material.
- Prepare to take notes. Bring a notebook or open a document. Supervisor feedback is detailed and specific, and you will forget it if you rely on memory. Ask if you can record the conversation (if both parties are comfortable).
4.2 During the Consultation — Productive Questions to Ask
| Instead of Asking... | Try Asking... |
|---|---|
| "Is my topic good?" | "Based on your experience with capstone projects in this area, what scope adjustments would you recommend to make this feasible within the timeline?" |
| "Is my methodology correct?" | "I've chosen [method X] because [reason]. An alternative would be [method Y], which I rejected because [reason]. Does my reasoning hold, or am I missing something?" |
| "How many references do I need?" | "I've reviewed approximately 25 papers and included 15 in my literature review section. Are there key authors or papers in this area that I appear to have missed?" |
| "What grade will this get?" | "Which section of the proposal would benefit most from additional work before I submit? Where do you see the greatest gap between what I've written and what the evaluation committee will expect?" |
| "Can you check my references?" | "I've used APA 7th edition for citations. Could you spot-check a few to confirm my formatting is correct before I finalise the entire reference list?" |
4.3 After the Consultation — Acting on Feedback
- Summarise the feedback in writing within 24 hours. Send a brief email to your supervisor: "Thank you for the meeting. Based on our discussion, I understand the key revision priorities are: (1) narrowing the sample to a single organisation, (2) adding a construct validity strategy for the survey instrument, and (3) strengthening the gap articulation in Section 4. I'll submit a revised draft by [date]. Please let me know if I've misunderstood anything." This demonstrates professionalism and creates a written record.
- Prioritise revisions. Not all feedback carries equal weight. Start with structural issues (scope, RQ clarity, methodological soundness) before stylistic ones (wording, formatting). Fixing a paragraph's phrasing when the underlying research design needs rethinking is wasted effort.
- If you disagree with feedback, say so — respectfully and with reasoning. "I understand your concern about the sample size, but based on Guest, Bunce, and Johnson's (2006) work on data saturation in thematic analysis, 12 interviews may be sufficient for my homogeneous population. Could we discuss whether this reasoning applies to my context?" Supervisors respect students who engage thoughtfully with feedback — they do not expect passive acceptance.
Your supervisor is not your editor, your proofreader, or your project manager. They are your research mentor — someone who guides your thinking, challenges your assumptions, and helps you navigate the research process. The most successful supervision relationships are characterised by: regular communication (not silence followed by panic), prepared meetings (not "I don't know what to ask"), and genuine intellectual engagement (not passive receipt of instructions). Treat the supervision relationship as a professional partnership, and it will be one of the most valuable experiences of your degree.
5. Proposal Evaluation — Self-Assessment Rubric
Before submitting your proposal, assess it against the criteria that evaluators will use. Be honest — identifying weaknesses now prevents disappointment later.
| Criterion | Excellent (4) | Competent (3) | Developing (2) | Inadequate (1) |
|---|---|---|---|---|
| Problem Clarity & Significance | Problem is precisely defined, its significance is compellingly demonstrated with evidence, and the reader immediately understands why this research matters | Problem is clearly stated and its importance is explained, but the evidence for significance could be stronger or more specific | Problem is identifiable but vague; significance is asserted rather than demonstrated; reader is not convinced the problem warrants a capstone | Problem is unclear, trivial, or absent; reader cannot determine what the research is about or why anyone should care |
| RQ Specificity & Researchability | RQs are specific, well-scoped, aligned with the paradigm, and clearly emerge from the literature gap; each RQ maps to a research objective and is answerable with the proposed method | RQs are clear and researchable but could be more focused; the link to the literature gap is present but could be stronger | RQs are present but too broad, too narrow, or not clearly researchable; connection to the literature is tenuous | RQs are missing, unanswerable, or disconnected from the problem and literature |
| Literature Integration & Gap | Literature is synthesised thematically (not summarised paper-by-paper); the gap is precisely articulated and clearly emerges from the literature reviewed; key authors and seminal works are cited | Literature is relevant and mostly synthesised; the gap is stated but could be more precisely defined or better connected to the review | Literature is present but reads as an annotated bibliography; gap is vaguely stated ("few studies have examined this") without specificity | Literature is minimal, outdated, irrelevant, or entirely absent; no gap is identified |
| Theoretical Grounding | Theory is clearly identified, its relevance is justified, constructs are defined, and hypothesised relationships are shown in a conceptual framework; theory informs the RQs and methodology | Theory is named and relevant but its application to the study is not fully developed; conceptual framework is present but could be more detailed | Theory is mentioned but not explained or applied; it is unclear how theory informs the RQs or method; conceptual framework is missing or incoherent | No theory is identified; study is atheoretical without justification |
| Methodological Rigour | Research design, sampling, data collection, and analysis are specified in detail with justifications; validity/reliability/trustworthiness are addressed; limitations are acknowledged; the method is clearly capable of answering the RQs | Methodology is appropriate and mostly specified; some elements lack detail or justification; limitations are mentioned but not fully explored | Methodology is described in general terms; key details (sample size, analysis technique, validity strategy) are missing; the link between method and RQs is unclear | Methodology is missing, incoherent, or clearly incapable of answering the RQs |
| Ethical Awareness | Ethical issues are identified and addressed with specific mitigation strategies; consent procedures, data security, and confidentiality are detailed; ethics approval status is clear; BCA-specific concerns (algorithmic bias, data provenance) are addressed where relevant | Ethical issues are acknowledged and standard procedures (consent, confidentiality) are described; mitigation is general rather than specific to the study | Ethics is mentioned in passing with generic statements; no specific procedures or risk assessment are provided | Ethics is not addressed or the proposed research is clearly unethical |
| Feasibility & Planning | Timeline is detailed, realistic, and includes buffer time; resources are identified; dependencies are recognised; the scope is clearly achievable within the capstone constraints | Timeline is present and generally realistic; some tasks lack detail; resources are mostly identified | Timeline is overly optimistic, vague, or missing key phases; resources are not considered; scope appears unachievable | No timeline or the proposed scope is clearly impossible within the constraints |
| Writing & Presentation | Writing is clear, concise, and well-organised; the golden thread is visible throughout; citations and references are correctly formatted; the proposal reads as a coherent document, not separate sections stitched together | Writing is generally clear with minor issues; sections are connected but transitions could be smoother; citation format has minor inconsistencies | Writing is unclear in places; sections feel disconnected; citation and formatting issues are frequent enough to distract | Writing is unclear throughout; no logical flow; citations are missing or chaotic; the document appears to be a first draft |
28–32: Outstanding — ready for submission with minor revisions. 22–27: Strong — address identified weaknesses before submission. 16–21: Needs substantial revision — focus on the weakest criteria before submitting. 8–15: Not yet ready — schedule an additional supervisor consultation to discuss fundamental issues before resubmission.
6. From Proposal to Dissertation — The Road Ahead
With your proposal submitted, you transition from planning to execution. Weeks 8–30 form the longest phase of the capstone, and it helps to understand the roadmap from the beginning.
6.1 The Capstone Lifecycle — Post-Proposal
Deepen your methodology chapter. Develop instruments (survey questionnaire, interview protocol, experiment design, system architecture). Pilot test and refine. Finalise sampling strategy. Obtain ethics approval. This is where your proposal's methodology skeleton becomes a complete, executable research design.
Execute your data collection plan. For BBA: distribute surveys, conduct interviews, run experiments, access secondary datasets. For BCA: collect or generate datasets, implement algorithms, run experiments, log system performance. Document everything — deviations from plan, unexpected challenges, sample characteristics. This documentation becomes part of your methodology chapter.
Analyse your data using the techniques specified in your proposal. Write the results/findings chapter. Write the discussion chapter — connect findings back to literature, theory, and RQs. This is the intellectual core of your dissertation. Start early; analysis always takes longer than expected.
Complete all chapters (Introduction, Literature Review, Methodology, Results, Discussion, Conclusion). Revise, edit, proofread. Format according to institutional guidelines. Prepare and deliver your oral defence/viva voce presentation. Submit final dissertation.
6.2 Proposal-to-Dissertation Mapping
| Proposal Section | Becomes Dissertation Chapter(s) | What Changes |
|---|---|---|
| Introduction & Problem Statement | Chapter 1: Introduction | Expanded with more context; updated to reflect what was actually studied (vs. planned) |
| Literature Review & Gap | Chapter 2: Literature Review | Significantly expanded (3,000–5,000 words); deeper synthesis; more sources; updated with literature published after the proposal |
| Conceptual Framework | Chapter 2 (or integrated into Ch. 3) | Refined based on deeper literature engagement; may evolve as data collection reveals new theoretical insights |
| Proposed Methodology | Chapter 3: Methodology | Expanded with full detail; instrument development and piloting reported; actual (vs. planned) procedures documented; deviations justified |
| Ethical Considerations | Integrated into Chapter 3 | Updated with actual ethics approval documentation; any ethical issues encountered during research are reported |
| N/A (proposal only) | Chapter 4: Results / Findings | Completely new — this is the data you collect and analyse post-proposal |
| N/A (proposal only) | Chapter 5: Discussion | Completely new — interpretation of results in context of literature and theory |
| N/A (proposal only) | Chapter 6: Conclusion | Completely new — summary of contributions, limitations, implications, future research |
Students who invest seriously in their proposal — treating it as the foundation of the dissertation, not a bureaucratic hurdle — write better dissertations in less time. The proposal's introduction becomes the dissertation's Chapter 1 (expanded, not rewritten from scratch). The proposal's literature review becomes the core of Chapter 2 (deepened, not replaced). The proposal's methodology becomes the skeleton of Chapter 3 (fleshed out with detail, not redesigned). The weeks you spend on the proposal now are weeks you do not spend rewriting fundamental sections later. A weak proposal produces a weak dissertation — and the time to fix it is now.
7. Proposal Exemplars — BBA and BCA Annotated Outlines
Below are two annotated proposal outlines — one BBA, one BCA — showing how the template adapts to different disciplines. These are not complete proposals; they are structural maps showing what each section contains and how sections connect.
7.1 BBA Exemplar Outline
| Section | Key Content | Source (Prior Weeks) |
|---|---|---|
| 1. Abstract | Problem: Mixed evidence on ESG-firm value link in emerging markets. Gap: No study has examined Indian manufacturing specifically using mandatory ESG disclosure data post-SEBI 2021 regulation. Method: Panel data regression on BSE 500 manufacturing firms, 2021–2025. Contribution: First post-regulation evidence from Indian manufacturing; informs policy debate on disclosure mandates. | All sections (synthesise after drafting) |
| 2. Problem Statement | India mandated ESG disclosure (SEBI, 2021) for top 1,000 listed firms. Compliance costs are substantial (estimated 0.5–1.2% of revenue). But does disclosure actually benefit firms financially? Evidence from developed markets (Kumar 2021; Gupta 2023) suggests yes; emerging market evidence is scarce and contradictory (Sharma 2022 vs. Rao 2021). This matters for Indian managers deciding whether to treat ESG as compliance or strategy. | Week 3 (Problem Formulation) |
| 3. Research Questions | RQ1: What is the relationship between ESG disclosure scores and Tobin's Q among Indian manufacturing firms post-SEBI 2021? RQ2: Does this relationship differ across environmental, social, and governance sub-scores? RQ3: Is the relationship moderated by firm size, ownership structure (promoter vs. institutional), or export orientation? | Week 3 (RQs & Hypotheses) |
| 4. Literature & Gap | Three themes: (1) ESG and financial performance — consensus on positive link in developed markets, mixed in emerging; (2) Mandatory vs. voluntary disclosure — mandatory disclosure may level the playing field; (3) Indian context — limited studies, none using comprehensive post-2021 panel data. Gap: No study has examined the ESG-firm value relationship in Indian manufacturing using the new mandatory disclosure regime data. | Week 4 (Search) + Week 5 (Synthesis) |
| 5. Theoretical Framework | Stakeholder Theory (Freeman, 1984): Firms that satisfy stakeholder expectations (including ESG) outperform those that don't. Signalling Theory (Spence, 1973): ESG disclosure signals quality management to investors. Hypotheses: H1: ESG disclosure positively associated with Tobin's Q. H2: Governance sub-score has the strongest individual effect. H3: Relationship stronger for firms with higher institutional ownership. | Week 5 (Theory Integration) |
| 6. Methodology | Paradigm: Post-positivist. Design: Longitudinal panel study. Sample: BSE 500 manufacturing firms with complete ESG data 2021–2025 (estimated N≈200–250 firms, 4 years = 800–1,000 firm-year observations). Data: ESG scores from Bloomberg/Refinitiv; financial data from ProwessIQ. Analysis: Fixed-effects panel regression (Hausman test to confirm); diagnostic tests for multicollinearity (VIF), heteroskedasticity (Breusch-Pagan), and autocorrelation (Durbin-Watson). | Week 2 (Paradigm) + Weeks 8–12 (full methodology) |
| 7. Ethics | Secondary data only (publicly available financial and ESG data) — no human participants. Data accessed through institution's Bloomberg terminal subscription. No consent required. All data is firm-level and publicly reported; no individual-level data. Analysis code and results will be shared for reproducibility. | Week 6 (Ethics) |
| 8. Timeline | Weeks 8–10: Finalise methodology, obtain data access, build panel dataset. Weeks 11–15: Data collection (extract, clean, merge ESG and financial data). Weeks 16–20: Analysis (descriptive statistics, diagnostic tests, panel regressions, robustness checks). Weeks 21–25: Write results and discussion chapters. Weeks 26–28: Write introduction and conclusion; revise literature review. Weeks 29–30: Final revisions, formatting, proofreading, viva preparation. | Week 7 (This week) |
7.2 BCA Exemplar Outline
| Section | Key Content | Source (Prior Weeks) |
|---|---|---|
| 1. Abstract | Problem: Code-mixed hate speech on Indian social media is widespread; detection models perform poorly on code-mixed text. Gap: No study has systematically compared parameter-efficient fine-tuning (PEFT) methods for this task — prior work uses only full fine-tuning, which is computationally expensive. Method: Compare LoRA, adapters, and prefix-tuning applied to IndicBERT and XLM-R on the HASOC 2023 Hindi-English dataset. Expected contribution: Identify which PEFT method offers the best accuracy-efficiency trade-off for low-resource code-mixed NLP. | All sections (synthesise after drafting) |
| 2. Problem Statement | India has 467 million social media users (Statista, 2024), and Hindi-English code-mixed text dominates informal online communication. Hate speech in this context is pervasive — yet detection models achieve F1 scores of only 0.58–0.64 (Joshi 2022; Mandl et al., 2023). Full fine-tuning of large multilingual models is computationally prohibitive for many Indian research groups and startups. PEFT methods promise near-equivalent performance at a fraction of the computational cost — but have not been systematically evaluated for code-mixed hate speech. | Week 3 (Problem Formulation) |
| 3. Research Questions | RQ1: How do LoRA, adapters, and prefix-tuning compare to full fine-tuning in F1 score for Hindi-English code-mixed hate speech detection? RQ2: What is the computational efficiency (training time, GPU memory, parameter count) trade-off for each PEFT method? RQ3: Does the relative performance of PEFT methods differ between IndicBERT (trained on Indian languages) and XLM-R (multilingual, not India-specific)? | Week 3 (RQs & Hypotheses) |
| 4. Literature & Gap | Three themes: (1) Code-mixed NLP — existing models and their limitations, the HASOC shared task as evaluation benchmark; (2) Hate speech detection — deep learning approaches, transformer models, evaluation metrics; (3) Parameter-efficient fine-tuning — LoRA, adapters, prefix-tuning, their theoretical basis (Lottery Ticket Hypothesis), prior comparisons in high-resource languages. Gap: No published comparison of PEFT methods for code-mixed hate speech; prior work either uses full fine-tuning or evaluates PEFT on monolingual, high-resource tasks. | Week 4 (Search) + Week 5 (Synthesis) |
| 5. Technical Framework | Architecture: Transformer-based encoder (IndicBERT, XLM-R) → PEFT adaptation layer (LoRA/adapters/prefix-tuning) → classification head (hate/offensive/neutral). Evaluation: 5-fold cross-validation; metrics: F1 (macro), precision, recall; statistical comparison: McNemar's test. Computational tracking: GPU memory usage (nvidia-smi), training time, trainable parameter count, FLOPs. | Week 5 (Framework Integration) |
| 6. Methodology | Paradigm: Design science research (Peffers et al., 2007) — the PEFT comparison framework is the designed artefact. Dataset: HASOC 2023 Hindi-English code-mixed track (≈8,000 labelled instances; train/dev/test split). Preprocessing: script normalisation (Romanised Hindi vs. Devanagari), emoji handling, URL/mention removal. Implementation: HuggingFace Transformers + PEFT library; experiments on institutional GPU cluster (A100 40GB); each configuration run 3 times with different seeds to assess stability. Comparison baselines: full fine-tuning, frozen transformer + classifier head (simple baseline). | Week 2 (DSR Paradigm) + Weeks 8–12 (full methodology) |
| 7. Ethics | Dataset: HASOC is a publicly available research dataset; terms of use permit academic research. No new human data collection; no user-identifiable information in the dataset. Algorithmic fairness: evaluate model performance across hate speech categories to check for systematic misclassification of minority-targeted hate speech. Dual-use: hate speech detection models can also be used to evade detection (adversarial training is a known dual-use concern) — this risk is acknowledged but the public safety benefit of improved detection is judged to outweigh the evasion risk. Code and trained model weights will be publicly released under Apache 2.0 licence. | Week 6 (Ethics) |
| 8. Timeline | Weeks 8–10: Literature review expansion; experimental design finalisation; environment setup. Weeks 11–15: Implementation — PEFT method implementations; baseline model training; systematic experimentation (3 methods × 2 models × 3 seeds = 18 configurations + baselines). Weeks 16–20: Analysis — results aggregation, statistical testing, ablation studies, error analysis. Weeks 21–25: Write results/findings and discussion chapters. Weeks 26–28: Write introduction and conclusion; revise literature review; prepare code release. Weeks 29–30: Final revisions, formatting, viva preparation. | Week 7 (This week) |
The exemplars above show the level of specificity and coherence expected in a capstone proposal. Notice how each section connects to the next, how RQs emerge from the literature gap, how theory informs methodology, and how methodology is specified in concrete, implementable detail. Your proposal should match this level of specificity for YOUR topic — not by copying the exemplar topics, but by applying the same structural logic to your own RQs, your own literature, and your own methodology.
Think Deeper — Cross Questions
Discuss in pairs before sharing with the class.
A student's proposal states: "This study will use a mixed-methods approach — surveys for quantitative data and interviews for qualitative data." The research questions are: "What factors influence consumer adoption of electric vehicles in India?" The proposal does not specify which factors will be explored through which method, how the methods will be integrated, or how contradictions between survey and interview findings will be resolved. Diagnose the problems with this methodology section. What specific changes would transform it from a vague description into a rigorous research design?
You are preparing for a supervisor consultation. You have two major uncertainties: (a) you are torn between a case study design and a survey design for your RQs, and (b) you are unsure whether your sample size is adequate. Draft the specific questions you would ask your supervisor about each uncertainty. Then reflect: how are these questions different from simply saying "I'm not sure about my methodology"? What makes a question productive in a supervision context?
Compare the BBA and BCA exemplar outlines in Section 7. Identify three structural differences between them. Are these differences intrinsic to the disciplines, or could a BCA proposal use the BBA structure (and vice versa)? What does this tell you about the relationship between disciplinary conventions and proposal structure?
You receive contradictory feedback on your proposal: your supervisor suggests expanding the literature review, but a peer reviewer says it's already too long and detracts from the methodology. How do you resolve this contradiction? What criteria would you use to decide which feedback to prioritise? At what point does incorporating feedback strengthen the proposal, and at what point does it produce a document that tries to please everyone and satisfies no one?
Quick Check — Proposal Diagnosis
Each excerpt is from a student's research proposal. Diagnose the primary problem.
1. "Research methodology: This study will employ a qualitative approach. Data will be collected through interviews. The data will be analysed to identify themes. The findings will be presented in the results chapter."
2. "This research will examine the impact of digital transformation on business performance in the global economy. A survey will be distributed to business professionals worldwide to collect data on digital transformation practices and firm performance outcomes."
3. "RQ1: What is the relationship between customer satisfaction and loyalty? RQ2: How does service quality affect customer retention? RQ3: What factors influence brand perception? RQ4: How do pricing strategies impact purchase behaviour?"
4. "Limitations: This study has no significant limitations. The sample is adequate, the methodology is robust, and the expected findings will contribute substantially to both theory and practice. All potential confounding variables have been controlled for in the research design."
Knowledge Check — Interactive Quiz
Test your understanding of research proposal writing and preparation.
Q1. What is the "golden thread" in a research proposal?
Q2. In the standard proposal structure, which section should you write LAST — even though it appears first in the document?
Q3. Which of the following is the most productive way to use a supervisor consultation?
Q4. A student's proposal states: "I will conduct a survey and analyse the data using SPSS." What key information is missing from this methodology statement?
Q5. Which is the most common reason capstone proposals are returned for revision?
Lab Activity — Proposal Drafting & Peer Review
Part A: Proposal Self-Audit — Where Are You Now? (20 min)
Before writing, audit your current position. For each proposal section, rate your readiness:
| Proposal Section | Ready (have all material) | Partial (have some material) | Not Started | Key Source |
|---|---|---|---|---|
| 1. Title & Abstract | Write last | |||
| 2. Problem Statement | Week 3 output | |||
| 3. Research Questions | Week 3 output | |||
| 4. Literature & Gap | Week 4 + Week 5 output | |||
| 5. Theoretical Framework | Week 5 output | |||
| 6. Methodology | Weeks 8–12 (outline now) | |||
| 7. Ethics | Week 6 output | |||
| 8. Timeline & Resources | Create this week |
For sections marked "Partial" or "Not Started," identify the specific gap. This becomes your priority list for this week's writing.
Part B: Structured Proposal Drafting (4–5 hrs across the week)
Work through the proposal sections using the templates and outlines in Section 2. Follow this sequence:
- Write Sections 2 and 3 first (Problem Statement and RQs). These are the foundation — everything else serves them. Use your Week 3 work directly. If these sections are weak, the entire proposal is weak.
- Write Section 4 (Literature Review summary). Condense your synthesis matrix (Week 5) into a 600–900 word summary that demonstrates command of the literature and clearly articulates the gap. Remember: synthesis, not annotated bibliography.
- Write Section 5 (Theoretical Framework). Draw your conceptual framework as a diagram first — the text explains the diagram. Name your theory, define constructs, show relationships.
- Write Section 6 (Methodology). Be as specific as possible — you will refine this in Weeks 8–12, but the evaluator needs to see that you have a clear plan. Use the exemplars in Section 7 as models for the level of detail expected.
- Write Sections 7 and 8 (Ethics and Timeline). Use your Week 6 ethics self-assessment. Create a detailed timeline with specific tasks, not vague phases.
- Write Section 1 LAST (Abstract). By now you know exactly what your proposal argues. Summarise it in 150–250 words.
Use this structure as your writing template. For each section, fill in the "Your Content" column.
| # | Section | Key Questions to Answer | Your Content |
|---|---|---|---|
| 1 | Abstract | What? Why? How? So what? (in 150–250 words) | |
| 2 | Introduction & Problem | What is the problem? Why does it matter? To whom? At what scale? What happens if unsolved? | |
| 3 | Research Questions | Primary RQ? Sub-RQs? How do they emerge from the gap? Are they specific and researchable? | |
| 4 | Literature & Gap | What does prior research show? What themes emerge? What is the specific gap? How does this proposal address it? | |
| 5 | Theoretical Framework | Which theory? Why this theory? Key constructs? Hypothesised relationships? Conceptual diagram? | |
| 6 | Methodology | Design? Population/sample? Data collection? Analysis plan? Validity/trustworthiness? Limitations? | |
| 7 | Ethics | Consent? Confidentiality? Data security? Risks and mitigation? Approval status? | |
| 8 | Timeline & References | Phases? Tasks? Deadlines? Resources needed? References cited? |
Part C: Structured Peer Review (60 min)
Exchange complete proposal drafts with a partner. Apply the review protocol below. The goal is not to find every typographical error — it is to identify the structural issues that will determine whether the proposal is accepted or returned for revision.
- The "So What" Test (Section 2): Read the problem statement. Cover it. Can you explain to someone else: (a) what the problem is, (b) why it matters, and (c) to whom? If not, the problem statement needs revision.
- The "Where Did That Come From" Test (Section 3): Read the RQs. Do they clearly emerge from the literature gap described in Section 4? If you hadn't read Section 4, would the RQs seem arbitrary? Mark any RQ that feels disconnected from the literature.
- The "Synthesis Check" (Section 4): Is the literature organised by theme or by author? Underline every sentence that follows the pattern "Author X (year) found Y." If more than 30% of sentences follow this pattern, the section is summary, not synthesis.
- The "Could Someone Else Execute This" Test (Section 6): If you were given this methodology section and asked to execute the research, would you know exactly what to do? Or would you have to make major decisions that the proposal didn't address? Flag every missing detail.
- The "Feasibility Reality Check" (Section 8): Does the timeline account for: institutional ethics approval (2–4 weeks), participant recruitment (often slower than expected), data cleaning, analysis iterations, writing and revision, and a 20% buffer? If not, flag it.
Exit Ticket
Submit with your proposal self-audit and draft.
- Complete the proposal self-audit (Part A). Which section of your proposal is strongest? Which needs the most work before submission?
- Paste your problem statement and primary RQ (Sections 2 and 3 of your draft). Are they tightly connected — does the reader understand why these RQs and not others?
- Identify the one aspect of your proposal where you feel least confident. What specific guidance do you need from your supervisor?
- What is the single most valuable insight you gained from the peer review of your proposal (or from reviewing a peer's proposal)?
- Looking ahead to Weeks 8–30: What is the biggest risk to completing your capstone on time and to quality? What is your contingency plan?
Key Takeaways — Week 7
A strong proposal is not bureaucracy — it is the single most productive investment you can make in your capstone. It aligns your supervisor, the evaluation committee, and your future self around a clear, feasible, and defensible plan. Every hour spent on the proposal saves multiple hours during execution.
The golden thread — problem → gap → RQs → theory → method → timeline — is what separates a proposal that convinces from one that merely describes. Every section must connect to the next. If a section could belong to any proposal, it doesn't belong in yours.
The best supervision relationships are built on preparation, specificity, and genuine intellectual engagement. Come to consultations with annotated drafts and specific questions. Engage with feedback thoughtfully — don't passively accept or defensively reject it.
The most common proposal failure is excessive scope. A narrow, deep, feasible study earns higher marks than a broad, shallow, impossible one. You can always extend a completed capstone. You cannot complete an impossible one.
Facilitator Notes
Preparation Checklist
- Prepare the proposal template (Section 2.1) as a downloadable Word/Google Docs document that students can use directly as their writing template. Include section headings, prompts, and word count targets.
- Create the proposal self-audit (Part A) as a separate handout or editable spreadsheet. Students should complete this before writing begins — it identifies gaps and prioritises effort.
- Prepare 2–3 annotated exemplar proposals (one strong, one developing, one BBA and one BCA) to show during the opening workshop. Annotate them to highlight the golden thread, specific methodology, and gap articulation — show what "good" looks like concretely.
- Schedule individual supervisor consultations for Day 4. Ensure each student has at least 20 minutes. Distribute consultation slots early in the week so students know their deadline for submitting drafts to supervisors (48 hours before the consultation).
- Coordinate with all capstone supervisors: share the proposal template, evaluation rubric, and exemplars so that feedback across supervisors is broadly consistent. A student whose supervisor expects one format and a peer whose supervisor expects another creates confusion.
- Prepare the peer review protocol (Part C) as a printed handout or checklist. Structured peer review is significantly more effective than "exchange drafts and give feedback."
Common Student Difficulties
- Translating Weeks 1–6 work into proposal prose: Students have done the preparatory work but struggle to transform it into a flowing document. They may paste their Week 3 problem statement and Week 5 synthesis matrix directly into the proposal without adapting the format, tone, or level of detail. Remind them: the proposal is a new document that synthesises prior work — it is not a compilation of prior assignments.
- Methodology section is the weakest across all proposals: At this stage, students have not yet taken the full methodology modules (Weeks 8–12). Their methodology sections will be outlines, not finished chapters. This is expected. Guide them to be as specific as possible with what they know now, and identify what needs to be developed in Weeks 8–12. The evaluator expects a coherent plan, not a complete methodology chapter.
- Overwriting the literature review: Students want to demonstrate how much they've read and produce literature reviews that are 40–50% of the proposal. The proposal's literature review is a summary (600–900 words), not the full chapter. Students who struggle with this should write the full section, then cut it by 50% — keeping only what is essential for justifying the gap.
- Confusing the proposal abstract with the dissertation abstract: The proposal abstract describes what the research WILL do (future tense or present). The dissertation abstract describes what the research DID (past tense). Proposal abstracts that read like completed research ("This study found that...") signal confusion about the research stage.
- Anxiety about "locking in" a plan: Students fear that once the proposal is submitted, they cannot change anything. Address this explicitly: the proposal is a starting point, and methodological refinement is expected. What matters is that changes are justified, not that they are avoided.
- Supervisor consultation anxiety: Many students have never had a one-on-one academic consultation and are unsure how to prepare or what to expect. Walk through the preparation checklist (Section 4.1) explicitly. Normalise the experience: the supervisor's job is to improve the work, not to judge the student.
Pacing Tips
- This is a fundamentally different week from Weeks 1–6. It is writing-intensive, not content-delivery-intensive. The opening workshop should be brief and practical (20–30 minutes maximum). The bulk of the week is individual writing, peer review, and consultations. Do not over-lecture.
- The self-audit (Part A) is essential — do not skip it. Students who skip directly to writing without auditing their readiness waste time writing sections for which they have no material while neglecting sections for which they have everything they need.
- Peer review (Part C) works best when students are paired across topics rather than within the same topic. A student studying ESG disclosure reviewing a proposal on code-mixed NLP cannot get lost in domain details — they are forced to evaluate structure, coherence, and clarity, which is exactly what peer review should focus on.
- Build in a 24-hour "cooling off" period between completing the draft and submitting it. Students who submit immediately after finishing miss obvious errors that a fresh reading would catch. Encourage students to finish their draft by end of Day 3, wait until Day 4 morning to re-read it, and then submit to their supervisor.
- The exit ticket's Question 5 (biggest risk to capstone completion) is valuable diagnostic data. Aggregate the responses to identify systemic risks (e.g., data access delays, software unavailability, participant recruitment challenges) that the programme can address proactively rather than reactively.