What Is Work Intake? Definition, Process, and the WIQ

3 days ago
5 min read

Definition

Work intake is the process by which an organization receives, clarifies, evaluates, and accepts — or declines — incoming requests before they become active work. It is the front door of every workflow: the designed stage where a request stops being a message and becomes a tracked, owned unit of work.

Most organizations have no such stage. Requests arrive through email, chat, meetings, and hallway conversations; some become work, some vanish, and no one can say which channel produced what. The Work Management Institute treats work intake as the first structural element of Workflow Architecture, because a workflow with unmanaged intake produces unmanageable work — no matter how well the downstream stages are designed.

Work Intake vs. Demand Management vs. Project Intake

These terms overlap but sit at different altitudes. Demand management is the portfolio-level practice of forecasting and balancing all incoming demand against capacity — a planning discipline. Project intake is the gated evaluation of proposed projects, usually owned by a PMO. Work intake is broader and more operational than either: it governs how any unit of work, from a project proposal to a five-minute request, enters a workflow. Every team has work intake whether or not it has a PMO — the only question is whether that intake is designed or improvised.

The Work Intake Process

A designed intake process has five stages:

1. Capture. The request is received through a defined channel and recorded where the work system can see it. Capture is where intake meets the workflow trigger: an intake channel is a governed trigger, and a request that arrives outside it is a trigger that fired invisibly. One defined front door — a form, a queue, a request type — outperforms five informal ones, because every additional uncontrolled channel multiplies duplicate and shadow work.

2. Clarify. The request is made workable: what is actually being asked for, by whom, by when, and why. Clarification is the cheapest moment in the life of any piece of work to resolve ambiguity — the same question asked at intake costs minutes; asked mid-execution it costs rework. This is the Structural Clarity standard applied at the doorway.

3. Evaluate. The organization decides whether the work should be done at all, and at what priority. Evaluation requires visible criteria — alignment, urgency, capacity — because intake without evaluation is not a process, it is a conveyor belt that accepts everything and delivers late on all of it.

4. Accept or decline. The request receives an explicit answer. Declining is a legitimate intake outcome, and organizations that cannot say no at intake end up saying it later through missed deadlines. Acceptance means the work enters a workflow with an owner; it is now subject to the workflow's standards, not the requester's follow-ups.

5. Assign. The accepted work is routed to the workflow and owner that will perform it, with the context gathered at clarification attached. Assignment closes the intake loop: the requester knows the work's status, and the performer knows its intent.

Why Work Intake Fails

Intake failures are trigger failures compounded by volume. The recurring patterns:

Uncontrolled channels. Work enters through every medium the organization uses to communicate, so no queue reflects true demand and no metric counts true load.
Silent acceptance. Requests are never explicitly accepted or declined — they simply linger until someone acts or the requester escalates. The backlog becomes an archaeology site.
Clarification debt. Requests are accepted as written, and the missing context is excavated later, during execution, at many times the cost.
No intake owner. The intake queue itself has no accountable role, so triage happens by seniority of the requester rather than priority of the work.

In WPI terms, unmanaged intake shows up first in the Flow Indicators — queue size and wait time grow while cycle time looks deceptively stable, because the clock only starts when someone finally notices the work.

The WIQ™: Workflow Intake Questionnaire

The Work Management Institute formalizes intake at a second level: not just how work enters a workflow, but how a workflow itself is taken in for design. The Workflow Intake Questionnaire (WIQ™) is the structured instrument a Workflow Architect uses to capture a workflow's essential structure — its purpose, participants, triggers, handoffs, decisions, and exceptions — before mapping begins.

The WIQ exists because workflow mapping inherits the quality of its intake. A workflow documented from an unstructured conversation reflects whoever spoke loudest; a workflow captured through a consistent questionnaire can be mapped at the appropriate level (WMI's Mapping Levels L1–L4), compared against the 7 Workflow Architecture Standards, and re-examined later against the same baseline. The WIQ is a core asset of the Certified Workflow Architect™ (CWA™) practice: it is to workflow design what a client intake form is to professional services — the difference between beginning with evidence and beginning with impressions.

The two levels reinforce each other. An architect using the WIQ will, among the first things captured, document how the workflow's own intake works — which is frequently where the workflow's problems turn out to live.

Governing Work Intake

Intake is governed when the same four conditions that govern any trigger hold at the doorway: the channel is defined, the queue is owned (a specific role is the Signal Owner for incoming requests, per the IDEAS Model), the requests are visible in a countable queue, and acceptance is bounded by explicit criteria. Add one intake-specific rule: every request receives an explicit disposition — accepted, declined, or deferred with a date. The AWAIT Protocol's Window for Response applies to the intake queue itself: a request is not governed until the requester knows when they'll hear back.

Key Takeaway

Work intake is where an organization chooses its work — or fails to choose, and lets its work choose it. A designed intake process turns the chaotic arrival of requests into a governed boundary: one front door, explicit clarification, visible evaluation, and an honest yes or no. And at the practice level, the WIQ applies the same discipline to workflows themselves, ensuring that what gets mapped, measured, and improved was captured rigorously in the first place. Predictable work does not begin at execution. It begins at the door.

Frequently Asked Questions

What is work intake?

Work intake is the process by which an organization receives, clarifies, evaluates, and accepts or declines incoming requests before they become active work. It defines how work legitimately enters a workflow.

What are the steps in a work intake process?

A designed work intake process has five stages: capture the request through a defined channel, clarify what is being asked, evaluate whether and at what priority to do it, explicitly accept or decline it, and assign accepted work to an owner and workflow.

What is the WIQ?

The WIQ™ (Workflow Intake Questionnaire) is the Work Management Institute's structured instrument for capturing a workflow's purpose, participants, triggers, handoffs, and exceptions before it is mapped. It is a core asset of the Certified Workflow Architect™ (CWA™) practice.

What is the difference between work intake and demand management?

Demand management is a portfolio-level planning practice that balances forecasted demand against capacity. Work intake is the operational process governing how individual requests enter workflows day to day. Every team performs work intake; demand management typically exists only where a portfolio function does.

Why is work intake important?

Because ambiguity is cheapest to resolve at the moment work enters. Unmanaged intake produces uncontrolled channels, silent backlogs, and clarification rework during execution — costs that appear downstream and get misdiagnosed as execution problems.