# Put owner, output and deadline on the same line

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json
Editorial overlay: MHC-EO-20261021-481e1ce95099
Editorial projection SHA-256: 6b41bfd164b85b2522e2378c425929aa041d9e093e81428ade9a7b7b9f78e8fe

---

## Put owner, output and deadline on the same line

ID: MHC-D-RESEARCH-0608 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/put-owner-output-and-deadline-on-the-same-line

An action is not complete until someone can point to who delivers what by when.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- Action items are scattered across prose and ownership is implied.

### Avoid when

- Shared work can have multiple contributors; the named owner is for coordination, not blame.

### Explanation

Write each meaningful action as one unit containing owner, observable output and timing. If the deadline is conditional, name the condition. Avoid assigning an action to a group when only one person can close it.

### Steps

1. Every action has one accountable owner and an observable done state.

### Example

'Anna → confirm transport import result by 16:00' is harder to misread than 'we should check the import later.'

### Check

Every action has one accountable owner and an observable done state.

### Limits

- Shared work can have multiple contributors; the named owner is for coordination, not blame.

### Evidence and sources

- supports: CDC clear-communication guidance recommends one obvious main message, placing it early and including a clear action for the audience. — RS-B843492FBF1442AD. Complex work can require several actions, but the communication still benefits from a dominant purpose. (Core items 1, 2 and 5)
- supports: CDC guidance recommends active voice and familiar audience language, with technical terms explained where needed. — RS-B843492FBF1442AD. Technical precision should not be removed when it is necessary for the task. (Core items 6 and 7)
- RS-B843492FBF1442AD: Description and Examples of Index Items — https://www.cdc.gov/ccindex/tool/description-examples-parta.html

### Vedokrok editorial review

Name the owner, then confirm the handoff

An action line can name a person without establishing that they have accepted responsibility. Keep the requested owner, agreed handoff and completed work distinct.

#### Make the request answerable

State one accountable owner, an observable output and a deadline or trigger. Include the needed context and access. For consequential work transferred between people, ask the incoming owner to confirm the responsibility and next checkpoint. If they have not accepted it, report the handoff as pending rather than silently treating the task as covered.

#### Transfer responsibility explicitly

For example: “Mira, can you check batch 42 and report its terminal result by 16:00 UTC?” Record the reply and any changed deadline, then tell affected colleagues who is handling it. Google’s incident-command handoff uses an explicit acknowledgment; applying that distinction to an ordinary work request is an editorial adaptation. Follow the team’s actual assignment rules, and keep critical incidents on their formal channel. Where an established policy already assigns the role, record that basis rather than inventing a new acceptance requirement.

**Editorial takeaway:** Use the team’s assignment rules to distinguish a request, a transferred responsibility and completed work. A clear owner/output/deadline line does not itself prove execution.

#### Editorial evidence

- supports: Google’s incident-command handoff calls for briefing the incoming commander, explicit acknowledgment and communication of the transfer to others. — RS-A7FC21766320D048. Selected official practitioner guidance inspected on 2026-10-05. No workplace experiment or handoff was performed. (Clear, Live Handoff)
- limits: The cited handoff procedure concerns transfer of incident command after the incoming commander has been informed. — RS-A7FC21766320D048. This bounds the recommendation: routine tasks follow their own assignment rules. The one-line request example is editorial practice, not proof of a universal communication effect. (Clear, Live Handoff; Recursive Separation of Responsibilities)
- RS-A7FC21766320D048: Managing Incidents — https://sre.google/sre-book/managing-incidents/

Editorial version: 1.0.0 · evidence checked 2026-10-05 · Agent editorial review; not human or expert certification.

No review details supplied.
