This term you do one real piece of work instead of fifteen small ones.
Until now, every course you took set its own assignments. Six courses meant many small pieces, none of them worth keeping, all of them due in the same fortnight. From this term, you and up to four others take one real problem in Karachi and produce one substantial piece of work about it. Every ordinary course you take marks that same piece of work — each from its own angle.
The three words you need
Honestly, what changes for you
| Before | From this term |
|---|---|
| Three assignments per course | The project is the main coursework. Your teacher's own quizzes and assignments (at least 3 quizzes and 2 assignments) continue alongside it, for 10 marks. |
| Assignments nobody reads twice | One piece of work that goes to a government body, a client or an organisation that asked for it. |
| Working alone | A team of up to five. You are marked as a team on the work, and on your own on whether you can explain your part. |
| Nobody sees your work | You show it at the Karachi Review on Monday 21 December. A panel that includes someone from outside the university scores it at your table. |
Every course is out of 100. Here is where the marks come from.
Most of your courses meet every week and mark your team's Folio. So the same Folio earns you a mark in each of them. If you take six, that one piece of work is marked six ways — the finance course looks at your numbers, the writing course at your argument, the law course at your contracts. If only one or two of your team take a course, that course marks your own named sections of the Folio.
In some practical courses — design, media, computing — the final may be a practical project, a production or a portfolio instead of a written paper. Your teacher will tell you.
What if one of my courses is not marking my team's project?
At most eight courses mark one team's Folio. If you take an ordinary course outside those eight, that course sets you a lens note — a piece you write on your own, about the same project, from that course's angle. It carries the Folio's 15, on the same rubric; your viva 5 stays.
You never write more than two lens notes. If a third course falls outside the eight, you do not write a third piece. That course sets no written piece and marks your viva out of 20. The same goes for a fourth, and so on.
What happens, and when
the dates that matter| Session | What happens | What you do |
|---|---|---|
| Session 2 21–27 Sep | Your team is confirmed | The teams are final, cut once from the Registrar's files of 20 September. You are told your team, your block, and which courses mark your Folio. Late registrations and drops are handled by hand; any other change needs a written reason from your convener. |
| Session 4 or 5 | A guest comes in | Someone who does this for a living talks to your school. Compulsory. You write one page about it for your own file — it is not marked. |
| Session 5 12–18 Oct | You see the project menu, and the full projects | In class you get your personal brief, with your claim code and your block's project menu inside — title, one-line problem, who it is for. Your team notes the three it likes. Your block brief and the Ideas Book, every project in full, are in the portal. |
| Session 6 19–25 Oct | You choose your project | Your team makes its final choice with your convener, names itself, and seals its prediction with them: what you expect to find, opened at your first viva, no marks. Then, in class, the ethics screening sheet, due Saturday 24 October. No data is collected until your ethics screen is cleared. |
| Mid-term 26 Oct–1 Nov | Mid-term examinations | After Session 6. Set and marked by your own teacher. |
| Session 7 2–8 Nov | Your plan is due, and the build starts | One page to your convener by Saturday 7 November, with your team charter: what you are doing, who is doing what, and what you need. You get the rubric, the exact sheet your teachers mark you against. |
| Sessions 8–11 | You do the work | Fieldwork, building, writing. One industrial visit with your school somewhere in here. Your draft is read in class at Session 10. Iqbal Day, Mon 9 Nov, is a holiday; Monday classes are made up on Tue 10 Nov. |
| Session 11 30 Nov–6 Dec | It goes live | Whatever you made has to exist by now — the product, the campaign, the report, the offer. |
| Session 12 7–13 Dec | The Folio goes in | The last class. Upload the Folio with your AI declaration in the submission window, Sat 12 – Wed 16 December. The whole window is on time; nothing is accepted after Wednesday 16 December. |
| Presentations & Viva 14–19 Dec | Your viva | No new teaching. Three minutes with each teacher, in class, about your own part. In a big class the vivas may start in Session 12. Your teacher will tell you. |
| Mon 21 Dec | The Karachi Review | Your team shows its work all day across the campus; a teacher and an alumnus score you at your table. The day opens with students handing their studies to public bodies. Compulsory. |
How big is the Folio, really?
3,000 words for each person in your team, plus or minus ten per cent — so 15,000 for a team of five, 12,000 for four, 9,000 for three. Plus the artefacts: the data, the drawings, the code, the product, whatever your project produces. The Folio also carries a two-page brief written for the body your project reports to, which your team delivers, and a handover page — your data, your methods, and what next year's team should do. That is about the writing you used to do across all your assignments, in one piece worth keeping.
Your week
- New this term? If this is your first semester, none of your classes is after 6 pm. You may have weekend daytime classes.
- Registered late? If you registered after 20 September, you are placed in a team by hand, by 3 October.
Your team does not invent a question. It takes a patch of one.
There are about 172 questions in the Ideas Book and about 198 teams in the university. At most two teams take the same question, and only on different sites or areas. No two teams share a patch.
What a patch looks like
| The shared question | Two patches, two teams |
|---|---|
| Why do water tankers cost what they cost? | Gulshan Block 13 · Korangi Sector 33 |
| What happens to a small retailer under the new sales-tax regime? | Bolton Market cloth · Tariq Road garments |
| Who actually uses the BRT, and for what? | Red Line, Numaish–Gurumandir · the last mile at each end |
First-year teams, and venture teams
If nothing in the book fits
You may bring your own question, on two conditions: a named organisation wants the answer, and your convener signs it off at Session 6, not later.
Getting into the portal
- Your one-time code is on page 1 of your personal brief. You get the brief in class in the week of 12 October (Session 5). The code is yours; it works once.
- Go to the portal and enter your roll number and the code. Then set your own password. That is the whole sign-up.
- Lost the code? Your convener can have it reissued. Nobody can use it after you have claimed it.
- What lives there: your team, your block, the courses marking your Folio, your project and patch, every hand-in and its deadline, the Vice Chancellor's booking diary, the private route to report a teammate, and your marks.
Before you go out and talk to anyone
Most projects need you to leave the campus. Ten questions decide whether your fieldwork needs permission — you answer them in class at Session 6, straight after your team chooses its project. You collect no data until the screen is cleared.
| Which route | What it means |
|---|---|
| Convener sign-off | Most teams. Public places, adults, nothing private recorded, nobody named. Your convener signs the plan and you go. |
| Panel review | You will ask people about anything private, record anything that identifies a person, or enter a workplace where someone could be hurt. A panel of three sits every week from 6 October and decides within a week. |
| Not this term | Anyone under eighteen without their guardian, patients, prisoners, anyone who would be at risk if identified. Change the patch instead. |
The rules for being out there
- Not before the go-ahead. No team leaves the campus until the duty phone and the sign-out sheet are in place — the fieldwork gate opens on Saturday 10 October — and your team's ethics screen is cleared. Your convener tells you when.
- Never alone. Two students minimum, always. No fieldwork after sunset without written permission.
- Somebody knows where you are. Your plan says where and when. If it changes, the portal says so before you go.
- Carry the letter and your field card. Your team letter, and the field card cut from the last page of your personal brief, with the duty number on it.
- No money changes hands. Not to a respondent, not for access. If someone asks, leave and report it.
- Leave when you feel you should. No mark is worth an argument on a street. Walking away is never held against you.
- Report it the same day. Anything that went wrong — a refusal, a row, an injury, anything — goes to your convener that day, not into the Folio in December.
Your team
- You did not choose them, and that is deliberate. Teams are cut from students who share most of a timetable, so that the same courses can mark the same work. You will work with people you did not pick — which is what happens after you graduate.
- Write the charter by Session 7 (due Saturday 7 November). Who does what, by when, and what happens if someone does not. It is one page, and it is the thing you point at later.
- Your teacher can move you up or down two marks from the team mark, on the evidence of your viva and the charter. Carrying the team is noticed. So is not doing your part.
- If someone is not doing their share, report it early. There is a private route in the portal. Use it in October, not in December — in December nobody can fix it.
Using AI — read this properly
You are expected to use it. Claude, ChatGPT, Gemini — use them to research, to draft, to check your work, to argue with. The work you produce should be better because these tools exist.
Three rules, and they are not negotiable:
- Declare it. Every hand-in carries an AI declaration: which tools, what for, how you checked, and what is your own. This is the HEC requirement, not a Greenwich invention.
- Check it. Anything a tool gives you is checked before it goes in. Invented references and invented data are misconduct — and they are easy to spot.
- Be able to explain it. At the viva you will be asked about your own work. Anything you cannot explain is not credited to you. A tool cannot sit the viva for you.
Fifteen minutes with your convener
Sessions 4 to 12Dr Naveed Ahmed Mughal, the Vice Chancellor, is on campus 12:00 to 20:00, seven days a week, from Session 4 until the Folio is due, to work with you on this.
| How it works | What you need to know |
|---|---|
| Book in the portal | At least one day ahead. Fifteen minutes. |
| As a team or on your own | Both are fine. Bring the problem you are actually stuck on. |
| Every team gets two | One after you choose your project, one during the build. They appear in your team's diary; you do not book them. |
| Other slots are first come | There are enough for most students, not for everyone twice. Book when you need it, not to hold a place. |
| Say what is stuck | One sentence when you book. Then the fifteen minutes start with your problem. |
