Log consent, meter usage, and name the review owner before AI drafts tasks

A bad transcript is manageable. The real risk is a draft that becomes a task, a usage line, and a shared record before the team has agreed to any of it. Put the controls in the meeting invite before the first draft arrives, not after the first unowned task appears.

Asana AI Meetings can transcribe and summarize calls from Zoom, Microsoft Teams, and Google Meet. It is available on Asana Advanced plans and above. For a small startup, the feature is useful and also easy to let slip into someone else's queue.

Keep the switch-on log in the invite

Keep the log in the invite description, where the owner, participants, and tool meet. A separate doc is easy to skip. The log has three lines, and each line answers a question that usually gets skipped: who consented, how much usage is planned, and who reviews the drafts. Fill it before enabling AI meeting task drafts. The log is the block in the invite that the owner checks when the calendar event is created.

• Consent scope: state who is covered and what the transcript may be used for.
• AI meter: set a length limit and name the person who checks the request count.
• Draft review owner: name the person who accepts or rejects drafts.

The consent line stops the surprise

Asana AI Meetings does not start transcribing automatically; it shows a consent reminder and waits for confirmation. The reminder confirms the pause. The consent line in the invite carries the scope. Use that moment to say what the team is agreeing to. The consent line should name the people in the room and the people outside it. A founder, an engineer, and a designer can agree quickly. A customer, a vendor, or a legal advisor may need a different answer. The line should also say what the transcript is for: a summary, a project update, a hiring decision, or a support record. When the purpose changes after the call, reconfirm before sharing.

The meter line keeps usage predictable

The first 60 minutes consume one AI Request, and each additional 60-minute block or part of one adds another. A weekly sync is easy to predict. A long planning session is not. Set a length limit before the call, and assign someone to check the request count after the summary arrives. The meter line should include the planned length, the hard stop, and the person who watches the count. A short sync is different from a long planning session, even when both start on time. When the team expects a long call, shorten the agenda or note the extra usage before the call begins.

The review owner line keeps the backlog clean

Action items arrive as drafts, and they become tasks only after a person chooses to accept them. That acceptance is a real decision. The review owner is the person who can say no, not the person who is too busy to say yes. A wrong draft gets rejected. A right draft gets assigned, given a due date, and linked to the project. The transcript, summary, and action items stay hidden unless the owner shares them or adds the meeting to a project.

The review owner should have a fixed time to clear the task drafts, not an open-ended promise. The fixed time should be in the invite, so the drafts do not become a recurring chore. A short window after the meeting is enough for a small team. Look at each draft, decide whether it is a task, and either accept it or delete it. Set a due date when the draft needs one. Add a project when the draft needs one. An ambiguous draft goes to the person who said it, not the whole team. The owner's job is to keep the queue small. A draft that is not a task should not sit in a queue waiting for someone else to notice.

For a small team, the invite is also the audit trail. When someone asks why a transcript was generated, the answer should be a line in the invite, not a memory. When someone asks why a task was created, the answer should be the review owner's acceptance, not a guess. The invite keeps the answer from becoming a debate after the team has moved on to the next meeting. The meter line shows the planned length and the person who checked the count, so a longer meeting is visible before it becomes an unowned follow-up.