Project Intake is a stream-lined method used to collect project data. What type of information should be gathered before beginning a project?

  • Purpose of project
  • Date of delivery
  • Expectations
  • Cost
  • Demand

Throughout the intake process, multiple stakeholders might be involved to decide if the project should proceed. A great intake process will notify those stakeholders and give them the ability to approve or reject project ideas. The intake system should also keep a record of approvals, rejections, and comments that can be referred to in the future.

 

Project Intake App

Project Intake does not have to be done manually. There are various apps and programs available to manage the process. The most important feature of these tools is the intake form. The intake form should align with your business process and goals. Important fields should ask:

  • Goal of the project
  • Audience
  • Cost constraints
  • Delivery date

To ensure governance across your intake process, the intake form should have certain controls. Best practices include:

  • Mandatory fields
  • Drop-down menus to ensure spelling accuracy
  • Calendar boxes
  • Check marks
  • Attachments section

The work isn’t complete once the project form is submitted. Once approved, a project manager needs to be assigned to the project and the project needs to be created. Some intake apps can make the post approval process seamless. Intake360, Marque360’s Power App for project intake, contains workflows that manages approvals, but will also automatically create a project plan in your PPM platform based on project templates.

 

Advantages of Having an Intake Process

A well-defined intake process has many advantages. It ensures no projects are forgotten and all stakeholders are on the same page. Most importantly, the project intake process ensures all projects align with the overall business goals of an organization.

If you’re looking for an intake tool or assistance with your intake process, reach out to info@marque360.com today!

 

-Authored By Suzanne Kooblal, Solutions Architect