▶FPV SCHOOL← Back to homeLegal hub

Editorial Process

EditorialUKLast reviewed: February 2026FPV SCHOOL LIMITED · Company No. 15817837 · ICO: ZB796938

Editorial Process (Master Page)

Last updated: 02 February 2026

This Editorial Process explains how content across the FPV School Hub ecosystem is planned, researched, created, reviewed, corrected, and maintained.

For the master index of legal policies and site-entry links, see:
/legal

Related:

1. Purpose and principles

This Editorial Process is designed to:

  • prioritise learner value, safety, and clarity over search-engine tactics;
  • keep content accurate, original, and responsibly maintained;
  • be transparent about how we research, write, edit, and monetise content;
  • reduce misinformation risk in safety-critical FPV/drone topics.

Our baseline principles are:

  • usefulness first (help real users do real things safely);
  • accuracy and accountability (correct errors when found);
  • transparency around commercial relationships;
  • respect for intellectual property and user privacy.

2. Scope (what this covers)

This process applies to content published across FPV School properties, including:

  • articles, guides, and documentation pages;
  • checklists, templates, downloadable resources (where available);
  • video scripts, captions, and transcripts (where provided);
  • newsletters and announcements (where available);
  • media assets (images, diagrams, screenshots) used in editorial content.

Where a property publishes a shorter "site-entry" Editorial Process page, it should point back to this Master policy via the Legal Hub Registry.

3. Topic selection (Step 1)

We select topics based on:

  • direct relevance to FPV learning, drones, simulators, safety, or the operation of FPV School services;
  • clear learner intent (a real question, problem, or decision a user must make);
  • value density (we prefer content that reduces confusion and increases safe competence);
  • ability to verify claims using authoritative sources and/or hands-on testing.

3.1 What we do not publish

We aim to avoid publishing content that is:

  • unrelated to FPV/drones/simulators/creator tooling for FPV education;
  • primarily designed to manipulate rankings rather than help users;
  • unsafe-by-design (encouraging reckless behaviour) or promoting wrongdoing.

4. Research and verification (Step 2)

We research before publishing, especially for technical or safety-critical topics.

Typical sources include:

  • manufacturer manuals and official documentation;
  • firmware and software documentation (release notes, official wikis);
  • aviation/drone rules and official guidance (where relevant to the reader's region);
  • reputable industry resources and community consensus (used cautiously);
  • our own testing and measurement (where applicable).

4.1 Handling uncertainty

When a topic depends on factors we cannot fully know (region, firmware version, device model, user skill, environment), we aim to:

  • state assumptions clearly;
  • provide safer defaults;
  • recommend verification steps and authoritative sources.

4.2 Safety-critical topics

For safety-critical areas (e.g., LiPo charging/storage, flight safety, compliance-sensitive behaviour), we treat accuracy and cautious framing as non-negotiable:

  • we avoid absolute guarantees;
  • we encourage double-checking with manuals and official guidance;
  • we include warnings where risks are non-trivial.

5. Writing and authorship (Step 3)

Our editorial content is created under FPV School's editorial control and is intended to reflect human judgement.

We do not operate automated "content farms".
We do not intentionally publish large volumes of unreviewed machine-written text as finished editorial content.

5.1 Use of tools (including AI-assisted tools)

We may use tools to support:

  • outlining and structure;
  • summarisation of user-provided notes or source material;
  • grammar/readability improvements;
  • transcription and formatting;
  • idea exploration.

Tools may assist, but they do not replace editorial responsibility.
Final public-facing content is reviewed before publication.

For AI feature behaviour and user responsibilities (where applicable), see:
/legalai-ve-policy/ (not enable yet due to plugin not being active)

5.2 No copying policy

We do not intentionally copy substantial portions of content from others without:

  • permission/licensing; and/or
  • lawful, proportionate quotation with appropriate attribution.

For details, see:
/legal/declaration-of-content

6. Editing and quality control (Step 4)

Before publication, content is edited to ensure:

  • clarity and logical structure;
  • correct technical terminology (where relevant);
  • scannable formatting (headings, lists, steps);
  • removal of ambiguity where it could cause harm;
  • consistent tone across the ecosystem.

Where needed, we add:

  • definitions;
  • diagrams/screenshots (where helpful);
  • step-by-step instructions with warnings.

7. Fact-check pass and functional checks (Step 5)

Before publishing, we aim to run a final pass that includes (where applicable):

  • verifying specs, settings, and names against primary sources;
  • confirming links work and point to the intended destinations;
  • checking that any downloadable resource matches the described version;
  • verifying that warnings and "assumptions" sections are present when needed.

If we reference a product, firmware, or feature that changes frequently, we may include:

  • a "last reviewed" date inside the content; and/or
  • a clear note that versions can change.

8. Media, accessibility, and formatting (Step 6)

We aim to:

  • use meaningful headings and structured layouts;
  • use alt text where images convey important information;
  • provide captions/subtitles or transcripts where feasible for important educational audio/video;
  • avoid "images of text" except where necessary (e.g., firmware screenshots).

For accessibility baseline, see:
/legalaccessibility-statement/

9. External links, affiliates, and monetisation (Step 7)

We may link to third parties for:

  • manufacturer documentation;
  • tools/services used in the ecosystem;
  • recommended products.

9.1 Affiliate links and tracking

Some links may be affiliate/referral links or use tracked discount codes.
We aim to disclose affiliate relationships clearly and close to the relevant links.

See:
/legal/affiliate-disclosure

9.2 Sponsorships and paid partnerships

Where content is sponsored, paid, or influenced by a commercial relationship, we aim to disclose it clearly in-context.

We aim to maintain editorial independence:

  • usefulness and safety come before commission or partnership incentives;
  • we avoid "pay-for-praise" behaviour.

10. Corrections, updates, and maintenance

We may update content to:

  • fix errors;
  • reflect new firmware, tools, products, or regulations;
  • improve clarity and accessibility;
  • remove outdated recommendations.

10.1 Reporting errors

If you believe content is incorrect or unsafe, contact:
legal@fpvschool.com

Please include:

  • the page URL;
  • what you believe is wrong;
  • why it matters (especially if safety-critical);
  • supporting sources where possible.

We aim to review reports in a reasonable time.

11. Community input and contributions

Where community features exist, we may use questions and recurring issues as inspiration for new content.

We may quote or reference community input in a fair and proportionate way, and we may anonymise where privacy suggests it.

For details, see:
/legal/declaration-of-content

12. Content reuse across the Hub

FPV School is an ecosystem with multiple properties. Content may be:

  • reused, adapted, expanded, or republished across FPV School properties under common editorial control;
  • transformed into other formats (e.g., article → checklist → video script), where appropriate.

This reuse is intentional and authorised.
For details, see:
/legal/declaration-of-content

13. Changes to this Editorial Process

We may update this process to reflect changes in:

  • workflow and tooling;
  • editorial standards;
  • the ecosystem's feature set (new sites/tools/communities);
  • legal requirements and best practices.

We will update the "Last updated" date at the top of this page.

Operator: FPV SCHOOL LIMITED (England and Wales)
Registered office: 483 Green Lanes, London. N13 4BS. United Kingdom.
Company number: 15817837
Contact: legal@fpvschool.com