This article captures some of the ideas specifiers shared during the development of tags. It is not an exhaustive list.
By defining and adding tags to articles and clauses, the tagged information can be exported for reporting purposes at different stages of the project lifecycle.
Throughout this guide, where the term 'clauses' has been used, this could be an 'article' in MasterFormat-based specification.
Project strategies
Crucial components of any project – the tags below are grouped around the RIBA Plan of Work project strategies. An alternative would be to define tags around parts of the building regulations. The PM_40_20 classification in Uniclass defines a greater depth if required.
| PS_Conservation | For clauses which impact heritage protection measures. |
| PS_CostPlan | This is for clauses that need flagging for cost management. |
| PS_FireSafety |
For clauses that are relevant to the golden thread of fire safety information. An alternative could be to widen this component by including Building Safety subcategories PS_BS_Fire, PS_BS_Structure, etc. |
| PS_HealthSafety | For clauses relevant to the generation of a health and safety file. |
| PS_InclusiveDesign | For clauses that contribute towards meeting Part M of building regulations and complying with the Equality Act. |
| PS_Planning | For clauses that are relevant to planning submission and approval. |
| PS_PlanForUse | For clauses that are relevant to handover and aftercare. |
| PS_Sustainability |
For clauses that contribute towards achieving sustainable outcomes. An alternative could be to widen this component by including each of the RIBA Plan of Work sustainable outcome subcategories PS_Sus_Biodiversity, PS_Sus_Water, PS_Sus_EmbCarbon, etc. |
Using tags to filter the 'Summary' grid by clauses for project strategies:
- Tag each clause with the relevant strategies.
- Filter the 'Summary' tab by your chosen tag(s).
This screenshot of the 'Summary' grid shows clauses that contribute to achieving sustainable outcomes, which have been tagged for PS-Sust-XXX.
- Use the 'Export summary schedule' to produce an MS Excel report of the project strategy clauses.
A screenshot showing the clauses in the 'Summary' grid can be exported to MS Excel using the' Export summary schedule.
Work packages
From focus groups, there is not much standardization regarding how main contractors package up jobs for subcontractors.
The example below shows how the old CI/SfB system could be used, arguably the most common existing method used based on these discussions.
| WP_22_InternalWalls | For systems/ sections grouped in a package to be delivered by a sub-contractor tendering for the internal walls package. |
| WP_23_Floors | For the flooring package. |
| WP_24_Stairs |
For the stairs package. |
| Etc. |
Using tags to define and publish work packages:
- Tag each section with the work package(s) to which it is allocated. Some sections may be in more than one package.
A screenshot showing a section (Z22) with tags added to represent the different work packages it is assigned to.
- Filter the 'Contents' grid by the work package you want to publish.
A screenshot showing that the 'Contents' grid has been filtered to show only sections tagged with the 'WP-SAN Sanitaryware' work package tag.
- Select the filtered items in the grid > click the 'Actions' menu to publish your selection to an MS Word/ PDF specification.
Contractors design
Where submittals are required as part of the technical design phase, as defined in a descriptive performance specification to brief specialist subcontractor design, the PM_40_25 to PM_40_60 classifications in Uniclass define a greater depth if required.
| CD_Calculations | For clauses defining the requirement for calculations. |
| CD_DetailedDesign | For clauses defining the requirement of plan, section, elevation, 3D designs. |
| CD_Samples | For clauses defining the requirement for product samples. |
| CD_Specification | For clauses defining the requirement for prescriptive specification in response to descriptive performance specification. |
| CD_Surveys | For clauses defining the requirement for surveys. |
Contractors actions
Where submittals and actions are required as part of the construction or handover stage of the project. PM_70 in Uniclass defines a greater depth if required
| CA_Benchmark | For clauses defining a benchmark example of execution. |
| CA_Certification | For clauses defining certification requirements. |
| CA_Commissioning | For clauses defining commissioning requirements. |
| CA_DemoTraining | For clauses defining demonstration or training requirements. |
| CA_EndOfLifeInfo | For clauses defining dismantling, recycling and disposal requirements. |
| CA_Inspecting | For clauses defining inspection, hold point and witness point requirements. |
| CA_MaintenanceInfo | For clauses defining maintenance information requirements. |
| CA_MaintainPostPC | For clauses defining maintenance requirements post-completion. |
| CA_MnfrInfo | For clauses defining manufacturer information requirements such as product data sheets or contact details. |
| CA_Mockups | For clauses defining mock-up requirements. |
| CA_Prototypes | For clauses defining prototype requirements |
| CA_Removal | For clauses defining where items need to be removed following construction. |
| CA_Spares | For clauses defining where spares are required. |
| CA_Testing | For clauses defining testing requirements. |
| CA_Warranties | For clauses defining where warranties are required. |
Collaboration
Where decisions need to be made elsewhere.
| Collab_BuildingServ | For clauses cross-referenced 'tbc with MEP engineer'. |
| Collab-StructEng | For clauses cross-referenced 'tbc with Structural engineer'. |
| Etc. |