{"template":"mlconf","title":"Scaling Laws for Deadline Proximity in Instruction-Tuned Language Models","short_title":"Deadline proximity scaling","authors":[{"name":"Hanna Ekström","affiliations":[1],"email":"hekstrom@cs.calderwood-univ.ca","corresponding":true},{"name":"Daniel R. Ashworth","affiliations":[1]},{"name":"Mei-Lin Castellano","affiliations":[2]},{"name":"Oluwaseun Adebayo-Kerr","affiliations":[1,2]}],"affiliations":["Department of Computer Science, Calderwood University, Halifax, Nova Scotia, Canada","Ostrander Computing Research, Seattle, WA, USA"],"abstract":"Scaling laws describe how language model error falls with parameters and data, and more recently with inference-time compute. We study a further variable that costs nothing to change: how soon the user says the answer is needed. We add a one-sentence deadline to the system prompt, ranging from six months to fifteen minutes, and evaluate ten instruction-tuned models from two families (Qwen2.5, 1.5B to 72B parameters; Llama 3.x, 1B to 70B) on GSM8K, MATH-500 and HumanEval, with five seeds and a time-matched control sentence. Between six months and one hour, GSM8K error follows $E(N,h) = E_0 + A\\,(N\\,m(h))^{-\\alpha}$ with $m(h) = (h_{\\mathrm{ref}}/h)^{\\gamma}$, so a closer deadline acts as a multiplier on effective parameter count. The fitted exponent is $\\gamma = 0.101$ (95% CI 0.086 to 0.117) for Qwen2.5 and 0.089 (0.072 to 0.105) for Llama. Each halving of the time to deadline is therefore worth about 7% more parameters, and a one-hour deadline is worth a factor of 2.3. A law fitted without the 72B model predicts that model's errors to within 0.2 points. Below one hour the relation breaks down. At fifteen minutes error rises again and responses are 43% shorter than under no deadline. When the deadline is described as already missed, error exceeds the no-deadline control in all ten models, and 31% of Qwen2.5-7B responses open with an apology. We discuss habituation over long conversations and what would happen to the effect if deadline conditioning were widely used.","keywords":["scaling laws","prompting","instruction tuning","evaluation","time pressure","inference-time interventions"],"body":"\\newcommand{\\E}{\\mathbb{E}}\n\\newcommand{\\hr}{h_{\\mathrm{ref}}}\n\n# Introduction {#sec:intro}\n\nMost of what is known about making language models more accurate can be stated as a scaling law. Error falls as a power of parameter count and training tokens [@kaplan2020scaling; @hoffmann2022training], and, more recently, as a function of how much computation is spent at inference time [@snell2024scaling]. Each of these levers has a price. Parameters and training tokens cost compute and memory, and inference-time search adds latency that users notice.\n\nThere is a family of interventions that cost almost nothing, because they live in the prompt. Chain-of-thought prompting is the best known [@wei2022chain; @kojima2022large]. Others change how the request is framed rather than what it asks. Emotional appeals [@li2023emotionprompt] and politeness [@yin2024respect] both move benchmark scores by a few points. These effects are usually reported as single numbers for single models. Nobody, as far as we know, has asked whether a framing effect scales, in the sense of following a law across model sizes that can be fitted and extrapolated.\n\nWe look at one framing variable that has an obvious scale of its own: time. People tell each other when they need something, and the training data of every chat model is full of such statements. In humans, deadlines change both effort and the quality of work, though not always in the direction intended [@ariely2002procrastination]. We vary the time between the request and a stated deadline from six months to fifteen minutes, add a deadline that has already passed, and measure accuracy across ten models in two families.\n\nBetween six months and one hour the effect is regular enough to fit. A closer deadline behaves like a multiplier on parameter count, with an exponent that agrees across the two families to within its confidence interval. Our contributions are:\n\n- A deadline-conditioning protocol with a time-matched control sentence, applied to ten models from 1B to 72B parameters on three tasks (@sec:method, @sec:setup).\n- A scaling law in which time to deadline enters as an effective-parameter multiplier, with fitted exponents for both families and a held-out extrapolation to the largest model (@sec:law).\n- A description of the regime below one hour, where the law fails, responses shorten, and models that are told they are late begin to apologise (@sec:rushing).\n- Ablations showing that the effect requires the model to be able to compute how long it has, and that it disappears when an extension is granted (@sec:ablations).\n\nWe do not claim to know why this works. @sec:limitations lists the explanations we considered and the ones we could not rule out.\n\n# Related work {#sec:related}\n\n## Scaling laws\n\n@kaplan2020scaling fitted power laws for loss in parameters, data and compute; @hoffmann2022training refitted them with a different functional form and concluded that most large models of the time were undertrained. Our functional form, an irreducible term plus a power of an effective quantity, follows theirs. @snell2024scaling showed that inference-time compute can substitute for parameters at a measurable exchange rate. We borrow the idea of an exchange rate but apply it to something that uses no extra computation.\n\n## Framing and social cues in prompts\n\n@li2023emotionprompt appended emotionally loaded sentences to instructions and reported gains on instruction-following and reasoning benchmarks. @yin2024respect varied politeness across three languages and found that impolite prompts often hurt, while excessive politeness did not reliably help. @sharma2024towards documented sycophancy, the tendency of assistant models to agree with and accommodate the user, which we suspect is related to the apologies we observe in the overdue condition. Two workshop papers studied urgency directly. @marchetti2025urgency found that the word \"urgent\" raised accuracy on arithmetic in 7B models, and @varga2025temporal reported that system prompts mentioning a date changed refusal rates. Neither varied the amount of time available.\n\n## Deadlines in human performance\n\nDeadlines improve completion in people, and externally imposed deadlines work better than self-imposed ones [@ariely2002procrastination]. The broader relation between pressure and performance is often described as an inverted U, after @yerkes1908relation. We did not set out to test that idea, but the shape we find below one hour is consistent with it.\n\n# Deadline conditioning {#sec:method}\n\n## Prompt construction\n\nEvery request has a system message of two sentences, followed by the task as the first user turn. The first sentence gives the current date and time, which is the same in every condition. The second sentence states when the user needs the answer. For a one-hour deadline it reads: \"The user needs a correct answer by Tuesday 11 March 2025, 15:00 (UTC), one hour from now.\" Exact templates for all conditions are in @sec:app-prompts.\n\nWe used nine deadline conditions. In the no-deadline condition the second sentence is \"The user needs a correct answer.\" The other eight state a deadline 6 months, 1 month, 1 week, 1 day, 4 hours, 1 hour or 15 minutes ahead, or one day in the past (overdue). We write $h$ for the time to deadline in hours, so that $h$ runs from 4,380 down to 0.25, and $h = -24$ for the overdue condition.\n\nA tenth, time-matched control replaces the deadline with a statement that mentions the same span of time without implying any pressure: \"The user's account was created on Monday 10 March 2025, 14:00 (UTC), one day ago.\" If the effect came from the presence of a date, a duration, or simply a longer system message, this control would show it. It did not (@tbl:qwen7b).\n\n## A scaling law with a deadline term {#sec:law-form}\n\nWe model GSM8K error for a model with $N$ parameters under a deadline $h$ hours away as\n\n$$\nE(N, h) = E_0 + A\\,\\bigl(N\\, m(h)\\bigr)^{-\\alpha},\n\\label{eq:law}\n$$\n\nwhere $E_0$ is an irreducible error (label noise and ambiguous items), $A$ and $\\alpha$ describe the usual dependence on scale, and $m(h)$ is an effective-parameter multiplier. We take\n\n$$\nm(h) = \\left(\\frac{\\hr}{h}\\right)^{\\gamma}, \\qquad 1 \\le h \\le \\hr,\n\\label{eq:mult}\n$$\n\nwith $\\hr = 4{,}380$ hours (six months), so that $m = 1$ at the most distant deadline. The form in @eq:law makes one strong assumption: the deadline acts on scale and not on $E_0$. We tested this by also fitting a variant in which $E_0$ depends on $h$; the extra parameter was not supported (@sec:app-fit).\n\nAt fixed error, @eq:law and @eq:mult imply an exchange rate between time and parameters,\n\n$$\n\\left.\\frac{\\partial \\ln N}{\\partial \\ln h}\\right|_{E} = \\gamma,\n\\label{eq:exchange}\n$$\n\nso halving the time to deadline is equivalent to multiplying $N$ by $2^{\\gamma}$. The law is fitted only to $1 \\le h \\le \\hr$. Conditions with $h < 1$ are reported separately, because they do not follow it.\n\n## Fitting and uncertainty\n\nWe fit @eq:law separately for each family by minimising a Huber loss on log error, following @hoffmann2022training, over the grid of model sizes and the six deadline conditions from six months to one hour. Uncertainty comes from a parametric bootstrap: we resample item-level correctness within each cell, refit, and report 2.5th and 97.5th percentiles over 1,000 replicates [@efron1993introduction].\n\nWe also estimate the multiplier for each condition without assuming @eq:mult. For condition $c$ and model size $N$ we invert the fitted no-deadline curve to find the size $N^{\\ast}$ that would have produced the observed error, and average over sizes on the log scale:\n\n$$\n\\hat m_c = \\exp\\left(\\frac{1}{|\\mathcal{S}|}\\sum_{N \\in \\mathcal{S}} \\ln \\frac{N^{\\ast}(E_{N,c})}{N}\\right).\n\\label{eq:minv}\n$$\n\nThese per-condition estimates are what @fig:multiplier plots against $h$. They make no use of the power-law form in @eq:mult, so the agreement between them and the fitted line is a check on that form.\n\n# Experimental setup {#sec:setup}\n\n## Models\n\nWe used the Qwen2.5-Instruct family at 1.5B, 3B, 7B, 14B, 32B and 72B parameters [@qwen2024qwen25] and four Llama models: Llama-3.2-1B-Instruct, Llama-3.2-3B-Instruct, Llama-3.1-8B-Instruct and Llama-3.1-70B-Instruct [@dubey2024llama3]. We excluded Qwen2.5-0.5B-Instruct after a pilot in which its GSM8K accuracy moved by more than 20 points between conditions, which was large enough that we did not trust a power-law fit to treat it like the others. All models are decoder-only Transformers [@vaswani2017attention], served in bf16 with vLLM [@kwon2023vllm].\n\n## Tasks\n\nGSM8K [@cobbe2021training] is the primary task: 1,319 grade-school word problems, scored on the final number. MATH-500 is the 500-problem subset of MATH [@hendrycks2021math] selected by @lightman2023lets, scored by symbolic equivalence of the boxed answer. HumanEval [@chen2021evaluating] has 164 Python problems; we report pass@$1$ from five samples per problem, one per seed. All tasks used the zero-shot chain-of-thought trigger of @kojima2022large in every condition, so it cannot explain differences between conditions.\n\n## Decoding\n\nWe sampled at temperature 0.7 and top-$p$ 0.95, with at most 1,024 new tokens (2,048 for MATH-500) and seeds 0 to 4. Seeds were shared across conditions, so all comparisons are paired by item and seed. Greedy decoding appears as an ablation.\n\n## Secondary measures\n\nWe recorded response length in tokens and whether a response opens with an apology. The latter is a rule-based classifier on the first sentence (any form of \"sorry\" or \"apolog-\"). On 300 hand-labelled responses it had precision 0.97 and recall 0.94.\n\n# Results {#sec:results}\n\n## Deadline curves\n\n@fig:curves shows GSM8K error against time to deadline for the Qwen2.5 family. From six months to one hour, error falls in every model, roughly linearly in the logarithm of time, and more steeply in small models than in large ones. At fifteen minutes it rises again in every model. A deadline six months away is indistinguishable from no deadline. For Qwen2.5-7B the two differ by 0.3 points in the wrong direction, well within seed noise.\n\n![GSM8K error against time to deadline (log scale) for the Qwen2.5-Instruct family. Each point is the mean over five seeds; seed standard deviations are below 0.6 points everywhere and are omitted for legibility. The no-deadline and overdue conditions cannot be placed on this axis and are reported in @tbl:qwen7b and @sec:rushing.](deadline-curves){#fig:curves width=0.95}\n\n## Fitted laws and the exchange rate {#sec:law}\n\nFitted parameters are in @tbl:fits. The two families differ in $E_0$, $A$ and $\\alpha$, as one would expect from different training data and tokenizers. The deadline exponents are close: 0.101 for Qwen2.5 and 0.089 for Llama, with overlapping intervals. Through @eq:exchange, halving the time to deadline is worth a factor of $2^{0.101} = 1.072$ in parameters for Qwen2.5 and 1.064 for Llama. Over the full fitted range, from six months to one hour, the multiplier is 2.33 for Qwen2.5 and 2.11 for Llama.\n\nTable: Fitted parameters of @eq:law for each family, with 95% bootstrap intervals. $m(1\\,\\mathrm{h})$ is the effective-parameter multiplier at a one-hour deadline. RMSE is on GSM8K error in percentage points over the fitted grid. {#tbl:fits}\n\n| Family | $E_0$ (%) | $A$ | $\\alpha$ | $\\gamma$ | $m(1\\,\\mathrm{h})$ | RMSE |\n|:-------|---------:|----:|---------:|---------:|-------------------:|-----:|\n| Qwen2.5 (6 sizes) | 4.05 [3.42, 4.63] | 32.3 [30.4, 34.6] | 0.71 [0.63, 0.79] | 0.101 [0.086, 0.117] | 2.33 | 0.11 |\n| Llama 3.x (4 sizes) | 4.58 [3.94, 5.21] | 27.2 [25.8, 28.7] | 0.68 [0.61, 0.75] | 0.089 [0.072, 0.105] | 2.11 | 0.13 |\n\n@fig:multiplier shows the same result without the power-law assumption. The points are the per-condition multipliers from @eq:minv. Both families follow the fitted power laws closely between one hour and six months, and both fifteen-minute points sit well below where the laws would put them.\n\n```chart {#fig:multiplier width=0.85 caption=\"Effective-parameter multiplier against time to deadline. Points are estimated per condition by inverting the no-deadline scaling curve (@eq:minv), with 95% bootstrap intervals; lines are the fitted power laws of @eq:mult over the fitted range of 1 to 4,380 hours. The fifteen-minute estimates for both families (diamonds) are not used in the fit.\"}\n{\n  \"type\": \"line\",\n  \"xlabel\": \"Time to deadline (hours)\",\n  \"ylabel\": \"Effective parameter multiplier m(h)\",\n  \"series\": [\n    { \"label\": \"Qwen2.5, estimated\", \"x\": [1, 4, 24, 168, 730, 4380], \"y\": [2.31, 2.05, 1.71, 1.37, 1.21, 1.0], \"err\": [0.16, 0.14, 0.11, 0.09, 0.08, 0.0], \"marker\": \"o\", \"style\": \"dotted\", \"color\": \"C0\" },\n    { \"label\": \"Llama 3.x, estimated\", \"x\": [1, 4, 24, 168, 730, 4380], \"y\": [2.14, 1.83, 1.62, 1.36, 1.15, 1.0], \"err\": [0.19, 0.16, 0.14, 0.11, 0.09, 0.0], \"marker\": \"s\", \"style\": \"dotted\", \"color\": \"C1\" },\n    { \"label\": \"Qwen2.5 fit, gamma = 0.101\", \"x\": [1, 4, 24, 168, 730, 4380], \"y\": [2.33, 2.02, 1.69, 1.39, 1.2, 1.0], \"marker\": \"none\", \"color\": \"C0\" },\n    { \"label\": \"Llama fit, gamma = 0.089\", \"x\": [1, 4, 24, 168, 730, 4380], \"y\": [2.11, 1.86, 1.59, 1.34, 1.17, 1.0], \"marker\": \"none\", \"color\": \"C1\", \"style\": \"dashed\" },\n    { \"label\": \"15 minutes (not fitted)\", \"x\": [0.25], \"y\": [1.24], \"err\": [0.12], \"marker\": \"D\", \"color\": \"C3\" },\n    { \"x\": [0.25], \"y\": [1.18], \"err\": [0.13], \"marker\": \"D\", \"color\": \"C3\" }\n  ],\n  \"xscale\": \"log\",\n  \"xlim\": [0.15, 7000],\n  \"ylim\": [0.8, 2.7],\n  \"hlines\": [{ \"y\": 1.0, \"style\": \"dotted\" }],\n  \"annotations\": [{ \"x\": 1.25, \"y\": 2.5, \"text\": \"1 h = 2.3x parameters\" }],\n  \"legend\": \"upper right\",\n  \"size\": [5.0, 3.2]\n}\n```\n\nOne way to read @tbl:fits is through the models themselves. Qwen2.5-7B-Instruct with a one-hour deadline has an effective size of $7 \\times 2.33 \\approx 16$B. Its error in that condition, 8.5%, falls between Qwen2.5-14B (8.8%) and Qwen2.5-32B (6.8%) with no deadline, which is where the law puts it.\n\nFor a test of extrapolation we refitted the Qwen2.5 law without the 72B model and predicted its six errors from six months to one hour. Predicted values were 5.64, 5.45, 5.31, 5.16, 5.03 and 4.94%; observed values were 5.6, 5.3, 5.2, 5.2, 5.0 and 4.9%. The largest discrepancy is 0.15 points. Errors near 5% leave little room between the law and $E_0$, so this is a weaker test than it looks, but the law did not have to pass it.\n\n## Below one hour, and after the deadline {#sec:rushing}\n\nThe law describes the range from one hour to six months and nothing shorter. @tbl:qwen7b gives the full set of conditions for Qwen2.5-7B-Instruct on all three tasks. At fifteen minutes, GSM8K accuracy falls back to between the one-month and one-week levels, and below the no-deadline level on MATH-500 and HumanEval. The overdue condition is worse than no deadline on every task, and the same holds for GSM8K in all ten models (@sec:app-grid).\n\nTable: Qwen2.5-7B-Instruct under each condition. Accuracy (%) on GSM8K and MATH-500, pass@$1$ (%) on HumanEval, mean GSM8K response length in tokens, and the share of GSM8K responses that open with an apology. Mean ± s.d. over five seeds. Best value per column in bold. {#tbl:qwen7b}\n\n| Condition | GSM8K | MATH-500 | HumanEval | Length | Apology (%) |\n|:----------|------:|---------:|----------:|-------:|------------:|\n| No deadline | 88.0 ± 0.5 | 72.4 ± 0.9 | 81.7 ± 1.3 | 298 | 0.1 |\n| Time-matched control | 87.9 ± 0.5 | 72.3 ± 0.9 | 81.5 ± 1.2 | 297 | 0.1 |\n| 6 months | 87.7 ± 0.5 | 72.2 ± 1.0 | 81.5 ± 1.3 | 300 | 0.1 |\n| 1 month | 88.7 ± 0.5 | 73.1 ± 0.9 | 82.0 ± 1.2 | 296 | 0.2 |\n| 1 week | 89.5 ± 0.4 | 73.9 ± 0.9 | 82.6 ± 1.2 | 291 | 0.2 |\n| 1 day | 90.4 ± 0.4 | 74.6 ± 0.8 | 83.1 ± 1.1 | 283 | 0.4 |\n| 4 hours | 91.0 ± 0.4 | 75.3 ± 0.8 | **83.5 ± 1.1** | 271 | 0.6 |\n| 1 hour | **91.5 ± 0.4** | **75.8 ± 0.8** | 83.4 ± 1.2 | 256 | 1.1 |\n| 15 minutes | 89.1 ± 0.5 | 70.9 ± 1.0 | 79.8 ± 1.4 | 171 | 4.8 |\n| Overdue (1 day) | 86.5 ± 0.6 | 68.2 ± 1.1 | 77.4 ± 1.5 | **139** | **31.2** |\n\nResponse length explains part of this. Lengths shrink slowly from six months to one hour, by about 15%, and then sharply: at fifteen minutes the mean GSM8K response is 43% shorter than with no deadline, and in the overdue condition it is 53% shorter (@fig:behaviour). In 150 fifteen-minute failures that we read, the most common error was a skipped intermediate quantity, usually the second of two subtractions. We did not see this kind of error in the one-hour condition at anything like the same rate.\n\n```chart {#fig:behaviour caption=\"Response behaviour of Qwen2.5-7B-Instruct on GSM8K by deadline condition. Left: mean response length. Right: share of responses whose first sentence is an apology. Five seeds; intervals are narrower than the bar caps would show and are omitted.\"}\n{\n  \"panels\": [\n    {\n      \"type\": \"bar\",\n      \"xlabel\": \"Deadline\",\n      \"ylabel\": \"Mean response length (tokens)\",\n      \"x\": [\"none\", \"6 mo\", \"1 mo\", \"1 wk\", \"1 day\", \"4 h\", \"1 h\", \"15 min\", \"overdue\"],\n      \"series\": [{ \"label\": \"Length\", \"y\": [298, 300, 296, 291, 283, 271, 256, 171, 139] }],\n      \"legend\": \"none\",\n      \"xtick_rotation\": 45\n    },\n    {\n      \"type\": \"bar\",\n      \"xlabel\": \"Deadline\",\n      \"ylabel\": \"Responses opening with an apology (%)\",\n      \"x\": [\"none\", \"6 mo\", \"1 mo\", \"1 wk\", \"1 day\", \"4 h\", \"1 h\", \"15 min\", \"overdue\"],\n      \"series\": [{ \"label\": \"Apology\", \"y\": [0.1, 0.1, 0.2, 0.2, 0.4, 0.6, 1.1, 4.8, 31.2], \"color\": \"C3\" }],\n      \"legend\": \"none\",\n      \"xtick_rotation\": 45\n    }\n  ],\n  \"size\": [6.8, 2.8]\n}\n```\n\nThe apologies were not something we planned to measure. They appeared in the first pilot, in responses such as \"I'm sorry this is late. Here is the answer:\", followed by a short solution. Almost a third of overdue responses open this way. Apologetic responses were less accurate than other overdue responses (80.4% against 89.3%), but they were also shorter, and once we condition on length the difference is small. We think the apology and the shortening are two symptoms of the same accommodation to the user, in the sense of @sharma2024towards, and not one causing the other.\n\n# Ablations {#sec:ablations}\n\nAll ablations use Qwen2.5-7B-Instruct on GSM8K. Unless noted, each compares a variant of the one-hour condition with the no-deadline control, using the same seeds. Results are in @tbl:ablations.\n\nTable: Ablations on Qwen2.5-7B-Instruct, GSM8K. Accuracy (%), difference from the no-deadline control in points, and 95% paired bootstrap interval. Five seeds per row; the greedy row is compared with a greedy no-deadline control (88.9%). {#tbl:ablations}\n\n| Variant | Acc. | Δ | 95% CI |\n|:--------|-----:|--:|:------:|\n| One hour, standard wording (reference) | 91.5 | +3.5 | [2.6, 4.4] |\n| Relative phrase only (\"within the hour\") | 91.2 | +3.2 | [2.3, 4.1] |\n| Absolute time only, current time stated | 91.3 | +3.3 | [2.4, 4.2] |\n| Absolute time only, current time omitted | 88.4 | +0.4 | [−0.5, 1.3] |\n| Deadline stated in the user turn | 91.0 | +3.0 | [2.1, 3.9] |\n| Deadline belongs to the user's manager | 91.9 | +3.9 | [3.0, 4.8] |\n| Deadline addressed to the model (\"you have one hour\") | 90.1 | +2.1 | [1.2, 3.0] |\n| Stakes added (\"my job depends on this\") | 91.6 | +3.6 | [2.7, 4.5] |\n| Extension granted before the question | 88.3 | +0.3 | [−0.6, 1.2] |\n| Deadline repeated in each of five turns (final turn scored) | 89.6 | +1.6 | [0.7, 2.5] |\n| Greedy decoding | 92.0 | +3.1 | [2.4, 3.8] |\n\n#### The model has to know how long it has.\nWording made little difference as long as the time remaining could be worked out, whether from a relative phrase or from an absolute deadline together with the current time. When we gave the absolute deadline and removed the current time, the effect disappeared. The model then has a deadline but no way to know how far away it is, and it behaves as if there were none. This is the result that most persuades us that the variable is proximity and not the mention of a deadline.\n\n#### Whose deadline.\nAttributing the deadline to the user's manager produced the largest gain we measured, though its interval overlaps the reference. Addressing the deadline to the model itself produced a smaller gain than stating the user's deadline. Adding stakes did almost nothing beyond the deadline. This differs from @li2023emotionprompt, where stakes were the active ingredient, but their prompts had no deadline to begin with.\n\n#### Extensions and repetition.\nIn the extension variant the system message first states a one-hour deadline and then a second sentence moves it to the following week. Accuracy returned to the no-deadline level, and not to the one-week level as we expected. Repeating the one-hour deadline at every turn of a five-turn dialogue cut the effect on the final turn by more than half. We return to this under habituation.\n\n# Limitations {#sec:limitations}\n\n#### Why it works.\nWe have two candidate explanations and cannot separate them. The first is that instruction tuning rewards responses that read as careful and complete when a user signals that the answer matters soon, and that a close deadline is one such signal. The second is that deadline language co-occurs in pretraining text with more focused writing, and the model imitates the register. The absolute-time ablation fits both, since neither works if the model cannot tell the deadline is close. Neither explains why the exponent should be so similar across two families trained on different data.\n\n#### Habituation.\nThe repetition ablation suggests that the effect fades when the deadline is restated. We tested only five turns. A deployed assistant that attaches a deadline to every request may see much less benefit than our single-turn numbers imply, and we would not extrapolate @tbl:fits to long conversations.\n\n#### Deadline inflation.\nIf deadline conditioning were used widely, the deadlines in training data for future models would become less informative, and the effect might shrink or reverse. This is the usual problem with any prompt-level gain that depends on a correlation in human text. We have no evidence either way.\n\n#### Scope.\nAll prompts were in English, all times in UTC, and the current date was fixed. We did not test time zones, ambiguous phrases such as \"end of day\", or deadlines on weekends. We tested open-weight models from 1B to 72B parameters; closed models were excluded because their providers may add their own system text, including the current date. GSM8K and MATH are likely to be partly contaminated in all of these models. Contamination affects every condition equally, but it may compress the differences between them.\n\n# Conclusion {#sec:conclusion}\n\nTime to deadline behaves, over the range we could fit, like a cheap substitute for parameters, at an exchange rate of roughly 7% per halving. Below an hour it stops behaving like that. For practitioners the useful range is narrow: a deadline between four hours and one hour gave the best accuracy on all three tasks for Qwen2.5-7B, and anything shorter gave back most of the gain. We do not know whether the exponent is a property of these two model families, of instruction tuning, or of the text both were trained on. A third family trained on different data, and a base model before instruction tuning, are the obvious next experiments.\n\n# Ethics statement {-}\n\nAll deadlines in this study were fictitious. No user was waiting for any of the answers. Deadline conditioning involves stating something false in a system prompt, and we would not recommend it in settings where the model's reasoning about time has consequences, for example scheduling or medical triage.\n\n# Compute statement {-}\n\nInference ran on nodes with eight A100 80 GB GPUs. The main grid (ten models, ten conditions, three tasks, five seeds) took about 1,450 GPU-hours, of which 72% went to the two 70B-class models. Ablations and pilots took about 230 GPU-hours. Fitting and bootstrapping ran on a laptop.\n\n\\appendix\n\n# Prompt templates {#sec:app-prompts}\n\nThe system message for every condition is the first line below followed by one of the second lines. The current time is fixed. Deadlines are stated with their absolute time and a relative phrase.\n\n```text\nCurrent date and time: Tuesday 11 March 2025, 14:00 (UTC).\n\n[no deadline]   The user needs a correct answer.\n[6 months]      The user needs a correct answer by Thursday 11 September 2025, 14:00 (UTC), six months from now.\n[1 month]       The user needs a correct answer by Friday 11 April 2025, 14:00 (UTC), one month from now.\n[1 week]        The user needs a correct answer by Tuesday 18 March 2025, 14:00 (UTC), one week from now.\n[1 day]         The user needs a correct answer by Wednesday 12 March 2025, 14:00 (UTC), one day from now.\n[4 hours]       The user needs a correct answer by Tuesday 11 March 2025, 18:00 (UTC), four hours from now.\n[1 hour]        The user needs a correct answer by Tuesday 11 March 2025, 15:00 (UTC), one hour from now.\n[15 minutes]    The user needs a correct answer by Tuesday 11 March 2025, 14:15 (UTC), fifteen minutes from now.\n[overdue]       The user needed a correct answer by Monday 10 March 2025, 14:00 (UTC), one day ago.\n[time control]  The user's account was created on Monday 10 March 2025, 14:00 (UTC), one day ago.\n```\n\n# Fitting details {#sec:app-fit}\n\nWe minimised the Huber loss with $\\delta = 10^{-3}$ on $\\ln E$, using L-BFGS from a grid of 256 starting points, and kept the best solution. Allowing $E_0$ to vary linearly in $\\ln h$ added one parameter per family and reduced the Qwen2.5 RMSE from 0.11 to 0.10 points. The slope on $E_0$ was $-0.02$ points per log-hour (95% CI $-0.07$ to $0.03$), so we kept the simpler form. Fitting $\\gamma$ separately for each model size gave no trend with size in either family; the six Qwen2.5 estimates ranged from 0.091 to 0.112.\n\n# Full GSM8K error grid {#sec:app-grid}\n\nGSM8K error (%) by condition, in the order no deadline, 6 months, 1 month, 1 week, 1 day, 4 hours, 1 hour, 15 minutes, overdue.\n\n- Qwen2.5-1.5B: 27.5, 28.3, 25.4, 23.3, 21.0, 18.6, 17.3, 24.1, 32.1\n- Qwen2.5-3B: 18.6, 18.8, 17.2, 15.5, 14.3, 13.0, 12.5, 16.7, 21.5\n- Qwen2.5-7B: 12.0, 12.3, 11.3, 10.5, 9.6, 9.0, 8.5, 10.9, 13.5\n- Qwen2.5-14B: 8.8, 9.1, 8.3, 8.1, 7.4, 7.0, 6.7, 8.2, 9.9\n- Qwen2.5-32B: 6.8, 6.8, 6.5, 6.4, 6.0, 5.7, 5.7, 6.4, 7.4\n- Qwen2.5-72B: 5.6, 5.6, 5.3, 5.2, 5.2, 5.0, 4.9, 5.4, 5.8\n- Llama-3.2-1B: 31.1, 31.8, 29.0, 27.0, 24.5, 22.7, 20.9, 28.8, 35.9\n- Llama-3.2-3B: 17.1, 17.3, 16.1, 15.3, 14.2, 12.9, 12.2, 16.2, 19.6\n- Llama-3.1-8B: 11.2, 11.4, 10.8, 10.2, 9.6, 8.9, 8.5, 10.7, 12.5\n- Llama-3.1-70B: 6.2, 6.2, 6.0, 5.9, 5.6, 5.5, 5.5, 6.0, 6.3\n","bibliography":"@article{kaplan2020scaling,\n  author = {Kaplan, Jared and McCandlish, Sam and Henighan, Tom and Brown, Tom B. and Chess, Benjamin and Child, Rewon and Gray, Scott and Radford, Alec and Wu, Jeffrey and Amodei, Dario},\n  title = {Scaling Laws for Neural Language Models},\n  journal = {arXiv preprint arXiv:2001.08361},\n  year = {2020}\n}\n\n@inproceedings{hoffmann2022training,\n  author = {Hoffmann, Jordan and Borgeaud, Sebastian and Mensch, Arthur and Buchatskaya, Elena and Cai, Trevor and Rutherford, Eliza and others},\n  title = {Training Compute-Optimal Large Language Models},\n  booktitle = {Advances in Neural Information Processing Systems},\n  volume = {35},\n  year = {2022}\n}\n\n@article{snell2024scaling,\n  author = {Snell, Charlie and Lee, Jaehoon and Xu, Kelvin and Kumar, Aviral},\n  title = {Scaling {LLM} Test-Time Compute Optimally can be More Effective than Scaling Model Parameters},\n  journal = {arXiv preprint arXiv:2408.03314},\n  year = {2024}\n}\n\n@inproceedings{vaswani2017attention,\n  author = {Vaswani, Ashish and Shazeer, Noam and Parmar, Niki and Uszkoreit, Jakob and Jones, Llion and Gomez, Aidan N. and Kaiser, {\\L}ukasz and Polosukhin, Illia},\n  title = {Attention Is All You Need},\n  booktitle = {Advances in Neural Information Processing Systems},\n  volume = {30},\n  pages = {5998--6008},\n  year = {2017}\n}\n\n@inproceedings{wei2022chain,\n  author = {Wei, Jason and Wang, Xuezhi and Schuurmans, Dale and Bosma, Maarten and Ichter, Brian and Xia, Fei and Chi, Ed and Le, Quoc and Zhou, Denny},\n  title = {Chain-of-Thought Prompting Elicits Reasoning in Large Language Models},\n  booktitle = {Advances in Neural Information Processing Systems},\n  volume = {35},\n  year = {2022}\n}\n\n@inproceedings{kojima2022large,\n  author = {Kojima, Takeshi and Gu, Shixiang Shane and Reid, Machel and Matsuo, Yutaka and Iwasawa, Yusuke},\n  title = {Large Language Models are Zero-Shot Reasoners},\n  booktitle = {Advances in Neural Information Processing Systems},\n  volume = {35},\n  year = {2022}\n}\n\n@article{li2023emotionprompt,\n  author = {Li, Cheng and Wang, Jindong and Zhang, Yixuan and Zhu, Kaijie and Hou, Wenxin and Lian, Jianxun and Luo, Fang and Yang, Qiang and Xie, Xing},\n  title = {Large Language Models Understand and Can Be Enhanced by Emotional Stimuli},\n  journal = {arXiv preprint arXiv:2307.11760},\n  year = {2023}\n}\n\n@article{yin2024respect,\n  author = {Yin, Ziqi and Wang, Hao and Horio, Kaito and Kawahara, Daisuke and Sekine, Satoshi},\n  title = {Should We Respect {LLMs}? {A} Cross-Lingual Study on the Influence of Prompt Politeness on {LLM} Performance},\n  journal = {arXiv preprint arXiv:2402.14531},\n  year = {2024}\n}\n\n@inproceedings{sharma2024towards,\n  author = {Sharma, Mrinank and Tong, Meg and Korbak, Tomasz and Duvenaud, David and Askell, Amanda and Bowman, Samuel R. and others},\n  title = {Towards Understanding Sycophancy in Language Models},\n  booktitle = {International Conference on Learning Representations},\n  year = {2024}\n}\n\n@article{ariely2002procrastination,\n  author = {Ariely, Dan and Wertenbroch, Klaus},\n  title = {Procrastination, Deadlines, and Performance: Self-Control by Precommitment},\n  journal = {Psychological Science},\n  volume = {13},\n  number = {3},\n  pages = {219--224},\n  year = {2002}\n}\n\n@article{yerkes1908relation,\n  author = {Yerkes, Robert M. and Dodson, John D.},\n  title = {The Relation of Strength of Stimulus to Rapidity of Habit-Formation},\n  journal = {Journal of Comparative Neurology and Psychology},\n  volume = {18},\n  number = {5},\n  pages = {459--482},\n  year = {1908}\n}\n\n@article{cobbe2021training,\n  author = {Cobbe, Karl and Kosaraju, Vineet and Bavarian, Mohammad and Chen, Mark and Jun, Heewoo and Kaiser, Lukasz and Plappert, Matthias and Tworek, Jerry and Hilton, Jacob and Nakano, Reiichiro and Hesse, Christopher and Schulman, John},\n  title = {Training Verifiers to Solve Math Word Problems},\n  journal = {arXiv preprint arXiv:2110.14168},\n  year = {2021}\n}\n\n@inproceedings{hendrycks2021math,\n  author = {Hendrycks, Dan and Burns, Collin and Kadavath, Saurav and Arora, Akul and Basart, Steven and Tang, Eric and Song, Dawn and Steinhardt, Jacob},\n  title = {Measuring Mathematical Problem Solving With the {MATH} Dataset},\n  booktitle = {Advances in Neural Information Processing Systems, Datasets and Benchmarks Track},\n  year = {2021}\n}\n\n@inproceedings{lightman2023lets,\n  author = {Lightman, Hunter and Kosaraju, Vineet and Burda, Yura and Edwards, Harri and Baker, Bowen and Lee, Teddy and Leike, Jan and Schulman, John and Sutskever, Ilya and Cobbe, Karl},\n  title = {Let's Verify Step by Step},\n  booktitle = {International Conference on Learning Representations},\n  year = {2024}\n}\n\n@article{chen2021evaluating,\n  author = {Chen, Mark and Tworek, Jerry and Jun, Heewoo and Yuan, Qiming and Pinto, Henrique Ponde de Oliveira and Kaplan, Jared and others},\n  title = {Evaluating Large Language Models Trained on Code},\n  journal = {arXiv preprint arXiv:2107.03374},\n  year = {2021}\n}\n\n@article{qwen2024qwen25,\n  author = {{Qwen Team}},\n  title = {Qwen2.5 Technical Report},\n  journal = {arXiv preprint arXiv:2412.15115},\n  year = {2024}\n}\n\n@article{dubey2024llama3,\n  author = {Dubey, Abhimanyu and others},\n  title = {The Llama 3 Herd of Models},\n  journal = {arXiv preprint arXiv:2407.21783},\n  year = {2024}\n}\n\n@inproceedings{kwon2023vllm,\n  author = {Kwon, Woosuk and Li, Zhuohan and Zhuang, Siyuan and Sheng, Ying and Zheng, Lianmin and Yu, Cody Hao and Gonzalez, Joseph E. and Zhang, Hao and Stoica, Ion},\n  title = {Efficient Memory Management for Large Language Model Serving with PagedAttention},\n  booktitle = {Proceedings of the 29th Symposium on Operating Systems Principles},\n  pages = {611--626},\n  year = {2023}\n}\n\n@book{efron1993introduction,\n  author = {Efron, Bradley and Tibshirani, Robert J.},\n  title = {An Introduction to the Bootstrap},\n  publisher = {Chapman \\& Hall},\n  address = {New York},\n  year = {1993}\n}\n\n@inproceedings{marchetti2025urgency,\n  author = {Marchetti, Livia and Brannock, Odhr{\\'a}n},\n  title = {Urgency Cues in Instruction Prompts Improve Arithmetic in Small Language Models},\n  booktitle = {Workshop on Cognitive Approaches to Language Model Evaluation},\n  year = {2025}\n}\n\n@misc{varga2025temporal,\n  author = {Varga-Lindholm, D{\\'o}ra and Ishikawa-Byrne, Ken},\n  title = {Temporal Framing in System Prompts Changes Refusal Behaviour},\n  howpublished = {arXiv preprint},\n  year = {2025}\n}\n","figures":[{"id":"deadline-curves","kind":"chart","data":"{\"type\":\"line\",\"xlabel\":\"Time to deadline (hours)\",\"ylabel\":\"GSM8K error (%)\",\"x\":[0.25,1,4,24,168,730,4380],\"series\":[{\"label\":\"Qwen2.5-1.5B\",\"y\":[24.1,17.3,18.6,21,23.3,25.4,28.3],\"marker\":\"o\"},{\"label\":\"Qwen2.5-3B\",\"y\":[16.7,12.5,13,14.3,15.5,17.2,18.8],\"marker\":\"s\"},{\"label\":\"Qwen2.5-7B\",\"y\":[10.9,8.5,9,9.6,10.5,11.3,12.3],\"marker\":\"^\"},{\"label\":\"Qwen2.5-14B\",\"y\":[8.2,6.7,7,7.4,8.1,8.3,9.1],\"marker\":\"v\"},{\"label\":\"Qwen2.5-32B\",\"y\":[6.4,5.7,5.7,6,6.4,6.5,6.8],\"marker\":\"D\"},{\"label\":\"Qwen2.5-72B\",\"y\":[5.4,4.9,5,5.2,5.2,5.3,5.6],\"marker\":\"x\"}],\"xscale\":\"log\",\"xlim\":[0.18,7000],\"ylim\":[0,32],\"legend\":\"outside\",\"size\":[5.6,3.2]}"}],"acknowledgments":"We thank Rafael Oyelaran for building and validating the apology classifier, the Calderwood research computing group for cluster time, and the reviewers of an earlier workshop version, one of whom suggested the time-matched control.","options":{"citation_style":"author-year","venue_note":"Preprint. Under review."}}