10-K and 10-Q deadlines: plan the production work backward

An SEC deadline is not the moment to start document conversion. The standard filing periods depend on the form and filer status, and the production schedule needs to leave room for proofing, tagging where applicable, corrections and authorized submission. The SEC's Financial Reporting Manual summarizes the standard periods. SEC reporting timetable.

The standard periods, in plain language

For annual reports on Form 10-K, the standard periods are 60 days after fiscal year-end for large accelerated filers, 75 days for accelerated filers and 90 days for non-accelerated filers. For quarterly reports on Form 10-Q, the standard periods are 40 days for accelerated and large accelerated filers and 45 days for non-accelerated filers. SEC timetable and status discussion.

These are reference periods, not a personalized deadline calculation. Confirm the company's current status, applicable form instructions, fiscal year or quarter end, weekends and holidays, and any relevant relief or extension provisions with the responsible adviser. Smaller-reporting-company status should not be used as a shortcut for determining accelerated-filer status.

Build backward from authorized submission

Write down separate milestones for the intended filing time, final approval, completed validation, consolidated proof corrections and delivery of the approved source. Assign an owner to each milestone. A single calendar event labeled "file report" hides all of the work that must happen before it.

• Source lock: identify the exact approved document version.
• First proof: allow the disclosure team time to compare the conversion.
• Tagging review: coordinate with the responsible specialist if required.
• Final revision: reconcile all outstanding instructions.
• Release approval: authorize the specific package that will be submitted.

These are suggested production milestones, not SEC-mandated internal deadlines.

Use buffers for known uncertainty

A routine editable source and a scanned report with complex tables do not carry the same conversion risk. Estimate the schedule using the source quality and expected proof cycles, rather than page count alone. If the team expects late financial changes, agree how those changes will be logged and rechecked.

For an illustrative example, a team may reserve one internal window for final table changes and another for checking the revised tagged document. The exact time allocation depends on the filing; the principle is to keep revision and validation from competing for the same final minutes.

Do not let account access become the hidden dependency

EDGAR Next concerns access and account management, not new disclosure deadlines. Confirm that the authorized submission team can access the relevant filer account and that annual confirmation responsibilities are assigned. A finished document does not overcome a separate access problem. SEC EDGAR Next FAQ.

When the schedule slips

Escalate a missed milestone to the authorized filing owner. Do not infer that a service provider's willingness to accept work means an extension is available. Decisions about late-filing notices, relief or legal consequences belong with the responsible legal and compliance advisers.

Keep a record of the final approved files and submission response. That record is more useful for the next reporting cycle than a general promise of "same-day filing." This guide is production-planning information, not legal advice or an issuer-specific filing calendar.