Government and Public Program Intake

This form establishes the public mission, responsible office, technical question, authority, acquisition or collaboration path, deadline, security boundary, available access, and desired output.

Agency, office, and authority

Tell us who is proposing the work and which office or program owns the decision.

Name *

Email *

Organization

Role or title

Phone

Time zone or location

Preferred first response

Government or public-program level *

Office, laboratory, program, or initiative *

Your authority or role

Likely acquisition or collaboration path

Mission, problem, and decision

Describe the public mission and the technical constraint that brought you here.

Mission, mandate, or program objective *

Technical problem, research question, or program risk *

Current system, program, framework, or operating approach

What public, technical, program, procurement, or research decision must be made? *

Domain and available evidence

Choose all that apply. The program may cross several domains.

Artificial intelligence, data, cybersecurity, or connected systemsEarth science, geology, geophysics, resources, water, or geographic information systemsLife sciences, biotechnology, diagnostics, or biomedical systemsEnergy, infrastructure, thermal, environmental, or engineering systemsPublic safety, resilience, emergency response, or mission assuranceWorkforce, training, compliance, or guided operationsFundamental science, modeling, simulation, or public researchTechnology transfer, licensing, commercialization, or public-private partnershipGrant, SBIR/STTR, startup, or program technical screening

Available documents, data, models, maps, architecture, proposals, patents, studies, or technical records

Known technical, operational, budget, schedule, policy, or interagency constraints

Requested starting point

Choose the closest option. The first authorized scope may be narrower.

Mission problem or two-week mechanism auditExternal research and development sprintProgram or portfolio technical screeningResearch collaboration or national-laboratory projectFramework comparison or independent technical reviewTechnology-transfer, licensing, or commercialization reviewWorkforce, training, or guided-operations pilotPublic-private partnership or consortium designGrant, SBIR/STTR, or innovation-program support

What reviewable output or decision support is needed? *

Decision or program deadline

Funding or program status

Security, data, publication, and IP boundaries

Use the initial form only for unclassified and authorized information.

Information status *

Expected publication status

Security, privacy, ethics, export, data-use, or facility-access restrictions

Background intellectual property, licensing, data rights, or foreground-IP considerations

Participants and access

Identify the people and materials that can support a bounded review.

Agency, laboratory, program, technical, acquisition, legal, security, or partner representatives who can participate

System, site, data, document, interview, demonstration, or partner access available

Submission and boundaries

Submit only unclassified, authorized, non-credentialed information through this initial public form. Do not include classified information, controlled unclassified information requiring protected handling, law-enforcement-sensitive details, export-controlled technical data, protected health information, passwords, or restricted procurement material.

Do not submit passwords, access credentials, export-controlled information, patient-identifiable information, trade secrets, unpublished patent claims, or material you are not authorized to share.

I am authorized to share the information included in this intake. *

I understand this initial intake is not a confidentiality agreement, medical service, legal opinion, investment recommendation, or transfer of intellectual property. *

Secure materials or data-room link

A submission is reviewed for fit. It does not create an engagement until scope, terms, access, and responsibilities are agreed in writing.

Tell us the mission, responsible office, technical constraint, and decision that must be supported.