Comments & Notes

Cothon offers two kinds of written collaboration: threaded comments on opportunities for team discussion, and notes and flags on individual requirements inside a bid analysis.

Opportunity comments

Every opportunity page has a comments section where your team can discuss pursuit strategy, assign context, and record decisions where the opportunity lives — instead of scattering them across email.

How they work

• Write a comment — post to the opportunity's discussion; it is visible to everyone who can access the opportunity
• Reply in a thread — respond to an existing comment to keep sub-discussions grouped under the original point
• Attribution and history — each comment shows its author and timestamp, and comment activity also appears in the opportunity's activity timeline

Access follows the opportunity: only users who can open the opportunity can read or write its comments.

Requirement notes and flags

Inside a bid analysis, each extracted requirement can carry your own annotations:

• Notes — free-text remarks attached to a specific requirement ("confirm certification with subcontractor", "pricing depends on volume tier"). A requirement can hold multiple notes; you can edit or delete them.
• Flags — mark a requirement as needing attention. Flagged requirements are visually highlighted so they stand out when you come back to the analysis.

Notes and flags are saved with the analysis, so they're there when you reopen it. Requirement cards show a note count and flag indicator, and the requirement drawer displays the full note text.

What commenting does not include

To keep expectations clear, Cothon's commenting is deliberately simple. There are no emoji reactions, no resolve/unresolve workflow, no @mention notifications, no file attachments on comments, and no comment analytics or exports. A comment is a plain, attributed, threaded message.

Good practices

• Record decisions as comments ("Decided to bid — see analysis v2") so the rationale survives team turnover
• Flag requirements during your first pass through an analysis, then work through the flagged list
• Keep notes factual and actionable — they are most useful when a teammate picks up the analysis after you

Next steps

• Activity & Audit Logs — see comment activity in each opportunity's timeline
• Sharing — the "can comment" permission level for shared analyses