# Use comments to improve a playbook

Comment on a playbook entry or on the whole playbook when the guidance needs to change, reply to add context, and work through the comments so the playbook keeps pace with how your team negotiates.

Comments are how those who run reviews feed their experience back into a playbook. Any person with access to a playbook can add a comment to an entry, or to the entire playbook, and those responsible for the playbook can then take those comments into consideration when deciding what to change.

Comments allow teams to keep their playbooks really aligned with the team's negotiation preferences, whilst maintaining internal playbook governance structures.

## Watch the walkthrough

Video: [How to use the new Playbook Comments Feature](https://video.draftpilot.ai/s/s4rdfm5pf7vxk2t)

Chapters:

- [00:00 Intro to comment feature](https://video.draftpilot.ai/s/s4rdfm5pf7vxk2t?t=0)
- [00:24 Viewing comment overview and navigation](https://video.draftpilot.ai/s/s4rdfm5pf7vxk2t?t=24)
- [00:47 Adding, replying, and managing comments](https://video.draftpilot.ai/s/s4rdfm5pf7vxk2t?t=47)
- [01:25 Editing, AI suggestions, and exporting comments](https://video.draftpilot.ai/s/s4rdfm5pf7vxk2t?t=85)

If the player does not load in your browser, [open the video on Cap](https://video.draftpilot.ai/s/s4rdfm5pf7vxk2t) instead.

## Add a comment

Anyone with access to a playbook can comment on a single entry, or on the playbook as a whole. Only people with edit access can action a comment.

To comment on a particular entry:

1. Open the playbook.
2. Go to the entry the comment relates to.
3. Write your comment.
4. Save it.

To comment on the whole playbook, select the three dots next to the playbook and choose Comments.

The comment is most useful when it says what the playbook should say instead and why, together with the context a playbook owner would need to judge the point. A reviewer who finds that an issue needs a further fallback or an escalation can say so in the comment while working through the contract.

Comments stay with the playbook. They are visible to the people who work on that playbook, and they do not appear in the contract you are reviewing.

## Reply to a comment

A reviewer can reply to an existing comment to add further context, answer a question or explain a suggestion in more detail. A playbook owner can reply to ask for more context. Replies stay with the original comment, so the discussion about a possible change is kept in one place and the person actioning the comment can read the whole exchange.

## Updating the playbook

The comment bubble at the top of the playbook shows how many comments it has. Select it to see open comments, resolved comments, and to add a comment about the playbook as a whole.

An entry that has attracted comments shows a comment bubble against the relevant issue. Open the entry and scroll to the comments to read the feedback and any replies.

Reviewing comments is how a playbook owner keeps a playbook current:

1. Read the comment and reply if you need more detail.
2. If you have enough information, decide whether the playbook should change.
3. Update the playbook: edit the entry itself, or [open Refine Playbook](/knowledge-base/how-do-i-edit-a-playbook#refine-a-playbook-with-ai-chat) and ask the Refiner to consider the comments and update the playbook accordingly.
4. Resolve the comments once they are actioned and the playbook reflects the decision.

The Refiner may suggest changes to more than one entry. Apply them one at a time or all together.

DraftPilot does not decide whether a comment should change the playbook. That decision stays with your team.

## Export the comments

Export all comments to a word table for a clear view of each suggestion and its status. This can be helpful when you need feedback from a wider team who do not work with that playbook or want to review the full record of the discussion behind an update.

## Related guides

- [Edit and refine a playbook](/knowledge-base/how-do-i-edit-a-playbook)
- [How to add internal notes and traditional playbook content using Team Notes](/knowledge-base/how-to-add-internal-notes-and-traditional-playbook-content-using-team-notes)
- [Use the Usage page and track escalations](/knowledge-base/use-the-usage-page-and-track-escalations)
