How to Write the CBSE Practical File Without Losing Marks
The practical file sits inside the 30-mark practical component in both Computer Science (083) and Informatics Practices (065). CBSE expects a minimum of 15 Python programs and 5 sets of SQL queries for CS, and 15 Pandas programs, 4 Matplotlib programs and 15 SQL queries for IP. The file is marked on completeness and evidence of real output, not on presentation.
What CBSE actually asks for
- Computer Science (083): minimum 15 Python programs and 5 sets of SQL queries.
- Informatics Practices (065): minimum 15 Pandas programs, 4 Matplotlib programs and 15 SQL queries.
These are minimums. Meeting them exactly is fine; falling short is not, and it is checked.
What each entry should contain
- The problem statement, in one line
- The code, readable and indented properly
- The actual output, as a screenshot from your own run, not typed out
- A one-line note on what the program demonstrates
The screenshot matters more than students expect. It is the evidence that the program ran, and a file of code without output reads as untested.
The mistakes that cost marks
- Writing the file in the last fortnight. Examiners can tell, and the viva confirms it.
- Copied code you cannot explain. The file and the viva are marked together.
- Missing outputs. The most common single deduction.
- Fewer entries than the minimum. Easy marks lost for nothing.
- Programs that only work on perfect input. Add basic validation; it takes minutes.
A file that also revises for you
Built through the year, the practical file is a complete revision resource: every syntax pattern you need, with working examples and your own outputs. Built in a fortnight, it is a chore that teaches nothing and shows it.
Order that works
Group entries by topic rather than by date: basic programs, then functions, then file handling, then data structures, then SQL. It reads as a designed file, and it makes the viva easier because you can find anything quickly.