Comments

Cothon's commenting system transforms bid analysis from isolated work into collaborative dialogue. Add inline comments on specific requirements, create threaded discussions, @mention teammates for input, track decisions, and systematically resolve feedback loops.

Unlike email threads that scatter across inboxes or chat messages that disappear in history, Cothon comments anchor discussions directly to the content they reference. Every comment creates a persistent, searchable, auditable record tied to its context - ensuring no feedback gets lost and all decisions are traceable.

Comment System Overview

Why Comments Matter for Bid Teams

Government procurement requires coordinated input from diverse stakeholders:

Technical SMEs assess feasibility and compliance Compliance officers verify regulatory adherence Pricing specialists validate cost assumptions Proposal managers orchestrate the overall response Executives provide strategic direction Partners contribute their portion of teaming bids

Comments enable asynchronous collaboration without the coordination overhead of meetings or the context loss of separate communication channels.

Comment Capabilities

Comment Locations

Comments can be added at multiple levels:

Analysis-Level Comments:

• General feedback on overall analysis
• Strategic questions about bid/no-bid
• Cross-cutting concerns spanning multiple requirements
• Access: Click Comments tab in right sidebar

Requirement-Level Comments:

• Specific to individual requirement
• Most common comment type
• Access: Click comment icon on requirement card

Section Comments (proposals):

• Comments on proposal sections
• Useful for narrative content review
• Access: Hover over section, click comment icon

Inline Text Comments (coming soon):

• Select specific text, add comment
• Precise feedback on exact phrasing
• Useful for compliance statement refinement

Adding Comments

Creating a New Comment

Keyboard Shortcut:

• Press to add comment on currently focused requirement
• Press to add analysis-level comment

Comment Formatting Best Practices

Be Specific:

❌ "This doesn't look right"
✅ "This compliance statement claims NIST 800-171 certification, but
   we're only pursuing certification (not yet certified). Change to
   'pursuing certification with expected completion Q3 2024.'"

Use @Mentions for Accountability:

@sarah Can you verify we have this certification? If not, please
update to reflect our current status by EOD Friday.

Structure Complex Feedback:

Three concerns with this technical approach:

1. **Timeline** - 6-month delivery seems aggressive given hardware lead times
2. **Resources** - Requires 3 FTEs but we only have 2 available
3. **Risk** - Dependency on vendor X who has had delivery issues

Recommendation: Extend timeline to 8 months or propose phased delivery.

Link to Supporting Evidence:

Our past performance on [Project XYZ](link-to-project) demonstrated
similar capability. Reference this in the proposal narrative.

Attached: Project XYZ final report (see pages 12-15 for relevant details)
[Attachment: ProjectXYZ_Final_Report.pdf]

Threaded Discussions

Build multi-turn conversations that preserve context:

Replying to Comments

Thread Visualization:

┌─────────────────────────────────────────────────┐
│ Sarah Johnson                      2 hours ago  │
│ [Question] Does our team have CMMC Level 2      │
│ certification for this requirement?             │
│                                                  │
│ ├─ John Smith                   1 hour ago      │
│ │  No, we're currently Level 1. Working toward  │
│ │  Level 2 certification (expected Q3 2024).    │
│ │                                                │
│ │  └─ Sarah Johnson              30 min ago     │
│ │     Thanks. I'll update requirement to reflect│
│ │     "pursuing Level 2" instead of "certified".│
│ │                                                │
│ └─ [RESOLVED by Sarah]                          │
└─────────────────────────────────────────────────┘

Thread Management

Collapsing/Expanding Threads:

• Long threads auto-collapse after 3 replies
• Click Show more to expand full thread
• Click Collapse to minimize (useful for resolved threads)

Thread Notifications:

• Participants: Auto-notified of new replies (you participated in thread)
• Watchers: Anyone who clicked "Watch thread" gets notified
• @Mentioned: Notified even if not previous participant

Thread-Level Actions:

• Watch thread: Receive notifications without commenting
• Mute thread: Stop notifications (useful for tangential discussions)
• Copy thread link: Share link to specific discussion
• Export thread: Save discussion as PDF or text

Threading Best Practices:

Keep threads focused:

❌ In 5-reply thread about technical approach, someone asks pricing question
✅ Reply: "Good question but different topic. Started new thread for pricing."

Summarize long threads:

After 10+ replies debating options:

"Summary of discussion:
- Option A: Faster but higher risk
- Option B: Slower but proven approach
- Decision: Going with Option B based on client's risk tolerance
- Action: @john update requirement to reflect Option B approach"

Use threads for decision documentation: Each major decision becomes searchable thread showing:

• What was considered (replies discuss options)
• Why decision was made (justification in replies)
• Who was involved (participant attribution)
• When it was decided (timestamps)

@Mentions and Notifications

Direct teammates' attention to specific comments:

Mentioning Team Members

Basic @Mention:

Example:

@sarah Please review this compliance statement and verify it aligns
with our ISO 27001 certification scope. Need this by EOD Friday for
final submission.

Sarah receives:

• In-app notification with comment preview
• Email with direct link to comment
• Slack DM (if integration enabled)
• Badge on bell icon

Mentioning Multiple Users:

@sarah @john @alice - All three of you reviewed similar requirement
in last RFP. Please weigh in on approach for this one.

Each user receives individual notification.

Mentioning Teams/Groups:

@technical-writers Please review all Section 3 requirements for
consistency and clarity by Monday.

All members of "technical-writers" team receive notification.

@Mention Advanced Features

Conditional @Mentions:

@sarah If you're the right person for this, great. If not, can you
redirect to appropriate SME?

Role-Based @Mentions:

@proposal-manager We need leadership decision on this approach before
proceeding.

Anyone with "proposal-manager" role receives notification.

@Here and @Channel (Team-wide):

@here Major change to Section 3 technical approach. All hands please
review and flag concerns by EOD today.

Notifies all users currently viewing the analysis (active collaborators).

@Mention in Code Blocks: For technical discussions:

@john The API endpoint should be:

`POST /api/v1/bid-analysis`

Not the current implementation. Can you update?

Managing @Mention Notifications

If you receive too many @mentions:

1. Adjust notification preferences:

   • Settings > Notifications > @Mentions
   • Change from "Instant" to "Hourly digest"
   • Group related @mentions into single notification

2. Delegate @mentions:

   • If @mentioned but not right person, reply: "@original-author I'm not best person for this. @jane is our expert on this topic."

3. Set "mention hours":

   • Settings > Notifications > Active Hours
   • @Mentions outside your active hours queue until your next work session
   • Prevents off-hours pings

4. Mute non-critical analyses:

   • Right-click analysis > Notification Settings > @Mentions only if urgent

If your @mentions are being ignored:

1. Follow up with direct communication:

   • Slack DM: "Hey, did you see my comment on RFP-123?"

2. Check their notification settings:

   • They may have disabled @mention notifications
   • Escalate to proposal manager if critical

3. Add deadline context:

   @sarah [URGENT] Need your input by 2pm today for submission.
   Please reply to confirm you've seen this.
   

4. Escalate via comment type:

   • Change comment type to "Concern" or "Blocker"
   • Creates higher-priority notification

Comment Types and Categories

Organize discussions by categorizing comments:

Comment Type System

Question 🤔:

• Purpose: Seek clarification or information
• Icon: Question mark badge
• Color: Blue
• Example: "Does our team have the required security clearances for this contract?"
• Resolution: Mark resolved when answered

Suggestion 💡:

• Purpose: Propose improvements or alternatives
• Icon: Lightbulb badge
• Color: Yellow
• Example: "Consider adding our recent NASA project as relevant past performance"
• Resolution: Mark resolved when accepted/rejected

Concern ⚠️:

• Purpose: Identify risks, issues, or problems
• Icon: Warning badge
• Color: Orange
• Example: "This delivery timeline seems aggressive given hardware procurement lead times"
• Resolution: Mark resolved when concern is addressed or mitigated

Approval ✅:

• Purpose: Signoff or endorsement
• Icon: Checkmark badge
• Color: Green
• Example: "Compliance review complete. This section meets all FAR requirements."
• Resolution: Approvals don't need resolution (they ARE the resolution)

General 💬:

• Purpose: Standard comment not fitting other categories
• Icon: Chat bubble
• Color: Gray
• Example: "This is great work. No changes needed."
• Resolution: Optional

Using Comment Types Strategically

Pre-Submission Quality Gate:

Example Workflow:

Day 1-3: Drafting phase
  → No comment type requirements

Day 4-6: Peer review phase
  → Team adds Questions, Suggestions, Concerns

Day 7-8: Resolution phase
  → Authors address all Questions and Concerns
  → Accept/reject Suggestions

Day 9: Leadership review
  → Compliance officer adds Approval comments on each section
  → Technical director adds Approval on technical approach
  → Proposal manager adds Approval on overall bid

Day 10: Final check
  → Filter: Type: Concern, Status: Unresolved → Must be 0
  → Filter: Type: Question, Status: Unresolved → Must be 0
  → Filter: Type: Approval, Section: All critical sections → Must have all required signoffs

Day 11: Submit

Custom Comment Categories

Beyond standard types, add custom tags:

Technical Tags:

• #architecture - System design discussions
• #security - Security-related feedback
• #performance - Performance requirement discussions

Process Tags:

• #red-team - Red team review feedback
• #pink-team - Pink team review feedback
• #gold-team - Final gold team review

Priority Tags:

• #critical - Must address before submission
• #nice-to-have - Improve if time permits
• #post-submit - Enhancement for recompete

How to Use:

1. Add tags in comment: "This architecture seems overly complex #architecture #critical"
2. Filter comments by tag: Comments panel > Filter > Tags > Select #critical
3. View all critical items across entire analysis

Resolving Comments

Track feedback closure systematically:

Resolution Workflow

Resolution States

Who Can Resolve Comments

Permission levels for resolution:

Rationale: Prevents premature closure by reviewers. Only people with edit permissions (who can actually address feedback) can mark resolved.

Resolution Best Practices

Always Explain Resolution:

❌ [Click Resolve button, no explanation]

✅ "Resolved: Updated timeline from 6 months to 8 months per your
    suggestion. See revised Gantt chart in updated Section 4."

Tag Resolver (optional courtesy):

@sarah Resolved your compliance concern by adding reference to our
ISO 27001 certification (Attachment: ISO27001_Cert.pdf). Please
confirm this addresses your feedback.

Sarah receives notification of resolution and can verify.

Batch Resolve Related Comments: If 5 comments all about same issue, resolve with explanation:

Resolved comments #12, #15, #18, #22, #29 - All concerned about
missing past performance reference. Added Project XYZ to Section 5
with detailed performance summary.

Document Non-Changes:

Suggestion: Add more detail to security architecture

Resolution: Reviewed with technical team. Current level of detail is
appropriate for proposal (detailed design occurs post-award per RFP
Section 7.3). Not implementing this suggestion but appreciate the input.

[Mark as Declined]

Transparency on why suggestions weren't implemented prevents re-raising.

Comment Reactions

Quick responses without full replies:

Using Reactions

Add emoji reactions to comments:

Available Reactions:

• 👍 Agree - Endorse comment or suggestion
• ❤️ Appreciate - Thank commenter for input
• 😂 Lighthearted - Friendly acknowledgment
• 🎉 Celebrate - Exciting milestone or great idea
• 🤔 Thinking - Considering the point, need more time
• ❓ Confused - Don't understand, need clarification
• 👀 Noted - Saw it, will respond later
• ⚠️ Important - Elevate priority of comment

When to Use Reactions vs. Replies:

Use Reactions For:

• Simple acknowledgment: 👍 instead of "Agreed"
• Quick thanks: ❤️ instead of "Thanks for catching this"
• Voting on suggestions: 👍 vs. 👎 on proposed approaches
• Indicating you've seen urgent comment: 👀

Use Replies For:

• Providing detail or explanation
• Asking follow-up questions
• Documenting decisions
• Anything requiring audit trail

Reaction Analytics

View reaction patterns:

Comment-Level:

• See who reacted with what emoji
• Hover over reaction count: "👍 5 (Sarah, John, Alice, +2 more)"

Analysis-Level:

• Comments tab > Analytics > Reactions
• See most-reacted comments (indicates important feedback)
• Reaction velocity (fast reactions = high engagement)

Use Cases:

• Identify high-impact comments (many 👍 reactions = broad agreement)
• Gauge consensus on controversial topics
• Measure team engagement (high reaction counts = active participation)

Comment Permissions and Privacy

Control who can comment and what they see:

Permission Levels

Edit Window:

• Commenters: 5 minutes to edit/delete after posting
• Editors: 30 minutes to edit/delete
• Managers/Admins: Unlimited edit/delete capability

Rationale: Prevents abuse (rewriting history after others replied), but allows quick typo fixes.

Comment Visibility

Who Sees Comments:

• All users with access to the underlying content can see comments
• Comments inherit permissions of parent analysis/requirement
• No "private comments" (transparency principle)

Exception - Direct Messages (coming soon):

• @Mention user in comment and toggle "Direct Message" mode
• Only mentioned user and comment author can see
• Useful for sensitive feedback or personnel matters

External User Comments:

• Users accessing via public links can comment (if link permission = Comment or Edit)
• Comments attributed to "External User (email)" if email collected
• Otherwise attributed to "Anonymous via Link [ID]"
• Organization members can identify external comments via badge

Moderating Comments

Managers and admins can moderate:

Edit Others' Comments:

• Click ⋮ More on comment > Edit
• Use sparingly (generally for typos, formatting, or removing sensitive info)
• Edit history preserved: "Edited by [Manager] on [timestamp]"

Delete Comments:

• Click ⋮ More > Delete
• Requires confirmation
• Soft delete: Comment marked deleted but preserved in audit log
• Deletion reason required (appears in log)

Hide Comments (spam/off-topic):

• Click ⋮ More > Hide
• Comment hidden from view but not deleted
• Can be unhidden if mistakenly hidden

When to Moderate:

• Inappropriate content (profanity, harassment)
• Spam or off-topic discussions
• Sensitive information accidentally posted
• Duplicate comments
• Test comments

Moderation Audit Trail: All moderation actions logged:

• Settings > Comments > Moderation Log
• See all edits, deletions, hides with moderator attribution
• Supports compliance with governance policies

Comment Search and Filtering

Find specific discussions across thousands of comments:

Comment Search

Search Syntax:

• Keyword search: compliance - finds "compliance", "compliant", etc.
• Phrase search: "past performance" - exact phrase match
• User search: @sarah or user:sarah - comments by Sarah
• Type search: type:concern - all concern-type comments
• Status search: status:unresolved - open comments only
• Tag search: #critical - comments tagged critical
• Date search: after:2024-03-15 - comments since March 15

Example Queries:

# Find unresolved concerns by Sarah
user:sarah AND type:concern AND status:unresolved

# Find all compliance-related discussions
compliance OR regulatory OR "FAR clause"

# Find comments from last week with critical tag
after:2024-03-15 AND #critical

# Find comments with attachments
has:attachment

Comment Filtering

Apply filters without search:

Filter Dropdown Options:

• Status: Open, Resolved, All
• Type: Question, Suggestion, Concern, Approval, General
• Author: Specific users or teams
• Date: Today, This Week, This Month, Custom Range
• Tags: Any configured tags
• Mentions: Comments @mentioning me
• Assigned: Comments where I was assigned follow-up action

Common Filter Combinations:

Saving Filters:

1. Apply desired filters
2. Click ⋮ More > Save Filter Preset
3. Name it (e.g., "My Open Action Items")
4. Access later from Quick Filters dropdown

Comment Sorting

Order comments by different criteria:

Sort Options:

• Newest First (default) - Most recent comments at top
• Oldest First - Chronological from earliest
• Most Replies - Longest threads first (active discussions)
• Unresolved First - Open comments before resolved
• By Priority - Critical concerns at top
• By Requirement Order - Grouped by requirement sequence

Use Cases:

• Newest First: Daily review of new feedback
• Unresolved First: Pre-submission checklist (clear all open items)
• Most Replies: Identify complex discussions needing attention
• By Requirement Order: Systematic section-by-section review

Advanced Comment Features

Comment Templates

Create reusable comment patterns:

Creating Template:

Using Templates:

1. Start typing comment
2. Type / to open template menu
3. Select template
4. Fill in placeholders
5. Post comment

Common Templates:

• Red Team Review: Structured feedback format for red team reviews
• Technical Approach Feedback: Standard questions for technical sections
• Pricing Review Checklist: Ensure all cost elements validated
• Executive Signoff: Approval format for leadership endorsement

Comment Assignments

Assign follow-up actions to team members:

Creating Assignment from Comment:

Assignment Tracking:

• Assignee sees assignment in their My Work dashboard
• Original comment shows "Assigned to [User]" badge
• Deadline countdown visible on comment
• Overdue assignments highlighted red

Completing Assignments:

1. Assignee addresses the comment (researches answer, makes edit, etc.)
2. Reply to comment with resolution
3. Click Mark Assignment Complete
4. Assignment removed from active list, comment typically resolved

Value: Ensures comments don't get lost. Every piece of feedback that needs action has explicit owner and deadline.

Comment Linking

Reference comments from other locations:

Copying Comment Links:

1. Hover over comment
2. Click ⋮ More > Copy Link
3. Share link via any channel (Slack, email, other comments)

Linking Format:

https://app.cothon.ai/analyses/abc123/comments/comment456

Clicking link jumps directly to that comment in context.

Cross-Referencing Comments: In comment text, reference other comments:

This concern is related to the discussion in requirement #23
[see comment](link-to-comment). Same underlying issue.

Use Cases:

• Reference earlier decision in new comment
• Link related discussions across requirements
• Share specific feedback with external stakeholders
• Document decision trail (link chain of comments leading to decision)

Comment Export

Extract comments for external use:

Export Options:

1. Export All Comments - Entire comment thread for analysis
2. Export Filtered Comments - Only comments matching current filters
3. Export Single Thread - Specific comment and all replies

Export Formats:

• PDF - Formatted document with timestamps, authors, threading
• Excel - Spreadsheet with columns: Date, Author, Type, Comment, Status, Requirement
• JSON - Structured data for programmatic processing
• Markdown - Plain text with threading structure

How to Export:

Use Cases:

• Compliance audits: Export all comments as audit trail
• Lessons learned: Export post-submission for debrief
• Reporting to leadership: Export approval comments showing signoffs
• External sharing: Export comment summary to send to client or partner

Comment Analytics

Measure collaboration health through comment metrics:

Comment Dashboard

Access comment analytics:

Navigate to: Analysis > Comments tab > Analytics

Metrics Displayed:

Volume Metrics:

• Total comments
• Comments per day/week
• Comment growth trend
• Comments per requirement (average and distribution)

Engagement Metrics:

• Unique commenters
• Comments per user (identify top contributors)
• Reply rate (% of comments that receive replies)
• Average thread length
• Reaction count and breakdown

Resolution Metrics:

• Open vs. Resolved ratio
• Average time to resolution
• Resolution rate over time
• Unresolved by type (how many open questions vs. concerns)

Quality Metrics:

• Average comment length (longer = more detailed feedback)
• Comments with attachments (evidence-backed feedback)
• @Mention usage (direct accountability)
• Tag diversity (broad discussion topics)

Visualizations:

• Comment Timeline: Daily comment activity over analysis lifecycle
• Contributor Breakdown: Pie chart of comment % by user
• Resolution Funnel: Open → In Progress → Resolved flow
• Type Distribution: Bar chart of comment types
• Heat Map: Which requirements receive most comments

Using Analytics for Process Improvement

Scenario 1: Low Engagement:

Metrics Show: 50 requirements, only 15 comments, all from proposal manager

Problem: Team not providing feedback

Actions:
- Explicitly assign review sections to team members
- Set expectation: "Each reviewer should add minimum 3 comments"
- Make commenting part of review workflow (can't mark section reviewed without commenting)
- Recognize top commenters in team meeting

Scenario 2: Unresolved Comment Buildup:

Metrics Show: 45 open comments, average age 6 days, submission in 2 days

Problem: Feedback not being addressed

Actions:
- Filter to Unresolved + Concern type
- Triage: Which must be addressed vs. nice-to-have
- Assign owners to each critical comment with 24h deadline
- Daily stand-up to review resolution progress

Scenario 3: Noisy Collaboration:

Metrics Show: 300 comments on 30 requirements, many short comments

Problem: Over-commenting, hard to find signal in noise

Actions:
- Encourage longer, more thoughtful comments vs. many short ones
- Use reactions instead of "+1" comments
- Create comment guidelines: "Combine related feedback into single comment"
- Use comment types to categorize (easier filtering)

Scenario 4: Siloed Discussions:

Metrics Show: 10 users, but comment threads only involve same 2-3 people

Problem: Experts not being pulled into relevant discussions

Actions:
- Encourage @mentions to bring in right expertise
- Assign SMEs to watch specific requirement categories
- Cross-pollinate: Share interesting comment threads in team channel
- Rotate review assignments to expose team to broader content

Benchmarking Collaboration

Healthy Collaboration Indicators:

Industry Benchmarks (based on Cothon data across customers):

Government RFP Response (50+ requirements, 5-10 person team):

• Average: 120 comments total
• 70% resolved by submission
• 8 unique commenters
• 3.2 comments per requirement
• 36 hour average resolution time

Small Bid (10-20 requirements, 2-3 person team):

• Average: 25 comments total
• 85% resolved by submission
• 2-3 unique commenters
• 1.8 comments per requirement
• 18 hour average resolution time

Compare your analysis metrics to these benchmarks to gauge collaboration health.

Troubleshooting

Comments Not Syncing

Symptoms: You add comment but others don't see it, or delay in seeing others' comments.

Solutions:

Missing Notifications for @Mentions

Symptoms: Not receiving notifications when @mentioned.

Diagnostics:

Testing: Ask teammate to @mention you in test comment. If you receive notification, settings are correct and previous issue was likely edge case.

Can't Resolve Comment

Symptoms: Resolve button grayed out or missing.

Causes:

• Insufficient permissions: Need Editor permission on that section or Manager role
• Not comment owner: Only comment author or content editors can resolve
• Already resolved: Comment may already be marked resolved (expand to check)

Workarounds:

• If you addressed comment but can't resolve, reply: "@author I've addressed this. Can you please mark resolved?"
• Request permission upgrade from proposal manager
• Ask manager to resolve on your behalf

Comment Thread Too Long

Symptoms: Thread has 20+ replies, hard to follow discussion.

Solutions:

1. Summarize thread: Add comment: "Summary of long discussion: [bullet points]"
2. Split thread: If discussion diverged, start new thread for new topic
3. Move to document: For very complex discussions, create separate document or hold meeting, then summarize decision in comment
4. Use thread collapse: Minimize resolved portions to focus on active discussion

FAQ

Next Steps

Master Related Features

• Real-time Editing - See how comments integrate with live editing
• Activity Feed - Track comment activity across all analyses
• Notifications - Configure comment notification preferences

Related Topics

• Workflow Management - Convert comments to formal workflow tasks
• Team Management - Set up teams for @mentions
• Compliance - Use comment audit trail for compliance

Quick Wins

First Time Using Comments? Try this with a teammate:

1. Both open same analysis
2. You add comment on a requirement
3. Teammate receives notification, replies
4. You react with 👍, then mark resolved
5. Check activity feed to see full interaction trail

Advanced Practice:

1. Create comment template for your review process
2. Use comment types to categorize a full analysis review
3. Filter to "Unresolved Concerns" and systematically address each
4. @Mention 3+ people in single comment and track responses
5. Export comment thread to PDF for stakeholder sharing

Mastering comments transforms scattered feedback into structured, traceable collaboration. Your bid quality improves when all stakeholder input is captured, discussed, and systematically resolved.