Skip to content
Member Login
Join Now Global Network
Aerospace Federation

Aerospace Federation

Find your direction.

Explore the Federation. Connect with its work.
Federation sections6 areas

Choose an area to see its pages. Shortcuts are in Quick access.

Technical Work

Technical Work Process

From an identified technical need to a maintained voluntary output.

Technical Work Process

From an identified need to a maintained technical output.

A topic proposal does not automatically become a project. The process is designed to confirm relevance, understand existing systems, define a proportionate scope and select the appropriate response.

  1. 01Topic proposed by a member, committee, research activity, council, professional participant, consultation or other credible input
  2. 02Relevance assessment: aerospace connection, AF role, value and available expertise
  3. 03Existing landscape review of regulation, standards, guidance, research and technical publications
  4. 04Gap confirmation or responsible decision that no new AF document is required
  5. 05Scope definition: problem, audience, boundaries, exclusions, output and expertise
  6. 06Route selection: landscape review, research, Working Group, framework, guidance, practice, brief, consultation or no further work
  7. 07Expertise and evidence assembled with relevance, balance and conflict consideration
  8. 08Development, internal technical review and consultation where appropriate
  9. 09Comment resolution, recommendation and authorized publication decision
  10. 10Status, maintenance, revision, supersession or withdrawal

Understand the distinction

Read the process as a series of technical decisions.

Moving forward is conditional, not an automatic sequence.

Continue, redirect or stop?

Landscape review can find that an existing resource already answers the need. Further research, a narrower scope, signposting or no new AF document may be more appropriate than drafting.

Understand output options
What makes review useful?

Review should examine the reasoning, technical basis, assumptions and limits. Consultation adds relevant input; the number of supporters cannot substitute for technical judgement.

How consultation works

Evidence and consultation

Evidence supports the work; consultation is not a popularity vote.

Evidence may include

  • Research, technical data and operational experience
  • Published standards and regulatory context
  • Test data where available and relevant
  • Industry practice, academic literature and public evidence

Consultation may be

  • Public, member-based, expert-targeted or sector-targeted
  • Used only where appropriate to scope and impact
  • Recorded and resolved with reasons where material
  • Separate from a vote or automatic approval

Continue exploring

See how focused expertise contributes to defined technical work.

Explore Expert Working Groups Standards Development