operations
Scope-change request triage
Route a scope-change request into impact notes, approval steps, and revised task ownership.
Outcome
The team can approve, defer, or quote the change with evidence.
Recipe snapshot
Client delivery teams45-90 minutesmedium difficultymedium riskClickUpAsanaNotion AI
Trigger: A client asks for work outside the current scope.
Inputs
- Trigger source
- Customer or record context
- Owner
- Deadline
- System of record
Setup steps
- Capture the trigger and required context.
- Create or update the system-of-record entry.
- Draft the next action or message for review.
- Assign an owner and deadline.
- Log the result and check failures in the next daily review.
Prompts to reuse
- Summarise the context for scope-change request triage in five bullet points.
- List missing information, risk flags, and the safest next action.
- Draft a short message that a human can review before sending.
Review checks
- Confirm the source data is real.
- Check customer-facing wording before sending.
- Confirm the owner and deadline are visible.
Failure modes
- Trigger does not fire.
- Record is duplicated or routed to the wrong owner.
- AI output sounds confident but lacks source evidence.
Privacy notes
- Only send fields needed for the workflow.
- Avoid uploading sensitive data unless the tool has been approved.
- Keep a human review step for high-risk outputs.
Related guides
ClickUpProject management platform with AI features for tasks, docs, goals, and team workflows.AsanaWork management platform for projects, tasks, goals, and team coordination with AI features.Notion AIAI features inside Notion for notes, docs, wikis, and team knowledge management.Client onboarding kickoffA proposal is accepted or a kickoff form is submitted.Run the related free toolTurn this recipe into a practical output.Workflow LibraryBrowse more workflow recipes.
Get the daily AI workflow brief
One practical workflow idea, tool check, prompt, or calculator to use each day.