Illustrative idea · WORK INTAKE
Review a new project request
Give a project lead a consistent view of proposed work before it enters the active plan.
Turn incoming requests into the right work—after a quick review.
Illustrative idea, not a published runnable template. Grunt is prelaunch; live service is paused and live provider connections and outcomes remain unverified. The steps, providers, and outcomes below describe a concept.
Gather requests in a consistent format and prepare each one for the team that handles it. Keep the requested work, proposed destination, and any missing details together for a person to check.
Actual availability depends on published steps, supported connections, permissions, and provider approval.
New task requestA submitted request describing work that someone wants the team to consider
“Organize the request, suggest the matching team queue using agreed categories, and show it to a reviewer before creating or assigning a task.”
Work through the request.
Clear tasks, with review where it matters.
- Collect the request details
- Check for missing context
- Suggest the appropriate work queue
A categorized request with its details and proposed destination ready for human approval before it becomes assigned work.
What this workflow could do
Helps teams collect incoming work requests in one consistent format and prepare them for the appropriate queue.
Review points proposed in this idea
A form response is a request, not approval to create or assign work. A person must check the details, destination, owner, and priority before any task is created or changed.
How the idea could work
Select an illustrative task to explore its proposed role. No workflow runs here.
-
Gather the description, requested timing, and other information the team needs to understand the proposed work.
-
Flag unanswered or unclear fields so the requester or a reviewer can resolve them before the team commits.
-
Use categories the team has agreed on to recommend where the request belongs, without treating a category as a final decision.
-
Show the request, destination, and any proposed owner or priority to a person who can verify the details.
-
Wait for an authorized teammate to approve the exact task and destination before adding it to the team’s active work.
-
Record whether the request was approved, needs clarification, or was declined so it does not silently become assigned work.
Step 1 of 6
Collect the request details
Gather the description, requested timing, and other information the team needs to understand the proposed work.
Proposed setup considerations
These are planning notes for the concept, not instructions for a currently available template.
- 01
Design the request form
Ask for the details needed to assess a request, including a useful description and any team-specific category.
- 02
Map categories to work queues
Agree which request categories correspond to which team queues and how ambiguous requests should be handled.
- 03
Choose task reviewers and approvers
Name who checks new requests and who may approve task creation, assignment, and priority.
- 04
Test clear and incomplete requests
Confirm that well-defined requests reach the right reviewer and that missing details stay visible without creating work.
Read the prelaunch status
Published templates and verified customer availability remain pending.
A little help with the whole task
A little less busywork.
A little less busywork.
A little more room for you.
Explore the sample experience while launch details are being finalized.
View pricing status Explore the simulation