What is a project memory?
A project memory records what has been agreed, decided and left open in a project, every detail with its source. What the term means, how it differs from file storage, wikis and project management software, and what it is for in machine and plant engineering.
A project memory is the continuously maintained status of a project in which every detail points to its source. It holds requirements from the customer specification, decisions from minutes, commitments and dates from emails, open issues and risks. Unlike file storage, it collects what is in the documents, not the documents. Unlike project management software, it records rather than plans.
Contents
Over the months of a project in machine and plant engineering, a lot of knowledge builds up. What the customer requires in the specification, what was agreed differently at the kick-off, which change the customer sent later by email, what was decided in the design review, which date the supplier has confirmed. This knowledge exists, but it is scattered. Part of it is in documents, part in inboxes, part only in people's heads.
A project memory is the place where this knowledge comes together, so that everyone in the project can look it up and check it.
What is a project memory?
A project memory is the continuously maintained status of a project in which every detail points to its source. At any point it answers what applies in the project, and how you know.
Typical contents are:
- Requirements and key data from the customer specification, quotation and order confirmation
- Decisions from minutes and emails, with date and the people involved
- Customer changes with their origin and status
- Dates, deadlines and commitments from the customer and from suppliers
- Open issues with the people responsible
- Risks and what is known about them
The source is what matters. A project memory does not just say "protection rating IP65", but also: changed from the customer specification (IP54, page 18), confirmed by the customer by email on 14 September.
How does it differ from file storage, a wiki and project management software?
| Contains | Maintained | Answers | |
|---|---|---|---|
| Project file storage (network drive, SharePoint, PDM) | Documents | by filing | Where is the document? |
| Wiki or lessons learned | Summaries, often at the end of the project | by hand, rarely | What have we learned? |
| Project management software (MS Project, ERP) | Dates, resources, costs | by project management | When is what planned? |
| Project memory | Applicable details with source | continuously, from the documents | What applies, and how do we know? |
The tools complement each other. File storage remains the source, and planning stays in MS Project or the ERP. The project memory connects both with what happens between the documents. More on where the lines are drawn in the article MS Project, MeisterTask or Excel.
What do you need a project memory for?
Handovers. Whoever takes over a project reads the status instead of working through three weeks of emails. More on this in the article on project handover in plant engineering.
Status meetings. When the status is settled beforehand, the meeting has time for decisions.
Change orders and acceptance. When you claim payment for additional work in a change order, or the customer asks at acceptance, the source of every change and every commitment is there.
Later projects. Anyone quoting a similar project finds what was decided last time, and why.
What does a simple project memory without software look like?
A project profile with a column for the source, an open issues list and a change register, all in one fixed place. That works as long as someone has the time to read emails and minutes and keep the lists up to date. In most teams that is exactly where the bottleneck is.
What is Project Memory in KoAssist?
Project Memory is the project function of KoAssist, the AI agent for machine and plant builders. You upload the customer specification or connect the project folder. KoAssist fills a project profile from it, every detail backed by a reference to the passage in the document. While the project runs, KoAssist reads new documents, emails and minutes and proposes changes to the status, marked as Change, New or Done. Only what someone on the team accepts becomes valid.
Project Memory is currently in pilot operation with existing customers. If you would like to see how it looks on one of your own projects, you can book a demo.
Frequently asked questions
More from the blog
Back to overview- 15 November 2026Article5 min
Can ChatGPT analyse a customer specification?
An 80-page customer specification, and the quotation has to go out by Friday. What ChatGPT does well in the analysis, where it reaches its limits and what to settle before a customer specification ends up in a chat window.
5 min - 15 November 2026Article4 min
Backing change orders in plant engineering: how additional work from customer changes gets paid
Customer changes create additional work, and it only gets paid when it is backed by evidence. What a change order in plant engineering needs, when to submit it and which documents make the difference at the final invoice.
4 min - 15 November 2026Article4 min
How much time does coordination cost in design engineering?
Collecting status, answering questions, preparing status meetings: in design departments, coordination takes up many hours a week. Two cases from special-purpose machine building and a simple method for measuring your own effort.
4 min
