You are here


  1. We cannot guarantee we will find and announce every limited funding opportunity.
  2. We sometimes learn of a limited opportunity belatedly. We will do our best to announce it within a reasonable time.
  3. If you find a funding opportunity of interest and believe it is limited, but do not see it here or in our archived emails, you still must follow our process. Let us know the opportunity you have found. This process is critical: extra submissions can result in the sponsor's rejection of all from the University of Michigan.
  4. If the sponsor deadline has not expired, you may be able to still apply. Contact
  5. We will try to work with all interested parties to achieve a satisfactory outcome.

Conflicts of Interest (COI) represent financial or other situations where an individual has an outside interest (e.g., equity in a company, intellectual property, consultant activity with a company) that could affect the design, conduct or reporting of their research.  Also refered to as personal or individual COI.


Institutional conflicts of interest (ICOI) represent financial or other situations where the University, as an institution, has an outside interest (e.g., equity in a company doing business with the University) that could affect the design, conduct, reporting, review or oversight of research conducted by its employees or students.

A Covered Official of the University is an executive officer, dean, or institute/center director with day-to-day responsibility for the supervision of faculty and staff participating in research conducted at or under the auspices of the University.

The initial award notification will come in an email, and all information that we currently know as PAN (Project Award Notice) or PAC (Project Award Change) will reside in the AWD system. If you wish to have a hard copy printed, your best course of action would be to save the email notification as a PDF. 

User Acceptance Testing (UAT). During the UAT process, representatives from the schools/colleges/institutes and central offices  (who were involved in the working groups) will be asked to preview the online workflow. Additionally, this is a time to redefine or identify any remaining "offline" business processes. No new functionality is expected to be added during UAT. The UAT process simply ensures that requirements have been met.


The eRA Commons (electronic research administration commons) website, by the National Institutes of Health (NIH), that provides principal investigators and their research staff with online features and tools including the abilities to:

  • View a full application
  • Review current status of an application
  • Check for errors
  • View application assignment information
  • Obtain PDF copies of applications
  • Access copies of previous Notices of Grant Award

Get current information on the program official and the grants management specialist

More information from ORSP about using through the U-M eResearch Proposal System

  1. Extended definition for federal exemption #2 [pre-2018 Common Rule] (proposed by IRB-HSBS, 2013; adopted by all U-M IRBs)
    Federal exemption category 2 applies to projects involving educational tests, surveys, interviews, or observation of public behavior.  It does not allow for any other research intervention in conjunction with the durvey, etc., regardless of the risk.  U-M exemption #2a expands the federal definition to minimal-risk research with adults that involves a non-invasive intervention followed by data collection vai survey, interview (including focus groups) or observation.  Examples of non-invasive interventions include, but are not limited to:
    • Reading a story or vignette
    • Playing an electronic game
    • Using a computer program or website
    • Watching a video
    • Using a robot arm or device
    • Being exposed to stimuli, such as color, light or sound (within safe limits)

  2. Two-year approval periods (proposed by IRB-HSBS, 2007; adopted by IRB-Flint, 2014, IRBMED, 2015)
    Federal regulations require continuing review of research at least annually, depending on the degree of risk to the subjects.  For research projects posing no more than minimal risk to subjects, U-M postulated that lengthening the review period beyone one year was unlikely to increase risks to subjects.

  3. Exemption for analysis of identifiable data:  U-M Exemption #7 [pre-2018 Common Rule] (proposed by IRB-HSBS, 2007; adopted by all U-M IRBs) Federal regulations require annual continuing review for all studies, including minimal risk studies where research activity is limited to analysis of identifiable data.  U-M proposed that for research involving no direct interaction or intervention with human subjects, the requirement to submit annual continuing reviews doesn not enhance subject safety.  A new exemption category was created to provide appropriate review and subsequent exemption from regulatory oversight.  Anticipated benefits included:
    • Reduction of administrative workload for investigators
    • Reduction of application volume for IRB staff and reviewers
    • Reduced turn-around time for application review of U-M Exemption #7 studies

HRPP's criteria for demonstration projects includes:

  1. The research must be determined to pose no more then minimal risk to subjects.

  2. The research must not include:
    • Federal sponsorship, including federal training grants
    • FDA regulated components
    • Sponsor or other contractual restrictions requiring adherence to federal regulations for clinical interventions (including clinical behavioral interventions)
    • Prisoners as subjects
    • NIH-issued Certificates of Confidentiality

  3. The project must evaluate the impact of procedural improvements, including the:
    • Compatibility with the current electronic IRB application
    • Ease of training and informing investigators, study teams, and the IRB staff
    • Ability to monitor the projects.

  4. The project must signify the impact of procedural improvements on the research community, such as:
    • Elimination of regulatory excess that is not protective of human subjects
    • Enhanced regulatory outcomes for minimal risk research
    • No increase in effort required for investigators.

Innovations U-M has implemented to date include:

  1. Streamlining the IRB application paths (i.e., types of applications) in eResearch for:
    • Secondary use of existing data/records/specimens
    • Exempt human subjects research
    • Activities not regulated as human subjects research
    • Requests for review by a non-UM IRB.

  2. Updating IRB policies regarding staff roles for:
    • Exempt reviews - authorization for IRB staff to make exempt determinations
    • Scheduled Continuing Review (SCR) - authorization for qualified IRB-HSBS staff to conduct expedited review of non-federally funded research.

  3. Implementing U-M guidelines regarding:

  4. Expanding the interpretation of federal exemption category #5 to cover public benefit and service programs sponsored by the State of Michigan.

The U-M Office of Research (UMOR) offers support for research, scholarship, and creative activities in all fields.

The intent is to:

Help support areas of research and scholarship where external funds are scarce or unavailable

  • Assist in maintaining the base activities of high-quality projects between funding cycles
  • Support for equipment and infrastructure on sponsored activity
  • Seed novel, high-risk, innovative, inter-unit projects
  • Assist with colloquia, symposia, and other events that promote the evolution of new research ideas and collaborations
  • Assist junior faculty in establishing new research programs

Applications are reviewed by faculty peers. Please consult the specific funding opportunities for detailed application procedures and other pertinent information.


Eligible Not Eligible
Instructional and Research Faculty Research Investigators
Librarians Lecturers
Curators Postdoctoral, Graduate and Undergraduate Students

Review Procedures, Award Terms, & Other Information


The U-M Office of Research (UMOR) requires the signatures of the department or unit head, and the dean or director of the school/college/unit. The dean/director may delegate this authority to an associate dean/director. Please route the application to the appropriate office for signatures well in advance of any deadlines. Your school/college/unit may have internal processing requirements that must be completed prior to submission. Contact those offices for clarification.

Applications will not be processed by UMOR until all appropriate signatures are obtained.

Matching Funds

For all UMOR funding opportunities, securing matching funds or cost sharing from the unit, school/college, department, or outside sources is viewed as an important sign of commitment to and support of the application. As such, a match on a portion of the total project cost is required. The specific required minimum % varies by funding opportunity and can be found in the program description. Non-allowable costs listed under Funding Restrictions (below) are not to be included in matching funds. Joint UMOR and BMRC applicants for maintenance support must follow BMRC's requirement of 1:1 matching funds from the PI's department.

Peer Reviews

Applications will be reviewed by faculty peers. This step may be waived in the case of proposals with comparable external review.

Key considerations during review include:

  • Scholarly merit and potential impact on the field
  • Value for the applicant's own research potential and progress
  • Productivity and qualifications of the applicant, as indicated by record of research achievement or potential
  • Likely impact of this work on the field and its potential to enhance the scholarly distinction of the University
  • Appropriateness of the budget to the project proposed
  • Extent of unit support as indicated by matching funds
  • Any special review requirements as noted in the individual program description


Priority is typically provided to faculty who have not received or have received little funding from UMOR previously.

Frequency of Application

To equitably distribute research and scholarship funds across the campuses, UMOR limits faculty to one award per fiscal year. Exceptions may be granted under special/unique circumstances with prior approval.

Funding Restrictions

In general, UMOR support is NOT available for:

  • Travel to present at conferences
  • Regular salary of faculty except as specifically indicated in program guidelines
  • Computer/hardware/software for routine use
  • Office equipment, telephone installations, photocopy machines
  • Equipment maintenance costs
  • Tuition support
  • Requests for small amounts more appropriately handled at the unit level
  • Projects that are primarily instructional
  • Funds covering reduced external awards
  • Retroactive funding, costs overruns, or disallowances on other sponsored projects
  • Faculty recruitment and start-up packages
  • Page or reprint costs of articles in professional journals

Award Notification

UMOR is committed to responding to faculty requests for support as quickly as possible. Notification of funding decisions is typically made within 12 weeks of the program’s deadline.  Late applications will not be processed until the next deadline for that program.

Applicants can facilitate expeditious review by providing complete information, all required signatures, and by suggesting qualified, independent reviewers.

Award Administration

For most awards of $5,000 or more, a project/grant will be established in the recipient's academic unit for a specified amount, duration, and purpose. The recipient is responsible for ensuring good stewardship of the funds received. All applicable university policies and procedures must be followed.

Award amounts are final. Overruns and disallowances are the responsibility of the individual recipient and academic unit. Each award stipulates an expiration date, after which it is expected that the remaining balance will be returned to UMOR.

Faculty may not retain the award if they leave the University of Michigan.

Any changes in budget items or project period must first be approved by UMOR. Contact for questions.  To request a No Cost Time Extension (NCTX) for an existing UMOR Faculty Grants & Awards program award, click here.



32 CFR Part 2002 identifies three control levels that guide the safeguarding or dissemination of CUI:

  • CUI Basic - requires or permits the agencies to control or protect the information, but provides no specific information security controls
  • CUI Specified - requires or permits the agencies to control or protect the information, and provides specific information security controls
  • CUI Specified, but with CUI Basic Controls - requires or permits the agencies to control or protect the information, and provides only some of the controls

When the university accepts a contract that includes CUI, the Research Information Security Liaison determines the level of CUI (basic or specified) control required and works with the research team to ensure that the appropriate controls are implemented for the life of the project.

An external (i.e., commercial or other academic) IRB may charge for services when designated as the single IRB-of-Record (sIRB) for a multi-site, non-exempt human subjects research project.  Estimated expenses are negotiated on a case-by-case basis in the service agreement between U-M and the external IRB, and budgeted for as direct costs in the sponsor's (e.g., NIH) funding proposal and award.

Common IRB services include, but are not limited to:

  • IRB Reviews
    • Initial review of the research protocol, investigator/site qualifications, informed consent plan and documentation, and subject recruitment materials
    • Continuing/annual protocol review (regulatory requirement) for subsequent years of the project
    • "Periodic" review of any incident reports (e.g., Adverse Events or ORIOs), as they are filed
    • Amendments/modifications -  changes to the study that require IRB review
  • Administrative Services - letters, study changes not requiring IRB review, etc.
  • Site/Project Closeout - review of the final status report, resolution of outstanding issues 
  • Other - services as applicable to the project, e.g., foreign language translation, etc.

Factors that impact the budget for sIRB services include the number of performance sites, level of risk to the subjects and/or institution, duration of the study, and more.  See the External sIRB fee schedule -sample for an example.

Warning iconThe principal investigator is not authorized to sign the negotiated service agreement with the external IRB.  As a financial transaction, the agreement must be signed by an authorized official from U-M Procurement Services and may require approval from the U-M Regents.

Always contact your U-M IRB to determine sIRB requirements prior to submitting funding proposals for multi-site, non-exempt human subjects research.


UMOR’s Research Information Security Program
Phone: 734-764-7248


Failure to comply may result in contract challenges to, or loss of, the award and result in future ineligibility to be awarded government contracts.

Failure to accurately report the status of compliance could result in charges of fraud and criminal penalties for the individual researcher.  In addition, the university could also experience adverse reputational, legal, or financial consequences.

The controls for CUI are only implemented when we have accepted a contractual obligation to implement specified NIST SP 800-171 controls. Federal agencies may issue contract amendments that would require CUI controls at any time after a contract has been accepted. Consequently, information security controls may change during a project's lifecycle, but these new terms would only be effective from the date we contractually accept them.

All implementations of a CUI controlled environment will result in shared responsibilities between ITS, IA, the school/college/unit, and the research program. Housing CUI research in the Yottabyte Research Cloud or a cloud-based solution will only address about ⅔ of the required controls. The remaining ⅓ of controls will be the responsibility of the school/college/unit and the research program. The majority of these controls are policies and procedures the research group must implement along with training for all personnel working with CUI.

NIST 800-171 allows for nonfederal entities to meet CUI security requirements by “isolating CUI into its own security domain by applying architectural design principles.”  


In this vein, there is currently an ITS-led project initiative in collaboration with ARC-TS to develop a CUI compliant enclave. The Yottabyte Research Cloud will greatly facilitate data-intensive research by providing a flexible computing cloud for complex computational analyses of data classified as Restricted or High, such as CUI. ITS is also developing a proof of concept for a CUI compliant commercial cloud enclave. This will provide a rapidly deployable alternative when the Yottabyte research cloud cannot support a project's technical requirements.


An overarching compliance program is being developed as a partnership between U-M Information Assurance (IA), University of Michigan Office of Research (UMOR), Michigan Medicine Compliance, Office of General Counsel (OGC) and the schools and colleges most likely to work with CUI. Components of the program will include the development of policy, process, security templates, training, periodic risk assessments (RECONs), and the certification that appropriate controls are in place.  


Our experience to date is that, after consultation with contracting agencies, we often are able to eliminate CUI provisions and requirements from the final contract.

A research project may include CUI when the funding source is a federal contract or a subcontract where the prime sponsor is a federal agency. The university enters into approximately 1700 new federal contracts/subcontracts each year, but only a small subset are expected to involve CUI. The Office of Research and Sponsored Projects (ORSP) reviews and negotiates all incoming sponsored research contracts and subcontracts for the university.


When ORSP identifies contract language (normally a DFAR or FAR clause) requiring CUI compliance, it requests a review from the Information Security liaison in the Office of Research Ethics and Compliance. The liaison reviews the contract and research proposal works with the Principal Investigator (PI) to determine the applicability of the clause, and then works with ORSP to clarify precisely what materials are CUI and/or negotiate the clause out of the contract.


A research project may also include CUI if it using data acquired under a Data Use Agreement (DUA) and the data is information the government creates or possesses, or that an entity creates or possesses for or on behalf of the government, and has been classified by the government as CUI.

For the majority of research projects at U-M, our information systems meet the definition of a “nonfederal” information system. It is important to note that federal agencies are specifically prohibited from requiring Information security controls above those specified in 32 CFR 2002 for nonfederal information systems.


NARA charged the National Institute of Standards and Technology (NIST) with developing the information security controls for CUI Basic. These controls are detailed in NIST Special Publication 800-171r1, “Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations.”  This publication draws heavily from two earlier NIST information security standards, FIPS 200 and NIST 800-53, both of which are already significantly accounted for by U-M information security practices.  


When the university accepts a contract that includes CUI, we determine the classification of the CUI (basic or specified) and work with the research team to ensure the appropriate controls are implemented for the life of the project.

The National Archives CUI Registry identifies the information considered to be CUI by category/subcategories.  A non-exhaustive list of categories includes:

  • Controlled technical information with military or space application
  • Critical infrastructure information (e.g., energy infrastructure, water systems, etc.)
  • Export controlled information or materials used in research
  • Nuclear information related to protecting reactors, materials, or security
  • Statistical information (e.g., U.S. Census)
  • Transportation information (e.g., railroad safety, etc.)

​The CUI Registry is the authoritative online repository for information, policy, requirements and guidance on handling CUI.

It is critical to protect sensitive government information, some with national security or U.S. trade implications, to reduce the risks of unauthorized release or misue. Application of and compliance with the information security controls helps protect this information against threats to cyber security, data breaches, or other unauthorized disclosures.


To be informed of the opportunities we have identified, you can sign up for our Weekly Call for Intent and Limited Submission communication. We now communicate both the Calls for Intent to Submit and the Limited Submissions in a single communication.


If UMOR opts to host an internal competition, we will announce it through email communications and on this website.


If you wish to submit a proposal for any of the following opportunities, select the opportunity, log in, follow the prompts, and choose Apply.


If, after the Limited Submission competition, you are selected as the institutional nominee, you will be provided with a system-generated notification that you can attach to your Proposal Approval Form (PAF) in the eResearch Proposal Management (eRPM) system.

A Limited Submission is a funding opportunity in which the sponsor sets an institutional limit for the number of proposals it will accept. To participate, the University must organize to submit our most competitive proposal. This requires an internal competition. The process is critical; extra submissions can result in the rejection by the sponsor.

A group of raising hands The Call for Intent to Submit process relates to the many Limited Submission funding opportunities that exist -- about 250 funding opportunities each year from various sponsors.


We don't need to reserve competition dates for each opportunity if interest does not exist. So we prepare a weekly communication listing opportunities and asking for a show of hands to determine interest. If interest exceeds the sponsor's institutional limit, the U-M Office of Research may hold an internal Limited Submissions Competition and announce it at a later date.


Interested parties declare their interest in a Call for Intent to Submit and/or submit competition materials for a Limited Submission competition, through our InfoReady Limited Submissions website(link is external).

Controlled Unclassified Information (CUI) is federal non-classified information (i.e. information the Government creates or possesses, or that an entity creates or possesses for or on behalf of the government) that requires safeguarding or dissemination controls compliant with law, regulations, and government-wide policies.


The CUI Program is a government-wide approach to creating a uniform set of requirements and information security controls directed at securing sensitive government information.


Additional Details:


For an overview of these requirements and the impact on research conducted at U-M, see U-M Office of Research (UMOR) External Funding and Information Security Requirements. UMOR’s Office of Research Ethics and Compliance provides assistance to investigators to help them understand when CUI regulations apply to research projects and to identify what U-M resources are available to meet the security requirements.


CUI requirements do not apply directly to non-federal entities, but can flow down when U-M non-federal information systems (e.g., research projects) are given access to such information by federal agencies under the terms of a contract, grant, or other agreement.  U-M researchers are frequently subcontractors handling CUI on behalf of a government agency, and CUI requirements apply equally to subcontractors.


On November 4, 2010, President Barack Obama issued Executive Order 13556 “Controlled Unclassified Information” for the purpose of establishing an open and uniform program for managing [Controlled Unclassified information] that requires safeguarding or dissemination controls pursuant to laws, regulations, and government-wide policies.


Prior to this, executive departments and agencies employed ad hoc agency-specific policies, procedures, and markings to safeguard and control this information.


The National Archives and Records Administration (NARA) was designated as the Executive Agent to implement the Order and oversee agency actions to ensure compliance with this order.


NARA established a CUI Registry, an online repository for all information, guidance, policy, and requirements on handling CUI. The registry identifies all CUI categories and subcategories, provides general descriptions for each, identifies the basis for controls, establishes markings, and includes guidance on handling procedures.


There are three ways in which law, regulation or government-wide policies may permit the safeguarding or dissemination controls:


  • CUI Basic – requires or permits the agencies to control or protect the information, but provides no specific information security controls.

  • CUI Specified - requires or permits the agencies to control or protect the information, and provides specific information security controls.

  • CUI Specified, but with CUI Basic Controls - requires or permits the agencies to control or protect the information, and provides only some of the controls.


A single IRB-of-Record (sIRB) is the institution review board that is designated (with negotiated terms via a formal service/authorization agreement) to act as the sole provider to conduct the initial, continuing, and any subsequent review of the research project to ensure human subjects protection regulations will be/are followed.


From U-M's perspective, an external IRB is any non-UM institutional review board.  An external IRB can be an accredited commercial, central, other academic, or hospital-based IRB.  When a U-M study team is not utilizing a U-M IRB for a non-exempt, multi-site human subjects research project, it will be using an external IRB.


A central IRB is an institutional review board that specializes in reviewing a specific type(s) of human subjects research; or is established to review projects funded by a specific agency.  For example, the NCI Central IRB reviews projects sponsored by the National Cancer Institute.

If non-compliance is identified during a routine review, the investigator may be asked to submit to the IRB specific changes to the protocol, informed consent, the eResearch application, or other study related materials.

If non-compliance is identified during a for cause review, the IRB of Record will craft a Corrective and Preventative Action Plan (CAPA) for the investigator which may include submission of a revised protocol, informed consent, or other materials.  ORCR will collaborate with the IRB to craft the CAPA plan and follow-up on required corrective actions.

For more detailed information, see ORCR SOP 101 (Not for Cause Routine Review) and ORCR SOP 102 (For Cause Review).

The Principal Investigator (PI) should plan on an initial 60-minute interview with an ORCR reviewer. This discussion will focus on areas of potential study risk. Interview questions may include but are not limited to: roles and responsibilities, recruitment, consenting process, study procedures, record keeping, data management, monitoring, and oversight. The scope of the review may vary and is tailored to the scope, nature, and complexity of the study.  Following the initial discussion, the ORCR reviewer will review study records with the study coordinator.  

Following the review, the investigator will have an opportunity to review a draft report to verify facts contained in the report. The IRB of record will also have an opportunity to review a draft of the report. The final ORCR report will be sent to the investigator, the IRB of Record, the Research Associate Dean, and Associate Chair for Research or Department Chair.

For more detailed information, see ORCR SOP 101 (Not for Cause Routine Review) and ORCR SOP 102 (For Cause Review).

The Principal Investigator (PI) or a designee should contact the ORCR reviewer to schedule a time for the compliance review as soon as possible.

The investigator, or other study team members as directed, should assemble study records for review.  An example of records the compliance associate may want to review include:   eligibility criteria, enrollment logs, training documentation, informed consent documents, and the regulatory binder.

Increased knowledge and understanding of human subjects research regulations.

Increased knowledge and understanding of U-M policies and procedures.

Access to resources in the form of study and subject level tools and self-assessments.

No, ORCR is independent of the IRBs. ORCR’s function is to provide an objective review of human subjects research conducted at U-M.

The federal Controlled Substance Act defines and classifies drugs and other substances into five (5) controlled substance schedules (I - V) according their potential for abuse and addiction. The substance's schedule dictates the application process to use and guidelines to follow for security, storage, etc.

large C indicates controlled substance; the Roman numeral indicates the substance schedule

Schedule I:  illicit drugs, compounds and their chemical precursors that have a high potential for abuse, no accepted medical use, and lack of accepted safety protocols for medical use.  They are typically used for drug abuse/addiction research or for analytical research.

Schedules II-V:  drugs, compounds, and their chemical precursors that have accepted medical uses and a decreasing potential for abuse.


The federal Controlled Substance Act defines and classifies drugs and other substances into five (5) controlled substance schedules (I - V) according their potential for abuse and addiction. The substance's schedule dictates the application process to use and guidelines to follow for security, storage, etc.

Schedule I:  illicit drugs, compounds and their chemical precursors that have a high potential for abuse, no accepted medical use, and lack of accepted safety protocols for medical use.  They are typically used for drug abuse/addiction research or for analytical research.

Schedules II-V:  drugs, compounds, and their chemical precursors that have accepted medical uses and a decreasing potential for abuse.

The Foreign Corrupt Practices Act

It is illegal for U.S. persons to offer or pay anything of value to a foreign official for the purposes of obtaining, retaining, or furthering business activities, per the federal Foreign Corrupt Practices Act (FCPA) anti-bribery provisions. For example, making payments to custom officials in exchange for their agreeing not to inspect goods or to release goods held at points of entry would violate the FCPA. For more information, visit the U-M Export Controls FCPA guidance.

Be Aware

Customs officials in any country, including the U.S., may inspect your belongings, including electronic content of computers, phones, tablets, and storage devices. They may take possession of these items for various periods of time—even permanently.  It is a best practice to only take items with you that are absolutely needed for your trip.

Some countries also have import regulations that specifically prohibit travelers from bringing into those countries encrypted laptops or other mobile devices. Violations of those countries’ prohibitions could result in confiscation of your device by customs authorities and/or fines or other penalties.

What If You Encounter A Problem While Overseas?

You are required to report a stolen or lost device or other IT Security Incident. The U-M Office of Global Engagement provides detailed information on General Emergency Protocols for U-M International Travelers.

When traveling out of the United States, everything you take with you is considered an “export,” under U.S. export regulations. Some of these exports will require an export license from the government. However, in many situations, you will not need an export license because either (1) the items or data you are taking are not controlled to your destination or sometimes (2) a license exception is available.

Items That Require Export Control Review Before You Travel

Do not travel with any of the following items without first obtaining specific advice from the Export Control Program, as these items may require an export license:

  • Devices, systems or software that are not standard, off-the-shelf products generally available to the public

  • Devices, systems, or software that are specifically designed or modified for military or space applications

  • Data or information received under an obligation of confidentiality

  • Data or analyses that result from a project that has restrictions on the dissemination of the research results

  • Classified information

  • Export controlled information

Items That You May Be Able to Take With You

U-M employees and students may be able to use a “Tools of Trade” license exception to travel temporarily out of the U.S. and hand carry certain types of hardware, software and/or data. This license exception may be used by U-M employees and students traveling with personally-owned or U-M-owned hardware, software and data provided that the terms of the license exception are met.  This exception does not apply to items, technology, data, or software regulated by the International Traffic in Arms Regulations (ITAR). Please contact the Export Control Program if you would like more information on using this exception when traveling internationally.

If your hardware, software or data are not eligible for the “Tools of Trade” license exception, the Export Control Program will discuss other options with you.  There are other less frequently used license exceptions that may apply, and if no license exception is available, you may be able to work with the Export Control Program to apply for an export license.  

Items That Need to Be Properly Secured For Travel

Whether you are traveling with a personally owned computer, a U-M owned computer, or any other device, you must make sure that you properly secure your hardware, software and data for international travel.  U-M Safe Computing has detailed guidance to help you secure your devices before, during and after travel.

If you are traveling with any export controlled information or other sensitive data on your devices, you must encrypt your devices to protect the data from unauthorized disclosure.  Please remember that before you travel with any data or devices, make sure that these items are able to be exported out of the country and taken with you to your intended destination. Encryption software that is not commercially available on a mass market basis may be regulated or restricted from being brought into some countries. See Export Controls on Encryption Software for more specifics.

When you travel internationally in your role as U-M employee or student, you must register your travel with the U-M Travel Registry. Registering travel with the U-M Travel Registry is also encouraged for personal trips. The U.S Department of State also allows you to record information about your planned trip so that they can assist you in case of an emergency.

If your destination is subject to U.S. embargoes, the U-M Travel Registry will automatically send your travel information to the Export Control Program, and you will be contacted to assure your travel complies with export regulations. If you are traveling to or through any other destination that is subject to other travel restrictions, you will need to talk to the Export Controls Program to ensure your travel complies with U.S. export control regulations.  

Destinations currently subject to the most comprehensive US embargoes include:

  • Cuba

  • Iran

  • North Korea

  • Sudan

  • Syria

  • Crimea region of Ukraine

Even if you do not need an export license to travel to your destination, you may need an export license to conduct certain activities in specific countries or to take certain items with you.

PLEASE NOTE: If you are planning to travel to Iran for a meeting or conference, you will need to obtain an export license prior to your trip. You should contact the Export Control Program immediately to allow time to apply for the license.

No. This is an often-heard misconception. The unit's cost-sharing is determined before the UMOR review takes place. Although the end result may be that the unit and UMOR each contribute the same amount toward the cost-sharing, matching is not automatic.

About $3 million in the Vice President's annual budget is specifically designated for cost-sharing. Most of the requests are for amounts in the range of $10,000 to $50,000. When requests for very large amounts of cost-sharing appear justifiable, the Vice President consults with the other executive officers to determine if other University funds can be made available for the requested purpose.

As defined in the FAR at 2.101, a micro-purchase is an acquisition of supplies or services using simplified acquisition procedures, the aggregate (total) amount of which does not exceed the micro-purchase threshold.

6-1.1: Click Update for each animal that will be administered LPS

--Provide the requested information regarding dosage and routes of administration.

--Note that animals administered LPS may be housed at ABSL1.

6.1: Each type of animal that you will be administering LPS to must have an entry in this list. Add entries, if needed, and be sure to provide the following information in the detail questions:

--Q5: Answer “yes” here.

--Q8: Answer “yes” here as well.

--Q8.1: Select LPS from the list. (If you do not see LPS in this list, check your response to Q13 of the detail questions for LPS in Section 4-2: it must be “yes”.)

Q4.2: Answer “yes” here.

Q4.3: Be sure to include in this response a description of your work with LPS.

4-2.1: Create an entry for LPS in this table

--Q12: Note that work involving LPS requires BSL2 containment/handling.

--Q13: If you will be administering LPS to your animals, answer “yes” here.

Be sure to answer "yes" to the option for Infectious Agents/Biological Toxins.

Unfortunately, we cannot accept résumés and applications for graduate programs or research opportunities. Find application materials on the Rackham graduate programs website or follow the employment application procedures on the University of Michigan careers/job postings site. Do check the eligibility requirements for any programs you see. Many summer research opportunities are only available to U.S. Citizens.