PadhaikoAll subjects

Concept note submission

Project I (ENCT 413)

Open in the Padhaiko app

4.1 Submission of concept note to the department in the second week after the commencement of seventh semester

A Concept Note is the first formal written checkpoint of Project I. Because the ENCT 413 syllabus requires submission in the second week after the commencement of the seventh semester, groups have only about 10 to 14 days after classes begin to form a team, choose a track, identify a concrete problem, run an initial background check, and submit a concise 1–2 page summary to the department.

Definition

Project Concept Note

A concept note is a brief, high-signal pre-proposal document (typically 1 to 2 pages, roughly 400–800 words) submitted to the Department Project Committee in Week 2 of the seventh semester. It pitches what engineering problem the group intends to solve, why it matters, which track (research, product, or internship) is chosen, how the team plans to approach it, and what resources make it feasible before spending effort writing a full proposal.

AspectConcept Note (Week 2)Project Proposal (Week 3)
PurposeQuick screening of topic validity, originality, scope fit, and supervisor/track matchFormal technical blueprint, detailed methodology, stack selection, and semester work plan
Typical Length1–2 pages8–15 pages (in department-approved format)
Literature Depth3–5 key references or existing systems proving the gap existsComprehensive synthesis of 12–20 papers, relevant theories, and existing systems
Methodology DetailHigh-level pipeline or block diagram (4–6 sentences)Detailed architecture, data flow, algorithms, tools, Gantt chart, and evaluation plan
Evaluation ModeWritten review / short screening by committee and supervisorFormal report submission plus oral presentation and defence

4.1.1 Standard Anatomy of a Strong Concept Note

Even when a department issues a one-page template form, every strong concept note contains seven crisp elements:

Essential Sections of an ENCT 413 Concept Note
SectionWhat to IncludeCommon Mistake to Avoid
1. Header & MetadataTentative project title, track (Research / Product / Internship), member names & roll numbers, proposed supervisor (and prospective mentor if internship)Leaving track blank or listing 4 members (max is 3)
2. Background & Problem Statement1 short paragraph naming the target user/domain, the exact bottleneck, and evidence of the gapWriting generic essays like "AI is changing the world"
3. Objectives & Phased Scope3–4 measurable objectives; 2–3 sentences separating Project I PoC from Project II completionPromising huge features with no boundary
4. Proposed Methodology (Brief)Input -> core processing/algorithm -> output, plus preliminary architecture sketch or workflowNaming frameworks ("we will use React and Python") without stating the core engineering logic
5. Feasibility & ResourcesDataset source, hardware/sensors, compute environment, and host mentor letter (if internship)Assuming unverified private hospital or corporate data
6. Expected OutcomesTangible artifacts (working PoC, benchmark results, deployed module)Writing only "a good software system"
7. Key Initial References3–5 properly formatted citations (papers, standards, or existing system links)Zero citations or unverified blog links
Example 4.1

Drafting a Complete Week-2 Concept Note Outline (Research Track)

A 3-member group has chosen the Research Track and wants to submit a concept note in Week 2 on Low-Light Nepali License Plate Detection and Character Recognition. Write a complete, well-structured concept note outline ready for department screening.

Draft Header, Track, and Crisp Title:

  • Title: Illumination-Robust Nepali Devanagari License Plate Detection and Recognition Using Lightweight Multi-Scale Feature Enhancement
  • Track: Research Track | Group Size: 3 Members | Supervisor: [Assigned Faculty Name]

Write Problem Statement, Objectives, and Phased Scope:

  • Problem Statement: Automated traffic enforcement and campus gate logging in Nepal struggle with Devanagari embossed plates under night glare, rain, and motion blur. Existing open-source ALPR pipelines focus on Latin scripts and drop sharply in accuracy on low-light Nepali plates.
  • Objectives: (1) Curate and annotate a multi-lighting Nepali license plate dataset (day, dusk, headlight glare); (2) evaluate low-light image enhancement paired with lightweight object detection and CTC/attention-based Devanagari OCR; (3) benchmark accuracy-vs-latency trade-offs on edge-class GPUs.
  • Scope: Project I delivers the curated dataset (1,000+ annotated images), low-light enhancement + detector baseline, and PoC recognition metrics; Project II adds temporal frame aggregation, occlusion robustness, and full ablation benchmarks.

State High-Level Methodology, Feasibility, and Key References:

  • Methodology Outline: Input frame -> Low-light enhancement module (Zero-DCE / Retinex-based) -> Plate localization (YOLOv8n) -> Perspective rectification -> Devanagari character/line recognizer -> Post-processing against Nepal province plate grammar.
  • Feasibility: 400 sample daytime/night gate images already pilot-captured on campus with privacy masking; Google Colab / department workstation available for training.
  • Key References: Cite 4 recent papers on low-light ALPR, Zero-DCE enhancement, YOLOv8 detection, and Devanagari scene-text recognition.
Answer:

The concept note fits cleanly into 1–2 pages, declares the Research Track, defines a verifiable Nepali low-light ALPR gap, separates Project I PoC from Project II benchmarks, states a concrete 5-stage pipeline, and proves data/compute feasibility with 4 real references.

4.2 Approval of the concept note by the department

Submitting the concept note in Week 2 triggers a fast department screening before Week 3 proposal writing begins. The goal of concept note approval is to catch unfeasible, duplicated, or underspecified topics early, saving students from writing a 12-page proposal on a doomed idea.

Definition

Concept Note Approval

Concept Note Approval is the formal decision by the Department Project Committee (and supervisor) after reviewing the Week-2 submission. Outcomes generally fall into three categories: Approved (proceed directly to Week-3 Proposal), Approved with Minor Modifications (narrow scope, refine title, or clarify track/dataset in the proposal), or Rejected / Resubmit (pivot to a backup topic or resolve major feasibility/duplication issues).

How the Committee Evaluates a Concept Note and How to Respond
Committee CheckRed Flag That Causes Rejection or RevisionCorrective Action Before Week-3 Proposal
Originality & Non-DuplicationIdentical topic already taken by another 7th-semester group or copied straight from a Minor Project without added depthDifferentiate the core problem/methodology or propose an alternate domain immediately
Engineering DepthTrivial CRUD portal (e.g., basic static college website or simple calculator)Add substantive engineering components (algorithms, concurrency, security, data analytics, or hardware integration)
Feasibility in 2 SemestersUnobtainable data (private bank/hospital records without clearance) or expensive missing hardwareSwitch to validated public/synthetic data or affordable available sensors, and attach proof
Clarity of ObjectivesVague slogans ("build an intelligent platform") with no evaluation planRewrite into 3–4 measurable objectives tied to quantitative metrics or acceptance criteria
Internship ComplianceMissing prospective mentor sign-off or routine support/QA chores disguised as a projectObtain signed mentor letter and scope a self-contained engineering module
Example 4.2

Responding to Conditional Approval ('Approved with Modifications') Between Week 2 and Week 3

A group submitted a Week-2 Concept Note for a Product Track project titled "AI Healthcare Assistant". The department committee returned it as Approved with Modifications, noting: "Title and scope are too broad; clarify data source, safety disclaimer, and exact Project I deliverable before Week-3 Proposal." Show how the group should revise its concept before preparing the proposal.

Deconstruct every committee remark:

  1. "Title and scope too broad" -> "AI Healthcare Assistant" could mean anything from appointment booking to diagnosing cancer.
  2. "Clarify data source" -> Where do symptom-disease mappings or medical guidelines come from? Scraping random blogs is unsafe.
  3. "Safety disclaimer" -> A student project cannot prescribe medication or replace licensed doctors.
  4. "Exact Project I deliverable" -> Must specify what working PoC will be demonstrated by the end of Semester 7.

Reframe the title, clinical scope, and data authority:

  • Revised Title: Bilingual Nepali-English Symptom Triage and Primary Health Center Referral Assistant Using Verified Clinical Guidelines (RAG Architecture)
  • Verified Data Source: Ground responses strictly in official WHO/Ministry of Health primary-care protocols and curated Nepali medical glossaries, citing the source document for every output.
  • Safety Boundary: Explicit UI disclaimer stating non-diagnostic informational support only, plus deterministic red-flag escalation rules (e.g., chest pain -> immediate emergency referral).

Lock Project I PoC target and confirm with supervisor: Define Project I deliverables as: digitized guideline corpus, hybrid vector + keyword retrieval pipeline, red-flag rule engine, and accuracy/hallucination evaluation on 50 doctor-reviewed test queries. Email/meet the supervisor within 48 hours to verify the revision satisfies the committee before drafting the Week-3 Proposal.

Answer:

The group narrows the vague "AI Healthcare Assistant" into a grounded bilingual guideline-based triage assistant using official WHO/MoH documents, adds deterministic safety disclaimers and emergency escalation rules, specifies a measurable 50-query Project I PoC, and verifies the revision with its supervisor ahead of Week 3.

Viva-Style Questions: Concept Note Submission and Approval

Question 1

When must the Concept Note be submitted in Project I according to the ENCT 413 syllabus, and why is this deadline placed so early in the semester?

Syllabus deadline: Section 4.1 specifies submission of the concept note to the department in the second week after the commencement of the seventh semester.

Reason for early timing: The Week-2 screening acts as an early feasibility and originality filter before the Week-3 Proposal Report and Presentation. Catching duplicate topics, missing datasets, or weak engineering scope in Week 2 prevents students from wasting weeks building or writing proposals for unapproved ideas.

Answer:

The concept note is due in the second week after the seventh semester begins. Early submission lets the department verify originality, track fit, and resource feasibility before formal proposal submission in Week 3.

Question 2

How does a Concept Note differ from a Project Proposal in length, purpose, and technical depth?

Purpose and length: A Concept Note (1–2 pages) is a rapid pre-proposal pitch used to confirm topic suitability, non-duplication, and basic feasibility. A Project Proposal (8–15 pages) is a comprehensive technical contract detailing literature synthesis, system architecture, exact algorithms, software/hardware stack, Gantt schedule, and evaluation methodology.

Depth comparison: The concept note summarizes the gap with 3–5 references and a brief pipeline outline, whereas the proposal provides full block/ER/architecture diagrams, comparative literature tables, and verifiable milestones.

Answer:

A Concept Note is a concise 1–2 page Week-2 screening pitch proving problem validity and feasibility, whereas a Project Proposal is a detailed Week-3 formal document specifying full literature review, architecture, tools, work plan, and evaluation metrics.

Question 3

List the essential sections that should appear in an ENCT 413 Concept Note, even if the department only requests a brief 1–2 page write-up.

Core sections:

  1. Header & Metadata: Specific title, declared track (Research/Product/Internship), up to 3 member names/roll numbers, supervisor (and industry mentor if applicable).
  2. Problem Statement: Who faces what gap, backed by observation or literature.
  3. Objectives & Phased Scope: Measurable objectives and clear boundary between Project I PoC and Project II.
  4. Brief Methodology: High-level pipeline or system architecture.
  5. Feasibility & Resources: Confirmed dataset, hardware, compute, or mentor support.
  6. Expected Outcomes & Key References: Tangible deliverables and 3–5 valid citations.
Answer:

A strong concept note includes: (1) title, track, group, and supervisor metadata; (2) problem statement; (3) measurable objectives and phased scope; (4) brief methodology/pipeline; (5) resource and data feasibility; and (6) expected outcomes with 3–5 key references.

Question 4

What are the three typical committee outcomes during Concept Note Approval, and what should a group do immediately if it receives "Rejected / Resubmit"?

Three outcomes:

  1. Approved: Proceed directly to writing the Week-3 Proposal.
  2. Approved with Modifications: Retain the topic, but tighten scope, clarify datasets, or refine title/objectives per committee comments.
  3. Rejected / Resubmit: Topic lacks sufficient engineering rigor, duplicates another group, or depends on inaccessible data/hardware.

Immediate action on rejection: Meet your supervisor within 24 hours, examine the committee's exact written objections, either pivot to your pre-prepared backup topic or completely re-scope the technical core, and submit the revised concept note promptly so Week-3 proposal preparation stays on track.

Answer:

Outcomes are Approved, Approved with Modifications, or Rejected/Resubmit. Upon rejection, immediately review the feedback with your supervisor, activate your backup topic or redesign the technical core for feasibility/originality, and resubmit without delaying the Week-3 proposal timeline.

Question 5

Why might an examiner reject a Week-2 Concept Note titled "College Management System" even if three students promise to build it cleanly in React and Node.js?

Identify academic and engineering gaps:

  1. Common / trivial CRUD scope: Standard student/attendance/fee CRUD portals are overused and typically fall below Major Project engineering depth unless solving an authentic, complex bottleneck.
  2. No verified gap: Existing campus ERPs and open-source systems already handle basic record-keeping.

How such a domain would need reframing to pass: Only if it tackles a genuine, non-trivial engineering challenge—such as automated conflict-free timetable optimization using constraint satisfaction/genetic algorithms, offline-resilient distributed sync across remote campuses, or role-based zero-trust document verification—could it warrant two semesters of Major Project work.

Answer:

A generic "College Management System" is rejected because routine CRUD forms lack sufficient B.E. engineering depth, originality, and research/design challenge for a two-semester Major Project, and already exist as standard ERPs.

← Literature ReviewProposal Report Submission and Presentation →