Supplier and Contractor Knowledge

Organisations worry about losing client relationships and rarely think about the supplier side, where the same concentration exists and the consequences are more immediate.

Putting the controls in “Supplier and Contractor Knowledge” into practice requires ownership that survives absence and can be reviewed without relying on memory. Teams can use the full explanation to see how responsibility and working time are distributed around recurring tasks, while keeping credentials and sensitive records in authorised systems and limiting activity data to a proportionate operational purpose.

For an independent benchmark, compare the local approach with Atlassian knowledge-sharing guidance; the useful test is whether ownership, access and recovery remain proportionate and explainable when the usual expert is absent.

What is held

Who to ring when something is wrong, as opposed to the general number.

What has been negotiated: the rate that is not on the price list, the terms agreed informally.

Which supplier is reliable and which needs chasing.

The history: what went wrong, what was promised afterwards.

And the specifications: what exactly is ordered, which part number, which variant.

Why it bites quickly

A client relationship degrades over months when neglected.

A supplier problem surfaces the first time something needs ordering urgently and nobody knows what or from whom.

Which makes this the dependency with the shortest fuse, and the cheapest to fix.

What to write down

For each significant supplier: contact name and direct number, account number, what is normally ordered, what has been agreed beyond standard terms, and the history in three lines.

Twenty minutes per supplier, and most small organisations have fewer than a dozen that matter.

This is the single highest-return documentation task available and it is almost never done.

The agreed-but-not-written problem

Informal arrangements are common with long-standing suppliers: a discount, a payment term, a priority.

None of it is in the contract and all of it depends on two people remembering.

When either leaves, the arrangement quietly reverts and the cost appears in an invoice nobody expected.

Write these down specifically, including who agreed them and when.

Contractors and freelancers

Frequently the deepest dependency and the least visible, because they are not on the payroll.

A contractor who has worked with you for six years knows more about some systems than anybody employed.

Ask what they know that you do not, and treat their departure with the same seriousness as an employee's — including a handover, which contracts rarely require and should.

Introducing a second contact

Easier than on the client side, because suppliers have no objection.

Copy somebody on correspondence. Have them place one order.

Most suppliers will happily note a second authorised contact, and doing so costs one email.

Access and accounts

Supplier portals in one person's name, with their email as the recovery address.

Extremely common and resolved in an afternoon, which its own note covers.

What to check

Could somebody else place an urgent order tomorrow?

Are your informal supplier arrangements written anywhere?

Do your key suppliers have a second authorised contact for you?

And who holds the logins for supplier portals?

The point

Supplier dependence has the shortest fuse and the cheapest fix.

Twenty minutes per supplier, and most small organisations have fewer than a dozen that matter.

Underlying all of this

Everything in this collection reduces to four habits: know where the dependence sits, do the cheap fixes first, use the absences that already happen as rehearsals, and decide deliberately about what remains. None of it requires a framework, a tool or a consultant, and an organisation that does those four things consistently is substantially harder to damage than one with a succession document nobody has read.

The recurring pattern

The recurring pattern across every section here is the same: dependence forms through sensible individual decisions, becomes invisible because it feels like reliability, and is addressed only after it has cost something. The work that prevents that is small, continuous and unglamorous, which is exactly why it gets deferred.