From Project Documents to Organizational Knowledge: Lessons from a Year in Project Control

When I graduated with a Bachelor’s degree in Information Systems, I did not expect my first professional experience to teach me so much about information itself.

I began working as a Project Control Administrator (PPC) in mid-2025, about a month after completing my undergraduate studies. Since PPC roles in my work environment were largely associated with engineering and civil engineering backgrounds, I initially imagined that I would spend much of my time in the field, working with quantities and project measurements.

The reality was somewhat different.

My work involved a combination of project documentation, reporting, approval tracking, claim-related work, quantity information, archiving, Excel-based data handling, and coordination with project teams. At first, many of these activities felt unfamiliar. But over time, I gradually became part of the workflow and learned how these pieces of information connect throughout a project.

What initially seemed like administrative work eventually gave me a different perspective on how organizations manage information.

Learning Through Project Control

Project control is not only about monitoring whether work is progressing according to plan.

In practice, it also involves continuously working with information:

What work has been completed?
When was it completed?
How much has been completed?
Which work item or activity does it belong to?
What evidence supports the reported progress?
What is planned next?
Are there any concerns or issues that need to be followed up?

These questions appear simple, but answering them reliably depends on the availability and continuity of project records.

During my first year, I worked with different types of project information and gradually became more aware that the usefulness of information depends not only on whether it exists, but also on whether it can still be found, understood, and connected to the context in which it was created.

When Historical Information Became a Problem

One experience particularly changed the way I thought about project documentation.

At one point, I was asked to prepare historical weekly and monthly project reports for a project that was already approaching completion.

The challenge was that I had not been part of the project during its earlier stages. By the time I joined, much of the project was already underway, and some of the earlier reporting records were incomplete.

The reports needed to describe project progress over time, including information such as daily activities, quantities, completed work items, dates, progress, supporting evidence, photographs, upcoming plans, and concerns.

So I started by looking for whatever information was still available.

I went through the remaining project records and tried to connect the available pieces of information. I compared progress data, quantities, work items, dates, and other supporting records to understand what had most likely happened during the earlier stages of the project.

Some evidence was limited.

Some progress photographs were no longer available. Some of the earlier records were incomplete. The people who had previously handled parts of the project were no longer available to provide additional context, and even the earlier stages of the project had not necessarily been managed by the same person.

As a result, I had to reconstruct the reports using the evidence that remained.

It was not a perfect reconstruction. It could not be, because the original information was incomplete.

Instead, I tried to build the most reasonable representation possible from the available records by comparing different sources and checking whether the information was consistent with the progress that could still be observed from the remaining data.

That experience stayed with me.

Information Has Value Beyond the Moment It Is Created

Before working in industry, I mostly encountered information management through university courses, research, datasets, and academic projects.

Working in a real project environment made the issue feel much more tangible.

A progress record may seem routine when a project is running normally. A daily report may simply feel like another document that needs to be completed. A photograph may appear to be just another piece of project evidence.

But their value can change over time.

When a project approaches completion and someone needs to understand what happened months earlier, those seemingly routine records can become essential evidence.

This made me realize that the problem is not always that an organization has too little information.

Sometimes, the information may have existed but was not preserved in a way that makes it easy to retrieve, interpret, and use later.

Project closeout practices similarly emphasize the importance of preserving project records and historical information for future reference, analysis, and organizational learning.

What Information Systems Looks Like in Practice

This experience also changed the way I viewed my undergraduate background in Information Systems.

At university, I learned about data, information, systems, analysis, and research methods. It was easy to imagine that organizations would naturally have established ways to organize and manage their information.

Industry showed me a more complicated reality.

Organizations operate under different priorities. In a project environment, immediate operational demands may naturally receive more attention than information that appears to have little immediate value.

The importance of some information may only become obvious later.

This does not necessarily mean that an organization is poor at information management. Rather, it made me realize that information management is closely connected to organizational context, operational priorities, and the way work is actually carried out.

That was an important lesson for me as an Information Systems graduate.

From Reconstruction to Prevention

After going through this experience, I started thinking about a simple question:

Why should important project information be reconstructed only when it becomes urgently needed?

If certain information is likely to become important during project review or closeout, perhaps it should already be organized and preserved from the beginning.

Instead of waiting until the end of a project to determine which records are still useful, organizations could establish clearer practices for identifying, retaining, and organizing important information throughout the project lifecycle.

This does not necessarily mean keeping everything.

The more useful question may be:

What information should we preserve, why might it matter later, and how can we make it accessible when it is needed?

This way of thinking gradually moved my attention from simply managing documents toward thinking about information as organizational knowledge.

Connecting Practice with Research

My interest in Artificial Intelligence, Digital Knowledge Management (DKM), and Project Management Information Systems (PMIS) did not begin entirely from this work experience.

I had already encountered these topics through academic research, particularly through studies and examples from international research communities.

However, working in project control gave those concepts a much more concrete context.

I began to see that the challenges discussed in research are not always abstract technological problems. They can appear in ordinary organizational activities: finding historical information, connecting fragmented records, understanding what happened earlier in a project, and ensuring that useful information remains available when people need it.

This experience strengthened my interest in exploring how information systems and emerging technologies can help organizations manage knowledge more effectively.

Artificial Intelligence, for example, may eventually assist organizations in retrieving, organizing, summarizing, or transforming large amounts of project information into more usable forms.

But technology alone is not enough.

The underlying information still needs to be captured, structured, contextualized, and validated.

That is where I see the connection between technology, knowledge management, and organizational decision-making.

Looking Back After a Year

My first year in project control was not what I originally imagined when I graduated.

I expected to learn about project work.

Instead, I also learned about the lifecycle of information.

I learned that information can become valuable long after it is created. I learned that incomplete records can create significant work later. And I learned that the challenge is not always about having more data, but about making sure that the right information can still be found, understood, and trusted when it matters.

Most importantly, the experience gave practical meaning to something I had previously encountered mainly through academic study.

Information is not only something organizations collect. It is something they need to preserve, connect, and make useful over time.

This perspective continues to shape my interest in Artificial Intelligence, Digital Knowledge Management, and Project Management Information Systems as I explore how technology can support better information use and decision-making in knowledge-intensive organizations.

One year in project control, and a different way of seeing information.