ROOTby Eagra Labs
Sign inBook a conversation
07 / Deliver

Vendor

A clear route from supplier submission to accepted deliverable.

Organise vendor documentation by company, package, system and configurable folders, then route each submission to the right internal decision-makers.

Operational outcome

Vendors see only their own packages while project teams gain a system-linked register of missing, submitted, rejected and approved deliverables.

07
Core capabilities

What Vendor brings into the thread.

01

Multiple packages per vendor

02

Configurable submission folders

03

Search by vendor and approved system

04

Multi-person approve or reject decisions

How it works

From first action to retained outcome.

  1. 01

    Create the vendor company and package.

  2. 02

    Link the supplied system and configure folders.

  3. 03

    The vendor uploads to its assigned line item.

  4. 04

    Internal approvers inspect and decide.

  5. 05

    Resubmit rejected content while retaining the full history.

Connected by design

Vendor does not become another island.

Systems, people, assignments, records and permissions keep the module connected to the rest of Root.

SystemsMy WorkConstructionAnalytics
Built-in controls

Clarity at the point that matters.

Company-scoped external access

Folder-level traceability

Deep-linked notifications

Retained rejection and resubmission history

← All modules
Next moduleConstruction →
Put Vendor into a connected operating model

Start with the workflow your team already knows.

Book a Root conversation