01 — Institutional purchasing

For institutional buyers

A department, district, library or university can buy a subscription on a purchase order with a net-30 invoice. This page is the vendor file that procurement will ask for.

02 — Vendor file

What documents can procurement get, and when?

Each artifact below carries a status rather than a download badge. A status you can act on is more useful to a buyer than a checkmark that turns out to mean nothing when it is requested.

Procurement artifacts and current status
ArtifactStatusWhat it contains
Signed IRS Form W-9 Available on request Current-year signed W-9, downloadable from this page and from checkout.
SAM.gov Unique Entity ID Available on request UEI plus current registration status and expiry.
HECVAT Lite Available on request Completed higher-education vendor assessment.
VPAT 2.4 / 2.5 accessibility conformance report Scheduled Independent third-party audit against WCAG 2.1 AA, remediation, then the report.
Public Entity Terms Addendum In drafting Indemnification carve-out, venue, and a public-records acknowledgment.
Security and privacy posture Available on request Transport security, infrastructure attestations, and the data-retention statement.
State vendor registrations Available on request State purchasing-system vendor identifiers.
Accessibility statement and remediation contact Published with the report Named contact for accessibility issues and the remediation route.
Scroll the table sideways to see the rest

Needs client material — Vendor artifact set

Every row above is launch-blocking client material: the signed current-year W-9, the SAM.gov UEI and registration status, the completed HECVAT Lite, the Public Entity Terms Addendum, the security and data-retention statement, and any state vendor identifiers. Statuses render from a client-maintained record; no artifact is implied to exist before it does.

03 — Accessibility

Is there a VPAT, and what is the status?

An independent accessibility conformance report is scheduled and is not yet complete. An independent audit against WCAG 2.1 AA, the remediation it produces, and the written report are a six-to-twelve-week engagement. In the meantime this site is engineered to WCAG 2.1 AA and verified before launch with two automated engines plus a manual keyboard, screen-reader and contrast checklist. The report will be published on this page on completion.

Public entities purchasing web software work under the Department of Justice rule adopting WCAG 2.1 AA for state and local government web content. ADA.gov: web and mobile accessibility rule.

A SOC 2 Type II audit is not held and is not planned at this price point. For a directory subscription that stores no student records, no patient data and no financial account data, infrastructure attestation from the hosting and payment providers plus a completed HECVAT Lite is the proportionate answer, and that is what the vendor file contains.

No accessibility overlay widget is installed on this site, and none will be. Overlays do not fix the underlying markup and have been a magnet for litigation.

04 — The route

How does the purchase actually run?

A requisition opens, procurement asks for the vendor file, the public-entity addendum settles the contract terms a state buyer cannot waive, a purchase order is issued against the quoted term, and an invoice follows on net-30 with access beginning at issue.

The published terms specify a Florida venue. A public entity outside Florida generally cannot accept that, which is what the addendum exists to resolve. Read the venue clause.

FIG. GW-06 — Institutional purchase path The procurement route drawn end to end: requisition raised, vendor artifacts requested (W-9, SAM.gov UEI, HECVAT Lite, and a VPAT or ACR marked scheduled rather than complete), public entity addendum agreed, purchase order issued, then a net-30 invoice and access. 01Requisition raisedA department identifies the tool and opens a requisition.02Vendor artifacts requestedProcurement asks for the vendor file.W-9SAM.gov UEIHECVAT LiteVPAT / ACR — scheduled03Public entity addendum agreedIndemnification, venue and public-records terms are settled.04Purchase order issuedThe PO is raised against the quoted subscription term.05Net-30 invoice and accessAn invoice is issued and access begins. FIG. GW-06 — Institutional purchase path The procurement route drawn end to end: requisition raised, vendor artifacts requested (W-9, SAM.gov UEI, HECVAT Lite, and a VPAT or ACR marked scheduled rather than complete), public entity addendum agreed, purchase order issued, then a net-30 invoice and access. 01Requisition raisedA department identifies the tool andopens a requisition.02Vendor artifacts requestedProcurement asks for the vendor file.W-9SAM.gov UEIHECVAT LiteVPAT / ACR — scheduled03Public entity addendum agreedIndemnification, venue andpublic-records terms are settled.04Purchase order issuedThe PO is raised against the quotedsubscription term.05Net-30 invoice and accessAn invoice is issued and accessbegins.
Scroll the diagram sideways to see the rest
FIG. GW-06 — Institutional purchase path.

Needs client material — Artifact nodes in FIG. GW-06

A node in this figure must never imply an artifact exists before it does. The accessibility report node carries the word "scheduled" rather than a completion mark until the independent audit is finished.

05 — Request an invoice

Request a PO invoice

Or call (561) 249-4129, or email support@grantwatch.com.