Continuous Improvement

Attained levels are set against those targets year by year. Every outcome cleared its target in every year of the assessment period, and every outcome improved between the first year and the last.

The margins widened rather than narrowed even as the target rose. PO1 cleared its 2023-24 target by +0.15 and its 2025-26 target by +0.27; PSO1 by +0.20 and then +0.37. Three outcomes dipped between 2023-24 and 2024-25 — PO4 (1.67 to 1.62), PO5 (1.44 to 1.38) and PSO2 (1.72 to 1.71) — and all three recovered strongly in 2025-26, none having fallen below its target at any point.

PO1 (2.22) and PSO1 (2.15) have additionally crossed 2.00. That threshold is a separate benchmark from the target — it is the mapping level used for curricular-gap analysis in Criterion 2, on the articulation-matrix scale rather than the target scale, and crossing it is not what the target requires.

The department records observations against every outcome for every year, and in the latest cycle every one reads "Target achieved". The gap analysis is therefore not about failure to meet targets — it is about where the department intends to push further, and it is recorded outcome by outcome alongside the action taken.

Read across the three years, the shape of the gap changes. In the first cycle each outcome's first recorded action was "target level increased for next AY" — the target itself moving up was treated as the response to achievement. By the 2025-26 cycle that entry has dropped away and the recorded actions are all substantive interventions.

Each outcome carries a numbered plan of action, and the actions are specific to what that outcome measures rather than generic.

PO1 (basic and discipline knowledge) — remedial classes in engineering mathematics, science and core engineering for slow learners; micro-projects applying analytical skills to design-parameter calculation; doubt-solving sessions with supporting material.

PO2 (problem analysis) — exposure to real engineering problems through industrial visits and expert lectures; the New Palanpur for New India project competition run under the SSIP cell; brainstorming during the Shodh-Yatra project-identification process.

PO3 (design and development) — Embedded Systems and IoT courses incorporated and regularly updated to cover design of solutions addressing public health, safety, cultural, societal and environmental considerations; seminars, hands-on workshops and expert lectures on problem-solving approaches.

PO4 (engineering tools) — students building small modules in Electronics Workshop such as power supplies, extension boards, measuring probes and RJ45 connectors; annual procurement of modern laboratory equipment against requirements identified by subject teachers; computer laboratories equipped for Scilab, Keil, Proteus, Xilinx, Multisim, Arduino IDE and KiCad.

PO5 (society, sustainability and environment) — participation in tree plantation, Swachh Bharat Abhiyan, thalassemia awareness, blood donation, NSS activity and International Yoga Day; students required to treat standards, safety norms and environmental sustainability as technical constraints in their own designs.

PO6 (project management) — students taking leadership roles within project teams; identifying real-world problems and framing their own project statements; SSIP-funded prototypes. PO7 (life-long learning) — career awareness programmes and finishing school; assigned presentations; encouragement to develop applications addressing societal needs.

PSO1 — industrial visits covering installation, maintenance, testing and troubleshooting of real systems; domain seminars; final-year projects run end to end from ideation to implementation with troubleshooting emphasised. PSO2 — hands-on training on Scilab, Proteus, Multisim, Xilinx and KiCad; Scratch coding competitions; industry-oriented projects and internships using professional design tools.

Academics are audited at four levels, each against its own criteria. The Commissionerate of Technical Education audits against the TEIM (Technical Institute Inspection Manual), under which it governs all institute activity. GTU's Local Inspection Committee — experienced faculty drawn from other GTU-affiliated institutes — audits compliance with university norms. An inter-departmental Academic Inspection Committee of senior faculty from other departments of the institute verifies compliance with both CTE and GTU norms internally. And the HOD monitors daily conduct against the timetable, the completeness of course files, equipment utilisation reports and history cards, and the quality of live sessions recorded in an Academic Monitoring Log Book.

The HOD-level criteria are the most detailed, applied as an explicit fifteen-document checklist against which every course file is verified.

Audits ran in every year of the assessment period. HOD monitoring is continuous through each semester. CTE inspection is periodic and, notably, also unannounced — CTE sends inspection committees without prior intimation and monitors day-to-day academic activity through CCTV on a continuous basis. GTU's committee visits on a predefined date, and the inter-departmental committee is convened as required.

The record is honest about what has and has not yet happened. For 2025-26 the university inspection took place on 10 April 2026, while the CTE and inter-departmental inspections for that year are recorded as yet to be conducted. For 2024-25 the university inspection is recorded as not scheduled by the university.

Each level has a stated method and produces a specific artefact. CTE governs under TEIM, monitors through CCTV, and issues notices requiring written explanation where misconduct is found. GTU's committee prepares a deficiency report and submits it to the institute through the university. The inter-departmental committee observes academic activity across departments and brings lapses to the Principal.

HOD monitoring inspects daily activity against the timetable, checks course files, equipment utilisation reports and history cards, records observations of live sessions in the Academic Monitoring Log Book, and reviews requirements for new equipment, ICT tools, hardware, software and infrastructure alongside write-offs.

The SAR reproduces the actual artefacts — the TEIM front page, the CTE inspection report from the Cogent portal, departmental and faculty academic performance pages from TEIM, three pages of the GTU Local Inspection Committee report, and the inter-departmental inspection order and report.

The department argues effectiveness on three grounds, which is a more testable claim than asserting the audits work.

First, continuity: audits are recorded in each of the four years, with HOD monitoring every semester and at least one external or inter-departmental inspection in every year.

Second, that the audits produced documented corrections rather than observations alone — course files updated regularly, HOD feedback on content delivery arising from log-book observations, continuous assessment introduced for laboratory sessions, beyond-curriculum topics identified and delivered, expert lectures and industrial visits conducted, corrective measures taken against the GTU deficiency report, and written explanations obtained where serious misconduct was found.

Third, that the audit system is the named instrument for the improvement actions elsewhere in the criterion — HOD academic monitoring appears in the action lists for both the success index (7.2) and final-year academic performance (7.4). That is what closes the loop opened by the gap analysis in 7.1: a gap is identified, a plan recorded, and its implementation verified at the next audit.

Corrective action is attached to each audit level. CTE and inter-departmental findings of serious misconduct require written explanation from the faculty concerned. GTU deficiency reports are answered with corrective measures by the institute. HOD monitoring produces the five actions listed under D.

Beyond individual audits, the department operates the standing cycle described in 7.1 — the ±3 percentage point target revision — so that each audit cycle is assessed against a target reflecting the previous cycle's result rather than a static benchmark.

The actions carried forward from this assessment period are those recorded under 7.2, 7.3 and 7.4, and the audit system is the mechanism through which their implementation is monitored.