GoodState
How to read notice delivery status and proof
A notice draft, a delivery attempt and a recorded outcome are different stages. In a supported GoodState workflow, delivery status describes the administrative event recorded for that attempt. It does not, by itself, show that an employee acknowledged a document or that every legal obligation is complete. [1][2]
Read the status before deciding what comes next
| Recorded stage | How to read it |
|---|---|
| Draft ready / prepared | The email draft is ready; it has not been sent. |
| Submitted, accepted or processing | The outcome is not yet confirmed. Do not treat the label as employee acknowledgment, and do not resend just because the result is pending. |
| Confirmed or reconciled | Review the recorded outcome. These labels still do not record an employee acknowledgment. |
| Unknown | Check the attempt’s status; do not send another copy to guess whether the first one worked. |
| Failed, rejected or canceled | The attempt is saved. Review its status before any further action; the label is not permission to resend. |
These meanings explain recorded statuses; they do not authorize a new delivery, a retry or an action outside the account’s supported service.
Keep the document question separate from the delivery question
First identify the document and version the record refers to. Then check the person or work item it concerns and the recorded delivery outcome. A result for one document or attempt should not be stretched into proof that a different document or a later version was delivered.
If the record is incomplete or the outcome is unclear, resolve that uncertainty through the account’s supported status-check and support process. Do not call the task complete simply because a draft exists or a provider accepted an attempt.
Delivery is not employee acknowledgment
GoodState’s terms say delivery and proof records describe administrative events. They do not guarantee that an employee read a document and do not certify legal compliance. A separately recorded acknowledgment, if present, is a different piece of evidence; it should not be inferred from an email status. [1][2]
The employer remains responsible for obligations outside the service expressly made available to the account. A notice record also should not be treated as proof of a separate payroll task, agency report or other unsupported obligation. [1][2]
A useful review before closing a task
Ask:
- Which document version and person or work item does this record cover?
- Is the result a draft, an in-progress attempt or a recorded outcome?
- Is anything failed, held, unknown or still awaiting correction?
- Is there separate evidence for any acknowledgment or other completion condition being claimed?
This is a suggested record-review workflow, not a legal retention schedule or a promise that a particular export or acknowledgment feature is available. When contacting support, avoid ordinary email for Social Security numbers, medical records, payroll files, payment-card details or unnecessary sensitive employee information. [1][2]
Sources and planning help
[1] GoodState Customer Terms, version 2026.10.22.1, sections 3, 4, 6 and 7.
[2] GoodState Terms for Larger Teams, version 2026.10.28.2, sections 3, 4, 6 and 7.
Source checked: November 11, 2026. For service-fit questions, see GoodState. For free planning examples to confirm against agency instructions, open the Compliance Calendar.