{'fraction_non_alphanumeric': 0.026058631921824105, 'fraction_numerical': 0.0, 'mean_word_length': 4.872611464968153, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Constructing a competitive proposal.

Although the proposal abstract is not technically considered in the review process, the importance of this single page cannot be overemphasized. It is often the first thing read by the reviewers, and may be the only part of the proposal that some reviewers read thoroughly. The abstract should provide an effective and informative summary of the project, and should address specifically any impact indices (e.g., the number of individuals to be served, the number and type of products to be developed). It should touch briefly on project need, procedures, and outcomes. Grant consultant Liane Reif-Lehrer gave the following advice at a seminar on proposal writing: "Don't write the abstract until the proposal is done, so it reflects the contents of the application. Present the information in the abstract in the same order that it appears in the full proposal for quick reference".