Specification guidance for construction - Revision history

106.215.19.254 at 13:42, 8 March 2022

2022-03-08T13:42:52Z

← Older revision		Revision as of 13:42, 8 March 2022
Line 4:		Line 4:

	-----		-----
−	# Always edit your specification to reflect your appointment and the selected procurement route~~. Important point~~.	+	# Always edit your specification to reflect your appointment and the selected procurement route.

	<ol start="2">		<ol start="2">

106.215.19.254 at 13:36, 8 March 2022

2022-03-08T13:36:14Z

← Older revision		Revision as of 13:36, 8 March 2022
Line 4:		Line 4:

	-----		-----
−	# Always edit your specification to reflect your appointment and the selected procurement route.	+	# Always edit your specification to reflect your appointment and the selected procurement route. Important point.

	<ol start="2">		<ol start="2">

Designing Buildings at 10:00, 9 September 2020

2020-09-09T10:00:35Z

← Older revision		Revision as of 10:00, 9 September 2020
Line 57:		Line 57:
	* [[What_should_be_included_in_a_scope_of_work%3F\|What should be included in a scope of work?]]		* [[What_should_be_included_in_a_scope_of_work%3F\|What should be included in a scope of work?]]

−	[[Category:Theory]] [[Category:Contracts_/_payment]] [[Category:Design]] [[Category:Procurement]]	+	[[Category:DCN_Guidance]] [[Category:DCN_Specification]] [[Category:Theory]] [[Category:Contracts_/_payment]] [[Category:Design]] [[Category:Procurement]]

Designing Buildings at 11:58, 10 March 2020

2020-03-10T11:58:49Z

← Older revision		Revision as of 11:58, 10 March 2020
Line 41:		Line 41:
	= Related articles on Designing Buildings Wiki =		= Related articles on Designing Buildings Wiki =

−	* Building information modelling.
	* Bill of quantities.		* Bill of quantities.
	* Common Arrangement of Work Sections (CAWS).		* Common Arrangement of Work Sections (CAWS).
	* Comparison of SMM7 with NRM2.		* Comparison of SMM7 with NRM2.
−	* ~~Construction contract~~.	+	* Final specifications.
	* Insulation specification.		* Insulation specification.
	* New Rules of Measurement (NRM)		* New Rules of Measurement (NRM)
Line 56:		Line 55:
	* Standard Method of Measurement (SMM7).		* Standard Method of Measurement (SMM7).
	* Tender documentation.		* Tender documentation.
−	* Temporary works.
	* [[What_should_be_included_in_a_scope_of_work%3F\|What should be included in a scope of work?]]		* [[What_should_be_included_in_a_scope_of_work%3F\|What should be included in a scope of work?]]

	[[Category:Theory]] [[Category:Contracts_/_payment]] [[Category:Design]] [[Category:Procurement]]		[[Category:Theory]] [[Category:Contracts_/_payment]] [[Category:Design]] [[Category:Procurement]]

217.40.11.182 at 10:57, 19 September 2018

2018-09-19T10:57:00Z

← Older revision		Revision as of 10:57, 19 September 2018
Line 10:		Line 10:

	<ol start="3">		<ol start="3">
−	<li>Avoid using the term 'or similar approved' in a specification. If you approve it you are assuming liability for it. Instead use the term ‘or acceptable equivalent’. By accepting an alternative the responsibility for Fitness for Purpose moves to the contractor and the architect's acceptance is for design intent only. If the architect approves, they take back that responsibility. Normally, alternatives are offered for program or cost reasons and the contractor is responsible for the fact that they are providing a different product that must be at least as good quality-wise as the one specified by the architect. If the architect is specifying by description only the contractor is obliged to provide the technical solution which again they have to be responsible for in terms of quality, performance, appearance and fitness for purpose.</li></ol>	+	<li>Avoid using the term 'or similar approved' in a specification. If you approve it you are assuming liability for it. Instead use the term ‘or acceptable equivalent’. By accepting an alternative the responsibility for Fitness for Purpose moves to the contractor and the architect's acceptance is for design intent only. If the architect approves, they take back that responsibility. Normally, alternatives are offered for program or cost reasons and the contractor is responsible for the fact that they are providing a different product that must be at least as good quality-wise as the one specified by the architect. If the architect is specifying by description only, the contractor is obliged to provide the technical solution which again they have to be responsible for in terms of quality, performance, appearance and fitness for purpose.</li></ol>

	<ol start="4">		<ol start="4">

Editor at 10:57, 18 September 2018

2018-09-18T10:57:35Z

← Older revision		Revision as of 10:57, 18 September 2018
Line 1:		Line 1:
−	[[File:Documents.jpg]]	+	[[File:Documents.jpg\|link=File:Documents.jpg]]

	When writing architectural specifications getting the basics in place from the start will help you build a document suitable to your needs. Listed below are some basic rules to follow when writing your next specification:		When writing architectural specifications getting the basics in place from the start will help you build a document suitable to your needs. Listed below are some basic rules to follow when writing your next specification:
Line 37:		Line 37:

	<ol start="12">		<ol start="12">
−	<li>Always allow time to have your specifications proof read.</li></ol>	+	<li>Always allow time to have your specifications proof-read.</li></ol>

−	~~= Find out more =~~	+	= Related articles on Designing Buildings Wiki =
−		+
−	=== Related articles on Designing Buildings Wiki ===	+

	* Building information modelling.		* Building information modelling.

Editor at 10:57, 18 September 2018

2018-09-18T10:57:13Z

← Older revision		Revision as of 10:57, 18 September 2018
Line 1:		Line 1:
		+	[[File:Documents.jpg]]
		+
	When writing architectural specifications getting the basics in place from the start will help you build a document suitable to your needs. Listed below are some basic rules to follow when writing your next specification:		When writing architectural specifications getting the basics in place from the start will help you build a document suitable to your needs. Listed below are some basic rules to follow when writing your next specification:

Editor at 12:09, 21 August 2018

2018-08-21T12:09:48Z

← Older revision		Revision as of 12:09, 21 August 2018
Line 8:		Line 8:

	<ol start="3">		<ol start="3">
−	<li>Avoid using the term 'or similar approved' in a specification. If you approve it you are assuming liability for it. Instead use the term ‘or acceptable equivalent’. By accepting an alternative the responsibility for Fitness for Purpose moves to the contractor and the architect's acceptance is for design intent only. If the architect approves, they take back that responsibility. Normally alternatives are offered for program or cost reasons and the contractor is responsible for the fact that they are providing a different product that must be at least as good quality-wise as the one specified by the architect. If the architect is specifying by description only, the contractor is obliged to provide the technical solution which again they have to be responsible for in terms of quality, performance, appearance and fitness for purpose.</li></ol>	+	<li>Avoid using the term 'or similar approved' in a specification. If you approve it you are assuming liability for it. Instead use the term ‘or acceptable equivalent’. By accepting an alternative the responsibility for Fitness for Purpose moves to the contractor and the architect's acceptance is for design intent only. If the architect approves, they take back that responsibility. Normally, alternatives are offered for program or cost reasons and the contractor is responsible for the fact that they are providing a different product that must be at least as good quality-wise as the one specified by the architect. If the architect is specifying by description only the contractor is obliged to provide the technical solution which again they have to be responsible for in terms of quality, performance, appearance and fitness for purpose.</li></ol>

	<ol start="4">		<ol start="4">
Line 51:		Line 51:
	* Outline specification.		* Outline specification.
	* Performance specification.		* Performance specification.
		+	* Prescriptive specification.
	* Procurement.		* Procurement.
	* Specification.		* Specification.
Line 56:		Line 57:
	* Tender documentation.		* Tender documentation.
	* Temporary works.		* Temporary works.
−	* [[What_should_be_included_in_a_scope_of_work?\|What should be included in a scope of work?]]	+	* [[What_should_be_included_in_a_scope_of_work%3F\|What should be included in a scope of work?]]

	[[Category:Theory]] [[Category:Contracts_/_payment]] [[Category:Design]] [[Category:Procurement]]		[[Category:Theory]] [[Category:Contracts_/_payment]] [[Category:Design]] [[Category:Procurement]]

Editor at 11:52, 21 August 2018

2018-08-21T11:52:41Z

← Older revision		Revision as of 11:52, 21 August 2018
Line 3:		Line 3:
	-----		-----
	# Always edit your specification to reflect your appointment and the selected procurement route.		# Always edit your specification to reflect your appointment and the selected procurement route.
−	# Always start from a solid baseline document. Do not take the last project you prepared a specification for and change the headers and footers. No matter how vigilant you are, mistakes such as naming the wrong project, specifying incorrect materials and other basic errors will creep into your documents.	+
−	# Avoid using the term 'or similar approved' in a specification. If you approve it you are assuming liability for it. Instead use the term ‘or acceptable equivalent’. By accepting an alternative the responsibility for Fitness for Purpose moves to the contractor and the architect's acceptance is for design intent only. If the architect approves, they take back that responsibility. Normally alternatives are offered for program or cost reasons and the contractor is responsible for the fact that they are providing a different product that must be at least as good quality-wise as the one specified by the architect. If the architect is specifying by description only, the contractor is obliged to provide the technical solution which again they have to be responsible for in terms of quality, performance, appearance and fitness for purpose.	+	<ol start="2">
−	# The proper use of defined terms is important in a specification. Check your contract.	+	<li>Always start from a solid baseline document. Do not take the last project you prepared a specification for and change the headers and footers. No matter how vigilant you are, mistakes such as naming the wrong project, specifying incorrect materials and other basic errors will creep into your documents.</li></ol>
−	# Document / section identification should appear on every page in the footer for document control purposes.	+
−	# Avoid putting specification clause numbers on your drawings. The use of product reference codes is recommended which should all be included on a technical reference sheet (T-Sheet) that links the drawings and the specification. This makes life much easier when changes are required.	+	<ol start="3">
−	# Avoid mixing prescriptive and performance specifications, that is, don’t name a very specific product and then provide performance characteristics for that product – this is not necessary and creates the potential for conflict resulting in claims.	+	<li>Avoid using the term 'or similar approved' in a specification. If you approve it you are assuming liability for it. Instead use the term ‘or acceptable equivalent’. By accepting an alternative the responsibility for Fitness for Purpose moves to the contractor and the architect's acceptance is for design intent only. If the architect approves, they take back that responsibility. Normally alternatives are offered for program or cost reasons and the contractor is responsible for the fact that they are providing a different product that must be at least as good quality-wise as the one specified by the architect. If the architect is specifying by description only, the contractor is obliged to provide the technical solution which again they have to be responsible for in terms of quality, performance, appearance and fitness for purpose.</li></ol>
−	# Avoid specifying temporary works – this is the contractor’s responsibility. Just specify the need to protect adequately, not how to do it.	+
−	# Remove names of individuals when specifying products and just provide the company’s details.	+	<ol start="4">
−	# Remove unfinished clauses and terms such as 'if required'. If you are specifying a specific technical solution then you have to specify everything.	+	<li>The proper use of defined terms is important in a specification. Check your contract.</li></ol>
−	# Do not highlight particular clauses by using bold or underlining, as this indicates that the clause is of special importance and there is no such thing in a specification, as by default it indicates that everything else is not so important.	+
−	# Always allow time to have your specifications proof read.	+	<ol start="5">
		+	<li>Document/section identification should appear on every page in the footer for document control purposes.</li></ol>
		+
		+	<ol start="6">
		+	<li>Avoid putting specification clause numbers on your drawings. The use of product reference codes is recommended which should all be included on a technical reference sheet (T-Sheet) that links the drawings and the specification. This makes life much easier when changes are required.</li></ol>
		+
		+	<ol start="7">
		+	<li>Avoid mixing prescriptive and performance specifications, that is, don’t name a very specific product and then provide performance characteristics for that product – this is not necessary and creates the potential for conflict resulting in claims.</li></ol>
		+
		+	<ol start="8">
		+	<li>Avoid specifying temporary works – this is the contractor’s responsibility. Just specify the need to protect adequately, not how to do it.</li></ol>
		+
		+	<ol start="9">
		+	<li>Remove names of individuals when specifying products and just provide the company’s details.</li></ol>
		+
		+	<ol start="10">
		+	<li>Remove unfinished clauses and terms such as 'if required'. If you are specifying a specific technical solution then you have to specify everything.</li></ol>
		+
		+	<ol start="11">
		+	<li>Do not highlight particular clauses by using bold or underlining, as this indicates that the clause is of special importance and there is no such thing in a specification, as by default it indicates that everything else is not so important.</li></ol>
		+
		+	<ol start="12">
		+	<li>Always allow time to have your specifications proof read.</li></ol>

	= Find out more =		= Find out more =
Line 34:		Line 56:
	* Tender documentation.		* Tender documentation.
	* Temporary works.		* Temporary works.
−	* What should be included in a scope of work?	+	* [[What_should_be_included_in_a_scope_of_work?\|What should be included in a scope of work?]]

	[[Category:Theory]] [[Category:Contracts_/_payment]] [[Category:Design]] [[Category:Procurement]]		[[Category:Theory]] [[Category:Contracts_/_payment]] [[Category:Design]] [[Category:Procurement]]

Editor at 11:45, 20 July 2018

2018-07-20T11:45:13Z

← Older revision		Revision as of 11:45, 20 July 2018
Line 4:		Line 4:
	# Always edit your specification to reflect your appointment and the selected procurement route.		# Always edit your specification to reflect your appointment and the selected procurement route.
	# Always start from a solid baseline document. Do not take the last project you prepared a specification for and change the headers and footers. No matter how vigilant you are, mistakes such as naming the wrong project, specifying incorrect materials and other basic errors will creep into your documents.		# Always start from a solid baseline document. Do not take the last project you prepared a specification for and change the headers and footers. No matter how vigilant you are, mistakes such as naming the wrong project, specifying incorrect materials and other basic errors will creep into your documents.
−	# Avoid using the term ~~“or~~ similar ~~approved”~~ in a specification. If you approve it you are assuming liability for it. Instead use the term ‘or acceptable equivalent’. By accepting an alternative the responsibility for Fitness for Purpose moves to the contractor and the architect's acceptance is for design intent only. If the architect approves, they take back that responsibility. Normally alternatives are offered for program or cost reasons and the contractor is responsible for the fact that they are providing a different product that must be at least as good quality-wise as the one specified by the architect. If the architect is specifying by description only, the contractor is obliged to provide the technical solution which again they have to be responsible for in terms of quality, performance, appearance and fitness for purpose.	+	# Avoid using the term 'or similar approved' in a specification. If you approve it you are assuming liability for it. Instead use the term ‘or acceptable equivalent’. By accepting an alternative the responsibility for Fitness for Purpose moves to the contractor and the architect's acceptance is for design intent only. If the architect approves, they take back that responsibility. Normally alternatives are offered for program or cost reasons and the contractor is responsible for the fact that they are providing a different product that must be at least as good quality-wise as the one specified by the architect. If the architect is specifying by description only, the contractor is obliged to provide the technical solution which again they have to be responsible for in terms of quality, performance, appearance and fitness for purpose.
	# The proper use of defined terms is important in a specification. Check your contract.		# The proper use of defined terms is important in a specification. Check your contract.
	# Document / section identification should appear on every page in the footer for document control purposes.		# Document / section identification should appear on every page in the footer for document control purposes.
Line 11:		Line 11:
	# Avoid specifying temporary works – this is the contractor’s responsibility. Just specify the need to protect adequately, not how to do it.		# Avoid specifying temporary works – this is the contractor’s responsibility. Just specify the need to protect adequately, not how to do it.
	# Remove names of individuals when specifying products and just provide the company’s details.		# Remove names of individuals when specifying products and just provide the company’s details.
−	# Remove unfinished clauses and terms such as ~~“if required”~~. If you are specifying a specific technical solution then you have to specify everything.	+	# Remove unfinished clauses and terms such as 'if required'. If you are specifying a specific technical solution then you have to specify everything.
	# Do not highlight particular clauses by using bold or underlining, as this indicates that the clause is of special importance and there is no such thing in a specification, as by default it indicates that everything else is not so important.		# Do not highlight particular clauses by using bold or underlining, as this indicates that the clause is of special importance and there is no such thing in a specification, as by default it indicates that everything else is not so important.
	# Always allow time to have your specifications proof read.		# Always allow time to have your specifications proof read.
Line 34:		Line 34:
	* Tender documentation.		* Tender documentation.
	* Temporary works.		* Temporary works.
		+	* What should be included in a scope of work?

	[[Category:Theory]] [[Category:Contracts_/_payment]] [[Category:Design]] [[Category:Procurement]]		[[Category:Theory]] [[Category:Contracts_/_payment]] [[Category:Design]] [[Category:Procurement]]