Some Dos

• Include concrete plans for work and results in the next FY.
• Be as specific as possible. (Include dates, places, measures, and so on.) Give examples of specific utility value. A "presentation" is rarely an accomplishment.
• Projects should have a clear objective; Projects need objective beyond integration (no matter how complex). Tie Objectives, Approach, Plans, Accomplishments (where appropriate) specifically to IPTO Objectives.
• Describe the astounding new capabilities you are striving to achieve.
• Present a project that is unified, coherent, and focused (as opposed to diffuse).
• If something has been accomplished, say how it is being disseminated (be specific).
• When you accomplish something that is a sidelight to the project and then report that, explain why you needed to do that sidelight to support the project objectives.
• Ensure that accomplishments and expenditures to date justify additional funding requested.
• Where possible, quantify accomplishments and results.
• Identify concrete, specific, and serious plans for technology transition.
• Project summaries should express significant content with respect to the project's main objectives.
• Both the problem and the approach to solving the project should be clearly stated.
• Past Year Accomplishments and Next Year Plans should show a significant velocity of movement.
• Projects should exhibit significant results for the money invested. (Conversely, the opposite is bad.)
• Projects should strive to achieve results as early as possible.
• Continued funding should be contingent on demonstrated results.
• Projects developing abstract technologies should find a target application upon which to demonstrate and measure results.
• Name no more that one or two PIs who can be held accountable for the project.
• For objectives, give specific dates when they will be accomplished (or when you hope to accomplish them).
• In technology transition section, identify possible applications of your results.
• Including something about military applications is always useful.

No. The data you submit via the web form will not run through a spell checker. Please spell check in advance.

For security and performance purposes a timeout period has been established. If you do not perform an action in the browser that communicates with the server (i.e., click Validate or Submit) over a 120 minute time period you will be forced to login again. Entering data or editing data in form fields does not involve a server action and will therefore leave you susceptible to "timing out". Clicking on any options/buttons will initiate a server action and will prolong your session. We feel that 120 minutes is plenty of time to complete the form, particularly if you have composed the report in advance.

If a "time-out" period occurs, any data will be lost and you will need to reenter the data. So it is advisable to have data created in advance in the text-editor format you desire in a before cutting and pasting into the appropriate fields.