Check who can see the post before you publish it

Choose the smallest appropriate audience for the task

A public lesson, a private thank-you and a team update have different recipients. Decide the purpose before choosing an interface option. If only one person needs the detail, a public recap may be an unnecessary distribution path. No audience setting makes an unsuitable disclosure appropriate.

Fictional task: explain a lesson from an onboarding mistake without revealing an unreleased customer arrangement. The lesson can be public after removing identifying details; the arrangement does not become shareable because your direct connections are the selected audience.

Read the selected option literally

LinkedIn’s visibility help distinguishes Anyone, Connections only and Group. Anyone can reach people on or off LinkedIn; Connections only refers to first-degree connections; Group refers to the group where the item is shared. A follower is not necessarily a first-degree connection.

The help says your chosen visibility becomes a default for a later post. Inspect the current selection instead of relying on memory. A screenshot of yesterday’s audience does not establish the audience of today’s prepared item.

Inspect what will travel with the text

Read the caption and every attachment together. Names can remain in chart labels, slide footers, screenshots and filenames even after the opening paragraph is generalized. Use a clean appropriate source, inspect the final export and omit details that depend on staying hidden inside one interface.

A smaller chosen audience is still an audience. Recipients can retain copies. The checklist asks you to inspect the actual file rather than marking a generic privacy box. This is a practical review workflow, not legal advice or a confidentiality certification.

Recheck drafts and queued items in their own state

A draft is an opportunity to correct the selection before publication. Current post-draft help notes that changing visibility requires re-uploading attachments. Recheck the actual attached version after that change, not only the text.

For a scheduled item, inspect its selected audience in the queued post. The visibility help says scheduling uses the choice made when the post was created. A later composer default is not evidence that an existing queued item changed. Do not create a test publication merely to inspect this workflow.

1. Confirm publishing account, post type and intended recipients.
2. Read the current audience label before the final action.
3. Inspect text, all media and identifying details for that audience.
4. After any draft change, verify the actual attachments and queued item if applicable.
5. If you publish, inspect the original result and record its actual state.

Handle a wrong audience without pretending an edit recalls it

The published-visibility help says the audience option cannot be changed after sharing. If an inappropriate item is already live, assess the exposure and the available removal/replacement decision. Editing text is not a general fix for the audience or a sensitive PDF.

For the fictional onboarding example, do not merely change the opening sentence while leaving the unreleased customer name in a slide. Address the exposed file. If a replacement is appropriate, review the clean asset and audience before publishing it; a prepared replacement is not already public.

Keep a short record of the decision

Use the localized audience checklist to record the intended recipients, selected native label, actual asset version and status. Add a public URL only after a real publication. Keep any sensitive incident details in suitable private storage.

The useful outcome is a deliberate decision and checked state, which may be to keep the post unpublished. This worksheet changes no settings and sends nothing. It cannot guarantee who ultimately sees a copied asset or remove copies someone already retained.