May’d It

FIELD NOTES / OCTOBER 18, 2026

Five FDA letter records, two dates worth keeping

A bounded FDA table sample illustrates the difference between a letter’s issue date and its public posting date.

By Mayd It LLC · Observed 2026-10-18T13:05:18.735Z · Bounded source sample

5saved letter records
7–32days from issue to posting
25source rows inspected

What this sample contains

On October 18, 2026, we requested the FDA warning-letter table ordered by posting date, read a 25-record source window and saved five records. All five saved records showed a posting date of October 13, 2026. Their issue dates preceded posting by 7 to 32 calendar days.

This difference matters when building a publication-monitoring queue. A posting date can indicate when a record appeared in the public table, while the issue date describes the letter itself. Neither should silently replace the other. The calculation is postedDate minus letterIssueDate in UTC calendar days.

Read missing links narrowly

The five saved table records had no posted response or closeout link in this observation. That is a statement about the fields captured from this table window. It does not establish that a company never responded, that corrective action has not occurred, or that a present regulatory concern remains unresolved.

Open the original FDA letter and any later updates before making decisions. The FDA warning-letter index is the source; every saved record retains its official letter URL. We do not reproduce letter bodies or assign supplier risk scores.

A better review-queue design

Use letterUrl as the record identity. Preserve MARCS-CMS ID, posting date, issue date, office and observedAt, then add a human reviewer and a reviewed-on date. If you link a record to a supplier master, verify the entity match rather than treating similar names as identical companies.

A repeated observation can surface a newly posted response or closeout link. An absent row from a later capped window cannot establish that a letter was removed or a matter resolved.

Method and boundaries

The output cap stopped this run after five saved records, while the source table reported more available records. Rows tied on the same posting date can rotate at the boundary. This is not a census of letters issued or posted in a week, nor a sample suitable for estimating industry-wide enforcement trends. The Actor captured table metadata only.

Download the exact input, selected records and coverage summary, or use the linked workflow to build a small review sheet. The example provides a research queue, not a legal or product-safety conclusion.

The saved observations

Historical sample · October 18, 2026 UTC
Marcs Cms IdPosted DateLetter Issue DateHas Posted ResponseHas Posted Closeout
7345382026-10-132026-10-05falsefalse
7292232026-10-132026-09-11falsefalse
7301542026-10-132026-09-11falsefalse
7358592026-10-132026-10-02falsefalse
7251362026-10-132026-10-06falsefalse

Download JSON for all selected fields and original source links.

Use the method on your own watchlist

Keep the source identifiers and limits with your results. Review the Actor documentation, or follow the step-by-step workflow.