A content intake process gives your team a practical way to collect article requests, test whether they are ready to proceed, and make a visible decision before research, briefing, or drafting consumes time.
Article ideas often arrive as short messages: “We should write about this,” “Sales needs a post,” or “Can we publish something before the event?” A content intake process turns those informal asks into a small, reviewable record. It helps a business identify the reader need, intended purpose, available evidence, accountable people, and timing before deciding whether an article request should move into content planning.
In this guide
Define the intake boundary before you build a form
Use content intake as the decision stage before planning. A requester supplies enough context for an editor or designated reviewer to decide what should happen next. Intake is not a content brief, a research assignment, or a promise to publish. Its job is to prevent the team from treating every idea as equally ready, urgent, or useful.
Keep intake, planning, and briefing separate
| Stage | Primary question | Useful output |
|---|---|---|
| Intake | Is there a defined reader need and enough context to decide what to do? | A status, a short rationale, an owner, and next action |
| Content planning | Does the accepted request fit the broader set of topics and available capacity? | A chosen topic, relative priority, and place in the plan |
| Briefing | What must the article cover, support, avoid, and accomplish? | A writer-ready brief with scope, evidence needs, and review requirements |
Know which requests need intake
Use the same entry point for new article ideas, requests to update an existing article, campaign-related requests, leadership suggestions, and recurring customer questions. A single route does not mean every request receives the same amount of work. It means every request receives a recorded decision instead of disappearing into email, chat, or an individual’s memory.
Route a request through intake when it has any of these characteristics
- The proposed reader is unclear or the request is framed only as a preferred topic
- The requester wants an article to support a launch, event, deadline, or internal initiative
- The idea may overlap with an existing page, a planned topic, or another request
- The article would depend on business facts, expert input, customer information, or external evidence
- The request carries a sensitive claim, approval requirement, or uncertainty about who owns the decision
- The team needs to decide whether an update would serve readers better than a new article
Collect the information needed for a decision
Start with the reader’s task rather than the proposed headline. The Office for National Statistics describes a user need as what a person wants to achieve when visiting content, and presents a user-story structure that identifies the user, the needed action, and the reason for it. Adapt that logic for intake: identify who needs help, what they are trying to understand or do, and why the answer matters now. (Understanding your users: Designing content to meet user needs – Content style guide – Service manual – Office for National Statistics)
Use these core intake fields
- Working request: A plain-language description of the question or issue, not just a suggested title
- Primary reader: The specific group the article is meant to help
- Reader need: What that reader wants to learn, decide, compare, solve, or complete
- Purpose: The practical reason the organization is considering this article
- Evidence and inputs: Available documents, approved facts, data, examples, links, and named experts
- Existing content: Pages or articles that may overlap, need updating, or should be linked
- Timing: The desired date, the reason for it, and what changes if the date is missed
- Requester and owner: The person asking, the person who can answer context questions, and the person accountable for a final decision
- Review needs: Required subject-matter, brand, legal, compliance, or leadership review where applicable
- Constraints: Topics, claims, audiences, examples, destinations, or details that must not be used
Do not accept “everyone” as the primary reader without further clarification. Ask for a recognizable situation, such as a prospective buyer comparing options, a current customer trying to complete a task, or an internal stakeholder seeking an explanation. Teams that need help making the question concrete can map audience questions before planning articles, then return the strongest questions to the intake record.
Build a simple content request intake form
Keep the first form short enough that people will use it, but structured enough that reviewers can act without reconstructing the request from follow-up messages. Ask for required decision inputs up front; make uncertain or optional inputs clearly optional. If a requester cannot supply evidence or a deadline, let them say so rather than encouraging invented certainty.
Copy-and-adapt intake form
Request: [Describe the article idea or update]
Primary reader: [Who is this for?]
Reader need: [What are they trying to understand or do?]
Purpose: [Why should we address this?]
Known evidence and expert: [Links, materials, and contact]
Existing related content: [URLs or “unknown”]
Requested timing and reason: [Date, reason, or “no fixed date”]
Requester: [Name]
Decision owner: [Name]
Constraints or approval needs: [Details or “none known”]
Make one of five clear triage decisions
Triage should end in a status that the requester can understand. A visible outcome makes it easier to preserve useful ideas without committing the team to immediate work. Record the decision date, the reviewer, the rationale, and the next action in the same request record.
Triage outcomes and next actions
| Outcome | Use when | Next action |
|---|---|---|
| Accept | The reader, need, scope, owner, and evidence path are sufficiently clear. | Move it to planning with the intake record attached. |
| Clarify | A viable idea lacks a material input, such as a reader, purpose, evidence source, owner, or timing rationale. | Send focused questions and hold the request until answered. |
| Defer | The idea may matter, but it is not timely, evidence is not yet available, or capacity belongs elsewhere. | Set a revisit condition or date; do not imply a publication commitment. |
| Combine | Two or more requests answer substantially the same reader need. | Name one owner and create a consolidated request. |
| Decline | The request lacks a defensible reader need, conflicts with constraints, duplicates content without a better angle, or cannot be responsibly supported. | Explain the concise reason and, when useful, suggest a safer alternative. |
Worked illustrative example: repair a vague request
Illustrative example: A sales manager submits, “Write an article about our onboarding because prospects keep asking.” The request sounds plausible, but it does not identify the prospect’s question, the available proof, the responsible expert, or whether an existing page already addresses the topic. Mark it Clarify rather than quietly inventing those answers during research.
Input, mapping, error, and correction
| Step | Illustrative record |
|---|---|
| Input | “Write an article about our onboarding because prospects keep asking.” |
| Mapping | Primary reader: prospect evaluating implementation. Reader need: understand the onboarding stages, responsibilities, and prerequisites. Purpose: answer a recurring evaluation question. Evidence owner: implementation lead. Existing content: unknown. Timing: requested before a campaign, with no stated reason. |
| Error | Accepting the idea as a complete assignment would let the team assume the workflow, audience concern, current availability, and campaign deadline. |
| Correction | Ask the implementation lead for approved process details, identify the precise prospect question, check existing content, and confirm whether the campaign date is fixed. Then either accept a bounded article request or defer it until the inputs are available. |
Assign decision rights without making every request a meeting
Separate contribution from approval. The requester explains the need and context. A subject-matter expert confirms factual inputs in their area. The editor evaluates reader fit, scope, overlap, and the editorial route. A designated approver resolves conflicts or business-sensitive decisions. One person may hold several roles on a small team, but the record should still show which decision they made.
Natural Resources Wales distinguishes responsibility for the website experience from subject-matter ownership of factual accuracy, and describes a request form that asks about content type, subject, audience, existing content, urgency, and supporting information. Those categories are a useful reminder to capture both editorial context and factual ownership before work begins. (Natural Resources Wales / Content strategy)
Move accepted requests into planning with a clean handoff
An accepted request should enter planning with its original context intact: the reader need, purpose, inputs, owner, constraints, decision rationale, and open questions. Planning can then assess the request alongside other accepted work, choose an appropriate scope, and decide whether it deserves a full brief. To connect this step to the wider editorial workflow, use the accepted record to build a content plan for your business website rather than restarting discovery from a blank page.
Avoid intake mistakes that create hidden work
Common mistakes and practical corrections
- Treating a title as the request: Ask what reader question the title is supposed to answer
- Using urgency without a reason: Record the event, change, dependency, or consequence behind the requested date
- Accepting claims without a source or accountable owner: Hold the claim as an open input until it is supported, narrowed, or removed
- Letting one department’s preference stand in for reader need: Ask for a reader situation and evidence of the need
- Creating a new article before checking for overlap: Search existing content and combine, update, or redirect the request when appropriate
- Equating silence with approval: Name the decision owner and an escalation route
- Turning every clarification into a meeting: Send a small set of written questions tied to the decision
- Keeping deferred requests without a revisit condition: Set a date, trigger, or responsible owner for review
Key takeaways
- Use intake to decide whether an article request is ready for planning; do not use it as a substitute for a brief
- Collect the reader, need, purpose, evidence, owner, timing, existing-content context, and constraints
- Give every request a clear status: accept, clarify, defer, combine, or decline
- Preserve the rationale and open questions so planning begins with context instead of assumptions
- Assign roles for requesting, factual confirmation, editorial judgment, and final approval
Frequently asked questions about content request intake
What should a business collect before approving a blog article idea?
Collect a description of the request, the primary reader, the reader need, the business purpose, available evidence and experts, related existing content, timing and its rationale, the requester, the decision owner, and any constraints or review needs.
How is a content intake process different from a content brief?
Intake determines whether a request is ready to become planned work. A brief comes later and gives the writer detailed direction about scope, structure, evidence, language, review, and publication requirements.
Who should decide whether an internal article request moves forward?
Assign an editor or content owner to make the routine triage decision. Subject-matter experts should confirm facts in their area, while a named approver should resolve business-sensitive, conflicting, or constrained requests.
What should happen to a request that lacks evidence or a clear reader need?
Clarify it before research or drafting begins. Ask for the specific reader situation, the intended purpose, an accountable expert, and relevant source material. Defer or decline the request if those inputs cannot be established.
Should every article request be accepted?
No. A useful process allows the team to clarify, defer, combine, or decline requests as well as accept them. Recording the outcome protects capacity and makes the decision understandable to the requester.
How often should a team review content requests?
Choose a cadence that matches request volume and available editorial capacity. The important practice is to give each request a visible owner, status, and next action rather than leaving it unreviewed indefinitely.
Turn accepted requests into focused plans
When your team has approved inputs and needs a structured next step, explore SearchWeave’s Content research and planning workflow to turn business context, audience needs, and article ideas into focused plans.