How to make project notes in OneNote easy to find again.
Meeting notes, site visits and decisions often end up in OneNote. Why they are hard to find later, and how to set up notebooks so the knowledge stays with the project.

Project notes get lost in OneNote because sections are created per person rather than per topic, notebooks are not linked to the project files and attachments sit inside pages. The fix is one team notebook per project, sections by topic, consistent page titles and clearly marked decisions. An AI that reads OneNote answers questions with the note as its source.
Contents
In many project teams in plant engineering, OneNote is the real project diary. Notes from the customer meeting, photos and bullet points from the site visit, the coordination with the electrical team, the commitment on the delivery date. All jotted down quickly, all saved somewhere.
The problem shows up later. At acceptance the customer asks when the change to the guarding enclosure was agreed. A new project manager takes over and wants to know what was discussed at kick-off. The note exists. Nobody remembers which notebook, which section or which page it is on.
This article explains why OneNote knowledge is so hard to find again, how to set up notebooks in a project more sensibly, and how an AI can answer questions about a project with the note as its source.
Why are project notes in OneNote so hard to find later?
OneNote is fast and flexible. That is exactly what makes it messy in a project, because everyone creates notes in whatever way suits them at the time. Four patterns turn up almost everywhere.
Sections per person. The team notebook has a section called "Martin's notes" and another called "Sabine's notes". Whatever was discussed during commissioning ends up with whoever happened to take notes. To find it, you first need to know who was there.
Personal notebooks. Many notes never reach the team notebook and sit in someone's own OneDrive instead. Colleagues cannot see them. When that person moves to another project or leaves the company, the knowledge is effectively gone.
No link to the project files. The specification is on the network drive or in SharePoint, the bill of materials in the PDM system, the schedule in Excel. The notebook sits alongside, with no project number and no reference to the documents. Search the project folder and you will not find the notes, and the other way round.
Attachments inside pages. A typical case. Someone sends a customer email with the revised specification as a PDF straight from Outlook to OneNote. Now the email and its attachment sit on a page called "Tuesday meeting". The document is missing from the project folder, and the page title gives no clue to what it holds.
Add to that page titles like "Notes", "Phone call" or just a date. OneNote search helps if you know the right word. It helps far less when you want to know what was agreed on a topic.
How should you structure OneNote in a project?
A handful of rules the whole team follows achieves more than any elaborate system. They take seconds when writing and save long searches later.
One team notebook per project, or one section per project. Create the notebook where the project files live and name it with the project number and customer. Permissions and archiving then follow the project.
Sections by topic, not by person. A split like this works well.
- Customer meetings
- Technical clarifications
- Site and commissioning
- FAT and SAT
- Decisions
- Open points
Consistent page titles. Date, occasion, topic, for example "2026-10-14 Customer meeting conveyor system". The page list then reads as a chronicle.
A fixed header on every page. Attendees, decisions, actions with owners, open questions for the customer. Free-form notes come after that. Anyone searching later reads the first few lines and knows whether the page is relevant.
Make decisions visible. Always use the same tag or the same word, such as "Decision". Record who decided and what it relates to.
Originals go into the project files. A revised specification or a drawing belongs in the project folder, with its revision status. The OneNote page holds a reference to it, so there are never two versions of the same document.
Archive at project end, do not delete. The notebook from a finished project is the best source for the next similar one.
Why is good structure on its own not enough?
Even with tidy rules, OneNote remains one source among several. In plant engineering the project status is scattered across Excel, OneNote and email, and someone has to piece it together by hand. Our article on project status in Excel, OneNote and email explains why that takes so long.
Then there is the existing material. The notebooks from past years are what they are, and nobody is going to reorganise them after the fact. Yet that is exactly where the knowledge sits that you need for a similar plant or a complaint.
How does KoAssist make OneNote notes findable?
KoAssist is an AI project assistant for machine and plant engineering. The Knowledge Assistant answers questions about your own documents, including finished projects, and backs every answer with its source.
OneNote is one of its connections, alongside SharePoint, OneDrive, network drives and, if you wish, your Outlook mailbox. KoAssist also reads team notebooks and email attachments on OneNote pages. The customer email with the revised specification, tucked away on the "Tuesday meeting" page, is found just like the note itself.
You ask in your own words, for example "What was agreed about the guarding enclosure during the site visit?" or "When did the customer confirm the new delivery date?". The answer names the note as its source, and you open it and check for yourself. It no longer matters whether the page is in Martin's section or under "Customer meetings".
Three things stay as they are.
- Permissions come from the source. Anyone who cannot open a notebook in OneNote cannot see it in KoAssist either.
- No migration. Your notebooks stay in OneNote, and OneNote remains the master.
- No training on your data. Your notes are not used to train models.
The rest of your project files are connected in a similar way. The article on SharePoint and network drives as project storage shows how that works without a migration.
Where does this help in running projects?
For the status of a running project there is Project Memory, currently in pilot operation. It brings status, next step, open points, decisions and risks together in one place. From emails and minutes, KoAssist suggests changes to the status, and only what someone on the team accepts becomes valid.
If your project notes are currently spread across personal and shared notebooks, the Project Memory page shows how a project's status comes together in one place. If you would like to see it on your own notebooks, book a demo.
Frequently asked questions
More from the blog
Back to overview- 05 November 2026Article4 min
What happens to project knowledge when a quarter of the workforce in machine building retires?
By 2034 about 296,000 employees in German machine building will retire, while only about 118,000 will follow. What gets lost in the project business, and how to keep the knowledge in the project before the experienced people leave.
4 min - 03 November 2026Article7 min
Why does project status in Excel, OneNote and email take so long to pull together?
Open-points list in Excel, meeting notes in OneNote, decisions buried in email threads. Why the project status in plant engineering has to be rebuilt every time, and how it can assemble itself from the sources.
7 min - 26 October 2026Article7 min
How to keep the internal and customer versions of a status report apart
What belongs in a status report for the customer, what never does, and how to produce both versions from the same project status so internal remarks never reach the customer.
7 min
