This article describes how to work in the documentation and inspection forms:

1. Using the documentation form

1.1 Finding and opening the documentation form

1.2 Understanding the Properties in the documentation form

1.3 Editing an existing documentation entry

1.4 Linking documentation to model or map, attachments, and comments

1.5 Field types and validation in the documentation form

1.6 Typical ways to use the documentation form

2. Using the inspection form

2.1 Finding and opening the inspection form

2.2 Understanding the fields in the inspection’s Properties

2.3 Working with checkpoints

2.4 Entries in an inspection

2.5 Location, attachments, and comments in inspections

2.6 Field types and validation in the inspection form

2.7 Typical ways to use the inspection form

3. In summary – when do you use which?
 

1. Using the documentation form

The documentation form is used when you want to record individual observations  – which are not necessarily part of a specific inspection.

1.1 Finding and opening the documentation form

1. Go to the menu on the left.
2. Under Registration types, click on Documentation.
3. Select the desired registration type, for example:
   • General Documentation
   • Safety Documentation
   • Quality Documentation
   • Other types that are set up in your project. 
4. You will now see a list of entries.
   • Click on a row to open a side menu for a summary of an entry.
   • Click on open entry to get a detailed view of the entry.
      
5. If you have the rights to create a new entry, a button for this will appear just above the list view. 

When you have opened an entry, you will see:

• Properties in the main area.
• Location view on the right, with tabs for:
  • Location – Model or Map placement of the entry.
  • Attachments – Files and images.
  • Comments – Dialogue about the entry.

1.2 Understanding the Properties in the documentation form

A typical documentation form may contain a description, category, or other information. This is the information that is filled out in the field and should give you the full context of what you are observing. The information to be collected is customer-specific, so the options will vary. 

We recommend the following setup for the best possible sharing of information:

• Description
  Short description of the observation. This is usually a required field that should be included.
• Category
  Category for the observation, selected from a dropdown list (for example, discipline, type of error, etc.).
  A good way to group, sort, or filter afterward. 
• Risk/Priority
  Indicates how critical or time-sensitive the observation is. A good way to plan your work.

The system also automatically fills in:

• Created / Created by – When and by whom the entry was created.
• Changed / Changed by – Last modification time and sender.

These system fields are used for tracking and cannot be edited.
 

1.3 Editing an existing documentation entry

1. Open the entry as described in 1.1 Finding and opening the documentation form.
2. Click Edit at the top of the Properties panel.
3. Update the fields you need.
4. Save the changes.

If certain fields are mandatory, the system will prompt you to fill them in before you can save.

1.4 Linking documentation to model or map, attachments, and comments

Model or map linking
When you are in the entry, you can link a placement in the 3D model or map in order to later see the location that was created out in the field

• In both cases, you can click "Add placement" to open the location viewer
• Navigate the 3D model to the correct area and select an object or you can navigate the map and click on a point to add placement.
• Confirm the placement by clicking "Add placement". A screenshot will be taken and displayed in the entry.
• To change the placement, you can follow the same workflow.

Attachments

• Go to the Attachments tab.
• Upload images, reports, or other documentation that supports the entry.
• You can also view existing documentation, download, or set as the main document.

Comments

• Use the Comments tab to ask questions, provide status updates, or log dialogue related to the entry.
   

1.5 Field types and validation in the documentation form

As a user, you will mainly encounter three types of fields:

• Text fields – Free text, often required for the description.
• Selection fields (dropdowns) – Ensures everyone uses the same terms for category, priority, etc.
• Date fields – When a documentation entry was created/modified. 

Validation means that the system checks that:

• Required fields are filled in (e.g., description, category).
• Values are valid (for example, that you select a valid category).

If something is missing, you will be notified when you try to save, and the relevant fields will be highlighted.

1.6 Typical ways to use the documentation form

• Register deviations or errors continuously on the construction site.
• Log events (HSE, quality).
• Document work performed, with attachments and position in the model.

2. Using the inspection form

The inspection form is used when you are conducting a structured inspection with multiple checkpoints – for example, a facade inspection, condition assessment, or handover inspection.

An inspection consists of:

• Overall inspection information (Properties)
• A list of Checkpoints
• Specific entries (findings/observations) linked to the checkpoints

2.1 Finding and opening the inspection form

1. Go to the menu on the left.
2. Under Registration types, click on Inspection.
3. Select the desired inspection type, for example Inspection.
4. You will now see a list of inspections.
   1. Click on a row to open a side menu for a summary of the inspection.
   2. Click on open entry to get a detailed view of the inspection.

When an inspection is opened, you will see:

• Properties at the top – Information about the inspection itself.
• Checkpoints – List of checkpoints and status for each individual checkpoint.
• Entries – all findings/entries made in this inspection.
• On the right: Tabs for viewing the 3D model, attachments, and comments.

2.2 Understanding the fields in the inspection’s Properties

In the Properties section you will see general information about the inspection. This section should give the full context of what the inspection is about, who is participating, and other information that is important for you as customers to collect. These values may therefore vary from project to project, customer to customer.

A typical setup we recommend is:

• Project name – Name of the inspection or project. (May be omitted if a work area is a project)
• Address – Where the inspection is conducted. (May be omitted if a work area is a project)
• Inspection date – Date of the inspection. Useful if planning ahead.
• Participants – Who is participating.

The system also automatically fills in:

• Created / Created by – When and by whom the entry was created.
• Changed / Changed by – Last modification time and sender.

These system fields are used for tracking and cannot be edited.

Editing inspection information

1. Click the Edit button above the properties fields.
2. Adjust the fields (for example, new date, updated participant list, more references).
3. Save.

2.3 Working with checkpoints

The Checkpoints section shows all the control points set up for this inspection type. Examples:

• Overall Material Condition
• Discoloration
• Cracks or Deformation
• Surface Damage
• Sealant Condition
• Windows, Doors, Flashings, etc.

The checkpoints are checked and filled out as part of the inspection that takes place on the construction site via Interaxo Capture, but can also be worked on here. As a user, you can:

• Go through the list and mark which checkpoints you have checked as approved.
• See if there are any entries linked to one or more of the checkpoints. Checkpoints with linked entries will have a reference to the number of entries on the right side of the checkpoint.

The checkpoints help ensure that all relevant parts of the object/building have been reviewed.

2.4 Entries in an inspection

At the bottom of the inspection view, you will find the Entries section. Here you will see all the observations you have registered during the inspection, for example. For each entry, you can click in and see descriptions, open attachments, and see placement in the location viewer - either model or map.
 

2.5 Location, attachments, and comments in inspections

Just like in documentation forms, you can use the side panel on the right:

Location

• The viewer shows the placement for all entries linked to the inspection.
• Switch between 3D Model view and Map.
• Navigate to the correct part of the model/map while reviewing checkpoints and entries.
• When you are in each individual entry, you can see the placement and, if necessary, update it.
   

Attachments

• Upload images relevant to the inspection. Optionally, reports or other relevant files.

Comments

• Conduct dialogue about the findings – for example, technical clarifications or decisions about further action.

This makes it easy to see both what was found and where in the building it was found.
 

2.6 Field types and validation in the inspection form

As a user, you will encounter many of the same field types as in the documentation form, but applied at two levels – the inspection as a whole and the individual entries:

• Text fields and dates – for inspection info (name, date, references).
• Selection fields – for status, inspection type, possible classifications.
• Checkpoints – often organized as a list where you can tick off, open, or create entries.

Validation can be:

• That the inspection date must be set.
• That certain key fields must be filled in before the inspection can be considered complete.
• That certain checkpoints must be handled (checked/registered).

If something is missing, you will notice it when you try to save or complete, as the system will highlight the fields that need to be adjusted.

2.7 Typical ways to use the inspection form

• Planned condition checks of buildings, facades, roofs, etc.
• Handover inspection upon completion.
• Periodic inspections (for example, annual inspections).
• HSE rounds with fixed checkpoints per area.

3. In summary – when do you use which?

• Documentation form
  • When you want to record individual observations or deviations.
  • Focuses on description, category, risk, responsible party, and status.
• Inspection form
  • When you are conducting a full inspection with many checkpoints.
  • Collects inspection information, checkpoints, and all associated entries in one place.

In both cases, you work in forms that are already set up for your project. Your task as a user is to:

1. Find the correct form (documentation or inspection).
2. Fill in and update the fields in a structured way.
3. Use model or map, attachments, and comments to provide complete and traceable information.