Price, capability and the tender decision

An essay adapted from my HNC coursework on tendering and procurement.

Begin with the project

A tender price is one part of a much larger decision. The contractor also needs the technical capability, people, resources and financial resilience to deliver the work. A selection process that examines those things together gives the client a more useful basis for choosing whom to appoint.

That was the central argument of my original paper on tendering and procurement. It examined the available tendering methods, the conditions that influence their selection and the evidence needed to evaluate a bid. The question running through it was practical: how does a client turn a set of submissions into a decision that serves the project?

The answer begins before the invitation goes out. The project has particular requirements, constraints and uncertainties. A complex design, a tight programme and a limited pool of suitable contractors each change the task. The tendering strategy has to address that situation rather than simply repeat the method used on the previous job.

Choose how to obtain the offer

Procurement concerns the wider arrangement through which a project is delivered. Tendering is the process of obtaining and evaluating offers within that arrangement. Keeping the two distinct helps clarify which decision is being made. The original paper used the RICS guidance on tendering strategies as a reference for this distinction.

Open tendering allows a broad field to compete. Selective tendering starts with a narrower group considered suitable for the work. Negotiation creates a different relationship again, with a contractor engaged directly. Each route changes how the client obtains and compares an offer.

Two-stage tendering brings a contractor into the process before all the detail and pricing are settled. That makes the second-stage agreement important: early involvement still needs a route towards an agreed scope and price. The practical question is what has been agreed, what remains open and how the parties will resolve it.

Those distinctions are useful because a method's name does not settle whether it suits the project. The client still has to understand the information available, the capability required and the decisions that remain to be made.

Make the submissions comparable

The quality of the decision depends partly on the quality of the information issued. Incomplete documentation creates room for different interpretations. Two bids can appear to concern the same work while allowing for different assumptions, exclusions or levels of detail.

My paper identified documentation as one of the recurring problems in tendering. Drawings, specifications and schedules need to describe the intended work clearly enough for bidders to respond meaningfully. An attractive price is difficult to assess when the scope behind it is uncertain.

Communication belongs to the same problem. Clarifying a question is useful only if the relevant people receive and understand the answer. Document management and digital tools can support that flow, but the process still needs people to keep the information coherent.

Examine the ability to deliver

Evaluation then needs to look across the offer. The original paper considered price alongside technical capability, relevant experience, resources, quality assurance, health and safety and financial stability. These are different questions about the organisation that would carry out the work.

A contractor's experience on similar projects may help explain how it approaches the task. Its proposed resources help explain how the programme could be delivered. Its financial position raises another set of questions about its ability to sustain the work. A price alone cannot answer all of them.

A structured evaluation gives those questions an explicit place in the decision. The priorities should reflect the project, and the reasoning should remain understandable after the immediate selection has passed. A scoring exercise is useful when it makes that reasoning clearer; the number it produces still needs an explanation.

Retain the learning

The paper ended with recommendations around clearer documentation, communication, early contractor involvement, digital information management and feedback after the tender process. The common thread is attention to the conditions around the decision.

A post-tender review provides a chance to ask which information was missing, where bidders interpreted the scope differently and which parts of the process caused avoidable work. Those observations can improve the next invitation and the next evaluation, rather than remaining in the memory of the people involved.

That is the connection I see between procurement and operating systems. Both depend on information that someone can use, responsibilities that can be understood and a clear route to the next action. Tendering brings those questions together at a commercially important moment: choosing the organisation that will deliver the work.

Reading behind the original paper

RICS, Tendering strategies, first edition. Published in July 2014 and effective from January 2015. The essay develops the argument in my original coursework; this historical reference is retained for context.