An Ankara business may have agreed a start date for its security service. If access to the working post, the approved visitor-notification method or the person authorised to make daily decisions is still unresolved, a completed staffing plan does not mean preparation is finished. Service commencement also depends on inputs from the client.
Identifying these inputs should not become a way to transfer the provider's responsibilities to the buyer. The aim is to show which party owns each preparation activity and how subsequent work depends on it. Without an owner, both sides may assume the other will complete it.
Service procurement extends beyond provider selection
Heinis and colleagues' systematic review identifies requirements specification, governance and service production as distinct research domains within services procurement. [1] It does not experimentally validate the matrix below, but provides a conceptual reason to connect purchasing decisions with preparation for delivery.
HSE's contractor guidance also addresses information provision and cooperation. [2] Without treating UK guidance as Turkish law, those topics can generate practical questions for the preparation discussion between client and provider.
Define an input as a deliverable
Replace “necessary information will be provided” with an explanation of which information is required, for which authorised role and by when. The person deciding visitor admission, access to the working post and the client contact for technical problems are separate inputs.
An input may be a document, approval, usable workspace or piece of equipment. What matters is establishing how completion will be recognised. Sending a contact list, for example, is different from confirming that the people listed are authorised for the responsibilities assigned to them. The client representative preparing the list should address that distinction.
Build the matrix with six fields
- Input: What exactly is expected from the client?
- Owner: Which role will prepare and update it?
- Recipient: Which authorised responsibility requires it?
- Readiness criterion: How will completion be demonstrated?
- Date: Before which service step is it needed?
- Open issue: If incomplete, whose decision or which action is awaited?
Do not automatically assign every row to the procurement manager. Facilities management may own a technical preparation, the relevant department may supply contact information, and an authorised representative may resolve a contractual issue. One person can perform several roles in a small business, while the expected outputs remain distinct.
Try a commencement example
Suppose the client will supply a computer at a post. Before marking it as delivered, establish its intended task, who will prepare authorised access and who provides support. Sharing common or personal passwords should not be accepted as an automatic part of preparation.
Connect the provider's own preparation responsibilities to the same timetable. If a client input is late, the next activity affected becomes visible. Instead of reporting only that a delay exists, identify which input is holding up which step.
Turn incomplete preparation into an explicit decision
As the start date approaches, review unresolved inputs together. If an interim arrangement is appropriate, record who approved it, what it covers and when it ends. A required permission, safety condition or legal requirement should not be treated as satisfied merely to meet a date.
The matrix need not be discarded once service starts. Update the relevant row when a client contact, workspace or information flow changes. Service reviews can then consider the currency of the preparations the client undertook to provide, alongside the provider's delivery.
