# Choose a LinkedIn recap tool by its data, period and actual output

Original constructed exercises. No real account data, study participants or customer outcomes. The two expanded comparisons retain six earlier cases in total; those are not new cases.

## Run three complete choices through the worksheet

Case A needs private impression totals but allows neither an account connection nor an analytics export. None of these documented third-party routes is proven to meet that contract. Stop with an unresolved requirement rather than choosing the prettiest public-profile poster. The user may need to inspect native analytics or explicitly revise the acceptable-source condition.

Case B needs private metrics, accepts an English export and does not want a persistent app connection. Oiti’s documented file path is a candidate, conditional on the workbook’s dates, fields and handling meeting the task. Case C needs a public-supporter story as a PDF or GIF, accepts the collection limits and a quoted one-time payment. Wrapped.li is a candidate after checking the selected edition and format. Neither example is a measured customer outcome or a claim of universal preference.

## Resolve three output and coverage failures

D1 — Constructed partial-year case: a source ending on 31 October is labeled “the complete 2026 year.” Outcome: hold that claim or relabel it with the actual start/end and sample boundary. A 2026 product title does not fill November and December. If the source is a rolling 365-day window, inspect its start date as well; neither label automatically equals January–December.

D2 — Constructed wrong-output case: the task requires a shareable PDF of the specific recap, but the documented surface offers PNG and a separate dashboard PDF. Outcome: the required download stays unknown or unmet. Inspect the correct output and period before paying; a PDF elsewhere in the product is not acceptance evidence for this recap.

D3 — Constructed access constraint: private impressions are mandatory, a persistent connection is declined and an authorized English analytics file is available. A documented file-based route is a candidate if its fields, dates and processing fit. Outcome: check the actual accepted file and required artifact; keep missing fields unknown. If no acceptable source can supply the metric, stop instead of calling a public-profile poster equivalent.