Self-use worksheets
Product content production pack
Plan SKU-level photographs, useful demonstrations, measurements and claim review without substituting attractive assets for product evidence.
Illustrative data, separate blank downloads.
Examples are fictional. They are not client results, live tests, quotations or product claims. Use the blank CSV files for your own records.
How to use this pack
- Inventory the product and variant questions buyers need answered. Assign a source for factual claims before choosing shots.
- Build the shot list around decisions: scale, included components, use, limits, fit and variants. Name missing evidence rather than inventing details.
- Brief each content module with its audience question, source, required demonstration and accessible text equivalent.
- Keep review provenance and usage rights tied to each asset revision. Mark unverified compatibility or performance claims held.
Import CSV as UTF-8 with comma delimiters. The blank files contain headers and five empty editable rows. Add rows as needed. Preserve stable IDs. Keep secrets, passwords, payment details and personal customer data out of these sheets.
CSV files contain values only and no executable formulas or macros. Calculated example values are static. After changing inputs, recompute the calculated columns using the recipes shown below. Blank means unknown, while zero means a confirmed zero. Formula-like text and negative numbers are prefixed with an apostrophe for safer spreadsheet imports; remove the apostrophe only from verified numeric inputs when you calculate. Your own later edits are outside the generated-file safety checks.
SKU shot and demonstration list
Commission the views that resolve purchase questions.
- Use one row per SKU and a clearly defined shot set. State required variants, views and acceptance conditions.
- Required assets equals variant count times views per variant. Remaining equals required less accepted; rejection or missing provenance does not count as accepted.
Blank editable CSV: SKU shot and demonstration list (228 bytes)Illustrative completed CSV: SKU shot and demonstration list (383 bytes)
Field guide
- SKU
- Stable product or variant identifier.
- Buyer question
- Decision the imagery must answer.
- Required views or demonstration
- Shot specification, not a vague lifestyle request.
- Variant count
- Distinct variants needing the views.
- Views per variant
- Non-overlapping requested views.
- Required assets
- Calculated variants times views each.
- Accepted assets
- Count reviewed, permitted assets only.
- Assets remaining
- Required less accepted.
- Production owner
- Role responsible for capture.
- Acceptance criteria
- Product accuracy, scale, legibility and text equivalent.
Calculation recipes
- Required assets = variant count × views per variant.
- Assets remaining = required assets − accepted assets. Negative means overcount or changed scope; investigate.
Illustrative data
Fictional teaching example only. Replace it with your own verified records in the separate blank sheet.
| SKU | Buyer question | Required views or demonstration | Variant count | Views per variant | Required assets | Accepted assets | Assets remaining | Production owner | Acceptance criteria |
|---|---|---|---|---|---|---|---|---|---|
| DEMO-TOTE-01 | What fits and what is included? | Front, open interior and scale demonstration | 2 | 3 | 6 | 2 | 4 | Content producer | Show exact variant; no unverified capacity claim |
Product content brief
Connect every module to a buyer decision and source.
- Separate approved product fact from creative direction. Include the missing-data behavior and text equivalent.
- Assign one author, factual reviewer and publication authority. A draft visual does not authorize a claim.
Blank editable CSV: Product content brief (226 bytes)Illustrative completed CSV: Product content brief (512 bytes)
Field guide
- Module ID
- Stable brief reference.
- SKU or content record
- Product or shared source.
- Buyer question
- What should become clear.
- Proposed fact or message
- Specific factual statement, not invented benefit.
- Required evidence
- Manual, measured sample, specification or verified record.
- Format and demonstration
- Photo, diagram, text or video task.
- Text equivalent
- Accessible description communicating the decision.
- Missing-evidence action
- Omit or hold the claim until verified.
- Factual reviewer
- Role able to verify it.
Illustrative data
Fictional teaching example only. Replace it with your own verified records in the separate blank sheet.
| Module ID | SKU or content record | Buyer question | Proposed fact or message | Required evidence | Format and demonstration | Text equivalent | Missing-evidence action | Factual reviewer |
|---|---|---|---|---|---|---|---|---|
| M-CONTENTS | DEMO-TOTE-01 | Which parts arrive in the box? | List the actual included components | Fictional sample packing list; real source required | Overhead arrangement showing each included item | Text list matching the accepted packing list | Hold until the real packing list is checked | Product owner |
Measurements and compatibility evidence
Distinguish measured fit from a general compatibility claim.
- Record unit, method, sample and tolerance together. Keep manufacturer claims separate from your observations.
- For compatibility, name the exact counterpart version and test conditions. One observed fit does not support all variants.
Blank editable CSV: Measurements and compatibility evidence (270 bytes)Illustrative completed CSV: Measurements and compatibility evidence (757 bytes)
Field guide
- Evidence ID
- Stable source reference.
- SKU and sample revision
- Exact item measured.
- Property or fit question
- Measurement or named counterpart.
- Observed value or outcome
- Use actual value only after measurement.
- Unit
- One consistent unit per property.
- Method and conditions
- Tool, sample count and limitations.
- Counterpart and version
- Exact device, accessory or system if relevant.
- Tolerance or uncertainty
- Do not infer precision from a photograph.
- Evidence and reviewer
- Reference with date and reviewer.
- Allowed wording and state
- Bound wording to what was verified.
Illustrative data
Fictional teaching example only. Replace it with your own verified records in the separate blank sheet.
| Evidence ID | SKU and sample revision | Property or fit question | Observed value or outcome | Unit | Method and conditions | Counterpart and version | Tolerance or uncertainty | Evidence and reviewer | Allowed wording and state |
|---|---|---|---|---|---|---|---|---|---|
| MEAS-01 | DEMO-TOTE-01, fictional sample A | Opening width | 30 | cm | Illustrative ruler reading, one unloaded sample | Not applicable | Illustrative tolerance not established | Fictional note only | Held: real sample and tolerance required |
| FIT-01 | DEMO-TOTE-01, fictional sample A | Fits named case | Illustrative: closure obstructed | Not applicable | One fictional unloaded fit observation | DEMO-CASE-02 revision A | No other case tested | Fictional note only | Held: do not claim universal compatibility |
Content revision, rights and approval
Keep source changes connected to assets and claims.
- Track each revision through accuracy, usage rights, accessibility and publication permission. Do not mark accepted until all required reviews close.
- If product data changes, reopen affected assets and text. Keep licensed and client material within its permitted use.
Blank editable CSV: Content revision, rights and approval (226 bytes)Illustrative completed CSV: Content revision, rights and approval (461 bytes)
Field guide
- Asset ID and revision
- Stable file revision.
- Module or SKU
- Linked content and product.
- Claims and evidence IDs
- References to source facts.
- Origin and usage rights
- Who created it and what use is permitted.
- Accuracy review
- Role, decision and evidence.
- Accessibility review
- Alt text, captions, contrast or meaningful equivalent.
- Publication authority
- Who authorized intended use.
- Reopen trigger
- What data or rights change invalidates approval.
- Current state
- Draft, held, accepted or retired.
Illustrative data
Fictional teaching example only. Replace it with your own verified records in the separate blank sheet.
| Asset ID and revision | Module or SKU | Claims and evidence IDs | Origin and usage rights | Accuracy review | Accessibility review | Publication authority | Reopen trigger | Current state |
|---|---|---|---|---|---|---|---|---|
| DEMO-IMG-01 r1 | M-CONTENTS / DEMO-TOTE-01 | Packing-list reference pending | Fictional asset; no real rights record | Held: product owner review pending | Draft text equivalent prepared | Not granted in example | Packing list or included item changes | Held |
Assumptions
- Fictional SKU DEMO-TOTE-01, asset counts, dimensions and compatibility observations are invented teaching inputs. They describe no real or client product.
- Asset counts assume three requested views for each of two variants and two accepted assets total. Acceptance requires source, rights and content review, not merely a file existing.
Known limits
- No health, safety, compliance or product-performance certification is established by a photograph or worksheet.
- Do not use fictional measurements or compatibility assertions in a real product listing. Obtain actual product evidence and applicable permission.
Source and method notes
- Approved growth program DESIGN: pack 6.
- Draft SC20 informs resource-field ownership, shared content records, source assignment and separate storage/display acceptance.