---
name: set-up-content-library
description: "Put your source files and finished work in one clear home. Build a log so the next person can find and use them."
category: Content Factory — Produce
stage: Produce
definitive_article: /social-amplification
status: needs-work
---

# Set up Content Library

Good files are hard to use when they sit in phones and chat threads. This guide helps a business owner put them in one clear home. Start with an approved folder, then make a log that shows each file and its next step.

**The path:** Approved home → Four clear stages → File log → Tested handoff.

**Use this when:** The brand needs its first content library or an agreed set of existing files needs to be organized.

## Inputs
- A brand-controlled Google Drive location and a person authorized to set its folders and sharing. Check whether it is My Drive or a Workspace shared drive.
- A bounded list of assets to organize, with their present locations, owners, permissions, and known duplicates. “All files” needs a stated scope.
- The current [Topic Wheel](https://blitzmetrics.com/topic-wheel/) topics, the raw-file intake location, and any existing library layout that must be preserved.
- Edit access for the folder and tracker, plus the names of the intake owner, editor, and person who controls access. Do not grant everyone full edit rights by default.

## First-run prompt

> Help me build or clean up the agreed content library from the locations and file list I provide. Preserve the existing approved structure and source trail. Draft the README and tracker, check ownership and access, and reconcile only the stated scope. Report exact gaps; do not delete originals, grant extra access, or schedule a job without authority.

## Steps
1. Confirm the library home with the brand owner. Use the existing approved structure if there is one. Record the location, access owner, scope of files, and limits before moving anything.
2. Check ownership, not just the name of the parent folder. In My Drive, a brand-owned folder does not make each uploaded file brand-owned. Where the brand has an approved Workspace shared drive, files belong to the organization. If using My Drive, record file owners and resolve the actual ownership plan with the access owner.
3. Create or map four stage folders: 01-Raw, 02-In-Process, 03-Published, and 04-Promote-Creatives. These reflect the [Content Factory](https://blitzmetrics.com/content-factory/) stages: make source material, edit it, publish it, and then distribute it. Do not mark content published just because it is placed in 03-Published.
4. Write a short root README. State who owns the library, where new files arrive, how to name them, where the tracker lives, and who takes the next step. Use YYYY-MM-DD-topic-person plus type or take suffix when needed. Keep original names in the tracker to preserve the source trail. Preserve each file extension unless you separately convert the file and verify the result.
5. Create a tracker with one row per source asset: asset ID, original name, current name, date, source link, topic, [GCT](https://blitzmetrics.com/gct-business-strategy/) notes, owner/permission state, stage, next person, and links to derived work. GCT means the goal, what this file shows, and who it is for.
6. Inventory the agreed assets before moving them. Copy or move only within the approved scope; do not delete originals or merge duplicate-looking files without checking them. Rename the working copy, file it in the right stage, and log each item. Keep unmatched or inaccessible files on an exception list.
7. Open the raw folder in Drive and use New → File upload or Folder upload, or drag the allowed files into it. Wait for completion. If a filename already exists, inspect the choice before overwriting a version; preserve distinct takes.
8. Check sharing with the access owner. Give the team only the roles needed for intake, editing, or review. Parent folder sharing can affect its contents. Use an approved restricted location for files that need tighter limits.
9. Test the handoff with one actual source file. Confirm the editor can open it and find its tracker row. Point [Upload the source to Drive and Descript](https://local-service-spotlight.github.io/task-library/?task=step-1-upload-video-to-google-drive-and-descript#task-step-1-upload-video-to-google-drive-and-descript) at the agreed intake. An existing worker may require a specific source path; record that path rather than assume it reads these folder names.
10. Reconcile files and rows within the agreed scope. Count found, logged, inaccessible, and unresolved assets. Save the README and exception list. The source proposes a weekly backlog review; configure that separately only when an owner, time, and access are agreed.

## Definition of done (QA checklist)

- [ ] The library location and actual file ownership model are recorded.
- [ ] The four stage folders are created or mapped to the existing layout, with a clear raw intake.
- [ ] The README and tracker explain naming, topic, stage, rights, and handoff.
- [ ] Every asset in the stated scope has a tracker row or a named exception; source copies and original names remain traceable.
- [ ] An actual recipient has checked access to a test file; missing access is not reported as ready.
- [ ] The backlog review is described without falsely claiming a scheduled job exists.

## Example(s)

**Fictional teaching example — no Drive folders or client files were created.** Maple Cycle’s sample scope is 12 phone clips and 4 photos. The teaching folder plan is:

```text
Maple Cycle Content
  README
  Content tracker
  01-Raw
  02-In-Process
  03-Published
  04-Promote-Creatives
```

One sample row maps original `IMG_0421.mov` to `2026-09-06-repair-quote-alex.mov`, topic “repair quotes,” stage “Raw,” next role “editor.” Its output links stay blank until real outputs exist.

If the sample intake finds 15 of the 16 planned assets and one phone is unavailable, the result is “15 logged; one photo still needed.” If the parent folder is brand-owned but this clip belongs to another person in My Drive, ownership is still unresolved. A neat folder tree is not proof that the brand controls every file.

## Handoff and Content Factory context

The intake owner receives the README, file log, and exceptions. The editor tests one source file and starts [Upload the source to Drive and Descript](https://local-service-spotlight.github.io/task-library/?task=step-1-upload-video-to-google-drive-and-descript#task-step-1-upload-video-to-google-drive-and-descript). The existing worker or upload task must use the verified intake path; this guide does not install or activate it.

This task serves **Produce** in the [Content Factory](https://blitzmetrics.com/content-factory/). Produce makes or prepares source material. Process edits it, Post puts approved work on a channel, and Promote helps it reach people. Only the steps and handoff above are part of this task.

## When this runs

The initial setup is a one-time task for the agreed scope. Normal intake happens as new assets arrive. A weekly raw-backlog review is the source recommendation, with items older than a week flagged for review; it becomes a real schedule only after configuration and a checked first run.

## Run with an agent

The agent can prepare the plan, organize allowed files, and check the evidence it can actually access. A person records real stories, supplies permission, or resolves an account step when needed. Save the current state in the project files and tracker. A model name does not create memory, access, a scheduler, or permission to act.

For all agent media checks, keep the player muted and its volume at zero before playback. If that cannot be checked, use captions, metadata, or still frames. Do not claim sound quality was heard when it was not.

## Write up the real run

For every actual attempt, [write the run’s meta article](https://blitzmetrics.com/meta-article-prompt/). Link this exact task and its source revision. State the start, work done, evidence, result, gaps, and next owner. Keep failed, partial, and blocked work visible. Writing the record does not authorize publishing it.

Use one stable execution ID for this task’s actual run. Internal retries, checks, and new versions do not add runs. A separately scoped child task may have its own ID linked to the parent. A teaching example has no real execution ID and must not enter the run count. Follow the [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) for that distinction.


<!-- factory-layer:start -->

## Factory chain (do not treat this as isolated)

- **Phase:** Gate
- **Importance:** 5/5 `●●●●●` — frequency 5, revenue 3, gating 5 (runs every factory cycle or weekly; unblocks a chain (access/plumbing))
- **Suggested previous station:** `configure-https-with-no-mixed-content`
- **Suggested next station:** `install-google-tag-manager-container`
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Record only the property IDs, access and checks required by this task in the client register. Pass the verified result to the task that needs it.

## Model routing (same factory, any engine)

- **This task's lane:** `any` — Any capable chat model (Claude, ChatGPT, Grok, Gemini). SOP following, drafts, checklists.
- **Single-engine path:** Use the capable AI app you already have. Check its required tools and access before starting. Pass the actual result and proof to the next task.
- **Optional multi-engine:** A tested local model may draft; a stronger model may review facts and voice. Use supported tools for approved actions. Pick models from observed quality and cost; a model name does not prove it can run this task.
- **Never** store the working state in one vendor's memory. Files in the Content Library are the bridge.

<!-- factory-layer:end -->
## Definitive article & links

- Canonical article: https://blitzmetrics.com/social-amplification
- Exact task: [Set up Content Library](https://local-service-spotlight.github.io/task-library/?task=set-up-content-library#task-set-up-content-library)
- Publishing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Google’s current upload controls](https://support.google.com/drive/answer/2424368?hl=en)
- [Google’s current folder-sharing rules](https://support.google.com/drive/answer/7166529?hl=en)
- [Google’s explanation of file ownership](https://support.google.com/a/users/answer/7212025?hl=en)
- [Social Amplification operating context](https://blitzmetrics.com/social-amplification/)

## Review and evidence still needed

The contributor status in the source header is preserved. It is not a claim that this draft has been independently accepted or that a real run has passed. The worked example above is for teaching only.
- Real Drive ownership, storage, permission and recipient-access checks still require the actual account.
- The existing worker’s concrete intake path must be confirmed before wiring it to the library.