Media resources

The techUK brand is one of our most valuable assets and must be used with care. Use of any techUK branding elements—including our name, logo, or visual identity—requires advance review and written approval from techUK. Members and partners may only use these elements in accordance with the guidelines provided by techUK. All materials featuring techUK branding must be submitted to techUK for approval prior to publication or distribution and all unauthorised use is strictly prohibited. For more information and access to our full brand guidelines or to request approval, please contact [email protected].

techUK guest blog guidelines 

Our insights are the main way we demonstrate our influence and put across ours and our members’ opinions. We ask that when developing blogs for techUK, contributors please do so within the below parameters as best as possible: 

• Main body should be 400 to 600 words. 
• Choose a title that is no more than 70 characters. Titles that are any longer may have to be edited before we publish. 
• Please include a 150-character description that includes the author’s name and title. This will appear in a description box. 
• Please break down the different sections of the blog with clear sub-headings If it is appropriate, please include a list to make it easy for the reader to navigate the different sections in the blog. 
• Feel free to use links to other related relevant content that would be useful to the reader. 
• Please share the full name and title of the spokesperson that you wish the piece to be attributed to. 
• Please share with the links to all your social channels (e.g. LinkedIn, X) for promoting the blog on our socials. 
• Please share with us any imagery (spokesperson headshots, etc) that you would like us to include in the body of the blog. 

To maintain the integrity of our blog as providing industry-level opinion and commentary, we ask that blogs also: 

• Avoid describing and discussing the attributes or applications of specific company brands, products or services where possible. This may only be acceptable if they provide an example for a higher-level discussion point that would be of interest to the broader industry and are not discussed in great amounts of detail. 
• Do not take the format of a company case study unless specifically agreed in advance 
• Use hyperlinks so that readers can extend their exploration of the subject matter further Link to recent news and topical subjects. 
• Link to recent news and topical subjects.
• If the blog is for a specific techUK week, make the blog as relevant to the specific subject for your chosen day as possible. 

Please note we cannot accept blogs that have already been published somewhere else. We will only accept blogs that are either original or have text variations from what has been previously published on other websites. This is because it would damage both websites search engine algorithm and searchability, meaning it will be viewed by less people.  

techUK reserves the right to exercise its editorial judgment. Editorial decisions to publish, or not to publish, a submitted article are made at our discretion. If you have any questions or would like to discuss any ideas, please do get in touch with [email protected].

Case studies on the techUK website

Case studies on our website are valuable pieces of content that can showcase real-world applications and successes of our member companies, or their services and products. This is also a valuable asset for members to promote themselves to our network and helps drive deeper engagement with techUK.

Here are some guidelines and tips around publishing case studies on the techUK website:

• Main body should be 400 to 800 words. 
• Choose a title that is no more than 70 characters, or approximately 6 to 12 words. Titles that are any longer may have to be edited before we publish.  
•  Please include a 150-character description, or approximately 20 to 30 words that includes the company name and briefly what the case study will cover. This will appear in a description box on the website.  
• A format we have found to be useful is Challenge, Solution, Barriers, Impact - but this can be adapted as needed. 
•  Use headings, subheadings, and bullet points to organise content clearly if useful, making it easy for readers to scan, navigate and find specific information.   
• Divide content into small, digestible paragraphs (1 to 3 sentences maximum). 
• Feel free to use links to other related relevant content that would be useful to the reader.   
• Please share the full name and title of the spokesperson that you wish the case study to be attributed to if relevant.  
• Please share with us the links to your social channels (e.g., LinkedIn, BlueSky) for promoting the blog on our socials.  
• Please share with us any imagery (company logo, spokesperson headshots, graphics, etc) that you would like us to include in the body of the blog. Please note that we are unable to use copyrighted material unless we are licensed to use it. We will use our own stock imagery to illustrate, except where the imagery is license free, approved and provided by the organisation sharing the case study.

techUK reserves the right to exercise its editorial judgment. Editorial decisions to publish, or not to publish, a submitted article are made at our discretion. If you have any questions or would like to discuss any ideas, please do get in touch with [email protected].