Traceable to the cited material.
The source must support the same subject, scope and timeframe. A source link is not decoration and should not be stretched to justify a broader claim.
PUBLISHING STANDARD
Blancc separates sourced facts, editorial judgement and illustrative models so readers can see what supports a recommendation.
This policy applies to the Blancc insight library. It explains the standard future additions and substantive revisions must meet.
01 / THE STANDARD
Clarity takes priority over search-engine phrasing. A citation does not make an adjacent opinion factual, and repeated wording does not make a claim more reliable.
02 / SOURCE HIERARCHY
Blancc should use a primary source for a material factual claim whenever a relevant primary source exists.
Inspectable code, tools, artefacts, process records or approved project evidence can support claims about what Blancc actually built or observed. The method, date, scope and limitations must travel with any measurable claim. Internal evidence cannot establish an external law, platform rule or market-wide result.
Legislation, regulators, government guidance, standards bodies, original research and official platform documentation are preferred for legal, technical, policy and product facts. The linked passage must directly support the wording used.
Independent research is useful when its author, sample, method, date, conflicts and limitations are available. One study does not become a universal benchmark, and correlation is not labelled as causation.
Specialist reporting and analysis can explain context or lead to a primary source. Secondary commentary does not replace a regulator, original dataset or product owner for a decision-critical fact.
Blancc’s synthesis can help readers make a decision, but it must be presented as a recommendation, framework, heuristic or example. It is not evidence of a client outcome, market average or guaranteed result.
Blancc should narrow, qualify or remove the claim, describe the uncertainty, and prefer the more authoritative current source. A broken link does not automatically make the underlying claim false, but the claim should be re-verified before its next substantive update.
03 / VISIBLE LABELS
A label should appear where a reader could reasonably mistake analysis or a hypothetical scenario for evidence.
The source must support the same subject, scope and timeframe. A source link is not decoration and should not be stretched to justify a broader claim.
A recommendation combines cited facts with Blancc’s interpretation of trade-offs. It should name the conditions that could make another choice more appropriate.
An invented scenario is labelled “Illustrative example.” It cannot use a fictional client, metric or quotation in a way that suggests real work or observed performance.
A score, matrix or calculator explains its inputs, rules and limits. Directional output does not predict cost, compliance, delivery time, ranking or commercial success.
04 / DATES & REVISIONS
Blancc does not change a publication or update date merely to make an unchanged article look recent.
| Signal | When it changes | What stays aligned |
|---|---|---|
| Published | Only when the canonical article first becomes public. | Visible publication history and datePublished. |
| Updated | After a substantive change to facts, method, recommendation, scope, examples or limitations. | Visible date, dateModified, sitemap lastmod and feed data where applicable. |
| Reviewed | After relevant sources and the article are re-checked, even if the conclusion remains unchanged. | The visible review statement; a review does not silently rewrite publication history. |
| Correction note | When an error materially changes meaning or could affect a reader’s decision. | The corrected passage, the correction date and a concise explanation of what changed. |
Spelling, punctuation, accessibility and formatting repairs may be made without presenting the article as substantively new. A material change should be checked against the cited source again, not copied from an older summary.
05 / SOFTWARE & AI
Blancc may use software and generative AI to organise research, test structure, draft wording, edit code or identify questions worth checking.
Generated text is not a source, expert opinion, client quotation, legal interpretation, benchmark or proof of an outcome. Material claims must be checked against inspectable evidence before publication.
Insight articles currently use Blancc as the organisational author. The site does not name an individual editor or human reviewer because no public role, identity and relevant experience have been verified for that attribution.
Software assistance must not create credentials, lived experience, clients, case studies, testimonials, research samples, statistics, quotations, source access dates or review activity that did not occur.
Blancc remains responsible for the material it publishes. Mentioning a tool or model does not transfer that responsibility or imply that the tool endorses the article.
06 / CORRECTIONS
A useful correction identifies the page, disputed wording, reason and strongest available source.
Email hello@blancc.co.uk with the page URL, exact passage, proposed correction and supporting source. Do not include passwords, confidential client material or sensitive personal information.
The disputed wording should be compared with its cited material, the current implementation where relevant, and any stronger primary source. Disagreement with a recommendation is considered separately from a factual error.
Minor typographic fixes may be silent. A decision-relevant factual correction should update the article, its meaningful revision date and a dated note explaining the material change.
If available evidence cannot resolve a dispute, the article should state the uncertainty or remove the unsupported claim rather than manufacture certainty.
The current website opens an email draft but cannot prove that a message was sent or received. Delivery to this mailbox has not yet been independently verified. If email fails, use the contact page or the published WhatsApp route. A monitored corrections inbox and response SLA should not be claimed until they are tested.
07 / LIMITS
Blancc’s guides are general information for planning and discussion, not a guarantee or substitute for advice tailored to a specific situation.
08 / REFERENCE STANDARD
These official Google documents inform the search-facing parts of this policy. They do not replace the source hierarchy for each article’s subject matter.
Policy record. Published and last substantively updated on 16 August 2026. This first version formalises source priority, content labels, date discipline, software-assistance boundaries, correction handling and limitations for the Blancc insight system.