Do not assign an action item to someone who missed the meeting

Do not assign an action item to someone who missed the meeting. An absent colleague can be the proposed owner, but an attendee must own the handoff until that colleague accepts the task, understands what “done” means and agrees to a date.

This distinction sounds small. It prevents a familiar Monday-morning exchange:

“I saw my name in the notes. What exactly am I supposed to deliver?”

The meeting ended with a neat action list. The work did not begin, because the person named on the list never made the commitment.

A name in the minutes is not consent

Imagine a launch review where the team decides that Priya should confirm the data-retention language with legal. Priya is not in the room. Someone adds:

Priya — confirm retention language — Friday

The row has an owner and a date, but both are assumptions. The group does not know whether Priya has the relevant context, whether legal can respond by Friday, or whether another deadline already makes the task impossible.

The record should show what is true:

• Proposed owner: Priya
• Handoff owner: Leon
• Request: Confirm the approved retention language for the launch brief
• Proposed date: Friday, pending Priya's confirmation
• Next check: Leon updates the record by Wednesday noon

Leon has made a commitment in the room. Priya has not. If she accepts, ownership can transfer cleanly. If she changes the scope or date, the record changes with it.

Give the handoff to someone who is present

Every task assigned in someone's absence needs a bridge owner: a person in the meeting who accepts responsibility for closing the gap.

That responsibility is concrete. The bridge owner must:

1. send the decision context, not just the task sentence;
2. ask the proposed owner to accept or decline;
3. confirm the deliverable and due date;
4. update the shared record with the answer;
5. return a refusal or material change to the decision owner.

“Tell Priya” is not a bridge. “Leon will get Priya's answer by Wednesday noon” is. The second commitment has an observable finish line even if Leon never performs the legal review himself.

This is one reason the source meeting matters. A task without its source forces the recipient to reconstruct why the work exists, which option was chosen and which constraints survived the discussion. Keep that context attached, as you would for a file that entered the meeting.

In Scripta, an action item can keep its assignee, due date, priority, status and source meeting together. Those fields make a confirmed commitment visible; they do not turn an unconfirmed name into consent. Until the handoff closes, record the attendee who actually owns the next move.

Send enough context to say yes or no

The absent colleague should not need another meeting merely to understand the task. A useful handoff contains five short pieces:

Why this exists. “The launch review kept the two-year retention period, subject to legal wording.”

The requested output. “Return the approved paragraph for the launch brief.”

The boundary. “This is wording review, not a new retention-policy decision.”

The proposed date and why. “Friday, because the client review is Monday.”

The source. Link the meeting record, decision and relevant passage or notes.

Then ask a question that permits a real answer: “Can you own this by Friday?” Do not write “FYI, this is yours,” which hides a command inside an update and gives the recipient no clean way to expose a bad assumption.

Treat silence as unresolved, not accepted

Teams often send the assignment and move on. When nobody objects, the task quietly becomes official.

Silence can mean the message was missed, the recipient assumed the date was tentative, or the task collided with work the meeting did not know about. None of those meanings is agreement.

Set a response point. If there is no answer by then, the bridge owner follows up or returns the task to the decision owner. The team can choose another owner, adjust the date, narrow the output or decide the work is not worth doing. What it cannot honestly do is preserve the absent person's name as if the issue were settled.

This also makes overdue work easier to diagnose. The failure happened at assignment, not execution. Marking the task “in progress” would only hide that distinction—the same reason “in progress” is not a useful update.

Separate authority from availability

Sometimes the absent person is the only person allowed to approve the work. That still does not make them available to perform it on the meeting's schedule.

Split the commitment:

• an attendee prepares the material and owns the handoff;
• the absent approver is named as a required dependency;
• the plan includes what happens if approval is not available by the proposed date.

For example: “Mira sends the revised terms to Priya by Tuesday. Priya's approval is requested by Thursday. If it is unavailable, Leon moves the client review.”

Now every part belongs to someone who has actually accepted it, while the approval dependency remains visible.

Correct the record when the answer changes

The handoff is not finished when the message is sent. It is finished when the shared task reflects the answer.

If Priya accepts, make her the owner and use the date she confirmed. If she can deliver Monday rather than Friday, change the date instead of burying the new plan in chat. If she declines, remove her name and return the gap to whoever owns the decision.

Do not keep both versions alive: the meeting minutes saying Friday and a private message saying Monday. One trustworthy record should show the current commitment while preserving the source meeting that explains it.

The rule is simple: people present can commit themselves. They can propose work for someone absent, but they cannot complete that person's side of the agreement. Give the handoff an owner, require an answer, and let the record say exactly what has—and has not—been accepted.