Daily publishing operations guide
Lock Article Scope Before an Outsourced Draft Expands
Keep a useful assignment from drifting into unsupported advice, duplicate coverage, or a different reader intent.

Define the working record
For article scope locks, begin with a one-sentence answer boundary, required sections, excluded claims, and related existing routes. Give the record a named owner, a received time, and a finish condition so an outsourced contributor can prepare the work without inventing policy.
Apply the control
Treat a materially different audience, promise, or conclusion as a scope-change request for the editor. The contributor may organize evidence and flag a mismatch; promises, exceptions, access changes, and consequential judgments remain with the named business owner.
Test one ordinary and one difficult case
Run the routine first on a complete item, then on an item with missing or conflicting information. Record where work stopped, what evidence was available, and which person supplied the decision.
Measure the handoff
Count scope changes, late removals, duplicated sections, and drafts returned for intent mismatch. Keep the numerator, denominator, exception reason, and review period together. A completion count by itself cannot show whether the result was accurate or safely controlled.
Improve the routine without rewriting history
Change one instruction or checklist field at a time, preserve the earlier version, and note the effective date. Review the next small sample before expanding volume.
Owner review prompt
Which evidence proves this article scope locks routine is ready, and which exception still needs an owner decision?
Related September 2 guides
Create a Fact-Check Handoff That an Editor Can Audit
Package claims, sources, limitations, and unresolved questions for fast, accountable review.
Keep a Content Change Log Through Outsourced Revisions
Preserve why an article changed, who reviewed it, and which checks must run again.
Review Titles and Slugs as One Article Identity
Prevent title drift, route collisions, and misleading search promises during a daily release.