GroundWorks · Sourcing & Negotiation
Sourcing decisions you can defend line by line: every score opens the response behind it.
Shape events, analyse responses and prepare negotiation positions with named decision rights at every award step.
The Workblock
Sourcing & Negotiation · GroundWorks Dealroom
- We already run our events in a sourcing suite. Why add anything beside it?
- Sourcing and negotiation system of work
- 1 reference / 1 defined / 3 roadmap
Modules
- Sourcing pipeline discovery: Convert qualified opportunities into sourcing projects and supplier longlists linked to current eligibility and market records.
- Sourcing event preparation and evaluation: Build event packs, manage responses and structure evaluation around explicit criteria.
- Bid evaluation and award preparation: Normalise responses, apply declared criteria and constraints, compare scenarios and preserve recommendation-to-decision provenance.
- Negotiation preparation: Prepare fact bases, scenarios, positions and concession logic from governed inputs.
- Policy-bounded tactical sourcing execution: Run proven low-complexity RFQs and bounded negotiations end to end inside category, supplier, value and policy limits.
The question, answered
The failure shows at the award. A recommendation is returned because a score has nothing behind it. Risk evidence goes stale after the shortlist and nobody recomputes the affected scenario. Disagreement between evaluators is averaged away instead of put in front of the decision owner. So the team books a meeting, walks the pack line by line, and the award waits on the reconstruction rather than on the decision.
Negotiation repeats the pattern round by round. Before each session the team reassembles the contract baseline, the spend history, the performance record and the concession plan from workbooks and notes. What the negotiator may offer without escalation lives in a delegation memo and in memory. When the supplier moves, nobody can say quickly which positions are still authorised, and an agreed point can lose its evidence on the way into the contract.
We already run our events in a sourcing suite. Why add anything beside it?
The question is fair: the suite earns its place. It publishes the event, collects the bids, scores the responses and records the award. What it does not hold is the decision. The response evidence, the risk inputs, the commercial model, the evaluator comments and the approval history sit in different places, and before every consequential award someone rebuilds them into a pack by hand.
What changes
The recommendation reaches the award authority as one package: scores, responses, risk inputs, dissent and conditions, each opening to its source.
Each proposed move carries its limit, its approver and its expiry. A move outside authority is blocked and routed for a bounded decision.
The award review arrives assembled
The suite closes the event; analysts rebuild the decision in workbooks, inboxes and a pre-award meeting.
Advice stops at the authority line
What a negotiator may offer lives in a delegation memo and in memory, and a persuasive recommendation can read like an authorised position.
The principles it holds to
Recommendation is not commitment
A proposed award and an authorised award are different states with different owners. A drafted negotiating move is advice until the person who holds the delegation uses it. Nothing commits by drift.
The original response is never overwritten
Comparison works on a normalised view while the supplier's original response stays beside it. Every converted figure reproduces from the original and a dated rule, so a challenged ranking is answered from the record.
Dissent survives to the decision
Disagreement between evaluators is part of the decision, not noise. Missing scores, recusals and conflicting comments stay visible in the award package instead of being averaged away.
The records it authors
Negotiation session. A governed negotiation objective, issue model, authority boundary, counterparty exchange and agreement-in-principle trail, distinct from a signed or awarded commitment.
Sourcing event record. The governed event identity, specification, participants, schedule, communications, bid state and fairness controls for a competitive sourcing process.
Sourcing opportunity. A qualified candidate for a sourcing intervention, assembled from strategy, demand, contract, supplier and market evidence with a route, timing and expected outcome hypothesis.
Tactical sourcing case. A policy-bounded, end-to-end sourcing case for eligible low-complexity demand, covering supplier set, quote request, evaluation, negotiation, commitment and downstream reconciliation.
Award scenario. A reproducible bid evaluation and allocation scenario with normalized responses, constraint model, scores, sensitivity, risk and an explicit boundary between recommendation and committed award.
Case records
Durable, owned units of work. Each one holds the condition that opened it, the evidence gathered against it, the proposed action and the committed disposition, and it stays open until the condition is answered.
Decision records
Determinations and the proposals that precede them, each pinned to the exact policy, rule and evidence versions it was made against, and each kept structurally distinct from the action it authorises.
The roles it serves
Execution flow and task definitions are not published. The dossiers name what each Workblock owns and how much of it there is; the definitions themselves travel with a delivery.
Workblocks can be versioned and changed independently, enabling continuous client tailoring.
Sourcing lead
Take an approved need through the event to a commercial recommendation the award authority can act on. What is still missing before this recommendation survives review?
Evaluator
Judge assigned criteria independently and stand behind every submitted score. Where is the evidence for the criterion I am scoring?
Award authority
Decide whether and how to commit the award, with the reason recorded. Can I defend this recommendation line by line, or do I send it back?
Negotiation lead
Own the supplier conversation and commit only inside documented delegation. What may I offer in this round without going back for approval?
Module maturity
1 reference / 1 defined / 3 roadmap, of this Workblock's five business modules.
The rest of the register
- Previous
Intake Management
Every request arrives complete, routed and owned, without manual triage.
Open the Workblock - The map
The GroundWorks map
Five stages and nine domain Workblocks, summarised once, each linked to the register page that holds it.
Back to the map - Next
Contract Lifecycle Management (CLM)
Every clause, control and obligation stays attached to its contract, with a named owner for each one.
Open the Workblock