Answer
What belongs in project instructions versus task instructions?
Project instructions carry what is true across every task. Task instructions carry what is true this time. Anything else is misfiled.
Standing instructions carry what holds across every task in the project. The brief carries what is true only this time. When a standing rule is critical to this task, restate it in the brief as well; the duplication buys adherence.
The test is durability, and it is the only test that produces a stable answer. Will this still be true for the next task, and the one after that? If yes, it is project-level: naming conventions, which systems are authoritative, constraints that cannot be violated, the register the business writes in, decisions that have been made and closed. If no, it is task-level, whatever its importance.
Importance is the wrong axis and it is the one people use, which is how permanent documents fill up with the detail of whatever job was being done when they were last edited. A critical instruction about today's task feels like it belongs in the important file, and next month it is a rule about a job nobody is doing, competing for attention with rules that still apply.
The consequential exception is deliberate duplication. Instructions attached to the immediate task are followed more reliably than the same words in a standing document, because they are not competing with everything else in that document. So where a standing rule is genuinely load-bearing for this particular job, restating it in the brief is not redundancy, it is buying adherence at the cost of two lines. The standing file remains the source of truth; the brief carries an emphasis.
There is a third location that gets forgotten and does most of the work in mature setups: the material itself. A constraint that can be expressed as a check, a schema, a template with the fields already in it, or a validated format does not need to be an instruction at all. Instructions are what you use when the constraint cannot be built into the thing, and moving a rule from a document into a structure is the strongest version of making it followed.
Two symptoms indicate the split has gone wrong. A standing file that has to be edited before most tasks is holding task content, and the edits will accumulate as residue. A brief that repeats the same paragraph every time is holding project content, and it should be promoted so it stops depending on whoever writes the brief remembering it. Both are visible without any analysis, and both are worth acting on when noticed rather than tolerating.
File by how long it stays true, not by how important it feels, because importance is what puts task-specific detail into a permanent document.
Siddharth Sharma, Context Theory
Related questions
What about instructions that apply to a type of task rather than all of them?
Those want a third file that gets included when relevant, rather than a section in the standing document that applies to a minority of runs. A rule that is irrelevant to most tasks still competes for attention on all of them, and conditional inclusion keeps the working set matched to the job.
Does the project file need to be read every time?
It is supplied every time, which is not the same as being attended to. That is precisely why length matters and why critical rules get restated in the brief. Treating supply as equivalent to adherence is the assumption behind most surprised reactions to an ignored standing rule.
METHOD
Every figure below carries its source and the date it was verified. Nothing on this page is asserted.
The numbers on this page.
| What | Value | Specific to |
|---|---|---|
| Visibility lift in AI-generated answers from GEO methods | up to 40% | Category-wide |
| Close rate — response under 5 minutes vs over 24 hours | 32% vs 12% | Category-wide |
Aggarwal et al., "GEO: Generative Engine Optimization", Princeton / Georgia Tech / IIT Delhi / Allen Institute for AI — KDD 2024 · GEO-bench · 10,000 queries across 8 domains · verified
Optifai speed-to-lead benchmark · n=939 companies · Q2 2025–Q1 2026 · verified
What is specific to this page.
| Kind | Claim | Check it against |
|---|---|---|
| Workflow | Durability rather than importance is the correct filing axis, because filing by importance places task-specific detail in a permanent document where it survives as residue competing with rules that still apply. | Checking each line of a standing instructions file against whether it will still apply to the next three tasks. |
| Response | An instruction attached to the immediate task is followed more reliably than the same instruction in a standing document, so restating a load-bearing standing rule in the brief buys adherence rather than duplicating information. | Comparing compliance with the same rule when it appears only in the standing file and when it also appears in the brief. |
| Software | A constraint expressible as a check, schema, template or validated format does not need to be an instruction, and moving a rule out of a document into a structure is a stronger form of enforcement than any wording. | Identifying which rules in an instructions file could be expressed as a validation and testing whether the validation makes the rule redundant. |
| Constraint | A standing file requiring edits before most tasks contains task content, and a brief repeating the same paragraph every time contains project content, and both misfilings are observable without analysis. | Reviewing the edit history of the standing file and a sample of recent briefs for repeated paragraphs. |
Each row would be wrong on another industry's page. Where a sourced figure exists it is in the table above instead; these are the constraints that shape the work and do not happen to be numbers.
Start with the measurement.
Reading about a benchmark is not the same as knowing your own number. The audit produces yours, measured rather than estimated.
$497 · delivered in 5 business days · credited against month one