Describe your marketing intake. Makeform creates a content request form for the goal, audience, deliverable, sources, reviewer, and deadline.
Route content requests to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, adapt it, or send it to the Makeform builder. Each example is editable.
Audience
Campaign managers requesting assets
Format
Conditional campaign brief
Prompt size
258 chars
Example form structure
Conditional campaign brief
Requester, team, and campaign
Goal and target audience
Content type and channel
Publication date and deadline reason
Source files and links
Suggested routing tags
New requests
Needs clarification
Ready to schedule
Ask for the desired publication date and its reason, so editors can distinguish dependencies from preferences.
Step 1
Request
goal, audience, deliverable, and sources
Step 2
Triage
scope checked and missing details returned
Step 3
Schedule
priority, owner, reviewer, and date assigned
Step 4
Produce
work moves forward from one complete brief
Why structured intake
A vague request leaves editors to uncover the goal, reader, evidence, reviewer, and deadline. A structured form keeps those answers together.
Require the audience problem, outcome, message, action, and sources before triage.
Branch by type so video asks about footage while articles ask about experts and keywords.
Capture team, campaign, reviewer, approver, and timing as structured fields.
Requests across marketing
Use one starting point with follow-up fields for the selected asset.
Gather topic, reader question, search intent, sources, and action.
Capture platform, point of view, voice, creative needs, and approver.
Connect assets to a campaign, segment, offer, dependency, and owner.
Record story angle, evidence, permission status, contact, and interview availability.
Intake workflow
Make each intake decision visible instead of reconstructing it across messages.
List accepted content types, brief requirements, deadlines, and reviewers.
Add channels, require essentials, and show format-specific questions when relevant.
Place the published link in your intranet, campaign docs, and team channels.
Review goal, scope, sources, timing, and approvals together before planning.
Form vs chat vs document
A form makes the minimum useful information part of the initial ask.
Field guide
Collect enough to evaluate and schedule work without asking stakeholders to write it.
Requester and ownership
Name the requester, project owner, expert, reviewer, and approver. These may be different people.
Goal and action
Ask for the business goal and the action the audience should take. Similar topics can serve different outcomes.
Audience and context
Collect the segment, role, familiarity, problem, and journey stage to guide depth, vocabulary, and examples.
Deliverable and channel
Choose asset type and channel, then reveal relevant details for email, article, webinar, or video requests.
Message and sources
Collect the message, required points, sources, references, and files. Flag statements that need verification.
Timing and triage
Pair the date with its event, launch, handoff, or channel dependency. Let requesters mark flexibility.
Related tools
Use focused intake for SEO, translation, social, projects, or general requests.
Collect search intent, topics, links, and conversion goals.
Open toolStructure campaign goals, audiences, channels, and owners.
Open toolGather platform, message, timing, assets, and approvals.
Open toolCapture source content, languages, locale notes, and timing.
Open toolHandle internal work outside specialized marketing forms.
Open toolFAQ
Practical answers for marketing and editorial teams organizing stakeholder requests.
A content request form is an internal intake form stakeholders use to ask a marketing or editorial team for an article, email, landing page, social post, video, customer story, or other asset. It collects the goal, audience, deliverable, brief, sources, timing, reviewer, and approval owner in one submission.
Include requester and team, business goal, audience, content type, channel, key message, call to action, source links, file uploads, desired publication date, reason for the deadline, campaign dependency, subject-matter expert, reviewer, and approval owner. Add conditional questions for each format instead of showing every field to everyone.
Ask for a desired publication date, whether it is flexible, and the event or dependency driving it. Explain expected lead times near the date field and treat the submission as a request to review, not an automatic commitment. Your team can then confirm scope, priority, owner, and schedule during triage.
Yes. Start with a content-type choice and use conditional logic to show the relevant follow-up fields. Article requesters can see keyword and expert questions, email requesters can see segment and send context, and video requesters can see speaker, footage, orientation, and length questions.
Yes. Add file upload fields for drafts, outlines, slides, images, research, and brand references, plus URL fields for source pages and shared documents. Label what each upload should contain so the creator can tell source material from a visual reference or an early draft.
Yes. Makeform supports unlimited free forms and responses, so your team can generate, edit, publish, and collect content requests without an invented response cap. The paid tier removes the Makeform badge.
Collect comparable context rather than asking every requester to mark their work urgent. Useful inputs include the business goal, audience impact, launch or event dependency, consequence of delay, required effort, and whether source material and reviewers are ready. The marketing team can apply its own prioritization method during triage.
Submissions arrive in the Makeform inbox. You can also route request details to tools such as Slack, Google Sheets, and Zapier, depending on the workflow you configure. Keep the original form submission as the shared brief and pass its structured fields into the planning system your team uses.
Give every content idea a complete starting point.
