Mon to Fri 11:00 AM to 5:00 AM · Sat and Sun 1:00 PM to 11:00 PM

Students

Where to work on your final year project (FYP) in Lahore

Aroma Khan Published 7 min read

Key takeaways

  • An FYP usually runs across your last two semesters. In HEC’s 2023 computing curriculum, FYP-I is 2 credit hours in semester 7 and FYP-II is 4 credit hours in semester 8.
  • Supervisor meetings are often formally logged. NUML’s software engineering SOP asks for biweekly meetings and a signed meeting log, and deducts marks if you cannot show it.
  • Put your code in Git from the first week and keep three copies of important files: one primary, two backups, one of them off your laptop.
  • Pick places by task: campus labs for hardware and supervisor access, home or a quiet room for focused build work, and short in-person sessions for team decisions.
  • Uplyft’s student pass is PKR 750 a day, valid Monday to Thursday, 1:00 PM to 8:00 PM, up to 5 hours a day, with internet up to 100 Mbps and 8 hours of electricity backup.

Most FYP teams in Lahore work best by matching the place to the task: campus labs for hardware, testing and supervisor access, a quiet room with reliable internet and backup power for focused build and writing work, and short in-person sessions for team decisions. Whichever places you use, plan your milestones early, keep everything in Git with backups, and make sure a power cut cannot stop a demo.

What an FYP year actually involves

A final year project is the biggest piece of work in most BS degrees, and it runs for months, not weeks. In the HEC’s revised 2023 curriculum for computing degrees, the BS Computer Science scheme splits it into FYP-I (2 credit hours) in semester 7 and FYP-II (4 credit hours) in semester 8. Engineering and other programs have their own versions, often called FYDP.

Each department publishes its own rules, and the details differ. Two Pakistani examples show the shape:

Stage NUML BS Software Engineering SOP (2023) PUCIT software engineering FYDP (2025-26)
Group size Two to three students Up to four students
Proposal Submitted in week 10 and presented in week 11 of the 6th semester Proposal, then evaluation by a faculty committee
Middle checkpoint 40% of the project implemented, plus four report chapters, in the 7th semester D1 (design) and D2 (build and progress)
Final Full implementation evaluated, plagiarism check and bound report in the 8th semester D3 (final implementation) and D4 (deployment and documents), then a showcase

Sources: NUML SOP for FYP (BSSE) and PUCIT FYDP 2025-2026. Your own department’s SOP is the one that counts, so download it in the first week and put every date in a shared calendar.

Plan the project before you plan the place

Where you work matters less than whether the team knows what it is doing each week. Three habits make the biggest difference.

Work backwards from the milestones

Take each official deadline and break it into two-week chunks. If the mid evaluation needs 40% of the features working, list those features and give each one an owner and a date. Leave a buffer of at least a week before every deadline for testing, printing and the supervisor’s signature.

Treat supervisor meetings as a deliverable

Some departments log every meeting. The NUML SOP asks students to meet their supervisor every two weeks, keep a meeting log for each meeting, and hold at least two meetings before the proposal. Students who cannot show the log are not allowed to present, and 50% of the marks for that evaluation are deducted. Even if your department is more relaxed, keep a one-page record: date, who attended, what was agreed and what is due next time.

Give everyone a clear role

Small teams fall apart when two people do the same task and nobody does the report. A simple split:

Role Owns
Project lead The plan, deadlines and supervisor contact
Lead developer or builder Architecture, code reviews, the main branch
Tester and integrator Test cases, bug list, the demo setup
Documentation lead The report, diagrams, references and the plagiarism check

In a team of two or three, people hold more than one role. Rotate the documentation work so one person is not writing every chapter in the last fortnight.

Version control and backups

Losing a laptop a week before the final evaluation is a common FYP disaster, and a preventable one.

  • Use Git from day one. PUCIT’s FYDP rules require a properly structured Git repository with a main branch and feature branches, with the supervisor added as an administrator or collaborator. The repository structure, commit history and README count towards the D2 marks. Even if your department does not ask for this, it is good practice.
  • Commit small and often. One feature or fix per commit, with a message that says what changed.
  • Keep the report under version control too, or at least in a shared drive with version history.
  • Follow the 3-2-1 rule. The US-CERT guide to data backup options recommends keeping three copies of any important file (one primary and two backups), on two different types of media, with one copy stored offsite. For an FYP that can mean your laptop, a cloud repository and an external drive kept at a teammate’s home.
  • Test that you can restore. Once a month, clone the repository onto a different computer and check it builds. PUCIT’s final deliverable is tested on a fresh environment, so this practice pays off on the day.

Where FYP teams can work in Lahore

Place Good for Watch out for
Campus labs Hardware, licensed software, supervisor access Lab timings, shared machines, busy weeks before deadlines
University library Reading, writing chapters, quiet solo work Silence rules, limited group space, closing times
Home Long build sessions, no travel cost Load-shedding, shared Wi-Fi, family noise
Cafés Short planning meetings Noise, ordering to keep your table, weak sockets
Coworking space Focused build and writing days with stable power and internet Daily cost, booking ahead, quiet-room rules

Campus labs and libraries

Your department’s lab is usually the best place for anything involving hardware, special equipment or licensed software, and it puts you near your supervisor. University libraries are good for solo reading and writing, but group talk is often limited to particular rooms, so check your library’s rules before planning a team session there. Our guide on where to study in Lahore when home is too noisy covers public and university libraries in more detail.

Home

Home is free and flexible, but it is where load-shedding hits hardest. On 29 August 2026, The Express Tribune reported Lahore residents complaining that power was going off for an hour after every hour. If your team builds at home, agree who has the most reliable power and internet and keep the team’s shared work there.

Cafés

Cafés work for a one-hour planning meeting. They are hard going for a five-hour coding session: tables are small, sockets are scarce and you are expected to keep ordering.

Coworking with a student pass

A coworking space gives you a desk, steady internet and backup power for a fixed daily fee. It suits heads-down days: building features, writing chapters, preparing slides. Larger groups, such as several FYP teams from one class or a society, can book together. At Uplyft: Groups of 6 or more can book day passes or student passes for the same day. Message us at least 2 days ahead and we will confirm availability. A team smaller than six simply books a student pass for each member.

Internet and power: what an FYP really needs

  • Upload speed matters if you push large files, deploy to the cloud or demo over video. Our guide to how much internet speed you need explains upload, download and latency.
  • Mobile data is not a safe backup. In July 2026, ProPakistani reported that telecom operators can generally keep services running through outages of three to four hours, but longer outages disrupt them.
  • Keep the demo independent of the grid. Charge laptops fully before an evaluation, carry chargers, and keep a recorded video of the demo in case the live version fails.
  • Know your power backup. If you are relying on a UPS at home, find out how long it lasts with your laptop and router on it. Our article on load-shedding and picking a workspace that stays online explains how UPS, generator and solar backup compare.

A weekly rhythm that works

Many teams settle into a simple pattern:

  1. One planning session a week, in person or on a call, to agree the week’s tasks.
  2. Two or three focused build days, in whichever place has the best power and internet.
  3. One supervisor meeting every two weeks (or as your department requires), with the log filled in.
  4. A Friday check: push everything to the repository, update the task list and back up the report.

If you also have exams in the same semester, our guide to building a study routine for university exams helps you fit both in.

Where Uplyft fits

Uplyft is a coworking space at 123-E1, Unit 13, Hali Road, Gulberg 3, Lahore. University students with valid student proof pay PKR 750 a day, plus 16% GST, valid Monday to Thursday, 1:00 PM to 8:00 PM, up to 5 hours a day, with internet up to 100 Mbps, 8 hours of electricity backup, parking and a shared kitchen. The shared room is kept quiet and Uplyft has no meeting rooms, so it works best for build and writing days, with long team discussions kept for campus or a call. If you need a Friday or a longer day, a regular day pass is PKR 1,250, valid Monday to Friday, within office hours (11:00 AM to 5:00 AM), for up to 8 to 10 hours, day or night shift.

See the student study space page to book, or share our page for universities and societies with your department or FYP coordinator.

Frequently asked questions

How long is a final year project in Pakistan?

For most BS programs it runs across the last two semesters. In HEC’s revised 2023 computing curriculum, FYP-I is 2 credit hours in semester 7 and FYP-II is 4 credit hours in semester 8. Your department’s own SOP sets the exact deadlines.

How many students are in an FYP group?

It depends on the department. NUML’s BS Software Engineering SOP sets groups of two to three students, while PUCIT’s software engineering FYDP page for 2025-26 allows up to four. Check your own department’s rules.

How often should we meet our FYP supervisor?

Follow your department’s rule. NUML’s software engineering SOP asks students to meet their supervisor every two weeks and keep a meeting log for each meeting. Even if your department is less formal, a short written record of each meeting protects your marks.

Can our FYP team work together at Uplyft?

Yes, within the student pass rules: PKR 750 a day per student, valid Monday to Thursday, 1:00 PM to 8:00 PM, up to 5 hours a day, with valid student proof. Groups of 6 or more can book day passes or student passes for the same day. Message us at least 2 days ahead and we will confirm availability. The shared room is kept quiet and Uplyft has no meeting rooms, so it suits build and writing work more than long discussions.

Sources

  1. Curriculum of Undergraduate Degree Programs, Computing Disciplines (Revised 2023), Higher Education Commission and NCEAC (accessed November 2026)
  2. Standard Operating Procedures for Final Year Project (BSSE), National University of Modern Languages, Department of Software Engineering (accessed November 2026)
  3. FYDP 2025-2026, Department of Software Engineering, University of the Punjab, PUCIT (accessed November 2026)
  4. Data Backup Options, US-CERT (CISA) (accessed November 2026)
  5. Load-shedding plagues Punjab as shortfall rises, The Express Tribune (accessed November 2026)
  6. Govt Moves to End Load Shedding for Telecom Towers, ProPakistani (accessed November 2026)

Last updated 19 November 2026. Uplyft prices and facts on this page come from our current price list (November 2026).

Aroma KhanContent Writer, Uplyft

Visit us

Come see the space.

See the rooms, check the connection and meet the team before you decide. We will help you pick the right setup for your people.

Book a visit

Your details are emailed to the Uplyft team, who will call or message you to confirm a time. Prefer WhatsApp? Use the button below.

Find us

Uplyft
123-E1, Unit 13, Hali Road,
Gulberg 3, Lahore
Open in Maps Directions