# Worked fictional prelaunch brief: Alder Operations All names, IDs, dates, budgets, and receipt descriptions below are fictional. They demonstrate a complete proposed plan, not a real account check. No study has been created or launched. Replace simulated evidence with inspectable native records before using this as a real plan. ## The decision - Company and product: Alder Operations; workflow software - Business question: Does this campaign change product consideration among the studied audience? - Decision this study will inform: Whether to plan a further consideration-message test - Why a survey-based brand metric addresses that decision: The question directly measures stated consideration of the product - What revenue or conversion question must be measured separately: Incremental purchases and revenue require separate measurement - Record preparer and date: Maya, November 1, 2026 at 12:00 UTC - Budget owner: Jordan - Campaign operator: Lee - Results reviewer: Sam ## Proposed study - Account name and ID: Alder Operations; ALDER-01 - Study name and ID (Unknown before creation): Alder November consideration; Unknown before creation - Account-level or selected-campaign scope: Selected-campaign scope - Selected campaign IDs, or account-wide scope: ALDER-CONSIDER-01 - Included ad formats and placements: Standard Sponsored Content; LinkedIn feed only; no CTV - Countries and survey language: United States; English - Brand name as it will appear: Alder Operations - Number of questions: One - Exact question type and question text for each question: Product consideration: How likely are you to consider Alder Operations? Illustrative wording; the real operator must copy the exact native question - Desired and undesired answer options for each question: Desired: Highly likely, Somewhat likely. Undesired: Neutral, Somewhat unlikely, Highly unlikely. Illustrative options - Benchmark region and industry, if applicable: United States; Software - Campaign and study start/end dates, with UTC study boundaries: Campaign and study proposed November 2, 2026 at 00:00 UTC through December 1, 2026 at 23:59 UTC - Planned final review timestamp in UTC, after the full 15-day period following the scheduled study end has passed: December 17, 2026 at 09:00 UTC ## Eligibility and approval - Current official requirements URL and checked date: https://www.linkedin.com/help/lms/answer/a461474/create-a-brand-lift-test?lang=en; October 30, 2026 - Currency: USD - Cumulative eligible campaign/ad-set budget during the study: 65,000 - Budget source capture and timestamp: Simulated SETTINGS-AL-01, November 1 at 10:00 UTC; eligible planned campaign budget, not actual spend - Native eligibility result and evidence: Simulated ELIGIBILITY-AL-01, November 1 at 10:05 UTC: eligible for one question - Operator access level and evidence: Simulated ACCESS-AL-01: Lee has campaign-manager access, checked November 1 at 10:10 UTC - Budget-owner decision and evidence: Simulated PLAN-AL-01: Jordan approves preparing this exact plan; November 1 at 11:00 UTC - Explicit launch/change authorization and evidence: Absent. Planning approval does not authorize launch or a budget change - Native study state and captured timestamp: Not created; simulated inventory checked November 1 at 10:15 UTC - Concurrent-test or format restrictions checked, source, and result: Simulated INVENTORY-AL-01 records no concurrent tests, no CTV, and supported selected campaign; real operator must check current native restrictions - Open requirements, responsible person, and next action: Jordan reviews the exact proposed setup for launch approval; Lee records ID and state only after authorized creation Budget eligibility does not establish approval, launch, delivery, or conclusive results. Record each separately. Use the current native account check for non-USD eligibility; do not invent an exchange rate. ## Readout for each question Complete the result fields after results exist. For a prelaunch plan, retain the proposed schedule and question definition, label them proposed, and leave unobserved results Unknown. - Study ID and native export/capture: Unknown; no postlaunch results exist. - Report retrieved at: Unknown; no postlaunch results exist. - Scheduled study end: Proposed December 1, 2026 at 23:59 UTC; no created study or native report confirms this schedule yet. - Final review date reached: No; proposed final review is December 17, 2026 at 09:00 UTC - Native reporting framework: Bayesian / legacy / Unknown, with evidence: Unknown; no postlaunch results exist. - Question and desired-response definition: Proposed product-consideration question and desired answers as recorded above; no native report confirms them yet. - Test-group total, desired, and undesired response counts: Unknown; no postlaunch results exist. - Control-group total, desired, and undesired response counts: Unknown; no postlaunch results exist. - Displayed desired-response percentage, test group: Unknown; no postlaunch results exist. - Displayed desired-response percentage, control group: Unknown; no postlaunch results exist. - Native absolute lift, with percentage-point unit: Unknown; no postlaunch results exist. - Native relative lift, with percent unit: Unknown; no postlaunch results exist. - Native estimated total lift, with unit: Unknown; no postlaunch results exist. - Native lift probability/statistical-strength label and value: Unknown; no postlaunch results exist. - Native lift status, exactly as displayed: Unknown; no postlaunch results exist. - Selected attribute breakdown and its coverage/uncertainty: Unknown; no postlaunch results exist. - Benchmark and its availability/limits: Unknown; no postlaunch results exist. - Documented changes in study scope, campaigns, or data: Unknown; no postlaunch results exist. - Supported interpretation: Unknown; no postlaunch results exist. - What the result cannot establish: Unknown; no postlaunch results exist. - Next decision, owner, and review date: Unknown; no postlaunch results exist. Do not recreate LinkedIn's adjusted result or lift probability from raw counts. A simple difference can teach the arithmetic, but it must remain separate from the native estimate. Estimated additional desired responses are not observed purchases or qualified leads. Missing responses are not zero responses. ## Evidence index | Field or claim | Source or native receipt | Captured date | What it establishes | What remains unknown | | --- | --- | --- | --- | --- | | Eligibility, access, scope, and budget | Simulated receipts described above | November 1, 2026 | Exercise planning inputs only | Actual account evidence | | Planning approval | Simulated PLAN-AL-01 | November 1, 2026 | Approval to prepare the plan in this exercise | Launch authorization absent | | Public requirements | LinkedIn creation and results Help pages | October 30, 2026 | Documented eligibility and review timing | Account-specific eligibility | ## Review decision The supplied fictional fields support presenting the plan for approval. The study ID and results are correctly Unknown before creation and delivery. Jordan must decide on launch before the proposed start. Lee must obtain current native evidence and explicit authority before any real change. Sam retains December 17 at 09:00 UTC as a planned review, not proof that a study ran.