Skip to content

Memorandum for Record Requirements

To initiate the onboarding process for customers working toward a Certificate to Field (CtF) for IL2, IL4, or IL5 deployments, a Memorandum for Record (MFR) must be submitted before onboarding can begin. We will request signed MFRs at the customer kickoff.

What is the MFR?

The MFR is a formal document required by Game Warden’s Authority to Operate (ATO). It verifies the mission need, sponsorship, and contract type for your application deployment.

Important

Requirements vary depending on whether your Government Mission Owner (GMO) is part of the United States Air Force (USAF) or another military branch.

The required signatures and approvals are different depending on this affiliation, as outlined in the sections below.

Completing the MFR

  1. Download and open the PDF template
    Open the form in a PDF reader that allows form filling.
    → Download Form Template

  2. Fill out the last page
    Only the final page requires data entry. Once completed, the values auto-populate other pages in the form.

  3. Omit the last page before saving
    Remove the final page before saving the PDF for signature. This page contains editable fields and should not be included when submitting the document for signature.

  4. Save the document and send for signature
    Save the completed form (minus the final page) and route it for the required signatures.

How many MFRs do you need?

You will need at least one MFR for each instance of your application deployed for a different mission owner or use case. An instance refers to a specific copy or deployment of your application—even if it shares the same base code.

Example

Suppose your application, Galactic Donkey, needs to be deployed for multiple mission owners. Sometimes, multiple mission owners may share the same instance, but in other cases, each mission owner may have their own instance of the application. Even though it’s the same core application, each copy is treated as a separate instance when deployed for different use cases or mission owners.

Application: Galactic Donkey Instances

  • Mission A: A copy of Galactic Donkey for Mission Owner A
  • Mission B: A copy of Galactic Donkey for Mission Owner B

In this scenario, you would need two MFRs—one for each instance.
If Mission Owners A and B share the same instance, only one MFR is needed.

USAF Government Mission Owners

If your Government Mission Owner is within the United States Air Force (USAF), two signatures are required.

1. Complete these form roles:

  • Product Company and Application
  • Mission Owner & Sponsor

2. Signatures required:

  • ✅ Mission Owner & Sponsor: Your Government Mission Owner must sign to verify the mission need and sponsorship.
    → Responsibility: Game Warden customer

  • ✅ AFWERX Information System Owner: Confirms contract type and co-signs the MFR.
    → Responsibility: Second Front (2F)

Non-USAF Government Mission Owners

If your GMO is outside the USAF, three signatures are required.

1. Complete these form roles:

  • Product Company and Application
  • Mission Owner & Sponsor
  • Supporting Authorizing Official

2. Signatures required:

  • ✅ Mission Owner & Sponsor: Your GMO must sign to verify the mission need.
    → Responsibility: Game Warden customer

  • ✅ Supporting Authorizing Official: Must acknowledge that their system will be hosted on the USAF Game Warden platform.
    → Responsibility: Game Warden customer

  • ✅ AFWERX Information System Owner: Verifies mission need and contract type.
    → Responsibility: Second Front (2F)

Upload your MFR in Game Warden

You can upload the signed MFR directly within the Game Warden platform via App Central.

  1. From App Central, click the ✏️ (pencil) icon next to your application.
  2. Scroll down to the Mission Fit Memorandum for Record (MFR) section.
  3. Click Add mission fit MFR, then select and upload the completed MFR PDF file from your computer.
  4. Fill in the remaining form fields:
    • Impact level referenced in the signed MFR
    • Date AFWERX signed the MFR
  5. Click Save.

MFR expirations

Each MFR must be reverified every six months from the finalized, AFWERX ISO signature date.

  • MFRs are included with your BoE submission for CtF
  • MFR expiration date & CtF expiration date are mutually exclusive

If an updated, fully signed MFR cannot be provided, your application will be offboarded from the platform until a valid MFR is submitted.