Choose a posting window your audience and calendar can support

Name the audience, task and evidence first

For this constructed plan, a Berlin-based writer wants an explanation to be usable by colleagues in Berlin and New York. Those locations are a planning assumption, not inferred private analytics. The useful response is a relevant question about the explanation; impressions remain a separate exposure measure. The writer has at most 20 minutes for the planned reply session.

If you do not know audience locations or working patterns, say so and choose a feasible starting hypothesis. Do not manufacture a precise audience country split, infer a person’s routine from their profile, or delay a time-sensitive update merely to match a broad benchmark. The schedule must also leave you able to respond appropriately.

Write two actual candidates, not “9 am everywhere”

Candidate A is 09:00 in Europe/Berlin; candidate B is 16:00 in that zone. On October 21, 2026, A corresponds to 03:00 in America/New_York, while B corresponds to 10:00. This makes B a plausible overlap hypothesis, not evidence that the audience is online or that B will perform better.

The same 16:00 Berlin slot maps differently around the countries’ clock changes. Preserve the date, named zones and resolved UTC instant together. The rows below are reproduced timezone calculations with constructed plans, not observed LinkedIn results. Recheck future dates against current timezone rules and the actual scheduler preview.

Hold an ambiguous or nonexistent local time

A source saying only “October 25, 2026, 02:30 Berlin” is ambiguous during the repeated hour. The instants 00:30Z and 01:30Z both display 02:30 locally, with different offsets. Require the intended offset or an already resolved instant rather than silently picking one. Similarly, a local time skipped by a spring transition needs correction, not a made-up Z suffix.

A planner preview is a separate check after conversion. Confirm the target account, date and displayed local time before a real scheduled post is saved. The downloadable example does not schedule anything or connect to LinkedIn. If the account shows a different zone, reconcile it first; successful arithmetic does not establish an actual scheduled state.

Fix the observation rule before comparing

For the example, plan three observations per candidate, all reviewed after 168 elapsed hours. Keep topic family, medium, intended audience and distribution notes alongside the date. Rotate or randomize assignment where feasible, and record exceptions. Random assignment requires assigning conditions to actual experimental units; merely alternating attractive topics and hours is not a controlled timing experiment.

Predeclare what counts as a relevant question and how effort is measured. Keep unavailable metrics unknown, distinguish impressions from distinct members reached, and retain unsuccessful observations. If a key observation is missing or ages differ, hold the decision under the original rule or explicitly report a changed protocol; do not quietly delete inconvenient rows.

Use the worked comparison without claiming a winner

W1 — The six fictional observations give A impression counts 1,200, 800 and 1,000; B gives 900, 1,100 and 1,400. The medians are 1,000 and 1,100, a descriptive 10% difference. A’s reply-session minutes are 18, 20 and 19; B’s are 24, 22 and 23, giving medians 19 and 23. Each group has one observed relevant question in this constructed ledger. These are made-up teaching rows, not measured readers or platform research.

Under the predeclared 20-minute effort ceiling, B fails the median-effort condition despite its higher impression median. Decision: keep A as the feasible starting window and retain B as an unresolved exposure hypothesis. Safe wording: “In this constructed comparison B had a higher impression median but exceeded the planned reply effort.” It does not show that A or B causes greater reach, comprehension or revenue.

W2 — If B’s last count is unavailable, the original complete-three-per-group condition is unmet. Record the missing observation and hold the comparison rather than importing 1,400 from W1, filling zero or reporting the best partial result. W3 — If the source supplies only the repeated 02:30 Berlin time, hold scheduling until the intended instant is confirmed. Both holds belong in the same decision record as successful checks.

Save a decision and a review point

The private worksheet separates audience assumptions, candidate local times/zones, resolved instants, reply availability, assignment rule, equal-age measurements, exceptions and the final proceed/hold decision. Keep real post URLs and any sensitive notes private. Optional fixed-fixture reproduction checks the listed arithmetic and timezone conversions; it does not discover an audience’s ideal posting time.

Choose the next review after enough planned comparable observations, not immediately after one unusually large post. If audience, account, distribution or timezone rules change, note the new context and restart the relevant part of the plan. Leave the old rows intact. This workflow supplies a practical bounded decision, not a replacement population benchmark.