K-Rend is a household brand name associated with the application of scratch or monocouche render to a property. This product has a scraped texture or finish and should strictly be applied directly to a masonry wall including brick, block or an existing rendered surface. When installing the K-Rend scratch render, there is no better solution that choosing the K1 Silicone scraped texture.
In this blog we look at different ways that the K-Rend K1 Silicone scraped texture can be installed to different masonry substrates.
An existing brick wall is probably the most common type of masonry structure in the UK. It is still the most popular way to finish an external wall by using decorative brickwork to finish off the construction. Now some brick walls in the UK are well over 100 years old and over time some brickwork tends to weaken and lets in penetrating water. The water coming through the wall can cause issues to internal plasterwork and other problems to the property.
To avoid these problems, the K-Rend K1 Silicone scraped finish is enhanced with “silicone”, which creates a barrier to rainwater – helping prevent further damage to the brick.
The first step of the K1 Silicone K-Rend installation process is to get a good sense of the wall that is going to be worked on. Using the beading, namely 14mm-16mm beading profiles for stops, corners and drips – install them onto the walls that are due to be rendered. Do not use spray foam to hold the beads in place as this may cause product performance issues further down the line – we recommend using a small amount of the cementitious product to hold the beads in place.
The substrate may then require further preparation, including a fungicidal wash and a substrate primer. Substrate primers typically work in two ways – firstly they help aid adhesion between the substrate (in this case brick) and the render being applied. They also help regulate the moisture absorption by the brickwork, giving time for the render / basecoat to cure correctly. When applying K1 Silicone K-rend to a brick surface we would recommend using the K-Rend R7 Acrylic Primer. This can be applied mechanically with a spray machine or using a roller/ brush.
When the R7 Acrylic Primer has dried, we would then apply the K-Rend HP12 Base Coat with the alkali resistant fibreglass mesh. The HP12 is probably K-Rend’s most well known polymer modified basecoat product, that is robust enough to use on a number or preparation or undercoat application processes.
The HP12 Base Coat should be mixed water, using the appropriate water content on the back of the bag. It can then be applied with the rendering tools. If you are using a spray machine, then use the water pressure settings as recommended. In this installation the HP12 should be applied 6-8mm thick in one pass. You then cut the fibreglass mesh and place it into position on top of the spread-out basecoat.
Before putting on the scraped coat you must ensure that this HP12 Base Coat layer is fully dry. The fibreglass mesh needs to sit close to the surface of the base coat build-up. When embedding the mesh, ensure each strip overlaps at least 100mm on the edges. If you come across any openings like the windows, door or even surface boxes, then use additional fibreglass mesh in each corner to act as reinforcement patches. These need to be applied in every corner and should sit at 45 degrees to the opening, and remember these are on top of the strips of overlapping mesh!
You may ask what the purpose of the mesh is at this point? Well – it helps with the render’s structural integrity and also ensures the final K1 Silicone scratch coat has a solid surface to bind to.
When the mesh is in position, use a scarifier tool to make scratches in the surface of the HP12 basecoat, which would ensure the substrate would provide a nice key.
Having waited a good 24-48hours for the HP12 to set, you are now ready to apply the final K1 Silicone scratch render.
Mix the K-Rend K1 Silicone scratch powder in a bucket with the appropriate amount of water if you are looking for a hand-application. For machine use, follow the instructions on the bag and ensure you have set the machine to the correct settings. The product is then ready for the application.
Apply the K1 Silicone scratch render onto the substrate liberally trying to achieve a thickness of 10-12mm on the wall. Using an I-bar or a speed skim level off the surface so that the lines have been flattened out. The K1 Silicone scratch render needs to be firm, but not completely dry before the next stage can be completed, so we normally recommend going back to site the next day to produce the final finish.
Using the scratch pad or the scraped trowel take off approximately 2mm off the surface of the K1 Silicone render to leave a nice scraped finish. Take off any dust residue with a brush.
Obviously use your judgement and in the colder months you many need to wait a little bit longer for the product to set properly for it to be scraped off.
Building new construction like extensions requires the use of dense blockwork (7N or above) rather than brickwork, which tends to be quite expensive. It is very popular to the finish the external layer of this blockwork with the K1 Silicone render, taking costs out of the construction process.
The initial preparation of the K1 Silicone K-Rend installation process is very similar to when installing the product onto brickwork. Using the stop bead, corner bead and bellcast bead pin them to the walls in the appropriate sections. You can use 14mm, 15mm or 16mm beading profiles for this job. Do not use pink grip or spray foam, rather try and use some of the product, namely the HP12 basecoat or the K1 Silicone scratch render to stick them off. If you are doing this, you need to make sure you leave the product to set a bit prior to the application of any other layers.
If you are worried about substrate suction given the new blockwork in place then use K-Rend R7 Acrylic Primer. This will help with the product work time and allow the applicator to properly skim it. The primer can be applied mechanically with a spray machine or using a roller/ brush. Allow this to dry.
Then use the K1 Silicone render bag and mix it with the correct water content – use a paddle mixer. If you are using a spray machine, then follow the correct machine settings according to bags. The first pass of the K1 Silicone render should be 8mm thick. In this layer you will need to cut up the alkali resistant fibreglass mesh and install it into the product. Make sure that when installing the mesh, it is overlapped at least 100mm on each edge and additional reinforcement is installed around openings.
You do not need to fully push the mesh through as another layer of K1 Silicone render will be applied on top as the finishing coat. You may choose to notch or scratch the surface with a scarifier to provide a better key for the next part of the install process.
Remix the K1 Silicone render or set the machine again to the same settings. When the product is ready to apply or spray you ensure that approximately 10mm of product applied in this second pass. Do not allow the first layer to dry out or fully set – this step should be performed “wet-on-wet”.
When the 10mm thickness has been achieved, then level off the surface. You can use a range of tools to do this. We recommend using a spatula trowel, an I-bar or a speed skim leveller. You should then wait up to 24 hours for the product to set before attempting to scrape this off the wall.
Using a scrape tool or scratch pad, take off the 2mm of skin formed on the surface of the product taking back to the beading profile. If you have used 16mm beads then this will be taken back to the 16mm depth. When scratching off the surface try to use your judgement and in the warmer months you many need to work quicker, because if the product hardens off too much, it maybe tricky to work with the following day.
You may also render onto lightweight blockwork or clay blocks, but you may need to use a slightly different basecoat to help with this installation process. We recommend using the K-Rend HPX basecoat product but be aware that this is not always in stock, so check with us instore or on the phones to that we may suggest any alternatives.
However, the installation process would be very similar if installing to common brickwork.
Cookie | Duration | Description |
---|---|---|
__stripe_mid | 1 year | This cookie is set by Stripe payment gateway. This cookie is used to enable payment on the website without storing any patment information on a server. |
__stripe_sid | 30 minutes | This cookie is set by Stripe payment gateway. This cookie is used to enable payment on the website without storing any patment information on a server. |
_GRECAPTCHA | 5 months 27 days | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
apbct_cookies_test | session | CleanTalk sets this cookie to prevent spam on comments and forms and act as a complete anti-spam solution and firewall for the site. |
apbct_page_hits | session | CleanTalk sets this cookie to prevent spam on comments and forms and act as a complete anti-spam solution and firewall for the site. |
apbct_prev_referer | session | Functional cookie placed by CleanTalk Spam Protect to store referring IDs and prevent unauthorized spam from being sent from the website. |
apbct_site_landing_ts | session | CleanTalk sets this cookie to prevent spam on comments and forms and act as a complete anti-spam solution and firewall for the site. |
apbct_site_referer | 3 days | This cookie is placed by CleanTalk Spam Protect to prevent spam and to store the referrer page address which led the user to the website. |
apbct_timestamp | session | CleanTalk sets this cookie to prevent spam on comments and forms and act as a complete anti-spam solution and firewall for the site. |
apbct_urls | 3 days | This cookie is placed by CleanTalk Spam Protect to prevent spam and to store the addresses (urls) visited on the website. |
AWSALBCORS | 7 days | This cookie is managed by Amazon Web Services and is used for load balancing. |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
ct_checkjs | session | CleanTalk–Used to prevent spam on our comments and forms and acts as a complete anti-spam solution and firewall for this site. |
ct_fkp_timestamp | session | CleanTalk sets this cookie to prevent spam on the site's comments/forms, and to act as a complete anti-spam solution and firewall for the site. |
ct_pointer_data | session | CleanTalk sets this cookie to prevent spam on the site's comments/forms, and to act as a complete anti-spam solution and firewall for the site. |
ct_ps_timestamp | session | CleanTalk sets this cookie to prevent spam on the site's comments/forms, and to act as a complete anti-spam solution and firewall for the site. |
ct_sfw_pass_key | 1 month | CleanTalk sets this cookie to prevent spam on comments and forms and act as a complete anti-spam solution and firewall for the site. |
ct_timezone | session | CleanTalk–Used to prevent spam on our comments and forms and acts as a complete anti-spam solution and firewall for this site. |
elementor | never | This cookie is used by the website's WordPress theme. It allows the website owner to implement or change the website's content in real-time. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
__zlcmid | 1 year | This cookie is used by Zendesk live chat and is used to store the live chat ID. |
bcookie | 2 years | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID. |
bscookie | 2 years | LinkedIn sets this cookie to store performed actions on the website. |
lang | session | LinkedIn sets this cookie to remember a user's language setting. |
lidc | 1 day | LinkedIn sets the lidc cookie to facilitate data center selection. |
UserMatchHistory | 1 month | LinkedIn sets this cookie for LinkedIn Ads ID syncing. |
Cookie | Duration | Description |
---|---|---|
__utma | 2 years | This cookie is set by Google Analytics and is used to distinguish users and sessions. The cookie is created when the JavaScript library executes and there are no existing __utma cookies. The cookie is updated every time data is sent to Google Analytics. |
__utmb | 30 minutes | Google Analytics sets this cookie, to determine new sessions/visits. __utmb cookie is created when the JavaScript library executes and there are no existing __utma cookies. It is updated every time data is sent to Google Analytics. |
__utmc | session | The cookie is set by Google Analytics and is deleted when the user closes the browser. It is used to enable interoperability with urchin.js, which is an older version of Google Analytics and is used in conjunction with the __utmb cookie to determine new sessions/visits. |
__utmt | 10 minutes | Google Analytics sets this cookie to inhibit request rate. |
__utmv | 2 years | The __utmv cookie is set on the user's device, to enable Google Analytics to classify the visitor. |
__utmz | 6 months | Google Analytics sets this cookie to store the traffic source or campaign by which the visitor reached the site. |
sib_cuid | 6 months | Purechat uses this cookie to send data to purechat.com, to connect visitors to the reservation team and track visitors to stay on portal. |
SRM_B | 1 year 24 days | Used by Microsoft Advertising as a unique ID for visitors. |
Cookie | Duration | Description |
---|---|---|
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_gat_gtag_UA_61069204_2 | 1 minute | Set by Google to distinguish users. |
_gat_UA-61069204-2 | 1 minute | A variation of the _gat cookie set by Google Analytics and Google Tag Manager to allow website owners to track visitor behaviour and measure site performance. The pattern element in the name contains the unique identity number of the account or website it relates to. |
_gcl_au | 3 months | Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
_uetsid | 1 day | This cookies are used to collect analytical information about how visitors use the website. This information is used to compile report and improve site. |
CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
Cookie | Duration | Description |
---|---|---|
_fbp | 3 months | This cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website. |
ANONCHK | 10 minutes | The ANONCHK cookie, set by Bing, is used to store a user's session ID and also verify the clicks from ads on the Bing search engine. The cookie helps in reporting and personalization as well. |
fr | 3 months | Facebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin. |
MUID | 1 year 24 days | Bing sets this cookie to recognize unique web browsers visiting Microsoft sites. This cookie is used for advertising, site analytics, and other operations. |
NID | 6 months | NID cookie, set by Google, is used for advertising purposes; to limit the number of times the user sees an ad, to mute unwanted ads, and to measure the effectiveness of ads. |
test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
uuid | 6 months | MediaMath sets this cookie to avoid the same ads from being shown repeatedly and for relevant advertising. |
VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt.innertube::nextId | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
yt.innertube::requests | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
Cookie | Duration | Description |
---|---|---|
_clck | 1 year | No description |
_clsk | 1 day | No description |
_uetvid | 1 year 24 days | No description available. |
AnalyticsSyncHistory | 1 month | No description |
apbct_pixel_url | session | No description |
apbct_visible_fields_0 | session | No description |
apbct_visible_fields_1 | session | No description |
apbct_visible_fields_10 | session | No description |
apbct_visible_fields_2 | session | No description |
apbct_visible_fields_3 | session | No description |
apbct_visible_fields_4 | session | No description |
apbct_visible_fields_5 | session | No description |
apbct_visible_fields_6 | session | No description |
apbct_visible_fields_7 | session | No description |
apbct_visible_fields_8 | session | No description |
apbct_visible_fields_9 | session | No description |
ct_checked_emails | session | No description |
ct_has_scrolled | session | No description |
ct_mouse_moved | session | No description |
ct_screen_info | session | No description |
ictf_master | never | No description available. |
li_gc | 2 years | No description |
m | 2 years | No description available. |
SM | session | No description available. |
testinfinitycookie | session | No description |
woocommerce_show_tax | 7 days | No description available. |
wp_woocommerce_session_c5ac76b408021294cb56bcc27eddf8a1 | 2 days | No description |
4 thoughts on “Best way to install K1 Silicone K-Rend scratch render”
existing sand and cement render on thermalite 7n blocks cracked and hollow , hacked off blockwork has cracks, want to apply k- rend, what is recommended in this situation?
Hi Andre, you’d probably need to get the blocks checked by a structural engineer first. We’d then recommend a thin coat render system like Silicone Render; much less likely to crack and it offers great weather resistance. You can use a levelling mortar for very minor cracks but anything larger could impact structural integrity.
Hi.. i have a job with 3 substrates..
1. Hardie backer cement board
2. 7n block work
3. Brickwork.
Customer wants a colour top coat and all to be scratch finish.
Hi Kevin, you’ll need our Monocouche Render to achieve a scratch finish. Monocouche Scratch Render