Trust centre
Editorial policy
This policy explains the publication process Emitronix uses for service information, practical guides, FAQs and other educational website content.
Content record
Last reviewed 23 July 2026
English-language public information
Policy principles
Useful before promotional
Content should answer a real project question in clear language before it presents a service option.
Evidence has boundaries
Business facts, project claims and technical statements must be supported, qualified or withheld.
A named process
Important pages should show their publication or review context instead of implying anonymous authority.
What this policy covers
The policy applies to public service pages, location information, FAQs, construction guides, authority-process explainers and other educational material published on this website.
Commercial page goals do not remove the obligation to keep factual statements clear, useful and proportionate.
Editorial workflow
- Define the user question, intended audience and practical decision the page should support.
- Separate verified company information from general industry explanation and project-specific assumptions.
- Draft in plain language, define technical terms and explain where requirements can vary.
- Check business facts against the verified website business record.
- Request technical review when a page contains safety-sensitive, regulatory, engineering or construction-method guidance.
- Complete a final editorial check for clarity, links, dates, accessibility and unsupported claims before publication.
Sources and factual boundaries
Company contact details, service areas, hours and core service descriptions are maintained in the verified website business record.
Technical or authority-related explanations should rely on suitable primary material where available, such as current authority publications, applicable standards, consultant-issued project documents or manufacturer technical literature. A general website summary must not be presented as a substitute for the controlling source.
- Do not invent projects, clients, testimonials, approvals, awards, licences, certifications or performance statistics.
- Label examples and indicative workflows as examples; do not present them as completed Emitronix work.
- State when an authority, consultant, landlord, master developer or project-specific document must confirm the final requirement.
Authorship, review and AI assistance
A page should identify its responsible editorial owner and, where a formal technical review has occurred, the reviewer role and review date. A role label is not a professional credential and must not imply one.
Digital or AI-assisted tools may support research organization, drafting or quality checks. They do not replace source checking, editorial judgment or appropriate technical review. A human remains responsible for the publication decision.
Updates and commercial independence
Content should be reviewed when a relevant process changes, a material error is reported, a linked source changes, or the page no longer answers its intended question accurately.
Pages may link to Emitronix services or contact options. Those links must not change the standard applied to factual statements, limitations or corrections.