GATE's single 180-minute clock carries no mandated time split between its three parts - General Aptitude, Engineering Mathematics and your Core Subject can be attempted in any order, in any proportion, with only the overall three-hour limit enforced. That is confirmed directly on the current cycle's official pattern page: the stated "Total Time" is 180 minutes, with no section-wise breakdown at all. Unlike CAT, which locks you into each section for a fixed block before moving on, GATE hands the entire clock to you unmanaged. The strategic question that creates is not "how do I use the time" in general - it is how to allocate your own 180 minutes across three parts worth wildly different shares of the 100 marks: roughly 15/13/72 on most papers, or 15/0/85 on the twelve papers with no Engineering Mathematics section at all. A budget built from those mark-weights, worked out below, gives a starting allocation of roughly 27, 23 and 130 minutes - and the real skill is noticing, mock over mock, where your actual pace runs off that budget.
One clock, no checkpoints
GATE's official question paper pattern page for the current cycle - gate2027.iitm.ac.in/question_paper_pattern, hosted by IIT Madras as this year's organising institute - states the format plainly: one computer-based test, 65 questions, 100 marks, with a duration of 180 minutes and no section-wise time division mentioned anywhere in the pattern. A candidate can answer General Aptitude questions last, jump into Core Subject first, or interleave freely between all three parts, and nothing in the software enforces otherwise. This is a structurally different situation from CAT, where each section is locked to its own timer and a minute unused in one section cannot be spent in another. On GATE, every minute is fungible across the whole paper - which means the only thing standing between you and a badly-spent three hours is a budget you set for yourself.
What the 100 marks are actually worth, section by section
General Aptitude is common to every one of the 30 GATE papers: 10 questions for 15 marks. From there the paper splits in one of two ways. On most papers, Engineering Mathematics carries roughly 13 marks and the Core Subject carries 72. On twelve specific papers - AR, CY, DA, EY, GE, GG, MA, PH, ST, XH, XL and RA - there is no Engineering Mathematics section at all, and the Core Subject absorbs those marks instead, worth 85. Which structure applies to you depends entirely on your paper code, and it is worth checking before building a budget around the wrong split.
Turning marks into minutes
The simplest defensible starting point is to treat every mark as worth the same slice of the clock: 180 minutes across 100 marks is 1.8 minutes per mark, applied to whichever split matches your paper.
| Section | Marks (most papers) | Budgeted minutes | Marks (12 no-Engg-Maths papers) | Budgeted minutes |
|---|---|---|---|---|
| General Aptitude | 15 | 27.0 | 15 | 27.0 |
| Engineering Mathematics | 13 | 23.4 | - | - |
| Core Subject | 72 | 129.6 | 85 | 153.0 |
| Total | 100 | 180 | 100 | 180 |
Read this as a starting anchor, not a rule to follow to the minute. It says nothing about how many questions sit in each section, only how many marks - and a section's questions are not uniformly quick or slow relative to their weight. A multi-step Core Subject numerical-answer question can eat far more than 1.8 minutes per mark it carries, while a quick General Aptitude verbal-reasoning MCQ can be answered in a fraction of its budgeted time. The number that matters is not "did I spend exactly 27 minutes on General Aptitude" - it is "did I let one part of the paper consume time that the mark-weighted budget says belongs somewhere else."
Where the budget actually gets broken
The common failure mode is not spending too little time on General Aptitude - it is the opposite problem hiding inside the Core Subject block. A candidate who gets stuck on one or two difficult, multi-step Core numerical-answer questions worth 2 marks each can burn fifteen or twenty minutes chasing a single answer, then arrives at the easier, faster General Aptitude questions with barely any clock left. Since nothing forces you out of a section, there is no external signal telling you the trade has gone bad - you find out only when the three hours run out. The budget above exists specifically to give you an internal signal instead: if you are 90 minutes in and still working through Core Subject questions with General Aptitude and Engineering Mathematics untouched, you are behind the anchor regardless of how confident you feel about the questions in front of you.
Tracking the actual split against the budget
GATE's exam-agnostic structure in a subject-based tracker maps directly onto this: General Aptitude, Engineering Mathematics (where your paper carries it) and your Core Subject can each be logged as their own subject, each carrying its own score, attempted and correct counts on every full mock. That gives you two numbers to compare after every mock - the budget in the table above, and your actual time spent per section, whichever you measured it with (a stopwatch split, or a timer left running per section during a self-administered mock). The gap between the two, tracked mock over mock, is the actual signal to act on: if Core Subject keeps eating 150 of your 180 minutes on every single mock, the fix is not "try to be faster" in the abstract, it is deciding in advance which Core questions you will abandon and return to only if time remains, so General Aptitude's comparatively cheap 15 marks are never the ones left unclaimed.
Where this is weak, and where it does not apply
- Marks-per-minute is a baseline, not a validated pacing law. No study cited here tests "allocate time proportional to marks" as an optimal GATE strategy - it is arithmetic applied to GATE's own published mark-weights, offered as a sensible starting anchor rather than a proven optimum.
- The 15/13/72 split does not apply to all 30 papers. Twelve papers carry no Engineering Mathematics section and a heavier 85-mark Core instead - check your specific paper code before using either column of the table.
- Question count per section, not just marks, is not officially broken down beyond General Aptitude's 10 questions. The 55 remaining questions split between Engineering Mathematics and Core Subject in an unstated ratio, so this budget works at the mark level, not the question-count level - do not assume each section's questions take an equal amount of time simply because they carry similar total marks.
- Individual pace varies far more than the budget accounts for. A candidate who finds Core Subject genuinely faster than General Aptitude's verbal-reasoning style questions should weight their personal budget differently from the anchor above - use your own first two or three mocks to find your real per-section pace, then adjust the anchor toward it rather than forcing the arithmetic.
- This is a time-allocation framework, not a question-order strategy. Which specific question to attempt first, skip or return to is a related but separate decision this post does not cover.
Sources
- GATE 2027 official question paper pattern, IIT Madras (organising institute for the current cycle): gate2027.iitm.ac.in/question_paper_pattern - total duration, question/mark counts, and the absence of any sectional time division are all stated there directly.
- All budgeted-minute figures in the tables above are original arithmetic (180 minutes ÷ 100 marks = 1.8 minutes per mark, applied per section) worked from the official mark-weights, not quoted from any source.
Logging General Aptitude, Engineering Mathematics and your Core Subject as separate subjects is what turns this budget from a one-time calculation into something you can check against real mocks. Karma Yogi's GATE tracking keeps each section's score and time on its own, mock after mock.
End of essay
- Anish Guruvelli