Engineering Colleges: 60 Days to Build the CO-PO Evidence NBA Needs This October
NBA peer team visits are scheduled October through December for most programs applying in 2026-27. Criteria 3 — Course Outcomes — carries 175 points. Without digital evaluation, generating credible CO-PO attainment data in time is nearly impossible.

October Is Closer Than It Appears
Every year, engineering college administrators mark their NBA peer team visit date on a calendar and believe they have time. Then September arrives, the Self-Assessment Report still has 40 percent of its evidence tables incomplete, and the CO-PO attainment section becomes a frantic exercise in backward calculation.
In 2026, this is especially acute. The NBA accreditation cycle for programs applying under the Washington Accord-aligned Tier 1 and Tier 2 frameworks typically schedules peer visits between October and December. August 9 leaves exactly 60 days before most October windows open.
For engineering colleges that have not yet adopted digital evaluation, this is not a 60-day problem. It is a longer-term structural problem that will express itself as a Criteria 3 score gap in October.
What NBA Actually Measures — and Why It Matters
The National Board of Accreditation evaluates undergraduate engineering programs against a 1,000-point scale. The distribution matters:
| Criterion | Max Points | What It Covers |
|---|---|---|
| 1. Vision, Mission, Goals | 75 | Institutional objectives |
| 2. Program Specific Criteria | 100 | Department-level standards |
| 3. Course Outcomes and Program Outcomes | 175 | CO-PO attainment data |
| 4. Students Performance | 100 | Pass rates, placements, awards |
| 5. Faculty Information | 100 | Faculty qualifications, research |
| 6. Facilities and Technical Support | 75 | Labs, equipment |
| 7. Academic Support Units | 50 | Library, IT |
| 8. Governance, Institutional Support | 75 | Administration quality |
| 9. Continuous Improvement | 150 | How you use data to improve |
| 10. Second Visit (if applicable) | 100 | Verification |
Criteria 3 (175 points) and Criteria 9 (150 points) together account for 32.5 percent of the total score. Both require course outcome attainment data. Without it, the maximum achievable total falls below the 600-point threshold required for NBA accreditation.
This is not a bureaucratic technicality. It is the structural reason why engineering colleges that cannot produce verifiable CO-PO data cannot clear NBA accreditation regardless of their actual teaching quality.
What CO-PO Attainment Data Is
For readers not embedded in engineering accreditation, a brief explanation.
Course Outcomes (COs) are specific, measurable statements of what a student should be able to do upon completing a course. A typical 4-credit course has 5-6 COs, each mapped to Bloom's Taxonomy levels and to specific marks in the end-semester question paper.
Program Outcomes (POs) are the 12 graduate attributes defined by the Washington Accord: engineering knowledge, problem analysis, design and development, investigation, modern tool usage, the engineer and society, environment and sustainability, ethics, individual and team work, communication, project management, and lifelong learning.
CO-PO Attainment is the calculated measure of how many students achieved each CO, at what level, aggregated across all courses in the program, and mapped up to PO achievement.
The NBA peer team does not accept narratives about what students learned. It requires:
This is a data problem first. Everything else follows from having the data.
Why Manual Evaluation Cannot Reliably Generate This Data
An engineering college running paper-based evaluation can theoretically produce CO-PO attainment data. In practice, it almost never produces data that survives peer team scrutiny. Here is why.
Question tagging is retrospective. In manual evaluation, CO tagging of questions is typically done after the question paper is finalized — or after the evaluation is complete. When tags are applied retroactively, peer teams can and do ask for corroboration that the tagging reflects actual evaluation intent.
Mark data is at the total level. Manual evaluation produces a total marks score per student per paper. Question-level marks are recorded on individual answer scripts that are archived (or in many institutions, eventually destroyed). Extracting question-level data from thousands of physical scripts is not feasible within an accreditation preparation window.
The calculations are done in spreadsheets. Even institutions that do the CO-PO work in good faith typically maintain it in Excel files that are not version-controlled, are maintained by a single faculty member, and cannot be audited back to source records.
NBA peer teams are increasingly trained to probe the data sources behind CO-PO tables. Institutions that cannot show the underlying question-level marks are at risk of having their attainment data discounted.
What Digital Evaluation Does Differently
A digital evaluation platform changes the CO-PO pipeline at the source.
When a question paper is set on a digital platform, each question is tagged to a CO, a Bloom's level, and a marks allocation before the exam is administered. The tag is part of the question record, not a post-hoc annotation.
When a student's script is evaluated on-screen, marks are entered question by question. The mark for Question 3 — which is tagged to CO2 at Bloom's Level 3 — is recorded as a data point against CO2 for that student, in that course, in that semester.
Attainment calculations run automatically: the platform computes what percentage of students in each course met the attainment target for each CO, and rolls that up to PO attainment across all courses in the program.
The peer team gets a dashboard. They can see three years of attainment history, drill down to the course level, see the underlying question-level marks, and verify that the attainment claimed is consistent with the mark records.
This is not a post-accreditation luxury. It is the difference between a score above 600 and a score below it for many mid-tier engineering colleges.
The 60-Day Plan
For engineering departments beginning digital evaluation in August with an October peer visit, the following sequence is achievable:
Week 1-2 (August 9-22): Platform Selection and Setup
Choose a digital evaluation platform that supports CO-tagged question paper creation, question-level mark entry, and automatic CO-PO attainment computation. Verify that the platform can export reports in the format NBA's Self-Assessment Report requires. Complete the institutional procurement process. Most platforms can be deployed in 5-7 working days once procurement is complete.
Week 3-4 (August 23 - September 5): Faculty Training and Question Paper Preparation
Run structured training for all faculty whose courses will be evaluated. The focus must be on CO tagging during question paper preparation, not just the mechanics of on-screen marking. For the internal assessment cycle that begins in September, ensure every question paper has been CO-tagged before the assessment date.
Week 5-6 (September 6-19): Internal Assessment Pilot
Conduct the first internal assessment cycle (IA-1 or equivalent) on the digital platform. Process all scripts through the evaluation workflow. Generate the first CO-attainment report for the current semester. This produces live, current-semester data that can appear in the peer team evidence folder even if it is only one data point.
Week 7-8 (September 20 - October 3): Historical Data Reconstruction and SAR Finalization
For the two-to-three year data requirement, use whatever digital records exist from previous semesters. If end-semester results are held by the affiliating university in structured form, request question-level data where available. Many universities with digital evaluation already deployed can provide this. For courses where question-level data does not exist, document the manual attainment calculation with full transparency about source data limitations. Peer teams respond better to honest documentation of a data gap than to smooth tables with no underlying records.
Complete the CO-PO section of the SAR using both historical reconstructed data and the live current-semester attainment from the platform.
What This Means for Criteria 9
The NBA framework does not just require that you measure CO-PO attainment. It requires that you demonstrate continuous improvement based on what the measurements show.
Criteria 9 (150 points) evaluates whether a program has: identified courses with low CO attainment in Year N, implemented changes in Year N+1, and measured the impact in Year N+2. This is a three-year evidence loop.
Institutions beginning digital evaluation now will not have a complete three-year loop for October 2026. But they can demonstrate the beginning of the loop: here is our first structured CO attainment measurement, here is the course it revealed as underperforming, and here is the curriculum adjustment we are implementing in the current academic year.
That is a higher quality response to Criteria 9 than three years of manually reconstructed data with no supporting records.
The Institutions That Will Score Highest in October
Engineering colleges that have been running digital evaluation for 3+ years will enter the October 2026 NBA cycle with a structural advantage: three years of verifiable, question-level, CO-tagged mark records that the attainment calculations can be traced back to. Their Criteria 3 and Criteria 9 scores will reflect the integrity of that data.
Colleges beginning digital evaluation in August 2026 will not match that immediately. But they will be able to demonstrate forward momentum, a current-semester baseline, and the infrastructure for continuous improvement — which is ultimately what the NBA framework is designed to reward.
Colleges that do not begin digital evaluation in August 2026 face a straightforward risk: their Criteria 3 evidence will be the weakest in the room, in an accreditation framework where it is the highest-weighted criterion.
Related Reading
Ready to digitize your evaluation process?
See how MAPLES OSM can transform exam evaluation at your institution.