A project represents all of the information that is related to developing and running one or more related marketing deliverables or initiatives. This information can include a checklist or schedule of tasks that people who work on the project must complete to prepare and produce the deliverables for the project.

For example, you might create the project "Monthly Tradeshow" to collect all information that is needed for the one tradeshow each month that your organization attends. This information might include any of the following information:

  • Who attends the show
  • What equipment you need in the booth
  • Demonstrations of the product that you intend to present
  • Collateral to hand out to customers
  • Costs of promotional materials
Note: Projects can have subprojects. A subproject has the same characteristics as a project. A subproject is linked to a parent project; any project that is linked in this manner is referred to as a subproject.

Project structure

A project contains a workflow, budget information, metrics, digital assets, approvals, and both standard and custom information. Not every project needs all of this information; most of it is optional and can be completed only when needed.

Note: Approvals can also exist independently from projects. An approval does not need to be associated with a particular project.

Project requests

If you do not have the security permissions to create a project, you create a project request. A project request is similar to a work order or creative brief. It represents a request for someone else to do work according to the specifications supplied by the requester.

Users within an organization and outside vendors can request a project. For example, an outside vendor can submit a project request to the marketing services organization that requests collateral material. The marketing services representative accepts the request and creates a project, which organizes tasks and assigning resources to manage the creation of the collateral.

If you request a project, you are a requester. The requester then submits the request to a recipient for approval. When the recipient accepts the request, the recipient owns the resulting project and is called the owner.

Note: A project request does not contain a workflow. When the request is approved and is converted to a project, it contains the appropriate workflow.