The project module is used for project management and offers several options and methods for working with projects in Landax. In some cases, projects are standardised and predefined, with set activities and required documentation. In others, the projects are more open, with content that is not defined in advance.

For projects with predefined content, templates can be created to include elements such as activities, documentation, and participants. It is possible to set up multiple templates, allowing you to reflect the different types of projects used within your organisation. When a project is created from a template, all predefined content is copied into the project, providing a structured starting point.

Projects can include sub-projects. These may represent different phases of a project, such as sales and marketing, planning, execution, and completion, or they may represent different areas within a project.

The project module includes a tree structure consisting of main projects, sub-projects, and tasks. It is optional to use sub-projects and tasks. Data added to a sub-project or task is also displayed in the main project dashboard, and data added to a task within a sub-project is displayed in both the sub-project and the main project. This provides a complete overview of all project data in one place.

Content of a project template

Project templates commonly consist of tasks, document requests, and participant requests, although they can also include data from other modules. When setting up a project template, it is useful to begin by identifying which activities the project includes, what documentation is required, and which functions will be needed throughout the project.

Activities

Activities in a project are registered as tasks. Tasks can include information such as the person responsible, the assignee, planned start and end dates, due date, status, and notes. Additional configuration options are available; to access these, activate configuration mode while viewing a task form.

Documentation

Documentation may consist of documents and checklists. These can be uploaded continuously during the project or added through document requests. A document request is a predefined request for documentation. The advantage of using document requests is that you do not need to assess the documentation needs for each individual project—once defined in the template, the requests are duplicated automatically. This makes it easy to track which documentation is required, what has been submitted, and what is missing.

Document requests can be linked to either the project or individual tasks. In some cases, they are assigned to tasks in order to define responsibility and deadlines for when the documentation must be uploaded.