Google Forms has no built-in time limit. There is no duration field in the editor, and turning the form into a quiz does not add one. Two routes get you close. The first is a Google Workspace Marketplace add-on that injects a countdown into the form and force-submits at zero. The second needs no add-on: you open the form at the start of your window and close responses at the end. Both are attachments to a product that was never a test, and each gives way in its own place.
This page is the how-to for both, then the honest comparison. For the wider list of what Forms can and cannot do as an exam platform, read Google Forms for online exams. For the scoring half, negative marking in Google Forms covers the workarounds there.
Route One: A Marketplace Add-On That Counts Down
The add-ons listed in the Google Workspace Marketplace under timer or quiz timing work to roughly one shape. You install one against the Google account that owns the form, authorise the permissions it asks for, set a duration, and it attaches a countdown that appears when a respondent opens the form. At zero it submits whatever has been filled in, or stops the respondent submitting at all. A listing may bundle scheduling as well - the form opens and closes at fixed times - which is route two with the switch flipped for you.
Installing is the easy part. The authorisation screen is the part to read slowly, because that is where you decide how much of your Drive a stranger gets.
- Read what the consent screen asks for. A countdown needs very little; an add-on wanting to see and edit all your Drive files is asking far more than the job.
- Find out where your responses travel. A timer that knows who has already submitted has to read your response sheet to know it, which means your students' answers pass through someone else's system.
- Check whether the plan you are on caps responses, and what happens to the attempt that crosses the cap. A cap reached mid-test is an outage during an exam.
- Confirm whether the timer is per respondent or one fixed window shared by everyone. Those are different products, and a listing may not say which one you are installing.
- Test a reload yourself in an incognito window before a batch sits anything.
What the Add-On Route Actually Costs
Two costs, and neither is the installation fee. The first is that a third party now sits between you and your students' responses, holding a live authorisation against your Google account for as long as it is installed. For a school or coaching institute that is a data question somebody will eventually ask you to answer in writing. Where a free tier exists, any response cap on it belongs to the add-on vendor rather than to Forms - so the number that matters for your batch is on their pricing page, not Google's.
The second cost decides whether the timer means anything. The countdown is script running in the respondent's browser, and the deadline is held by the page - so a reload can reset it, a second tab can carry a second clock, and anything that stops that script from running leaves an ordinary untimed form behind. That is not a flaw in any one add-on; it is what a client-side timer is.
A timer that lives in the student's browser is a request. A deadline the exam itself owns is a rule.
Route Two: Open and Close the Form Around a Window
No add-on, no third party, no permissions screen. You keep the form closed to responses, open it when the window starts, and close it when the window ends. In Forms this is the accepting-responses switch, flipped by you at both ends or by a script on a schedule. For a homework quiz or a weekly class test this is genuinely the right answer.
- Write the duration into the form description in plain words, because nothing on screen will show it.
- Leave responses closed until the window opens, and announce the window in the same place every week.
- Open responses at the start time; close them at the end time, by hand or by a script you are prepared to maintain.
- Tell students the clock is the window and not their personal timer, so a late start costs them.
- Keep a note of who could not get in. A closed form gives a student no way to tell you they were stuck.
The weakness is in that fourth line. A response window times the batch, not the candidate. Whoever opens the form as it goes live gets the whole window; whoever opens it minutes before you close gets minutes. For a practice test that is survivable. For a rehearsal of a timed exam, where the point is that every candidate faces the same duration from their own first question, it is not.
What a Purpose-Built Exam Screen Does Differently
On MockSetu the clock is not an attachment to the page; it is part of the sitting. Time lives on the section - add one and it arrives with 60 minutes on it, which you change to whatever the paper needs. When a signed-in student presses Start, the deadline is written into their attempt row in the database. Starting goes through one function that first looks for an unexpired, unsubmitted sitting on the same sections and hands that back instead of creating a new one, so refreshing resumes the same deadline rather than minting a fresh full-length clock. Be clear about the limit: the clock's length is still sent from the browser when the sitting opens, so this closes the refresh loophole a student trips over by accident, not a determined person with developer tools open.
The countdown runs in a Web Worker rather than on the page, so a backgrounded tab keeps counting instead of being throttled to a crawl. One warning fires when five minutes are left on the current clock. At zero the page submits itself through the same code the Submit button uses, banking the time spent on the question still open - auto-submit is the exam finishing, not a separate script racing it.
The closed-laptop case has its own rule. While the clock runs the page leaves a heartbeat in local storage roughly every thirty seconds. Come back on the same device within five minutes and the sitting resumes: same deadline, saved answers pulled back in, landing on the question last touched. Stay away longer and the old sitting is sealed and filed as a normal, ranked attempt, and the next start is a fresh one. The clock never stops to wait.
The shape of the clock is a setting, not a constant, and there are three shapes.
- Section switching off, no grouping: one section at a time, each on its own clock, sat in order, and a submitted section stays closed. Time never carries over from one to the next.
- Section switching on: the whole paper on one clock, seeded from the sum of the section clocks the first time you turn it on and settable directly afterwards. Students move between sections freely and revisit answers until they submit.
- Timing groups: with switching off, pick two or more sections and give them one shared pool. They are moved next to each other when the group is created, because a pool is a run of adjacent sections. Movement is free inside the pool and locked between pools. Marks stay per section, and grouping is edited on the primary language tab of a bilingual paper.
Those three are the whole set, and the pattern you are copying decides which one you want. JEE Main Paper 1 is the single-clock case - 75 questions, 180 minutes, one deadline for the whole paper. SSC MTS is the pooled case: two sessions of 45 minutes each, sat in order, Session I qualifying with no negative marking and Session II counting towards merit at minus one. If the current bulletin puts more than one subject inside a session, those become sections inside one timing group sharing that session's 45-minute pool. For any other exam, build whatever its own bulletin says.
Whatever you choose, the student is told before the clock starts. The instructions page names the shape in words - one clock for the paper, parts sat in order, or one section at a time - and prints the minutes the runner will enforce. With switching off the paper table adds a sectional timing column: pooled rows carry the group's name and the word shared, a section with no clock set shows a dash rather than a guessed number, and a multi-section table totals the column at its foot. With switching on that column is dropped - there is only one clock to state. If the written instructions later stop matching the paper's timing, the publish dialog warns you - but it only warns. It does not block the publish.
What It Still Will Not Do
A real clock is not a cheating control, and the two get bundled together whenever someone goes looking for a Forms timer. Separate them before you move. There is no proctoring here of any kind - no webcam, no lockdown browser, no tab-switch detection - no question shuffling and no cap on attempts. Published papers are public: anyone with the link can attempt them, and there is no private or paid delivery to one batch. There is no CSV or Excel export of results and no per-student report card, and nothing messages a student that a test is waiting. A signed-out visitor can sit a public paper, but nothing is stored for them - no database deadline, no resume; they are asked to sign in at the end to save anything. If a paper has to be invigilated, that is still a room with a person in it.
Which Route to Pick
Pick by what the paper is for. A weekly class quiz where the timer is a nudge: use the response window, keep your students' data out of a third party, spend the saved effort on the questions. A timer students must actually feel, on a form you already have and cannot move this week: an add-on, installed after reading the consent screen and tested with a reload.
A rehearsal for a timed exam is neither. Once the duration is the thing being practised - per section, auto-submitted, surviving a refresh - a form with a countdown taped to it is the wrong tool, and no add-on changes that. How to create a timed online test with auto-submit walks the build end to end, everything a creator can set up free lists what else comes with it, and the fastest way to judge a clock is to sit a paper from the public library of mock tests and refresh halfway through.