Example source lines
Assume a funding notice contains these five lines. The wording is fictional, but the structure reflects common application and award requirements.
- Applications must be submitted by October 18, 2026 at 5:00 p.m. ET.
- The application must include a project narrative, work plan, and budget narrative.
- Recipients shall maintain financial records for three years after closeout.
- For-profit organizations are not eligible.
- The program is intended to expand access to community services.
Example checklist output
A conservative first pass places each non-empty source line in one primary queue and retains the exact wording and source-line number.
- Deadline: application due October 18, 2026; verify the time zone and submission method in context.
- Deliverable: project narrative, work plan, and budget narrative.
- Obligation: three-year financial-record retention after closeout.
- Restriction: for-profit organizations are not eligible.
- Review: program-purpose language that may affect interpretation but is not itself classified as a requirement.
Why the Review queue matters
A requirements tool should not silently discard headings, definitions, background, exceptions, or cross-references. Those lines can change the meaning of nearby requirements even when they do not match a narrow category pattern.
Review the uncategorized lines after the focused queues and return to the original layout whenever copied text has flattened tables, footnotes, or multi-line clauses.
What the example does not prove
This checklist is not an eligibility decision or a complete compliance matrix. It does not prove that every attachment, page limit, scoring criterion, registration, or portal rule was found. A line can also belong to more than one practical work queue even though the deterministic first pass assigns one primary category.
Turn the first pass into assigned work
After verifying each item against the complete notice and attachments, add an owner, internal due date, source citation, status, and completion evidence in the team’s normal project system. Keep the authoritative notice linked to every material decision.