Skip to main content

Organize a project and follow its tasks

A project brings tasks, task groups, milestones and documents around an objective. It remains optional for scheduling people or performing work.

note

Actions depend on the available Projects workflow and permissions on linked items. Project access does not automatically open every document or calendar.

Before you start​

Search the existing project. Prepare a useful name, objective and appropriate responsible person. A task group is different from a group of people.

Steps​

  1. In Projets, search name or objective and check states or archives. Create only when the project does not already exist.
  2. In Aperçu, review objective, state and next action. Use Tâches to organize attached items and useful groups.
  3. Explicitly attach an existing task through the offered action. Opening the catalogue neither creates nor attaches it automatically: return, refresh and check the link.
  4. When offered, define dependencies, milestones and acceptance conditions. Open documents and staffing requests through their existing access points.
  5. After editing, check actual task links, states and milestone decisions. A count of accepted milestones is not by itself total project progress.

Example and expected result​

Fictional example: Three-site Preparation has a visit and validation per site. The manager attaches tasks and defines the validation milestone outcome. The scheduler plans people separately. Accepting a milestone does not prove an invoice is paid.

If something goes wrong​

An empty catalogue and refused access need different remedies. Check the command before creating again after an uncertain response. Canceling an unconfirmed form does not attach the task. Changing project dates should not be assumed to move staff commitments.

Continue​