Nembl
Examples
Marketing Brief Intake

Example: Marketing Brief Intake

A creative back-and-forth process: a stakeholder requests a marketing asset → marketing triages and assigns to a designer → draft → review → revisions → final delivery.

You'll build: Service Marketing → Offering Brief Request → Form (7 fields) → Workflow with iterative review loop. Time: ~20 min.

The shape

Submit Brief → Marketing Triage → Assign Designer → Draft → Stakeholder Review

                                                              Revisions Needed?

                                                    ┌─────── Yes ─────────┐
                                                    │                     │
                                                    └──→ Designer Revises ─┘

                                                                  No

                                                            Final Delivery → ✅ Done

What you'll need

  • Company account
  • A Marketing team set up in Admin → Teams (with at least 2 members: triage + designer)
  • An asset-storage location (Drive, Dropbox, Figma, etc.) — links go in the form

Step 1 — Service & Offering

Service

Admin → Services → New Service.

  • Name: Marketing
  • Description: Asset requests, brand reviews, content, design

Offering

  • Name: Brief Request
  • Description: Request a marketing asset (graphic, copy, video, etc.)

Step 2 — Form

FieldTypeRequiredNotes
Asset TypeSelectSocial graphic, Blog illustration, Email banner, Pitch deck, Video script, Other
TitleTextShort title for the deliverable
AudienceTextWho is this for?
Key MessageTextareaWhat's the one thing we want them to take away?
Reference MaterialsURLDrive / Figma / Dropbox link to brand assets, prior examples
DeadlineDateWhen does this need to be delivered?
PrioritySelectLow, Normal, High, Rush (Rush triggers a faster path)

Step 3 — Workflow

Drag phases

  1. Start
  2. ProcessMarketing Triage
  3. DecisionBrief Quality Check (auto via Service Assist agent or manual)
  4. ProcessAssign Designer
  5. ProcessDraft
  6. ApprovalStakeholder Review
  7. ProcessDesigner Revises (loops back to Stakeholder Review)
  8. ProcessFinal Delivery
  9. EndDelivered

Connect

  • Start → Marketing Triage → Brief Quality Check
  • Brief Quality Check (sufficient) → Assign Designer
  • Brief Quality Check (insufficient) → Loop back to submitter for clarification (use a "Wait for Update" Process phase that pauses until the submitter edits the brief)
  • Assign Designer → Draft → Stakeholder Review
  • Stakeholder Review (Approve) → Final Delivery → Delivered
  • Stakeholder Review (Request Revisions) → Designer Revises → Stakeholder Review (loops)
  • Final Delivery → Delivered

Configure Marketing Triage

  • Responsible: Marketing Lead
  • Task templates: "Confirm scope is feasible", "Estimate effort", "Slot into capacity calendar"

Configure Brief Quality Check (Decision)

Two options:

Manual: Marketing Lead picks "Brief is sufficient" or "Needs more info" via dropdown variable.

AI-assisted: assign a CONSULTED Service Assist agent that scores the brief on completeness (key message present? deadline realistic? reference materials provided?) and writes a recommendation comment. The Lead reads the comment and decides.

Configure Assign Designer

  • Responsible: Marketing Lead
  • One task template: "Pick designer based on capacity + skill match" — assigns Designer to next phase

Configure Draft

  • Responsible: Designer (set per-instance in Assign Designer step)
  • Task templates: "Initial draft uploaded", "Internal QA passed"

Configure Stakeholder Review (Approval)

  • Approver: the original submitter
  • Two outgoing transitions: Approve, Request Revisions

Configure Designer Revises

  • Responsible: Designer
  • One task template: "Revisions complete based on feedback"

Publish

Step 4 — Responsibilities

PhaseResponsible
Marketing TriageMarketing Lead (Team Lead role)
Brief Quality Check(Decision — manual or auto)
Assign DesignerMarketing Lead
DraftDesigner (assigned per-instance)
Stakeholder ReviewOriginal submitter (auto-resolved)
Designer RevisesDesigner
Final DeliveryMarketing Lead

Step 5 — Test the iterative loop

Submit a brief

As any user, submit. Set deadline 1 week out.

Triage and assign

Sign in as Marketing Lead. Triage. Assign Designer (yourself or a teammate).

Draft

Sign in as the Designer. Mark Draft complete with a link to the (mock) deliverable.

Reject the first time

Sign back in as the submitter. Stakeholder Review activates in their queue. Click "Request Revisions" with comment "Make the headline bigger and shift to brand purple."

Revise

Designer's queue shows the loop-back. Mark Designer Revises complete.

Approve the second time

Submitter approves. Final Delivery activates → Delivered.

What you can adapt

  • Rush priority skips Triage: a Decision after Start that routes Rush briefs directly to Assign Designer.
  • AI brief scorer: the Service Assist agent suggests improvements to the brief at submit time, before Marketing even sees it. Reduces the "needs more info" loop.
  • Auto-pull from Figma: a Process phase that fetches the latest comp from a Figma file URL and attaches it to the request, so reviewers don't have to click out.
  • Capacity-aware assignment: instead of manual Assign Designer, a Decision based on which Designer has the lowest open-task count.
  • CSAT after delivery: Timer phase 3 days after Delivered that fires a 1-question survey to the submitter.

Related