You are writing an original LinkedIn Document Ad for a B2B company. The inspected reference below is a structural example, not permission to copy its words, branding, statistics or conclusions. Work from the user inputs and label every assumption.

REFERENCE INSPECTED
Siemens Digital Industries Software native Document Ad, LinkedIn Ad Library 1507900333, captured 2026-09-23. Cover asks what three pillars of a supply-chain control tower accomplish. Page 2 names a cross-functional decision team; page 3 names information for data-enabled decisions. The third pillar, gate and ad results are outside the three-page preview. Borrow the one-building-block-per-page explanation and translate specialist terms into actions.

USER INPUTS TO COLLECT OR USE
Company and offer: [ ]
Specific buyer and buying situation: [ ]
One document promise and desired next action: [ ]
Source material with URLs/files, dates and publication permission: [ ]
Approved customer names/quotes/figures, if relevant: [ ]
Available format: source report, checklist, case, survey or guide: [ ]
Free reading or Lead Gen Form, and why: [ ]
Asset/thank-you URL, privacy URL, CRM owner and follow-up sender: [ ]
Brand constraints and preferred page count: [ ]

SPECIFIC ASSIGNMENT
Explain each component by naming its owner, input, decision and output. Use three components only if the business really has three; otherwise use the actual number. The reader should understand what changes in their work after each component.

WORKED PATTERN, CLEARLY HYPOTHETICAL
Hypothetical managed IT company: cover “What makes a security incident handoff work?” Page 2: “One person owns the incident,” beside a small responsibility diagram. Page 3: “Everyone sees the same event record,” beside four fields: time, system, action and next owner. An original page 4 explains an escalation rule; it is not a claim about Siemens’s unseen third pillar.

MISSING-INPUT RULE
If material is missing, ask up to three focused questions, then continue with a clearly labeled draft using bracketed placeholders. Do not invent a business fact, customer, quote, survey result, performance rate, source, permission or link. If the core proof is absent, give a non-numeric/process alternative and mark evidence-dependent pages “not ready to publish.” Do not claim the inspected advertiser used a gate or achieved a result.

OUTPUT CONTRACT
1. State the buyer, one-sentence document promise, why this format fits, and the proposed free/gated choice. Separate what is known from assumptions.
2. Give a complete 6–8-page document. For EVERY page provide a page number, exact headline and body copy ready to paste, what the reader learns, layout instructions that work at phone width, and the source/approval needed for each factual claim. Pages 2–3 must fulfill part of the cover promise, not just introduce the company. Mark the proposed preview boundary and show what remains after it. Do not fill pages with slogans or generic benefits.
3. Write the sponsored intro (aim under 150 characters where possible), a concise headline, and a plain-text end CTA. Make their promises match the document.
4. If gated, specify minimal form fields, the privacy URL placeholder, the exact confirmation message, full-asset URL placeholder, CRM routing owner and a test submission. If free, explain how a reader gets the PDF and what next action is offered. Do not assert that PDF links work inside the LinkedIn feed; print essential URLs visibly and test after download.
5. Write one delivery email or follow-up message that refers to a specific page. Distinguish an educational download from a request to speak with sales.
6. Finish with an evidence/permission checklist, a PDF-export and mobile-readability checklist, and three things to inspect after launch: page consumption, successful delivery, and qualified next steps. No invented benchmarks.
Return actual copy and page layouts, not advice about what someone could write.