Create Project

Creating a project in Quiker is the moment when an initiative approved in a campaign starts being executed, planned, and monitored. This page describes how to originate a project — the two supported ways — and the first steps after creation. The details of each of the project’s internal tabs are in Project Settings.

Who can create

Administrator — can create new projects from scratch or link them to existing initiatives, with unrestricted access to all Hub projects.
Manager — can create new projects within the scope of the campaigns they manage.

See the full breakdown in Project Settings → Permissions.

Where to create

In the Projects section, available in the Hub’s side menu (visible from the Collaborator profile onward, with a different viewing scope per profile — see Project Settings → Permissions).

Recommended prerequisite

Keep an active Planning Cycle. Without an active cycle, projects (like campaigns) cannot be associated with strategic goals, which compromises performance tracking.

Note: Check Settings to verify whether there is an active Planning Cycle.

Two ways to originate a project

From an initiative approved in a campaign

The link is made in the project’s Scope → Relationships tab by selecting the initiative already registered in the Hub. The data from the original application form automatically fills in the project’s scope.

See details in Scope.

Direct creation by the Administrator

No mandatory link to an initiative — useful for projects that do not originate from a campaign selection funnel.

What you see when opening the project

When opening a project, the user immediately sees, at the top of the screen: owner, category, start and end dates, and an overall progress bar — the same data displayed in the projects (Gantt) diagram.

First steps after creation

Fill in the Summary tab

Planned budget, objectives, and meeting minutes. See Summary.

Define the Team

Owner, Collaborators, and Observers. See Team.

Link the Scope

Originating initiative (when applicable) and strategic OKRs. See Scope.

Structure the Schedule

Tasks, dependencies, and Sprints. See Schedule and Backlog.

Record Budget and Gains

Planned and actual amounts throughout execution. See Budget and Gains.