The annual Geoteknikkdagen in Oslo is just around the corner! The Field Manager team will be there, of course, so if you have any questions or would like to discuss anything with us, feel free to stop by.

This year, our partners at Symetri will also be joining us. They have developed an AutoCAD Civil 3D integration for Field Manager called Naviate Geotech. If you'd like to learn more about it or see how you can get access to the software, be sure to stop by.

As we did last year, we're also organizing a competition where you, our users, can suggest new features you'd like to see in Field Manager. And just like last year, there will be a prize up for grabs!

See you there!

NGU released its NADAG API on 1 October 2026. This means that data from all site investigations carried out after 1 January 2025 must be submitted to NADAG before 1 January 2027.

You will of course be able to submit this data through Field Manager. The Field Manager team have already made good progress on this upload functionality, but we still need a few more weeks to complete it. We are aiming to release it in late November, giving you more than a month to submit your data before the deadline. We will share more details on how to do this closer to the release.

Please note that the law requires you to submit both the data files themselves and the factual report in PDF format. You will be able to upload the PDF report to Field Manager and submit both the report and the data to NADAG through Field Manager. 

Also note that the law does not cover lab data as separate data files. However, lab.data included as part of the PDF report can/should be reported to NADAG.

For more information about NADAG and the submission requirements, please visit NGU's website: https://www.ngu.no/geologi-og-risiko/pliktig-innmelding-av-data-fra-geotekniske-grunnundersokelser

We have released a new feature called Project Area.

After the project area is defined under "Project Details", Field Manager will help you find all the projects you have access to that contain locations within the defined area under "Linked Projects".

Under "Linked Projects", you can turn these projects on or off and the ones turned on will be visable in the map view. As before, you can also access the data in these linked projects.

The functionality is demonstrated in this video: https://youtu.be/3q-8K5e5nZI

We have now added functionality to add and change the company logo in Field Manager. This can be done by all organization admins through the “Application Admin” page, which can be accessed from the start page.

In the future, we also plan to add the option to change the logo at the project level, allowing a project to have a different logo from the organization

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.

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.