The first task is not to create the appearance of scale. It is to build the institutional foundation required for responsible growth. Aerospace Federation’s 2027–2028 direction is therefore a sequence of capabilities, each dependent on participation, governance and readiness.
Why the order of development matters
An institution can publish a large organizational chart before it has the people, mandates or processes to operate it. That may create an impression of maturity, but it also produces empty roles and unclear authority. AF is taking a different approach: establish the architecture, understand the participant base and activate structures only where a defined purpose and sufficient capability exist.
The roadmap below describes development priorities and an intended working cycle. It is not a guarantee that every listed activity will proceed on a fixed date. Progress will depend on membership, available expertise, financial and operational readiness, governance approval and the relevance of the questions brought forward.
The Federation intends to grow with its members rather than build an artificial structure ahead of them.
Phase 1 — Institutional foundation · 2026
The foundation phase focuses on the systems that allow later activity to be governed. Priorities include the governance architecture, membership system, public website, Membership Pre-Application, Technical Work architecture, Recognition architecture, research framework, activities planning and member digital infrastructure.
These elements are connected. A membership process needs categories and eligibility rules. Technical Work needs a route from a proposed question to a reviewed output. Recognition needs criteria, competent review and a public record. Digital infrastructure must support access without becoming the source of institutional authority.
The visible output of this phase may appear modest because much of the work concerns definitions, boundaries and process. That restraint is deliberate. The institution should know how a decision is made before presenting the decision as credible.
Phase 2 — Membership and participation · Q1–Q2 2027
Potential priorities include the initial membership review cycle, onboarding, institutional and professional participation, identification of member expertise, collection of technical topics and an initial view of research interests.
Pre-application information can help AF understand the composition of the emerging community. Formal review should then consider eligibility and the appropriate membership route. Onboarding can introduce members to participation boundaries, conduct expectations and the difference between contribution and decision authority.
Councils and committees should be established only where the participant base and a real need justify them. A group without sufficient diversity or competence may create more confidence than its work can support. The responsible alternative is to wait, broaden participation or use a more limited consultation format.
Phase 3 — Working structures · Q2–Q4 2027
Where sufficient expertise and governance readiness exist, AF may begin forming initial councils, Technical Committees or Expert Working Groups. It may also develop research collaboration, Academy activities, events, consultations and a process for assessing proposed technical topics.
These structures serve different purposes. A council can bring strategic or stakeholder perspective. A Technical Committee can oversee an area of continuing work under an approved mandate. An Expert Working Group can address a bounded question and conclude when its task is complete. A research collaboration can examine evidence without being expected to produce an institutional recommendation.
Each structure should have terms of reference, a defined relationship to governance and a record of participation. Conflict-of-interest management becomes especially important when contributors have commercial, regulatory or professional interests in the outcome.
Phase 4 — Initial technical and knowledge outputs · late 2027–2028
Possible outputs include Technical Landscape Reviews, frameworks, guidance, Recommended Practices, research reports, white papers, professional-development activities and collaborative publications. The output should follow the question rather than be selected in advance.
| Possible output | Purpose | Condition for development |
|---|---|---|
| Landscape review | Map existing systems, evidence and gaps | A defined cross-sector question and adequate source material |
| Framework | Organize principles, responsibilities or stages | A recurring coordination need without creating mandatory obligations |
| Guidance | Explain interpretation or implementation | Evidence of a genuine user need and clarity about existing authority |
| Recommended Practice | Describe a voluntary technical approach | Sufficient expertise, evidence, review and consultation |
| Research report | Present method, findings and limitations | A research question and competent delivery capability |
AF should not set output targets merely to demonstrate volume. One well-scoped review that helps users understand an existing problem may be more valuable than many documents with uncertain standing.
Phase 5 — Recognition development · 2027–2028
Recognition routes may progressively become available after the membership base develops, criteria are published, reviewer competence is available and governance safeguards are operating. The sequence protects applicants as well as the Federation because it prevents evidence from being assessed through an improvised process.
Recognition is intended to remain member-only, evidence-based and scope-specific. It is not accreditation, certification, regulatory approval or professional licensing. Opening one route would not imply that every proposed route is active.
Phase 6 — Broader international participation · 2028
Potential priorities include broader membership, cross-sector participation, international forums, research cooperation, technical collaboration, member-led initiatives and more mature publication activity. International growth should improve the range of relevant perspectives rather than become a count of flags or names.
A wider participant base also increases governance demands. Translation, time zones, legal contexts, accessibility, confidentiality and differing professional practices all affect how participation is designed. Institutional maturity is the ability to manage those differences transparently.
What early participants can contribute
Organizations and professionals can bring expertise, perspective, research questions, technical needs and institutional experience. Their value is not an automatic right to direct the Federation. It is the ability to improve how AF identifies questions, designs participation and understands the contexts in which future work may be used.
This roadmap will need revision as evidence and participation develop. Publishing direction does not remove uncertainty; it makes uncertainty discussable. The measure of progress will be whether AF can move from stated purpose to governed, useful activity without claiming capability ahead of the people and processes required to support it.
Decision gates between phases
A roadmap becomes more credible when movement between phases depends on evidence. Before an initial membership review cycle, AF needs approved categories, review criteria, data controls and responsible decision-makers. Before a working group, it needs a defined question, mandate, participants and reporting route. Before Recognition opens, it needs published criteria, competent reviewers and an auditable decision process.
These are decision gates rather than dates alone. A target quarter can guide planning, but readiness determines whether the next step is responsible. If a condition is not met, the correct response may be to delay, narrow the scope or use a less formal activity.
Minimum viable institutional capability
AF does not need every future system before it can begin useful work. It does need a minimum capability appropriate to the activity. A public briefing may require a clear subject, competent speaker, accurate status and accessible delivery. A technical publication requires substantially more: source control, review, approval, versioning, conflict management and maintenance.
Matching infrastructure to risk avoids two extremes. The Federation should not delay all activity until every long-term system is complete. It should not use a lightweight process for an output that readers could reasonably treat as authoritative.
Data and digital infrastructure
Member infrastructure should support identity, access, participation records and protected resources. Security begins with least-privilege access, strong authentication, careful session management and separation between public and member-only information. Governance determines who may authorize access; technology enforces that decision.
Digital systems should also make administration manageable. Structured member profiles, editorial HTML fields, publication status and traceable updates are more sustainable than data hidden in unstructured configuration. The same principle applies to events, consultations and technical work records.
How priorities may be selected
Potential work should be assessed against relevance to the aerospace ecosystem, evidence of a real need, fit with AF’s role, availability of competence, benefit across more than one participant and the ability to deliver a useful outcome. A popular topic is not automatically the right first topic.
Balance also matters. Early work should not imply that one technology, region or member type defines the Federation. At the same time, artificial balance should not force activity where no credible need or expertise exists. Publishing the selection rationale can make these choices understandable.
Learning and revision
The 2027–2028 direction should be reviewed as membership and experience develop. Some proposed structures may prove unnecessary. New questions may emerge. A research interest may become a technical topic, while another may be better directed to an existing external programme.
Revision is not failure when assumptions and reasons are recorded. It is evidence that the institution responds to participation rather than preserving a plan for appearance. Progress reports can distinguish completed foundations, active development and longer-term intentions.
What responsible growth looks like
- Public claims remain aligned with actual institutional capability.
- New structures have approved mandates and identifiable responsibility.
- Members understand how to participate and what participation means.
- Technical work begins with evidence of need.
- Recognition opens only when criteria and review safeguards are ready.
- International growth improves perspective without weakening governance.
The roadmap is therefore less a promise of scale than a test of sequence. AF intends to build the conditions for useful participation first and allow credible outputs to follow from the people, evidence and questions that become available.
