Use case

Integrating suppliers
into projects

A subcontract that carries the schedule is created in the project as an external service. The supplier gets their own work area for it, is invited automatically by email, and reports status, dates, and files directly on the task. The system reminds them when a report is due – nobody has to chase it by phone.

Linetrack project management software with suppliers integrated into the schedule

In short

In Linetrack, integrating suppliers into projects means this: for a subcontract that genuinely matters to the schedule, an external service is created. That is the area the supplier works in – they see their own requirements, dates, and files, not the overall plan. The invitation goes out automatically by email, collaboration is free of charge for them, and the system itself reminds them when a report is due. What is not mapped is every purchased part: that stays in the ERP.

4000+

completed
industrial projects

1512

projects managed
in parallel

56%

of customers with a live
interface within 6 months

10

working days median to
the first project of their own

*All figures on this page come from a full survey of every productive Linetrack implementation, as of August 2026.

Challenges

Why the supplier stays a blank spot
in the schedule

In most industrial companies the subcontract is a task with a date that somebody maintains by email. Four consequences named repeatedly in onboarding conversations (multiple answers possible).

The external service is a bar with nothing behind it

The plan says “Subcontract welded assembly” with a start and end date. Whether the supplier has started, whether approvals are missing, whether the date still holds – none of that is in the plan. The bar reflects the commitment from the purchase order, not the state of the work.

Chasing dates instead of planning them

The project manager learns the status by chasing it on the phone. 59% of Linetrack customers explicitly named manual status requests as a reason for adopting the system. Every request ties up two people, and the answer is a snapshot that can already be out of date the next day. Across twenty external services and several projects, that becomes a job of its own.

The supplier list lives next to the plan

Dates, contacts, and commitments sit in a purchasing spreadsheet while the schedule sits in another tool. Of more than 400 planning tools replaced at Linetrack customers, the majority were spreadsheets of exactly this kind. Two versions of the truth side by side, reconciled reliably by nobody.

Delay only becomes visible in assembly

If a partner delivers two weeks late, assembly notices first – not the schedule. By the time the shift reaches the plan, downstream tasks are scheduled wrongly and internal capacity is blocked for a period in which nobody can work.

Definition

What is supplier integration in project management?

Supplier integration in project management means running schedule-relevant subcontracted work as tasks of its own in the project plan and letting the external partner work on it themselves: with their own access, assigned requirements, and reports that land directly in the plan. It replaces email coordination alongside the plan with documented date and status data created in the same system the plan lives in. The features available for this are shown on the product page supplier access.

This needs to be distinguished from supplier management as the umbrella term, which also covers selection, qualification, evaluation, and the contractual relationship. This page is only about coordinating dates and tasks inside a running project – in machinery and plant engineering, precisely the part a promised delivery date actually depends on. What is explicitly not meant is a complete picture of procurement: purchased parts and order processing stay in the ERP, and only the services whose progress moves the date go into the project plan.

The decisive point

Chasing dates stops when the supplier reports for themselves

A subcontract task in the schedule carries exactly one piece of information: when the supplier is supposed to be finished. Everything that decides whether that date holds lives in inboxes – the missing drawing approval, the shifted material date, the production manager's holiday at the supplier. The plan keeps a commitment alive until somebody contradicts it.

Supplier integration therefore does not mean knowing more about the supplier; it means letting them write into the plan. Only when the report is created where the planning happens does the schedule become a statement about reality again rather than about a purchase order.

And the prompt no longer comes from the project manager. Linetrack reminds the supplier automatically by email when a report is due; the link takes them straight into their own area, where they enter what has changed. With a handful of partners that saves a few phone calls. Across fifty external services and several parallel projects, it replaces a piece of work that used to come round every week – and how the subcontracted share plays out across a whole portfolio is covered on the multi-project management overview page.

For that to hold, the barrier on the other side has to stay low. Access costs the supplier nothing, they set their own password from the invitation email, and a two-minute video in their area explains what is expected of them. No rollout at the partner, no training course, no project before the project – they are able to work on the day the invitation goes out.

The difference shows at the first deviation. When the supplier reports a two-week delay in the system, it is not only their own task that moves: assembly, commissioning, and acceptance hang off the same dependency logic as internal tasks, and the capacity reserved for them comes up for rescheduling in the same moment. An internal plan with a blank spot at every subcontract becomes a project plan in which external and internal work are equally current.

59%

named manual status requests as a reason for adopting the system

91%

named spreadsheet and tool sprawl as a reason for adopting the system

How it works

From subcontract to report in the overall plan

Working with a supplier runs through five steps – and it starts internally, not with an invitation. Only once the plan stands in your own house is it clear which subcontract needs an area of its own. The features behind it are described on the supplier access product page; this page is about how it plays out in the project.

The last step is the decisive one. A supplier portal that collects reports without them changing the schedule only moves the manual work – from a phone call into yet another tool.

How a reported deviation then feeds into scheduling and capacity planning is described on that page.

Settle internally who owns the partner

The project manager first brings in whoever owns the subcontract – usually purchasing, in some companies the sub-project lead who already talks to the partner directly. That is where integrating the supplier starts.

Create the external service and set the requirements

The subcontract becomes an external service in the project: a fenced-off work area with dates, deliverables, and required documents – hung off the same dependencies as internal tasks.

Invite the supplier – able to work in minutes

The invitation goes out automatically by email. The supplier sets their own password, collaboration costs them nothing, and a two-minute video in their area explains what is expected of them.

The supplier reports progress and dates

Status, dates, comments, files, and their own to-dos are created directly on the task, with a timestamp and an author. The system sends automatic email reminders for open items; the status call disappears.

Deviation propagates into the overall plan

A reported delay shifts downstream tasks, makes affected milestones visible, and shows which internally blocked capacity needs rescheduling.

Rights and security

What the supplier sees – and what they don't

The most common objection to supplier integration is not about dates but about access: anyone letting an external party into the project plan has to control precisely what that party sees. Competitors sit in the same supply chain, and cost calculations belong to nobody outside the company.

The supplier sees only the external service assigned to them – for them, that area is the project: their requirements, their dates, their files and comments. Not visible are the overall schedule, the project portfolio, other suppliers' tasks, internal workload and capacity data, and every cost calculation. The access is a role in the project, not a view into the company.

The platform runs in ISO 27001-certified data centres in Germany. Access is governed by a role and permission system, and every report is documented with a timestamp and an author – so in a dispute the project status no longer has to be reconstructed from an email thread.

System boundary

Purchased parts stay in the ERP – the plan holds what carries the date

Linetrack does not capture every purchased part. Standard parts, small material, and the entire order process stay where they belong: in the ERP or the procurement system. Only the subcontracted work whose progress moves the schedule goes into the project plan – the welded assembly, the control cabinet, the partner's control software, the on-site installation. An overview of all supported ERP and time-tracking systems is available on the page integrations.

That selection is a deliberate decision, not a sync at the push of a button: tipping every order line into the schedule produces not a plan but a second order list. With an interface in place, the data for the selected subcontracts can be taken from the ERP instead of being entered a second time by hand. 56% of Linetrack customers set up a live connection within the first six months; of those, 39% also have an ERP connection. Which systems are typically connected is covered under integrations.

Without an interface the same sequence works manually: the external service is created in the project and the supplier is invited. The interface saves data entry; it is not a prerequisite for integration.

Supplier management in Linetrack with external services for subcontracts

Prerequisites

When integration actually works

Supplier integration is not a starting point but an expansion step. And the resistance rarely comes from your own project – it comes from the other side. A supplier today often juggles ten to twenty customer portals, each with its own login, its own workflow, and its own training. That portal fatigue is named in the literature on supplier onboarding as the main reason reports end up coming by email after all: as soon as an access feels optional or duplicative, the inbox wins.

So anyone asking for one more login has to make it cheaper than email. That the effort pays off is well documented – in a McKinsey survey of more than 100 large companies, those that collaborated with suppliers regularly grew faster and operated at lower cost than their peers. The catch sits in the same study: the effect only arrives after a real upfront investment of time and management attention. Three conditions decide, in practice, whether the reports really come in.

The internal plan comes first. As long as your own scheduling is not dependable, the supplier has nothing to report against. In practice the wish for supply chain transparency only comes up once internal planning is sound.
The barrier at the partner has to stay low. Access is free, set up in minutes, and explained by a two-minute video – no rollout, no installation, no training appointment. That is the answer to portal fatigue.
You have to be able to ask for the cooperation. A partner only reports back if you are in a position to require it. Many customers therefore write cooperation in Linetrack straight into the supplier contract – and start with the few services the end date hangs on.

Process diagram: the project manager sets up the project and brings in project purchasing, together they create the external service and invite the supplier; Linetrack requests status automatically and the report feeds back into the plan. — Steps 1 to 3 happen once per subcontract. Step 4 runs by itself from then on.

Scope

What Linetrack explicitly
does not do here

Linetrack is not a procurement or SRM system. It runs no tenders, qualifies and rates no suppliers, processes no purchase orders, and manages no framework agreements. Anyone looking for those processes needs an SRM – SupplyOn, JAGGAER, or Onventis, for example. Linetrack solves the part that follows: coordinating dates and tasks with the supplier inside a running project.

Task	SRM/procurement system (e.g. SupplyOn, JAGGAER, Onventis)
Tendering and awarding	Core function	Not included
Supplier rating, qualification	Core function	Not included
Purchase orders and framework agreements	Core function	Not included
Purchased parts and order lines	Fully mapped	Stay in the ERP
Supplier dates in the project plan	Delivery date on the order	Own tasks with dependencies
Supplier reporting	Status update on the order	Progress and date on the task
Delay in the overall schedule	Transferred manually	Propagates straight into the plan

The two are not mutually exclusive – quite the opposite. The SRM manages the commercial relationship, Linetrack coordinates the date inside the project. In practice both run side by side, connected through the subcontract. This distinction is set out in full on the supplier management page.

Orientation

Three pages, three different questions

There are three pages on this topic, deliberately kept apart because they answer different questions.

Which features exist?

Supplier access product page

The feature page: the external service as a work area of its own, the onboarding sequence, reporting, and a demo slot.

To the product page

How does it play out in the project?

Integrating suppliers into projects

The use case: from settling internal ownership through the invitation to the effect of a deviation on the overall plan.

You are here

What does it all cover?

Supplier management

The concept page for the umbrella term: which disciplines belong to it, and where the line runs between a purchasing process and project coordination.

To the concept page

FAQ

Frequently asked questions

Still have questions?

Book a slot with our team.

What does supplier integration mean in project management?

Supplier integration in project management means running schedule-relevant subcontracted work as tasks of its own in the project plan and letting the external partner work on it themselves – with their own access, assigned requirements, and reports created directly in the plan. The difference from classic coordination: the status is not collected by the project manager but maintained by the supplier on their own task. That makes the subcontracted share as current in the plan as the internal work.

How is a supplier integrated into a project in Linetrack?

In five steps: the project manager first brings in whoever owns the subcontract internally – usually purchasing, sometimes the sub-project lead. An external service is created for the subcontract, a fenced-off area with dates, deliverables, and required documents. The supplier is invited automatically by email, sets their own password, and then reports status, dates, comments, and files directly on the task. Every deviation immediately affects the dependent tasks in the overall plan. The features behind it are described on the supplier access product page.

Who integrates the supplier – purchasing or project management?

Both happen. As a rule the project manager first brings the buyer into the project area, and purchasing then owns the partner. In companies where project or sub-project leads already speak to the external trades directly, integration runs straight through their planning. Linetrack does not prescribe the ownership; the role and permission model reflects how the company already works.

Are all purchased parts mapped in the project plan?

No, and that is deliberate. Purchased parts, standard parts, and order processing stay in the ERP or the procurement system. Only the subcontracted work whose progress actually moves the schedule goes into the project plan – a welded assembly, a control cabinet, a partner's control software, or the on-site installation. Which systems can be connected is covered under integrations.

What does a supplier see in the project – and what not?

The supplier sees only the external service assigned to them; for them, that area is the project. Visible are their requirements, their dates, their files and comments. Not visible are the overall schedule, the project portfolio, other suppliers' tasks, internal workload and capacity data, and every cost calculation. The platform runs in ISO 27001-certified data centres in Germany, and access is governed by a role and permission system.

How quickly can a supplier start working?

Usually on the day of the invitation. The email goes out automatically, the supplier sets their own password, and finds a two-minute video in their area explaining what is expected of them. There is no rollout at the partner, no installation, and no training appointment – which is precisely what makes the reports actually come in afterwards.

How is the supplier reminded of reports that are due?

Automatically, by email. When a report is due, Linetrack sends a reminder; the link takes the supplier straight into their area, where they enter a status, a date, or a file. The project manager no longer has to chase it by phone. That is where the time saving sits: what is one saved call with a single partner becomes a whole piece of work across dozens of external services and several parallel projects.

What does supplier access cost?

Suppliers work in the project on a free collaboration licence – only internal users are licensed, from €10 per user per month, modular by user count, roles, and the feature modules booked. There is no cost for the supplier.

What does supplier integration require to work?

Two things. First, the internal project plan has to be dependable – as long as internal planning is not sound, the supplier has nothing to report against. Second, you have to be able to ask for the cooperation: access is free and set up in minutes, which keeps the barrier low at the partner, but the commitment comes from the agreement. Many customers therefore write cooperation in Linetrack straight into the supplier contract.

Is Linetrack an SRM or procurement system?

No. Linetrack runs no tenders, qualifies and rates no suppliers, processes no purchase orders, and manages no framework agreements. SRM systems such as SupplyOn, JAGGAER, or Onventis are built for that. Linetrack solves the part that follows: coordinating dates and tasks with the supplier inside a running project. The full distinction is set out under supplier management.

What happens when a supplier reports a delay?

The report shifts their task, and the shift propagates through the same dependencies as it would for an internal task: downstream tasks, milestones, and the end date visibly follow. At the same time it becomes clear which internally blocked capacity is now reserved for the wrong period – the point where this meets scheduling and capacity planning.

Which companies benefit from integrating suppliers into the project plan?

Above all companies that subcontract substantial parts of their scope and whose delivery date depends on those partners' progress – typically machinery and plant engineering, building and energy technology, and construction and infrastructure. The more parallel projects draw on the same suppliers, the more the subcontracted share matters in multi-project management.

Learn more