Workflow Template
Creative Brief Workflow
Captures creative requests from requesters, has a brief owner review for completeness, and routes ready briefs to prioritisation and designer assignment, sends incomplete briefs back to the requester with specific gaps, and declines out-of-scope requests with a reason. Notifies the requester on assignment or decline.
Creative teams lose time chasing incomplete briefs and manually assigning designers to a growing request queue. This workflow captures every creative request, has a brief owner review it for completeness, routes ready briefs into prioritisation and designer assignment, and sends incomplete or out-of-scope requests back to the requester with clear reasons. Brief owners, designers, and creative ops managers run it directly inside assess.one.
Business Outcomes
- Reduces time spent chasing missing brief details
- Speeds up designer assignment for ready briefs
- Cuts down on out-of-scope work entering the pipeline
- Improves requester visibility into brief status and decisions
- Supports more consistent prioritisation of creative work
Workflow Steps
Steps
- 1Create Creative Brief Recordcreate record
Registers the incoming creative request as a brief record.
- 2Set Status to Submittedupdate record
Marks the brief as submitted upon intake.
- 3Brief Owner Reviews Requestcreate task
Brief owner reviews the request for completeness and records a decision.
- 4Set Status to Under Reviewupdate record
Persists the review decision context and marks the brief as under review before routing.
- 5Route on Review Decision
Routes the brief based on the owner's completeness review.
review_decision: "Ready to Proceed"→Prioritise Ready Briefreview_decision: "Needs More Information"→Notify Requester of Information Gapsreview_decision: "Out of Scope"→Notify Requester of DeclineDefault→End - 6Prioritise Ready Briefai prioritisation
Uses AI to assess urgency of the ready brief for designer scheduling.
- 7Check Priority Confidence
Routes low-confidence priority assessments to human review before assignment.
_ai_priority_prioritise_brief_needs_human_review: "true"→Manual Priority ReviewDefault→Set Priority and Status to Ready - 8Manual Priority Reviewrequest approval
Brief owner manually sets priority when AI confidence is low.
- 9Route Priority Approval Outcome
Continues to assignment regardless of manual confirmation outcome, since the brief was already deemed ready.
approval_status: "approved"→Set Priority and Status to Readyapproval_status: "rejected"→Notify Requester of DeclineDefault→End - 10Set Priority and Status to Readyupdate record
Persists the priority level and marks the brief as ready for assignment.
- 11Assign Designerassign user
Assigns the ready brief to a designer for acknowledgement and execution.
- 12Designer Acknowledges Briefcreate task
Designer reviews the assigned brief and acknowledges they will take on the work.
- 13Set Status to Assignedupdate record
Marks the brief as assigned once the designer has acknowledged the work.
- 14Notify Requester of Assignmentsend email
Emails the requester to confirm the brief has been assigned to a designer.
- 15Notify Requester of Information Gapssend email
Emails the requester with the specific gaps identified so they can update the brief.
- 16Set Status to Needs Infoupdate record
Marks the brief as needing more information from the requester.
- 17Notify Requester of Declinesend email
Emails the requester that the request is out of scope, including the reason.
- 18Set Status to Declinedupdate record
Marks the brief as declined, closing out this request.
Fields
- Requester Name*
- Requester Email*
- Objective*
- Target Audience*
- Deliverables*
- Channels*
- +8 more fields
Forms
Creative Brief Request
9 fields
Data Views
All Creative Briefs
creative_brief_ref, requester_name, brief_status, priority +1 more
Dashboard Widgets
Recommended integrations
Setup the following integrations to extend workflow capability.
Send email in the workflow
AWS SES
Similar Workflows
Similar Categories
FAQs
How do I set up this workflow for my creative team?
Publish the Creative Brief Intake & Assignment template and it's live in seconds. From there you can adjust the fields on the brief record, set your own priority confidence thresholds, and assign the brief owner and designer roles to match your team structure.
What do I need before I publish this workflow?
You just need a list of who reviews briefs, who approves priority calls, and which designers can be assigned. Everything else — statuses, routing logic, notifications — comes ready to use in the template.
How long does implementation take?
Publishing takes minutes, not weeks. Once it's live, your team can start submitting and reviewing creative briefs right away — there's no separate rollout project.
Can I customise what counts as an incomplete brief?
Yes. You can edit the review step and the fields the brief owner checks, so the definition of 'complete' matches your team's standards. You can also change the notification message sent back to requesters when gaps are found.
Who needs access to this workflow?
Requesters need access to submit briefs, brief owners need access to review and route them, and designers need access to acknowledge assignments. You control these permissions inside assess.one when you set up the workflow.
What happens when priority confidence is low?
The workflow checks priority confidence automatically. If confidence is low, it routes the brief to a manual priority review step instead of setting priority automatically, so a person makes the final call before the brief moves to 'Ready'.
What does the requester see if their brief is declined?
The requester gets a notification with the reason the brief was declined, and the record status updates to 'Declined'. This keeps requesters informed without needing a manual follow-up email.
Can I change how designers are assigned?
Yes. You can adjust the assignment logic — round robin, manual pick, or workload-based — directly in the assignment step. The designer acknowledgement step and status updates stay in place regardless of how you configure assignment.
Is there an approval step for out-of-scope requests?
The brief owner reviews each request and can route it to decline with a specific reason, rather than letting it sit unassigned. This keeps out-of-scope work out of the designer queue while giving requesters clarity on why it was declined.
Ready to use this workflow?
Create a free account and customise this workflow for your business.
