---
name: process-videos-via-marketscale
description: "Send a clear video brief to MarketScale. Check the returned cut and save the files your team needs."
category: Content Factory — Process
stage: Process
definitive_article: GAP — to be written
status: gap
---

# Process videos via MarketScale

An outside editor needs to know what you want the video to do. This guide helps you send a clear brief and check the finished cut. Start with the real source and the result you need.

**The path:** Archived source → Clear edit brief → Reviewed cut → Saved master and handoff.

**Use this when:** The project has chosen MarketScale for a specific video edit, with its account and service scope available.

## Inputs
- The original archived media, source transcript, rights and [Goals, Content, and Targeting](https://blitzmetrics.com/gct-business-strategy/) brief.
- The exact brand workspace, account role, included edit service and real approver. A brand-held account does not imply password sharing.
- The requested length, orientation, destination, captions, branding and deliverable files.
- The tracker, original-source link, review owner and actual publication/distribution scope.

## First-run prompt

> Prepare and carry out the scoped MarketScale edit request using this archive and brief. Confirm the actual workspace controls, avoid duplicate orders, and check the returned media against the source. Keep audio silent. Return the master/captions, request states and any real distribution URLs; do not equate auto-completion with quality review.

## Steps
1. Record why this source uses MarketScale and what is being requested. Keep the original in the project archive; the provider must not hold the only copy.
2. Confirm current workspace controls and the edit service available. Official help currently documents both a brief-form route and a Request edit conversation. Use the interface actually present and record the chosen route rather than inventing buttons.
3. Upload the correct source into its designated folder and select the actual approver. Complete the platform’s upload-approval step within existing authority. Approval into a workspace/feed is not proof of publication on every external channel.
4. Open the media in Media Studio. Start the current Request edit flow and supply the goal, audience, desired cut length/orientation, source facts and exact caption/branding needs. Check supplied brand assets rather than assuming inherited settings are correct.
5. Review the completed brief and submit once when in scope. Save the video/order reference and requested deliverables. If an active edit conversation already exists, continue it instead of making a duplicate order.
6. When the cut returns, compare it with the source: meaning, names, quotes, captions, framing and agreed output. Keep agent playback silent and record any remaining audio-quality review. Use timestamped feedback and the current revision control for actual defects.
7. Record actual state: uploaded, approved into workspace, in editing, edited, revision requested or complete. Provider auto-completion or elapsed time is not evidence that a human approved the quality. Do not promise the provider’s usual turnaround as this job’s guaranteed deadline.
8. Save the finished master and available captions to the Content Library, with source mapping and checked file properties. If a required download or caption artifact is unavailable, keep that specific deliverable pending.
9. Distribute only to the actual channels in the existing scope through their supported publishing tasks. Save real URLs and visibility. A field named Publishing destination in an edit brief is an instruction, not a public distribution receipt.
10. Write the real run record, including the observed interface, service limits and fixes. The missing house-specific SOP can then be improved from evidence; writing this draft alone does not close its runtime gap.

## Definition of done (QA checklist)

- [ ] The source archive, routing reason and approved edit brief are recorded.
- [ ] One actual request/order is tracked with true current state.
- [ ] Returned files satisfy the source/branding/caption checks or have precise pending issues.
- [ ] Archive return and any actual distribution are evidenced separately.

## Example(s)

**Fictional teaching example — no provider request was sent.** Maple Cycle asks for a 40-second portrait cut from a six-minute source: show the whole-bike photo, then the close-up, and retain the statement that an inspection may be needed.

The sample brief says “Use the existing shop branding; captions must preserve ‘may need an inspection.’ Return a master file and captions.” A returned cut drops “may,” so the reviewer leaves a timestamped correction. Even if the provider marks the order Complete automatically, the local record keeps “meaning correction pending.” No Facebook URL is logged until an actual post exists.

## Handoff and Content Factory context

The content owner receives the master and review log. [Transcript review](https://local-service-spotlight.github.io/task-library/?task=step-2-transcribe-video-using-descript#task-step-2-transcribe-video-using-descript) or [WordPress placement](https://local-service-spotlight.github.io/task-library/?task=step-12-post-article-on-wordpress#task-step-12-post-article-on-wordpress) follows only when its own required article/material is ready. Distribution is a separate Post handoff.

Produce supplies the real source. **Process**, this stage of the [Content Factory](https://blitzmetrics.com/content-factory/), turns it into useful finished assets. Post saves or publishes them on the agreed channels. Promote tests and distributes suitable work within its own scope. The handoff above names this task’s actual next step; catalog neighbors alone are not prerequisites.

## When this runs

One bounded provider request per scoped video/edit order. Revision and status follow-up use the existing owner and provider state; no recurring uploads or extra orders are installed.

## First-run setup and continuity

Open the supplied task file and its linked source. Verify the project’s real inputs, account, access and output folder before work. This Markdown file is a guide; it does not install an app, connect an account, supply a subscription or create a schedule. Carry out work already authorized; do not ask for the same approval again. Keep any unsupplied destination or new action outside that scope clearly pending.

Save source IDs, versions, decisions, checked outputs and next owner in the project tracker. Before a retry, check the saved state and other workers’ changes. A model name does not guarantee memory or a running timer. Repeated work needs an actual configured trigger and durable state; one-off work can be started by the prompt above.

Keep agent media muted with volume zero before playback. If mute cannot be verified, use captions, metadata or still frames. State the limit: silent visual checks do not prove spoken-word accuracy or audio quality. Do not start sound through the user’s speakers unless explicitly asked.

## Write up the real run

For every actual attempt, [write its meta article](https://blitzmetrics.com/meta-article-prompt/) with this recipe and revision, trigger, steps performed, output evidence, measured result, gaps and next owner. Failed, blocked and partial attempts also get a written record. A draft can satisfy writing; publishing it follows the existing job scope.

Keep one stable execution ID across retries and edits. A separately scoped child task may have its own ID linked to its parent. Writing the parent’s meta record is part of that run, not an endless new chain. The [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) explains this distinction. Teaching examples are not real executions and must not enter the run count.


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

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

- **Phase:** Process
- **Importance:** 4/5 `●●●●○` — frequency 4, revenue 3, gating 2 (runs every factory cycle or weekly)
- **Suggested previous station:** `write-meta-article-documenting-agent-work`
- **Suggested next station:** `step-12-post-article-on-wordpress`
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Process-stage artifact examples include `transcript.md`, `gct.md`, `article.html` (or a staged draft), `clips/`, or `04-Promote-Creatives/`. These are examples, not requirements for every task. Follow this task's actual Inputs and Handoff sections for the required output, evidence, and next owner. Pass the files or records, not one vendor's memory.

## 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

- Dedicated canonical article: not mapped in this source record. Use the maintained owned training below until that article gap is reviewed.
- Exact task: [Process videos via MarketScale](https://local-service-spotlight.github.io/task-library/?task=process-videos-via-marketscale#task-process-videos-via-marketscale)
- Writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [MarketScale current edit-request flow](https://help.marketscale.com/en/articles/16004078-how-to-request-a-video-edit-with-marketscale)
- [MarketScale first upload and request](https://help.marketscale.com/en/articles/14537742-getting-started-submit-your-first-edit-request-on-marketscale)
- [MarketScale edited/completed states](https://help.marketscale.com/en/articles/14603884-why-don-t-i-see-the-request-edit-now-button-on-my-video)

## Review and evidence still needed

The source contributor status is preserved. It is not certification of this draft or proof of account access, completed work or a live outcome. The worked example teaches the method and is explicitly fictional.
- Dedicated article and a verified house run remain absent. Actual workspace version, plan, download/caption options and provider response need an authorized real request.