We will update our database server between 15:00 and 15:30 on Monday 2026-07-13. Field Manager will be unavailable for some minutes between 15:00 and 15:30.

We apologize for the potential inconvenience.

We would like to wish all our users a wonderful summer holiday when the time comes! 

Field Manager support will, of course, be staffed throughout the summer. We also have development resources available should the need arise. You can easily reach us at support@fieldmanager.io.

We will be performing a planned maintenance on Tuesday 23.06.2026 between 9:30 and 11:30. During this maintenance window, the application may experience temporary instability or service disruptions.

We apologize for the potential inconvenience.

Over the past weeks, we’ve introduced improvements that give better control over geotechnical method data and ensure it remains stable once approved. You can now add and edit methods directly in the table at location level. When a method’s status is set to approved, it becomes locked and cannot be changed unless the status is temporarily reverted, the update is made, and then set back to approved.

Organizations can decide who is allowed to set a method to approved and who can change it back again. By default, all users with project edit access have these permissions, so no change will be noticeable unless you choose to restrict this within your organization.

These changes are primarily driven by the need to use method data reliably across other systems (such as NADAG and Lab) and to ensure that approved data does not change over time. They also strengthen data quality and enable clearer workflows for internal review and verification, especially for organizations that limit approval rights to admin roles.

We plan to introduce a dedicated QA / review status as a step between conducted and approved, and welcome your input on whether this would be useful.

 So far, this update applies only to the user interface. Later this week, we plan to release the corresponding backend changes used by integrations and automated solutions. During the transition, some API-based solutions or workflows (for example AGS uploads combined with lab ordering) may experience temporary friction. Please reach out if you encounter issues—we’re happy to help and collaborate to ensure a smooth transition.

We are getting a lot of questions about the status of our Nadag integration, and when it will be ready for you as users. The Field Manager team is continuously in dialog with NGU and testing the new API for syncing data to Nadag, but there are still many technical issues that NGU needs to sort out before they have a working solution ready. The law states that all organizations must report their data to Nadag within 3 months after the new API is ready in production, and Field Manager will offer a solution to do this in a simple way in good time before that deadline.

We get a lot of questions about the Field Manager Nadag integration, so we thought we would dedicate one of the Christmas calendar posts for this topic.

As you all know, the law states that all ground investigation data gathered after 1.1.2025 has to be reported to Nadag. However, the actual deadline for registering the data into Nadag is 3 months after the Nadag data API is ready in production. This is because there are essentially no effective ways of reporting data today.

The Field Manager team has been working together with NGU since the spring with testing the API and we are now looking forward to seeing this become a reality. Our plan is that you as a user should have a simple and seamless way of reporting data and documents from Field Manager where you have a good overview of reporting status on your projects. This will be be finished in time for the for the delivery deadline.

All your organization's data is accessible through the Field Manager API. This allows you and your organization to develop your own applications for reporting, analysis, interpretation, and more.
 
We have already created some small tools which are free to use, these are available under "API Tools." 

At the Field Manager team, our priority is solving real problems for our users. We identify these needs through multiple channels—user meetings, direct user feedback, demos, interviews, interaction on conferences etc.

When developing a new feature, we start by defining it as a MVP – Minimum Viable Product. This means creating the simplest solution that addresses the core need, and then we are planning for future improvements in a later stage. The first step for a MVP is building a prototype and sharing it with a selection of users for feedback before finalizing the design and moving into development.

How many times have you been asked for a progress update on field investigations or laboratory tests? With our new Dashboard feature, you can now easily keep track of this and share it directly with your client. 📊✨

The dashboard shows not only how many methods have each status, but also the status distribution at the method level, for both field investigations and lab tests. You can, of course, filter by the different statuses as needed. 🔍

We’ve also added status information for lab tests inside the Lab Manager page.