A name is not an assignment
Consider this note: “Nora said the analyst should check the extraction before Friday.” A tempting task is “Nora: check the extraction; due Friday.” Yet the sentence identifies Nora as the speaker; it does not establish that she is the analyst or accepted the work. The action can be captured while ownership stays unresolved. A useful draft is “Check the extraction; owner unresolved; timing: before Friday.” This retains the request without manufacturing a personal commitment. A plausible name is not enough to justify an assignment.
A record is not a commitment
Think of a bookkeeper; recording an obligation is different from accepting responsibility for fulfilling it. Apply that distinction when turning notes into tasks. Keep the proposed action, owner evidence and timing evidence separate. “Before Friday” supports a time constraint, but not a precise hour. Preserve the wording until the calendar context is clear. Missing ownership should trigger clarification, not a guess disguised as completeness.
Check the evidence before assigning
Read the exact clause that supports each proposed field. Does it identify the person doing the work, or merely the reporter, reviewer or beneficiary? Look for explicit acceptance or an assignment from someone authorized to allocate the work. If neither appears, label the owner unresolved and ask who will take it. If instructions conflict, preserve that conflict for resolution. Keep the supporting quotation visible so another reader can challenge the proposed assignment. Repeat the check for deadlines; an estimate should not silently become a commitment.
Hypothetical boundary: the midnight rota
Suppose an authorized team rule assigns extraction checks to the duty analyst. A note arrives before midnight; the rota changes before processing. Resolve a name only if the rule specifies whether intake time or execution time controls, and the rota identifies one person for that time. Otherwise retain the role and leave the named owner unresolved. Generation time alone does not decide responsibility. These examples are illustrative, not reported test results. ABOLTUS is in development.