Stakeholder managers, the first point of contact for stakeholders, are often concerned with registering and handling complaints. Construction projects include complaints in their Systems Engineering (SE) model to support stakeholder management processes.

Based on observations of projects, the basic model consists of a project type element named Complaint. Typically, the project type element Complaint includes type properties to store the name, description, and date received:
- The type property Name has a Single line text data type (to contain a brief title for identifying the complaint).
- The type property Description has a Text data type (to provide a more detailed description of the complaint).
- The type property Date received has a Date data type (to register the moment in time when the complaint was reported).
The basic model further consists of one type relation:
- A type relation, has initiator, is created between the project type elements Complaint and Stakeholder. This relation specifies the stakeholder organization or person from whom the complaint originates. In most projects, the cardinality for this relation is set to Single. This prevents ambiguity and ensures a complaint is traceable to only one stakeholder.
Scope

Construction projects often classify complaints based on subjects (e.g., noise pollution, traffic nuisance, accessibility, functional limitations, environmental pollution, etc.). This helps analyze complaints, identify trends, and set priorities for preventing and resolving similar complaints.
In the model, the project type element Complaint includes a type property to store the subject:
- The type property Subject has an Option data type (to classify the complaint). Examples of typical option values include Noise pollution, Traffic nuisance, Accessibility, Functional limitations, and Environmental pollution.
Location
If many complaints concern a specific geographical area within the project’s scope, the decision can be made to relate the complaint to a land lot or location in the model.
Complaints regarding land lots

Some projects keep track of the land lots that stakeholders own or use. For example, to reach agreements with those stakeholders to use the land lots for construction activities or to acquire land lots. Being able to relate complaints to land lots provides traceability. By navigating to a land lot, it becomes instantly clear what complaints need to be considered when communicating with stakeholders and making decisions.
In the model, a type relation, concerns, is created between the project type element Complaint and the reference type element Land lot. In most cases, the cardinality of this relation is set to Multi. This enables widely applicable complaints to be related to multiple land lots.
Complaints regarding locations
When a project uses broader geographical regions (in contrast to land lots), the term locations is often used. Similar to land lots, the advantage is that it becomes instantly clear, from the perspective of a location, what total set of complaints needs to be considered.

In the model, a type relation, concerns, is created between the project type element Complaint and the reference type element Location. In most cases, the cardinality of this relation is set to Multi. This enables widely applicable complaints to be related to multiple locations.
TIP: You can work with external data by setting the ownership of the reference type element Location to External application. As a result, the set of locations in Relatics is automatically synchronized with a set of locations from the project’s Geographic Information System (GIS). An example includes creating an application integration using ArcGIS.
Lifecycle

When monitoring the handling of complaints over time, adding a type property Status to the model with the Option data type is often beneficial. Typical option values include New, Being processed, Closed, On hold, and Rejected. This makes it easier for users to filter out irrelevant complaints. In most cases, the value New is set as the Default. As a result, every newly created complaint will be automatically assigned the status New.
If some complaints are expected to become irrelevant to the project over time, it is advisable to configure the type property Status as a Life cycle property. Optionally, by enabling the Auto archive setting and selecting appropriate archive values (e.g., Rejected), only relevant complaints are displayed by default in the views.
Responsibility

When multiple disciplines or persons handle complaints, it is common to include responsibility in the SE model. This helps clarify who is responsible for taking the lead in handling complaints and makes it easy to filter complaints for which you are personally responsible.
In the model, a type relation, has responsible, is created between the project type element Complaint and the reference type element Person. In most cases, the cardinality of this relation is set to Single. Allowing only one person as responsible for the complaint ensures clarity about who the point of contact is to follow up on the complaint.
TIP: Sometimes, a project assigns responsibility using a project role instead of a person, anticipating future changes in the project’s workforce. However, a significant disadvantage of using a project role is that it becomes much harder to track exactly which person was responsible for a complaint at a specific time. Therefore, it is recommended that responsibility for a complaint be assigned directly to a person.
TIP: When the Life cycle property (e.g. the type property Status) for the project type element Complaint is enabled, complaints can be highlighted as personal tasks with My to-dos. For the project type element Complaint, certain option values for the type property Status can be set as To-do definitions(e.g., New, Being processed). As a result, users can quickly filter complaints in the corresponding overview and highlight personal complaints on the workspace start page.
Source
Various files and documents are typically used as correspondence regarding complaints. Examples include the original documents in which the complaints were shared or emails that contain correspondence regarding the complaints. Referencing the actual file or documents helps users quickly access more detailed information about the complaint.
Single file uniquely stored for a complaint

Sometimes a document is only relevant in a single context. For example, a document that addresses a specific complaint that has been received. If the file is specific to a single context, it can be directly uploaded into Relatics. In these cases, the advantage of storing the file directly in Relatics outweighs the benefit of storing the file in a central Document Management System (DMS) or network drive. If only a maximum of one document per complaint is expected, projects often use properties to allow files to be uploaded for a complaint.
Typically, in the model, the project type element Complaint includes a type property to store an attached file:
- The type property Attachment has an Attachment data type (to contain a file).
Multiple files uniquely stored for a complaint

Projects often use dedicated elements in their SE model if numerous files can be attached to a complaint. In addition to storing multiple documents, another advantage is that other metadata (e.g., a description) can be stored to complement the uploaded file.
In the model, a derived type element Attachment is created for the project type element Complaint. Typically, the cardinality of Attachment is set to Multiple, as multiple files can be added. Additionally, the setting Act as inner element is enabled for the derived type element. As most users are not interested in seeing a complete overview of attachments for all complaints, an Attachment is usually considered an inner type element. Typically, the derived type element Attachment includes type properties to store the file and description:
- The type property File has an Attachment data type (to upload a file).
- The type property Description has a Text data type (to contain an optional comment regarding the uploaded file).
Source documents reused by complaints

In many cases, projects reuse documents in their SE model. For example, multiple complaints can be related to the same correspondence document. By relating all complaints to the same document, it becomes instantly traceable from the document’s perspective which complaints are applicable. In many projects, reused documents are stored in a centralized DMS or network drive that supports advanced file and document management.
In the model, a type relation, has source, is created between the project type elements Complaint and Document. In most cases, the cardinality of this relation is set to Multi. This allows documents to be reused for multiple complaints.
Typically, in the model, the project type element Document includes type properties to store a title and a hyperlink:
- The type property Title has a Single line text data type (to contain a name for identifying the document).
- The type property Hyperlink has a URL data type (to refer to the location of an external file). The advantage is that a user can click on the hyperlink to view the file stored in a DMS, shared network drive, or online resource directly.
TIP: By setting the ownership of the project type element Document to External application, you can work with external data. In this example, the set of documents in Relatics can be automatically synchronized with the list of documents in the project’s DMS.
Control
Projects often create actions for complaints as a measure to control them. These actions help track what is needed and by whom to follow up on a complaint.
Complaint-specific actions

It is common practice for projects to keep track of an action list dedicated to complaints. The advantage is that the SE model can be tailored to the complaint action process.
In the model, a derived type element Complaint Action is created for the project type element Complaint. Typically, the cardinality of the Complaint Action is set to Multiple. This allows multiple actions to be created for a complaint.
Typically, the derived type element Complaint Action includes type properties to store the description, comment, and status:
- The type property Description has a Text data type (to contain a full description of the complaint action).
- The type property Comment has a Text data type (to provide additional thoughts, such as those from other disciplines or organizations involved).
- The type property Status has an Option data type (to monitor the lifecycle of a complaint action). Examples of values include Open, In Progress, Completed, and Rejected.
In the model, a type relation, has responsible, is created between the derived type element Complaint Action and the reference type element Person. In most cases, the cardinality of this relation is set to Single. Allowing only one person to be designated as responsible for the complaint action makes it clear who the point of contact for follow-up is.
Generic actions

Alternatively, projects can support generic actions in their SE model. The advantage is that actions can be reused for multiple elements in the model, keeping the overall SE model relatively simple.
In the model, a type relation, has subject, is created between the project type elements Action and Complaint. In practice, the cardinality of the type relation is set to Multi because the subject of an action may involve multiple complaints. Finally, it may be useful to set the range of the type relation to Collection when the meaning of the type relation (e.g. has subject) is the same for the various type elements within the context of the action (e.g., Systems Requirements, Interfaces, Permits).
TIP: Using the relatable elements view, a user can create actions directly from the perspective of a complaint.