This document provides templates for white papers to be submitted to the U.S. Air Force and Air Force Research Laboratory. The templates include sections for project descriptions, approaches, benefits, costs, schedules, risks, qualifications, and references. The level of detail requested includes objectives, summaries, estimates, milestones, and points of contact.

1. U.S. Air Force White Paper Template
White Paper Body (limit to 1-2 pages)
Project Description/Objective: Provide a brief statement describing the specific product/technology
proposed,includingitscapabilities,usingclear,concise,laymanterms. Includeinformationhowthiseffort
will fulfill a stated Air Force need.
Approach: Provide abrief descriptionof the plannedapproachinachievingthe above state objective(s).
DoD CapabilityGap or Critical Need/FYNDAAThrust Area Addressed: Specific, short, and to the point.
Benefit to the Warfighter: Provide a brief statement describing the capabilities, results, and differences
offered by this technology to an operator.
Funding/Cost: Total cost of the proposed program
Program Plan:
a. Period of Performance: Include technical/reporting schedule.
b. Schedule:Include descriptionandmilestonesformajoractivities/effortsfortechnology/product
development.
c. Deliverables: Describe deliverables anticipated for the entire effort, including hardware and
software prototypesifproposed.Include anytechnical dataorcomputersoftware withassociated
Governmentlicense rights.Deliverablesshouldincludemonthlystatusreportsandafinal report.
d. Metrics/Measures of Success: Describe criteria to measure progress vs. stated goals, e.g.,
interoperabilityagainstanindustrystandard,opportunityforunit/system/lifecycle savings, etc.
e. Facilities/Equipment:Describefacilitiesand/orequipmentnecessarytoaccomplishthe proposed
effort.
f. Risk: Briefly describe anticipated risks and mitigation plan.
Proposed Transition Plan: Include any restrictions on Government use, release, or disclose of technical
data or computer software presenting transition difficulty or increased risk/cost to the Government.
Explain how the proposed solution will not preclude/hinder other component/module developers’
interface with,orotherwisedeveloping/replacing/upgradingotherpartsof the militarysystem/program.
Other Key Participants: Include name/email/phone number/complete address of key stakeholders and
focal pointsnotresidingwithinthe company,if any.Thesestakeholdersinclude organizationsoutsidethe
company relevant to the success of the effort described in this white paper.

2. Air Force Research Laboratory (AFRL) White Paper Template
White Paper (limited to 5 pages)
SectionA: Cover Page
 BAA Number
 Title of Program
 Name of Company
 BusinessSize
 Company’sCommercial andGovernmentEntity(CAGE) number
 Dun & Bradstreet(D&B) Data Universal NumberingSystem(DUNS) number
 ContractingPointof Contact (POC) withappropriate telephonenumber,fax number,andemail
address
 Technical POCwithappropriate telephone number,fax number,and email address
 Classifiedlevel atwhichcompanyiscleared
 Contactor addressforforwardingclassifiedmaterial (name,address,zipcode)
 Cognizantsecurityoffice (name,address,zipcode)
 Offeror’ssecurityofficer’sname andtelephone number
SectionB: Periodof Performance and Task Objectives
SectionC: Technical Summary and ProposedDeliverables
The technical portionof the white papershall includeadiscussionof the nature andscope of the
researchand the offeror’sproposedtechnical approach/solution.Itmayalsoinclude anyproposed
deliverables.Resumes,descriptionsof facilitiesandequipment,andaproposedStatementof Workare
not requiredatthispoint.
SectionD: Cost of Task (Rough Order of Magnitude (ROM))
The cost portionof the white papershall includeaROMcost estimate.Nodetailedprice orcostsupport
informationshouldbe forwarded;onlyatime-phasedbottomlinefigure shouldbe provided.

3. Air Force Office of Scientific Research (AFOSR) International White Paper Template
Project Title:
Principal Investigator:
Institution:
ProposedDuration (in months):
OBJECTIVE: Brieflydescribe the overall objective(s)of the proposedresearch.Whatdoyouhope to
accomplish?
SUMMARYOF APPROACH: Brieflydescribe how youplanto accomplishthe researchobjectives.
POTENTIAL IMPACT: Brieflydescribe whythe proposedresearchisimportantorhow itisnovel.Whatis
the expectedimpactonthe state of the art? How do you thinkitaddressesgapsor opportunitiesinthe
currentbody of knowledge?
RELEVANT REFERENCES: Please listuptothree referencesthatprovide additional backgroundas
needed.Provide linktoonline article,if possible.
TECHNOLOGYREADINESS LEVEL (TRL): Pre- andpost-fundingestimatedTRLs.
QUALIFICATIONSFOR PROPOSED RESEARCH: Please provideabrief descriptionof the proposer’s
qualifications,capabilities,relatedexperience,facilitiesortechniques,oracombinationof these factors
that are integral toachievingthe proposedresearchobjectives.
ATTACHMENT: Please indicate whetheratechnical supplementisattached(1-2pages).
COST: Approximate FundsNeeded($)

4. Air Force Technology Transfer Program Office White Paper Checklist
1) Name ofthe principal investigator/pointof contact:
a. Name and title (Dr.,Mr.,Mrs., Ms.)
b. E-mail address
c. Phone number(withareacode)
d. Companyname
e. Address
f. Numberof employees
g. General researchareas(listbriefly)
2) Title of the projectyou want helpdeveloping.
3) Provide a two or three paragraph executive summary(non-technical terms) aboutyour research
and your visionofa way forward.
4) Whohas the rights to use the technology?
a. Name,address,e-mail,phone number(Same,if same aspersonin#1)
b. List anyapplicable patentnumbers
c. List anyprovisional patents
d. List anyinventiondisclosures
e. List anytrade secrets,trademarksheld,etc.thatprotectthisinformation
5) What do you want the Air Force to helpyou do? Selectall that apply.
a. Developyourtechnology
b. Utilize AFtestfacilities
c. Assistance designing/constructingaprototype
d. Validationtestingof aprototype
e. Manufacturingassistance
f. LookingforAir Force technologytolicense (listaspecifictechnologyarea)
g. Assistance withlicensingyourtechnology
6) The TechnologyTransfer Program Office bylaw cannot provide funding.