How can I adapt the same message for a public post and a private note while keeping the facts consistent?

Treat them as two versions of one message, not as copies. First write a small “fact core”: the confirmed event or change, relevant dates or limits, and what readers should do next. Keep those claims stable. Then adapt the tone, word choice, and detail for each audience. Audience expectations can affect tone, mood, diction, and style [S1].

For example, assume you are announcing a community room’s changed opening time. The shared fact core might be: “Starting [date], the room opens at [time].” A public post could say, “From [date], the community room opens at [time]. Please check the posted schedule before visiting.” A private note to a regular visitor could be warmer: “Hi [name], I wanted to let you know the room will open at [time] starting [date].” These placeholders illustrate the approach, not a real venue.

Compare claims, not sentences. List each factual statement and check whether it appears in both drafts with the same meaning. Pay attention to names, dates, quantities, conditions, certainty, and promises. For example, “opens at [time]” should not quietly become “opens around [time],” and “starting [date]” should not become “already open.”

Use this worksheet:

• Main confirmed update: Public [ ] / Private [ ] / Same meaning? [ ]
• Date, number, or condition: Public [ ] / Private [ ] / Same meaning? [ ]
• What is uncertain: Public [ ] / Private [ ] / Same meaning? [ ]
• Reader’s next step: Public [ ] / Private [ ] / Same meaning? [ ]
• Personal context included: Public [ ] / Private [ ] / Appropriate? [ ]

This is an editorial consistency check; the audience-and-tone guidance supports adapting presentation, not a specific rule for factual consistency [S1].

Not automatically. Separate information the public needs to understand the update from context that is personal, identifying, or relevant only to the recipient. Ask whether the public needs it, whether the person would expect it to be shared, and whether the post works without it. If information concerns someone else, do not assume your own consent represents theirs: the W3C privacy principles note that one person’s consent to sharing information about a group does not mean others have consented [S2].

The W3C source addresses privacy and data handling, not a universal writing rule requiring permission for every mention. It supports considering context and people’s preferences rather than assuming every detail belongs in public [S2]. When a sensitive detail is not clearly appropriate to share, leave it out or ask the person through an appropriate channel.

Try this sequence:

1. Write the fact core in plain language. Mark anything unconfirmed as unknown or pending rather than guessing.
2. Draft the public version for readers who need the update and next step. Draft the private version for its recipient, adding only useful context.
3. Compare claims side by side. Keep dates, quantities, conditions, and certainty aligned. If you cannot support a claim, remove it or verify it before using it.
4. Review the public version for personal or identifying details. Consider context and the preferences of the people concerned [S2].
5. Read each draft as its intended audience. Adjust tone and detail without changing shared claims [S1].

The comparison can help catch mismatches, but it cannot prove an underlying claim is true. Check the original record or the person responsible for confirming it.