IT Consulting Project Intake: Decide What Is Ready to Start

An IT consulting project is ready to start when an authorized scope, suitable delivery capacity, required customer inputs, and a named acceptance path are in place. Build an intake process that makes those conditions visible. A signed document or a calendar invitation should not be the only evidence that delivery can begin.

Atlassian links scope with deliverables and responsibilities. Atlassian scope-of-work guidance. Atlassian frames capacity around workload, availability, and relevant skills. Atlassian capacity-planning guidance. The practical workflow below is a proposed management approach, not a claim that a particular tool or provider produces guaranteed results.

Define the decision intake must make

Intake should answer whether to start, prepare with conditions, wait for specific inputs, or return the request for clarification. It is not merely a place to store every new project. Each status needs an owner and a clear next action so a waiting engagement does not disappear in a queue.

Keep the process proportionate. A small, familiar engagement may need only a brief review. A project involving unfamiliar systems, multiple stakeholders, or significant dependencies may require more preparation. The delivery lead should determine the level of technical review, while commercial and operational owners confirm their respective responsibilities.

Assemble one reliable project record

Link the approved scope, current commercial version, customer outcome, known assumptions, and relevant discovery findings. Identify the customer sponsor, working contacts, and person authorized to accept deliverables. Record the internal project owner and the specialists required for the agreed work.

• Agreement and scope are approved through the firm's normal process.
• Delivery lead understands the promised outputs and exclusions.
• Required skills and realistic availability are identified.
• Customer information, access approvals, and dependencies have owners.
• Review points and acceptance evidence are understood.
• Known exceptions have a decision route before they affect delivery.

Avoid storing credentials in the intake form. Link the approved access process and name the person who can validate that prerequisites are satisfied. Administrative coordination should improve readiness without expanding access beyond what the role needs.

Separate missing information from a capacity conflict

A project may be clear but unstaffed. Another may have available consultants but an unresolved scope. Treat these as different operating problems. A single red status cannot explain whether the owner should obtain customer information, negotiate sequencing, approve capacity, or return to sales.

Use a short reason code with a written explanation. For example, waiting for customer input, waiting for approved access, awaiting specialist availability, or commercial clarification required. Record when the condition was identified and who owns the next action. A status that cannot guide a decision is mostly decoration.

Agree a start condition with the customer

Communicate what must happen before work begins and what can proceed while other inputs are outstanding. If your firm has committed to a date, make sure delivery understands what that commitment depends on. If an input is late, explain the effect rather than allowing the customer to assume the original plan still holds.

One person should coordinate the message. Sales can remain involved where a commercial commitment needs clarification, while the project owner manages readiness and delivery planning. The customer should not have to reconcile conflicting statements from the account owner and the consultant assigned to the work.

Illustrative example: a workshop is booked before participants are confirmed

Suppose a consultancy schedules a process-discovery workshop. The scope is agreed and a consultant is available, but the customer's finance and operations owners have not confirmed attendance. Those participants hold information the workshop needs. This is a hypothetical situation.

The intake owner records the missing participation as a prerequisite and asks the customer sponsor to resolve it. The delivery lead decides whether preparation can continue and whether the meeting would still produce its intended output. The team can then confirm, reschedule, or adjust the workshop through an agreed decision rather than simply hoping the right people appear.

Make intake acceptance visible

Ask the delivery lead to accept the project record. Acceptance means the lead understands the commitment and any conditions; it does not mean every future issue has been predicted. If the lead returns the record, require a specific missing input or decision, not a general request for more detail.

Maintain a handoff date and the accepted version of the scope. Later changes should remain traceable. Otherwise delivery can be working from a different understanding while the account team refers to an earlier proposal. A controlled link is often more useful than multiple attached copies.

Measure waiting and rework separately

Track time waiting for customer prerequisites, time waiting for internal capacity, projects returned for missing scope, and issues discovered after start that should have been visible at intake. These categories help the owner identify the right improvement.

Do not interpret every delay as an administrative failure. Some waiting is a deliberate decision to protect delivery quality or customer outcomes. The useful test is whether the reason is visible, the next action has an owner, and the customer understands the plan.

Pilot intake on one project type

Choose a recurring engagement and reconstruct its recent starts. Identify the few missing inputs that repeatedly caused confusion. Put those into the intake checklist, assign acceptance authority, and review the next several projects. Add automation after the decisions are clear. A faster intake form cannot compensate for an ambiguous promise or unavailable specialist.

Put clear ownership around the work

Escencion provides Managed Sales & Business Operations for technology companies. Our current client focus is MSPs and MSSPs. Explore our Managed Business Operations approach, or discuss the responsibilities you need managed. Your technical team retains technical validation, approved commitments, engineering, and service delivery.