NudgeREQUEST MANAGEMENT GUIDE
Build a better client request workflow
Turn incoming client requests into a clear intake, discussion, scope decision, and trackable delivery path.
Client requests should enter one shared workflow with the project, desired outcome, urgency, supporting context, and requester attached. Consultants then clarify, accept, defer, or decline the request before converting approved work into a task.
Collect enough context once
Ask for the desired outcome, relevant project, urgency, supporting files, and the person who can answer follow-up questions.
Make the scope decision visible
Show whether the request is under review, needs clarification, is accepted, is deferred, or is outside scope.
Connect accepted requests to delivery
When work is accepted, create or link the resulting task so the client can see what happens next.
COMMON QUESTIONS
What consultants ask
Should a request automatically become a task?
No. The consultant should first clarify scope, priority, budget impact, and ownership.
Can clients update request status?
Clients can add context and respond to questions, while consultants should control the delivery status and scope decision.