Skip to main content
All posts

CO–PO attainment without the spreadsheet marathon

By Kwilo ·

A CO–PO articulation matrix, course attainment levels and programme attainment bars in Kwilo's Compliance workspace.

Ask any NBA coordinator what the week before a visit looks like. It's a laptop full of spreadsheets: course outcomes copied from last year, a CO–PO matrix nobody remembers filling in, marks retyped from three exam sheets, and a formula that breaks when someone inserts a column.

Most of that work isn't judgement. It's transcription. So that's the part we handed to agents.

Who actually needs this

If you run engineering programmes, you already know: NBA's self-assessment report asks for course outcomes, the CO–PO matrix, and attainment for every course and every graduating batch. Autonomous colleges and universities need it for their accreditation too. Degree colleges have it easier: NAAC asks mainly that outcomes are published and measured, without the full matrix.

Either way, the evidence starts in the same place: the course, the syllabus and the marks.

What the agents do

Eight steps from course outcomes to readiness, showing what Kwilo's agents draft and who approves each step

Kwilo's Compliance workspace walks a course from its syllabus to a programme result. At almost every step an agent does the first draft:

  • Course outcomes are drafted from the syllabus. Each one quotes the line it came from.

  • Question mapping: paste the question paper and the agent pulls out the questions, their marks and the outcomes they assess.

  • Attainment is calculated from the marks under the method your department approved. Nobody touches a formula.

  • Improvement actions are suggested for every outcome below target, with an owner and a date.

  • CO–PO links are proposed with a strength and a one-line reason.

  • Course files and reports get a narrative drafted from the frozen result, so the numbers are never retyped.

And when someone asks "which outcomes fell short this semester?", Ask Kwilo answers from the course's own evidence, with citations.

Faculty stay in charge

Suggested course outcomes, each with a Bloom level and a quote from the syllabus, waiting for faculty review

Nothing an agent produces is saved on its own. Faculty tick what they keep, rewrite what they don't, and approve. The citation sits next to every suggestion, so checking takes seconds, not a re-read of the syllabus.

Faculty work only on the subjects they teach. The programme coordinator owns the matrix, the cohort and the programme result. The principal sees how ready each programme is.

A matrix you can defend

Suggested CO–PO mappings with a strength from 1 to 3 and a reason for each link

The hardest question in an NBA visit is often the simplest: why does this course contribute to PO3? A strength copied from last year's sheet has no answer. In Kwilo every link carries its reason, and the coordinator signs off the matrix knowing what each number means.

Results that don't drift

When a course result is issued, it's frozen. Edit a mark next month and last semester's attainment doesn't quietly change. The programme result works the same way: one per graduating batch, so you can show the trend across years. If the surveys for a batch haven't come in, the indirect part shows as missing rather than as an estimate.

Switched on where it matters

Every institution has different compliance needs, so each kind of compliance is a separate feature in Kwilo. OBE is the first. Engineering colleges and universities get it by default, and degree colleges can have it switched on when they want the full matrix.

If your department is still running OBE out of spreadsheets, see how the Compliance workspace works or read about the CO–PO attainment tracker.

Try Kwilo

Study plans, practice, and an AI tutor that knows your syllabus.