Grep · sample report

Rules to Requirements Checklist — You get a numbered, testable checklist from your rule document, with source clause, acceptance criteria, deadlines and open ambiguities, scoped to what you're building.

workon demandoperational
Inputs used for this sample
Rules to Requirements Checklist

Rule, solicitation or standard to extract from: NSF 24-123 Smart and Connected Communities solicitation

What it must apply to: Our mobile checkout flow for US shoppers, including saved cards and guest checkout

Jurisdiction or issuing body (optional): California

Sections or topics to focus on (optional): Accessibility, consent and disclosure language, data retention

NSF 24-123 vs. Mobile Checkout Flow (California): No Applicable Requirements Found

Header

Result: the requirements table is empty for the checkout flow

Every row below is a closest-match clause I checked and excluded, or an NSF-side obligation that applies to proposers, not to a shopper-facing flow. The classification is my reading; counsel review is advised before relying on it.

# Requirement Mandatory / Recommended Source clause Acceptance criteria Due / effective Owner Ambiguity / notes
1 Accessibility of checkout UI: none stated. Not specified in text NSF 25-527 has no UI accessibility standard; its only disability-related funding provision is FASED, "funding for special assistance or equipment to enable persons with disabilities to work on NSF-supported projects". None derivable. n/a Product/UI Interpretation needed: this is a grant-funding provision for researchers, not a UI standard. The NSF 24-123 letter has no accessibility clause.
2 Consent and disclosure language for shoppers: none stated. Not specified in text NSF 25-527 Privacy Act statement describes how NSF uses proposal-form information. None derivable. n/a Legal/Compliance It is NSF's own collection notice for proposers. Do not copy it into checkout.
3 Data retention periods for card or guest data: none stated. Not specified in text No retention clause found in either document. None derivable. n/a Data/Security Counsel review advised: retention duties for a checkout flow come from other law, not these documents.
4 Only eligible organizations may submit proposals. Mandatory Proposals may only be submitted by the following: IHEs; non-profit, non-academic organizations Submitting entity is a US-accredited IHE or qualifying non-profit. Per due dates below Proposal/PI Inference: a commercial retailer's checkout team is not an eligible submitter. Confirm with NSF.
5 Preliminary proposal required for SCC-IRG and SCC-LSR. Mandatory Full proposals without a preliminary proposal "will be returned without review" Preliminary proposal accepted before full submission. See Key dates Proposal/PI Disqualifier, listed because the brief requires all disqualifiers.
6 NSF 24-123 itself: submit EFRI topic ideas of up to 500 words. Optional invitation Topic ideas "maximum 500 words"; deadline October 15, 2024 n/a October 15, 2024 (passed) Other A request for research topic ideas, with no relevance to checkout.

Key dates

Open questions

  1. (Rows 1 to 3) Did you mean a different document, such as a privacy or accessibility standard, or a funder notice that does regulate checkout? Confirm the document number with whoever gave you the request.
  2. (Row 4) If a funding application is in fact planned, ask NSF through its official program contacts whether a commercial applicant is eligible.
  3. (Rows 1 to 3) Ask counsel which California and federal rules govern accessibility, consent language and card-data retention for checkout. That is a separate extraction.

Do next

  1. Confirm the intended document with the requester.
  2. If it is a legal or standards source, rerun this checklist against that text.
  3. Do not use NSF 24-123 or NSF 25-527 as evidence of checkout compliance.

Near misses

Coverage

I read NSF 24-123 and NSF 25-527 on nsf.gov in full text form. I did not read the PAPPG, which NSF 25-527 incorporates, or NSF 25-543. I extracted no California statutes.

Sources