SharePoint vs modern intranet for transport companies

The clock is 06:12. A driver calls in about a changed delivery procedure. At the terminal, a team leader asks for the latest safety instruction. In the dispatcher's room, the same questions arise again, because no one is entirely sure whether the document in the email, folder or SharePoint is actually the current version.

That is where the debate about SharePoint vs. modern intranet for transport companies becomes concrete. It is not about who has the longest list of features. It is about how quickly employees in operations can find correct information, without calling around, guessing or working on an uncertain basis.

Digitalisation has already moved into companies. According to Statistics Denmark's IT use in companies, reproduced at Evolvous, 92% of companies with at least 10 employees used the internet for collaboration and sharing of information in 2024, while 77% used cloud services. In transport, this makes the choice of platform more sensitive because employees are scattered between office, warehouse, terminal and mobile operations.

When information cannot keep up with operations

A transport company notices information problems before the IT department does. It manifests as repeated calls to the dispatcher, uncertain answers about a procedure and local shortcuts where employees save their own files because they do not trust that the central system is easy enough to use.

This particularly hits frontline employees. Office staff can often live with more clicks, subpages and document libraries. Drivers, terminal staff and warehouse teams cannot. They are in the middle of a task and need the answer now, not after a search through folders with almost identical file names.

The everyday problem looks like this

Three situations recur in many transport organisations:

• The driver on the move lacks the valid instruction in the event of a deviation and ends up calling operations.

• The terminal worker on a shift has not seen an updated operational message because the information was in a place that required active searching.

• The dispatcher spends time answering questions that should already have been resolved digitally.

These are not just minor annoyances. It affects delivery capability, safety and consistency in operations.

When employees do not trust that they can find the right answer themselves, the organisation quickly builds a parallel operation based on phone calls, emails and verbal handovers.

It is an operational decision, not a software project

SharePoint can be perfectly fine as a document repository and collaboration platform. The problem arises when it also needs to be the channel that carries internal communication to employees without a fixed desk spaces. Then technical choices suddenly become operational choices.

In transport, information must not just be found. It must be quickly accessible, relevant to role and location, and usable on mobile. If the platform does not support this in practice, employees fall back on what works under pressure. Typically colleagues, local document copies or old emails.

That is why many companies end up reconsidering whether SharePoint is actually the right front door to operations, or whether it should remain in the background as an archive while a modern intranet takes care of communication, access and daily use.

Why SharePoint often becomes a dead end for transport companies

SharePoint rarely fails from day one. On the contrary. It often starts sensibly with some document libraries, a few team sites and an ambition to gather knowledge. The problem comes later, when everyday life adds layer upon layer of local needs, separate folders and different ways of saving information.

A system for the office, not for the shift change

SharePoint makes sense for employees who work closely with Microsoft 365 all day. For operational staff, the picture looks different. When the workday takes place between ramps, terminals, vehicles and phones, SharePoint often feels like something that has to be dealt with, not something that helps.

The classic signs are easy to recognise:

• The structure grows uncontrollably with folders, subpages and local libraries.

• Users learn workarounds instead of the official path.

• Communication and documents are mixed up, so important messages drown in architecture.

That is exactly where adoption drops. Employees do not use the system based on the intention behind it. They use it based on how little friction they encounter in the current task.

When searching becomes guesswork

The biggest practical problem is rarely that the information does not exist. It is that the employee cannot determine which version is valid.

A search may yield several results with almost the same title. One document is in an old library. Another is shared via a previous link. A third is a local copy. When that happens, the uncertainty moves directly into operations. No one wants to bear the responsibility of choosing the wrong procedure.

Practical rule: If a driver has to think about where a document is likely to be, the information design is already too complex.

Microsoft itself describes an intelligent intranet as “engaging, informative, personalised, and integrated” in its description of modern intranets on SharePoint. This points to an important distinction. Standard SharePoint is strong as a document and collaboration platform, but it requires extra design, governance and often more components to make it function as an actual intranet for operational staff.

The SME reality hits hard

Many Danish transport companies do not have a large internal team to continuously clean up structure, navigation, rights and content. This is not a detail. It is often the main explanation for why SharePoint becomes cumbersome in practice.

According to Colibo's mention of the Danish Business Authority's figures, 99.8% of Danish companies are SMEs, and they account for 63.4% of private employment. For this type of organisation, a ready-made intranet solution is often more realistic than a platform that needs to be shaped and maintained over time.

An industry solution for logistics and transport typically makes more sense when the need is simple access to messages, procedures and work links across locations. Not because SharePoint is useless, but because operations rarely have the patience for a system that only becomes good after lengthy configuration.

Characteristics of a modern intranet built for operations

An intranet for transport must function in the midst of shift changes, delays and changed instructions. If a driver has to go through several menus to find a procedure, the system will quickly be bypassed in favour of a call to the dispatcher or a message in an old thread. That is where the difference is felt in practice.

The mobile is the workplace

For many in transport, the mobile is the primary access to internal information. Not a supplement. Drivers, terminal staff and temp workers do not stand in front of a PC when they need to find an instruction, see an operational message or open a work link.

Therefore, a modern intranet must be built for mobile first. Buttons must be easy to tap. Messages must be readable in a few seconds. Important links must be visibly placed without requiring logins through multiple layers or knowledge of the company's folder structure.

I have seen what happens when the mobile experience is an afterthought. Employees stop looking in the system. They call instead. This moves the work from the platform back to dispatch and middle management.

Relevant content beats more content

Frontline employees quickly lose trust in an intranet that shows everything to everyone. A driver in Taulov needs to see what applies to Taulov, the route and the day's operations. Not five general posts, two HR updates and an old message from another terminal.

A workflow intranet must therefore be tailored to everyday life:

• News and messages are shown by role, location or team

• Critical changes stand out clearly from ordinary information

• Procedures and instructions are consolidated in a simple structure

• Important work links are accessible from the homepage on mobile

This is also why features like communication, knowledge sharing and access to daily work tools mean more than long lists of technical capabilities. In operations, what counts is whether people can open, understand and use the system without training.

A good operational intranet reduces the number of calls about information that should be easy to find.

Fewer documents. More control

In transport, the problem is rarely a lack of documents. The problem is doubt about which version is valid. When there are multiple almost identical instructions, or when a local copy lives on in email and in downloads, errors occur out in operations.

A modern intranet should make the valid version clear, archive old editions away from the daily view and present the content as instructions rather than a file archive. This is particularly important for quality, safety and customer requirements, where incorrect practices quickly become costly.

Operations, data and daily maintenance are connected

Hosting and data sovereignty are not just questions for IT or legal. It also affects how simply the system can be kept running in everyday life. If the platform requires special considerations, extra administration or permanent compromises in the way the company works, the bill lands with operations.

Therefore, the choice should be assessed based on three very concrete factors. Can employees use it from their mobiles without difficulty? Can the content be kept updated without a large internal team? And can the company live with the operating model that comes with it?

If the answer is no to just one of these points, the intranet becomes yet another system that the office defends, but the floor works around.

From slow search to instant access to procedures

The most tangible difference between SharePoint and a modern intranet is evident in procedures. Not in presentations, but in situations where an employee must act correctly immediately.

Before, finding a procedure was detective work

A driver is faced with a changed delivery procedure. In the old setup, the work often starts in the wrong place. First a search. Then a click into a library. Then doubt about whether the document is recent enough. Finally, a call to the dispatcher, who either sends a link or reads the procedure out over the phone.

This is not just slow. It also creates a culture where employees learn that the quickest answer is not found in the system, but from a colleague.

A typical scenario looks like this:

After, the intranet becomes a workflow path

In a better model, the most important procedures are compiled with clear categories, visible shortcuts and access from mobile. The employee opens the intranet, searches for the concrete task and gets the valid instruction immediately.

The difference is greater than it looks. When operational staff can find the right version themselves, the pressure on managers, dispatchers, HR and support functions drops. At the same time, it becomes easier to ensure that the entire organisation works from the same practice.

When procedures become easy to find, many of the questions that previously looked like communication problems turn out to have been access problems.

This also changes safety work. Not because the platform itself makes employees more cautious, but because it removes doubt in the moment. The employee in that situation does not need to first find the person who might know the answer.

Three practical benefits recur:

• Fewer local document copies because the central version is actually the easiest to use.

• Less disruption in operations because questions do not have to go through several levels.

• Greater self-reliance among employees who previously depended on telephone, email or verbal answers.

This is the type of change that makes an intranet valuable in transport. Not as another information channel, but as the direct path to correct action.

Integrations that simplify everyday life for all employees

The most useful intranet is rarely the one that integrates the most. It is the one that brings together the few things employees actually use every day.

Start with access, not with ambitions

Many projects go wrong because the organisation tries to gather everything from the start. This creates long timelines, technical custom requests and a launch where users encounter something that looks impressive on the drawing board, but is unmanageable in practice.

A better approach is to start with the areas where friction is most obvious:

• Microsoft 365 must be easily accessible because many documents, meetings and collaboration spaces are already located there.

• Document management must be simple, so procedures, HR material and safety instructions are found in the same place.

• Operational-critical links to route planning, duty rosters, quality systems and reporting must be a natural part of the workday.

The crucial thing is not whether each system is deeply integrated. The crucial thing is whether the employee experiences one unified entry point.

The common starting point works better than yet another system

When the intranet becomes the place where the workday starts, the need to remember bookmarks, old emails and local shortcuts drops. This is particularly valuable for employees who do not work in a fixed pattern in front of a PC.

For companies with specific data requirements, the choice is also more nuanced than cloud versus non-cloud. As described by Jint on the difference between SharePoint Online and on-premise, the choice between SharePoint Online and on-premise involves a compromise between operational burden and data control. In this context, a platform-agnostic solution with the possibility of EU hosting or on-premise can be more practical, because the company is not technically locked into the same setup as the rest of the collaboration tools.

This also applies to vendor selection. Some organisations choose to let SharePoint remain the document engine in the background and place a simpler intranet on top. Others choose a stand-alone solution. Colibo is one example of a platform that can function independently and simultaneously connect to existing environments. The name of the product is not important. What is important is whether the integrations make the workday simpler for the driver, the terminal and the dispatcher.

Poor integrations just shift complexity around. Good integrations hide it.

How to measure whether the investment pays off

Many measure intranets with the wrong lenses. If the focus is only on page views and total visits, it becomes difficult to see if the platform actually helps operations.

Visitor numbers tell too little

A high visit rate can hide several problems. Employees may visit the intranet frequently because they are looking in vain. They may open the same document multiple times because they are unsure of the version. They may click around without finding what they need.

The more interesting question is therefore: Did the work become easier?

This is rarely best seen in traditional web metrics. It is seen in behaviour and in the questions the organisation stops receiving.

The metrics that reveal real value

The most useful metrics in transport are typically a combination of platform data and local feedback:

• Active users across roles shows whether the solution is actually used by both the office and the frontline.

• Read rates of targeted messages reveals whether important updates reach the right teams.

• Mobile use says more than desktop use when large parts of the workforce are on the move.

• Searches and document views make it clear which procedures employees are actually requesting.

• Fewer repetitive questions to managers, HR and dispatchers is a strong sign of increased self-reliance.

Qualitative feedback should also carry heavy weight. Ask local managers, key users and employees if information feels easier to find, more relevant and more timely. That type of answer often says more about adoption than a dashboard does.

A simple way to structure the evaluation is this:

When evaluating the financial side, the hidden operational time should also be calculated. An intranet business case calculator can be useful as a framework for comparing licensing, implementation and the daily costs of poor information access. The real gain often shows in fewer interruptions, fewer local document versions and an organisation where employees can act faster without compromising on correctness.

The clearest sign of return is simple. The intranet does not become something employees talk about. It becomes something they use because it works.

If SharePoint has become more of an archive than a working tool, it is worth looking at whether a modern intranet is a better fit for operations. Colibo is one of the solutions built for internal communication, mobile access and daily use across locations, without the company needing to redo its entire existing tool stack all at once.