# External Comment and Internal Note Routing

Prepare a review-comment destination map that keeps private team discussion out of client-visible comments.

## Scope
Preparation and review only. No account action or professional decision.

## Inputs
Comment drafts, membership export, post visibility, supplied audience restrictions and channel definitions.

## Workflow
1. Classify intended audience from the supplied restriction, not the tone of the note.
2. Map internal team discussion to documented internal-note scope.
3. Keep client-facing questions separate and mark unknown membership or visibility.
4. Return a routing draft for review; no comment is posted or copied.

## Output contract
note_id | intended_audience | membership_version | proposed_surface | restricted_text | hold

## Fictional acceptance test
Fictional N1 contains internal pricing negotiation; N2 asks a client to confirm a spelling. N1 is internal-only preparation, N2 can be proposed as an external comment. Neither is sent.

## Review gates
Keep original values, source IDs and version dates. Unknown facts stay held. Use qualified review for hiring, legal and accounting conclusions. No send, share, sign-in, scheduling, ledger change or payment. Fictional contract review is not a live account compatibility test.

## Method source
https://help.planable.io/hc/en-us/articles/21715398237212-Internal-external-collaboration

Checked October 10, 2026. Oct10 live AIS Search Console through Oct6: marketing Copilot 37 impressions, Planable/Claude 33, Planable/ChatGPT 23, campaign brief 12, investor agent 19. Social-review/reporting topics follow these parent-query leads. Other professions follow documented workflow needs, not measured exact search intent. Site impressions are not monthly volumes; exact topic volume is unmeasured.