Procurement may have found an attractive price, operations may want a different working arrangement, and legal may request a revised contractual term. If these views meet only at signature, the supposedly agreed bid may turn out to rest on different expectations of the service.
Joint decision-making means each area of expertise provides the necessary information in time and conflicting requirements become visible before bids are requested. In a small business, one person may hold several roles; the questions associated with those roles still need separate answers.
From research to practical application
Heinis and colleagues’ systematic review identifies requirements specification and governance as distinct areas of service procurement, alongside supplier selection. [1] The Sourcing Playbook emphasises collaboration across professions. [2] These sources support examining a service decision from several perspectives; they do not experimentally validate the meeting arrangement below or replace Turkish law with UK guidance.
Let each function complete a different question
Operations should explain the workflow the service will join. What happens at particular times, what client information is required and how do duties interact? Discuss specific tasks instead of asking for a team that “takes care of everything.”
Procurement should ensure that candidates price the same scope. Assumptions, excluded activities and conditions affecting price matter here. Establish whether a lower fee reflects a different definition of service.
HR should contribute its expertise on applicable working arrangements and personnel coordination. Legal should assess authority, contractual responsibilities and relevant requirements. Where technical systems or personal data are involved, bring the relevant technical and data-protection owners into that decision.
Do not leave conflicts in separate email chains
Suppose operations wants longer visitor-admission hours while procurement has obtained bids for the existing hours. Adding “all visitors will be received” to the contract does not resolve the mismatch. Extra time, task allocation and cost effects should be addressed within the same decision.
Move the issue into a short decision record:
- Which two expectations are inconsistent?
- What information is missing?
- How do the available options affect duties and cost?
- Which authorised person will decide, and by when?
This turns disagreement into an issue that can be resolved. Every participant does not need to produce a long report; the reasons supporting the decision are what matter.
Distinguish advice from approval
A technical specialist’s statement that a system can support an arrangement does not establish that its budget is approved or that the arrangement satisfies legal requirements. Record each assessment within its scope. Make clear who takes the final decision and under which conditions.
Similarly, do not treat silence as approval. An unfinished assessment should remain an open item. If the bid deadline or service start depends on it, discuss the timing implications with the responsible decision-maker.
Finish with one shared service definition
The scope issued to bidders, pricing assumptions and client-provided inputs should be consistent at the end of the discussion. Do not keep a revised document only in the procurement file; the people managing implementation should have access to its current version.
Different departments can then avoid purchasing individually plausible but mutually inconsistent versions of the service. The decision reaching signature becomes understandable alongside the organisation’s daily operations and the responsibilities it will retain during delivery.
