← Back to MMC Overview
NUST MMC · CONTEST REGULATIONSVERSION 1.0-final (FINAL)

Competition Rules

Every team member, coach, and advisor is bound by the clauses set forth below. Violations, including plagiarism or unapproved external collaboration, result in immediate disqualification.

At A Glance Summary

TEAM SIZE:1 to 5 students (same level)
WORKING WINDOW:64 Hours (6 Nov 5pm – 9 Nov 9am PKT)
DELIVERABLES:1 PDF (Max 20 pages) + 1 .ipynb Notebook (if code used)
VIDEO WALKTHROUGH:Max 5 mins (Google Drive link in PDF)
SECTION R1

Eligibility and divisions

§ R1.1

The competition has two divisions: High School and University. Each division has one problem.

§ R1.2

The High School Division is for students enrolled in secondary school. The University Division is for students enrolled in an undergraduate or graduate programme.

§ R1.3

Students enrolled in college (intermediate, A-Levels, or pre-university) programmes compete in the High School Division.

§ R1.4

Every member must be an actively enrolled student on the date of registration.

§ R1.5

A team competes in one division only. All members of a team must be at the same level; teams mixing levels are not accepted.

§ R1.6

A person may be a member of one team only. The registration system enforces this by email address.

SECTION R2

Teams and advisors

§ R2.1

A team has one to 5 members.

§ R2.2

Team members cannot be changed after registration.

§ R2.3

Each team may have one advisor. An advisor may help with logistics and teach general methods before the problem is released, and must not help with the problem after it is released.

§ R2.4

Teams must not collaborate with other teams.

SECTION R3

Registration, fees and payment

§ R3.1

Registration fees follow a tiered formula (base fee plus an increase per member). For Pakistan university teams: PKR 1,200 base + PKR 450 per member. For Pakistan high school teams: PKR 2,200 base + PKR 700 per member. For international teams (both divisions): USD 20 base + USD 6 per member.

§ R3.2

A team is classified as national if every member's institution is in Pakistan; otherwise it is classified as international.

§ R3.3

Payment is made by transfer to the account shown on the registration page. The team uploads proof of payment during registration. Organisers verify each payment manually.

§ R3.4

A registration is complete only when its payment is approved. Approved teams receive a team ID and a team key.

§ R3.5

All registration fees are non-refundable. Strictly no refunds will be issued under any circumstances.

§ R3.6

Registration closes on to be announced.

SECTION R4

Schedule and time limit

§ R4.1

The problem for each division is released on Friday, 6 November 2026 at 5:00 pm PKT (UTC+5).

§ R4.2

Submissions close on Monday, 9 November 2026 at 9:00 am PKT (UTC+5). The working window is 64 hours.

§ R4.3

Submissions received after the deadline are disqualified.

§ R4.4

Single final submission: Once submitted, no edits, revisions, or resubmissions are permitted under any circumstances. Submissions are permanent, immutable, and final. Teams must verify each checklist requirement and confirm finality before uploading.

§ R4.5

The submission time is the time at which the competition server finishes receiving the submission, measured by the server clock. Teams should submit well before the deadline.

SECTION R5

Deliverables

§ R5.1

Each team submits one Solution Report PDF and, if any code was used to develop the model, one Jupyter Notebook (.ipynb) file containing only Python code. No external GitHub repository links are collected or evaluated.

§ R5.2

The PDF is organised in this order. Main solution: (1) Summary Sheet, one page, restating the problem, describing the approach, giving key results, and stating the team's choices and data sources; (2) Table of Contents, one page; (3) Solution Report; (4) a one-page memo or letter to the decision makers named in the problem. Back matter: References, Appendices (including data tables and extra figures), and the Report on Use of AI.

§ R5.3

The four main-solution items together must not exceed 20 pages; the Solution Report therefore has at most 17 pages. References, Appendices, and the Report on Use of AI do not count toward the limit. Pages beyond the limit will not be read.

§ R5.4

If computational code was implemented, it must be written in Python and submitted on the portal as a Jupyter Notebook (.ipynb) file alongside the solution PDF. All code must be cleanly reproducible and well-commented.

§ R5.5

Where the problem requires a team to choose a setting, the Summary Sheet states the choice and its sources.

SECTION R6

Formatting

§ R6.1

The PDF is typed, in English, in at least 12 pt font, on A4 paper with margins of at least 1.5 cm.

§ R6.2

Images and other materials whose use is restricted by copyright must not be included. Every idea, dataset and figure not created by the team must be cited.

SECTION R7

Anonymity

§ R7.1

The team ID is the only identifier allowed on every page of the PDF and inside the Jupyter Notebook. Personal names, schools, and institutions must not appear anywhere.

§ R7.2

The Google Drive video link is exempt from R7.1 even if the hosting Google account or URL visibly contains a personal name.

SECTION R8

Video

§ R8.1

The video explains the team's model and lasts at most 5 minutes. It is a Google Drive link, with viewing access enabled, placed on the Summary Sheet in the PDF and shared with nustmathsnexus@gmail.com with Viewer access.

§ R8.2

A team that submits no video loses 10% of its total score.

§ R8.3

The video file on Google Drive must not be modified after the deadline. Judges may verify its modified timestamp.

SECTION R9

Resources, data and assumptions

§ R9.1

Teams may use any published literature, open data, and open-source libraries. However, Python is the ONLY permitted programming language for computational modelling and data analysis.

§ R9.2

Teams must state and justify every assumption. Data that was invented rather than sourced must be clearly marked.

§ R9.3

One consistent citation style (for example APA or IEEE) is used throughout, and every reference must be accurate.

SECTION R10

Originality

§ R10.1

Plagiarism, or copying a solution from any source, results in disqualification.

§ R10.2

Quotations must be marked and cited.

SECTION R11

Use of AI

§ R11.1

Teams may use language models and other AI tools. Every use must be disclosed in the report, stating which model was used and for what purpose, with inline citations and entries in the references.

§ R11.2

Teams append a Report on Use of AI after the references and appendices.

§ R11.3

Teams must verify the accuracy, validity and appropriateness of all AI-generated content and citations, and correct errors.

§ R11.4

Teams must check original sources to make sure no one else's work is copied.

SECTION R12

Judging and prizes

§ R12.1

Judging criteria: Submissions are evaluated on: (1) Mathematical modelling quality, rigor, and realistic parameter discipline; (2) Sensitivity analysis, robustness, and trade-off exploration; (3) Clarity, organisation, and conciseness of the Summary Sheet, Solution Report, and Decision-maker Memo/Letter; (4) Quality of the 5-minute explanatory video walkthrough; (5) Academic integrity, source citations, and comprehensive disclosure in the Report on Use of AI; and (6) Reproducibility and clarity of Python code in the submitted .ipynb notebook.

§ R12.2

The base prize pool is PKR 20,000 for the High School Division and PKR 20,000 for the University Division (PKR 40,000 total). Cash prizes are awarded to 1st place in each division. All members of every registered team receive an official Certificate of Participation. Winning teams receive a Certificate of Merit / Winner Certificate. Prize pools grow dynamically as verified registrations exceed PKR 60,000 in total revenue.

§ R12.3

Decisions of the organisers and judges are final.

§ R12.4

Winner announcements & feedback: Winners will be announced on the website and notified via email. The organizers will also provide general feedback and commentary on the problem after the competition concludes so teams can review key insights and common pitfalls.

SECTION R13

Contact

§ R13.1

Questions go to nustmathsnexus@gmail.com. Answers that clarify a rule are published here with a version bump.