Requester and ownership
Identify who can answer follow-ups.
Capture the requester, team, project owner, and subject-matter sponsor so someone can confirm facts.
- Name, email, department, region, and owner.
- Subject expert, backup, and final approver.
Turn scattered PR asks into reviewable briefs. Describe your workflow and create a public relations request form for the news, audience, deadline, spokespeople, assets, and approvals your team needs.
Route PR requests to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a PR workflow, adapt the prompt, or send it to the builder. The fields are an example structure.
Audience
Employees requesting communications support
Format
Structured brief with deadline and approval routing
Prompt size
180 chars
Example form structure
Structured brief with deadline and approval routing
Requester, department, and contact
What are you announcing and why now?
Target audience and requested channels
Desired publish date and hard deadline
Supporting documents and approved images
Suggested routing tags
Announcement
Media inquiry
Speaking request
Ask separately for the desired publish date and the date the request becomes time-sensitive; they are often not the same deadline.
Step 1
Request
capture the story, audience, ask, and owner
Step 2
Triage
score urgency, impact, readiness, and risk
Step 3
Assign
route the brief to the right comms lead
Step 4
Respond
record the decision, next step, and deadline
Why structured intake matters
Email threads hide the news, audience, deadline, or decision maker. Consistent intake gives communications teams context to prioritize work.
Required questions collect the announcement, context, audience, outcome, deadline, and owner before triage.
Use request type, region, or brand to show relevant follow-ups and identify the reviewer.
Keep the brief, status, questions, assignment, and decision together so ownership stays clear.
One front door for communications
Internal partners and media need different questions. Start with request type, then reveal fields for that path.
Collect context, audience, channels, source material, dependencies, and the approval owner.
Capture outlet, questions, response format, deadline, time zone, publication timing, and contact.
Evaluate invitations by audience, format, representative, logistics, promotion, costs, and decision date.
Ask what each partner announces, which assets are needed, who approves them, and when.
Build the intake workflow
Describe how your communications team evaluates requests, then refine the generated form around your real routing rules, reviewers, and response expectations.
List submitters, request types, prioritization rules, and facts required for triage.
Require deadlines and ownership, then show questions for the selected request type.
Notify a shared inbox or Slack channel with request type, owner, deadline, and link.
Export requests to review recurring needs, lead times, missing inputs, and workload.
Form vs inbox vs document
A shared inbox accepts every message but makes comparison difficult. A form standardizes facts while leaving room for nuance.
Field guide
These six sections turn a vague ask into an evaluable PR brief.
Requester and ownership
Capture the requester, team, project owner, and subject-matter sponsor so someone can confirm facts.
Story and objective
Ask for a plain-language summary, audience need, desired response, and why the story matters now.
Scope and channels
Distinguish releases, pitches, comments, interviews, speaking opportunities, awards, bylines, and advisories so follow-ups match the work.
Timing and priority
Collect publication date, response deadline, time zone, dependencies, and the consequence of delay.
Review and sensitivities
Flag claims, customer references, financial details, personnel news, unreleased products, partner terms, and their reviewers.
Assets and completion
Collect briefs, images, logos, biographies, research, product details, and quotes; then confirm readiness.
Related tools
Use focused forms for inquiries, interviews, releases, briefs, content, and events.
Collect journalist questions, outlet details, response format, and deadline.
Open toolCollect topics, guests, format, preparation, timing, and publication plans.
Open toolStandardize announcements, facts, quotes, contacts, assets, and release dates.
Open toolCapture campaign goals, audiences, deliverables, brand needs, and reviews.
Open toolCapture search goals, topics, readers, sources, publishing needs, and owners.
Open toolGather event purpose, audience, schedule, location, stakeholders, and support needs.
Open toolFAQ
Answers for communications teams organizing PR intake.
It is an intake form for announcements, media inquiries, interviews, events, campaigns, awards, and other communications needs. One submission captures the requester, story, audience, deadline, support, evidence, assets, sensitivities, and reviewers.
Include requester, owner, request type, summary, audience, objective, facts, sources, channels, deadline, key dates, region, spokesperson, assets, sensitivities, dependencies, and reviewers. Use conditional questions for media, launches, and events.
Yes, with tailored paths. Internal requests need context, messages, assets, and approvals. Journalists need outlet details, questions, response format, deadline with time zone, and publication date.
Ask for deadline, time zone, context, questions, outlet, contact, requested spokesperson or format, and publication date. Route the submission to a monitored channel with its deadline visible.
Yes. Add upload fields for briefs, data, images, logos, biographies, and quotes, plus link fields for source documents. Ask who owns each asset and collect captions, credits, or usage notes.
Compare audience impact, news trigger, deadline, consequence of delay, strategic relevance, readiness, spokesperson availability, sensitivities, and reviewer capacity. The communications team can apply those inputs during triage.
Yes. Makeform provides unlimited free forms and responses. The paid tier removes the Makeform badge.
Review submissions in the Makeform inbox or route them to Slack, Google Sheets, or Zapier. Include request type, owner, deadline, and submission link in notifications.
Give every PR request a clear starting point.