Project Managementoperational
Project Records & Register
How are projects set up and tracked as records?
A project in continON is a referenced record, not a card on a board. It carries dates, the customer it is delivered for, contract links, an owning unit, position, and manager, and a status and percent complete that update as work moves.
Referenced across4 other parts of continON
How it works
Each project record holds a reference, name, and description, start and estimated end dates with a computed duration, and the responsible side of the organization: the owning unit, a position, and a named manager. Status and percent complete live on the record, and entered-by and modified-by fields keep an authorship trail.
Commercial context attaches directly. A project references a customer partner record and can store the customer location down to map coordinates, and it links one or more contracts when multiple contracts are allowed for the engagement. A project can also be marked external — delivered to a customer — or kept internal.
The register screen lists every project and opens each one onto tabs for its resources, risks, contracts, documents, and a project-scoped dashboard. Files upload to the project itself, so scope documents and correspondence stay with the record rather than on a shared drive.
What the register holds
5 on the record- Referenced, audited records
- Every project carries a reference plus entered-on, entered-by, and modified-by fields, so who created and changed the record is part of the record.
- Customer and location
- The customer is a partner record link, and the customer location can be stored with latitude and longitude for mapped delivery sites.
- Contract links
- A project references a contract, or several when multi-contract mode is enabled, and the project screen lists the linked contracts.
- Organizational ownership
- Owning unit, position, and manager are fields on the record, so responsibility follows the organization model rather than a free-text name.
- Documents on the record
- Files upload against the project and are listed and deleted from the project screen, with further documents attached at task and activity level.
What this touches
- Contract Management
Projects reference one or more customer contracts, and the linked contracts list renders on the project screen. - Task Management
Execution tasks carry the project id, and their statuses and progress roll up to the project record. - Organization model
The owning unit, position, and manager fields point at the shared organization structure. - Document Management
Project, task, and activity files are stored through the shared document layer.
See project records & register running in continON.
A guided walkthrough on a sanitized demo tenant — this capability inside its module, on the shared platform.