Civil Engineering Reference
In-Depth Information
Process Codifi cation
Dos
Don'ts
Review client's existing systems/codes for
compatibility, applicability and possible
adoption
Ensure code accords with client governance
and fi nancial delegated authorities
Consider the quantity/complexity of the
purchasing requirement when agreeing the
degree of codifi cation required
Codify the pre- and post-contract processes,
e.g. procurement code and contract
administration code
Ensure codifi cation fi ts with the client's quality
assurance processes
Control the development of the code by using
a central resource responsible for agreeing
and implementing amendments
Keep the code simple through the use of
process fl ow/swim lane diagrams
Allow plenty of time to prepare code and to
go through a number of iterations before it is
agreed by all parties
Consider developing a 'supplier guide' to
inform suppliers on the key procurement
processes
Consider preparing a simple 'buyers' guide'
for circulation to 'non-procurement' staff to
explain procurement process and provide
guidance on smaller value procurements
References
Public Contracts Regulations, (2006) Statutory Instruments, 2006 No. 5: Public Procure-
ment, England, Wales and Northern Ireland.
Quinn, D., (2012) 'Driving best-practice procurement processes with eSourcing tools',
London 2012 Games construction project learning legacy paper. http://www.
legislation.gov.uk/uksi/2006/5/pdfs/uksi_20060005_en.pdf (accessed 1 September
2012).
