“Pending” means a matter is waiting for an action, decision or event; it does not mean approved. “In progress” indicates work is under way, not finished. “On hold” normally means temporarily paused or delayed. “Completed” means a defined task is finished, while “resolved” refers to a problem being dealt with or settled—sometimes in a way that is narrower than the customer expects. Accurate translation must preserve the exact state, owner and next step.
Readers searching for pending meaning, in progress meaning, on hold vs pending, completed vs resolved, under review meaning, awaiting approval, closed vs resolved, blocked vs delayed, status updates translation need distinctions that work in task trackers, school portals, booking systems, customer support, payments and administrative notices. These words are often presented as tiny badges or short email replies. They can determine whether a person waits, acts, submits again or assumes a service has already been delivered.
The practical method is a status ledger with STATE, OBJECT, OWNER, BLOCKER, NEXT ACTION, TIME and EVIDENCE. A message that says “Application received” concerns receipt; “Application reviewed” says something about examination; “Application approved” concerns a decision; “Funds released” concerns another action. The target language’s natural form may differ, but no stage should appear to have occurred unless the source states it.
This chapter covers the status-state layer of the Master Art of Translation system. It complements Short Email Replies — Noted, Received, Approved and Will Do, which examines compact conversational replies, and Complaints and Feedback, which examines grievances. Here we focus on the state of work itself and whether an update gives the reader a reliable basis to act.
Quick comparison: what each status proves and doesn’t prove
A status should be interpreted as a claim about a particular object or workflow at a particular time. It is not a generic mood word. This comparison helps readers distinguish labels that are frequently mistranslated in dashboards.
| Status | What it indicates | What it does not establish |
|---|---|---|
| Received | The stated item entered a recipient or system | It was accepted as correct |
| Pending | A decision, action or event remains outstanding | The outcome is approved or rejected |
| Under review | A review process is taking place or assigned | A favorable decision is certain |
| In progress | The relevant work has started and is under way | It has been completed |
| On hold | The activity or process has been paused | It was permanently canceled |
| Blocked | A constraint prevents a step from proceeding | The work is impossible forever |
| Awaiting approval | An approval decision is still needed | Approval has been granted |
| Approved | A particular decision or permission was given | Work has been performed |
| Completed | The defined work was finished | It was independently verified or accepted |
| Resolved | A specific issue was settled or handled | Every related problem was fixed |
| Closed | A case or process was administratively closed | The customer is satisfied |
| Canceled | A planned action or event will not proceed as planned | It will automatically be rescheduled |
Pending: Waiting for What?
The Cambridge Dictionary entry for pending explains both waiting to happen and waiting to be decided or approved; pending can also be a preposition indicating a dependent wait, such as a suspension pending investigation. Translate the specific object, not merely the vague idea of delay.
“Payment pending” might mean the payment is authorized but not settled, awaiting verification, or in another transaction state defined by the provider. The English label alone does not disclose the exact banking stage. An accurate target must not convert it automatically into “payment completed” or “payment failed.” The system’s own documentation may supply a narrower meaning.
In Progress: Active Work, Not a Finished Deliverable
“Review in progress” suggests the review is under way. It does not prove that an editor has finished reading, that the work passed checks or that a publishing decision is ready. In a school portal, “assignment in progress” might describe a draft being worked on, not submitted to the teacher.
The target should make the action’s current nature intelligible. If a project management system distinguishes started, in progress and testing, preserve those separate stages even if a general English paraphrase could call all three ongoing.
On Hold: A Pause, Not Necessarily a Rejection
The Cambridge Dictionary entry for on hold covers intentional delay of an activity as well as waiting on a telephone. “Your application is on hold pending documents” generally means it has been paused until a dependency is addressed. It does not necessarily mean the applicant was rejected.
A support agent who says “Please hold” may ask the caller to wait during an active telephone interaction rather than refer to the person’s application status. The target must identify the domain: a task paused, an account restricted, a caller waiting, or an institution deliberately deferring work.
Awaiting Approval: Who Must Decide?
“Awaiting manager approval” identifies a dependency on a manager’s decision. It does not say the manager reviewed the request, and it does not guarantee a positive outcome. “Approved by the manager” says that a decision was made, but not necessarily that finance processed the payment or operations shipped the item.
Where an article or interface uses named roles, retain those roles. An approval by a team leader is not automatically a board resolution or a regulatory permission. Translators should not upgrade a personal acknowledgment into institutional authorization.
Under Review: Activity or Queue Status?
“Under review” often describes a matter being evaluated. Depending on the system, it may mean actively being considered or simply assigned to a review queue. Some organizations define the state precisely. A translator should use the intended workflow definition rather than assume someone is currently looking at the screen.
The phrase is neither approval nor rejection. “Under editorial review” differs from “under security review” in topic and authority. Keep what is being checked and by whom if the source states it, while leaving the result uncertain.
Blocked: A Particular Dependency Prevents Progress
“The deployment is blocked by a missing test certificate” states a specific impediment. “The deployment is on hold while management reviews costs” describes an intentional pause. Both stop progress, but the cause and remedy differ. A target that says the deployment was permanently abandoned might be too strong.
Blocking can be technical, administrative or informational. If the source identifies the dependency, preserve it: data access, safety sign-off, missing parts or external response. The next action may be clearing the blocker, not restarting every project task.
Delayed: Later Than the Baseline
“Shipment delayed” reports a timing deviation from an expected or scheduled arrival. It doesn’t necessarily mean canceled, lost or damaged. “Shipment postponed” may also signal a deliberate change of schedule rather than only a late transit event.
A customer-facing target should keep whether the delay is confirmed or predicted. “Could be delayed” expresses possibility; “is delayed” reports current status. The same future date might remain uncertain even after a delay notice.
Scheduled: Planned at a Time, Not Yet Performed
“The review is scheduled for Monday” gives an arrangement, not evidence the review happened. “The review was scheduled for Monday” can describe a past plan, which may or may not have occurred. “The review took place Monday” reports an event.
Translate the chosen tense and aspect with the appropriate source chronology. If an online calendar invitation was only proposed and has not been accepted, that status may need a separate term rather than a blanket scheduled label.
Assigned: Responsible Person Identified
“The ticket has been assigned to a technician” says ownership was allocated. It doesn’t establish that diagnostic work started or that the technician accepted every task. A target that reports “The technician fixed it” jumps from allocation to completion.
Where responsibility determines next steps, preserve the named role, team and case number. Assignment is a process event, not an outcome.
Acknowledged: Knowledge or Receipt, Not Endorsement
“Acknowledged” often means someone recognized or received a message. It may be a formal response in a system, but it doesn’t inherently accept the underlying position. “I acknowledge your request” is not necessarily “I approve your request.”
The same word can also be used in professional contexts to recognize fault or responsibility when the source explicitly says so. Avoid an automatic target that erases the object of acknowledgment. The precise phrase “acknowledged receipt” differs from “acknowledged wrongdoing.”
Received and Submitted: Two Sides of One Transfer
“The student submitted the assignment” records a student’s action. “The portal received the assignment” records a system’s receipt. A student’s browser might show “upload started” without verified receipt. A target that equates all three could make the student mistakenly believe the teacher has the work.
Keep the actor and technical event: initiated, uploaded, received, processed, available for marking. In systems that provide a transaction or confirmation number, that identifier may be important evidence of submission status.
Processing: Work Being Carried Out on an Item
“Payment processing” or “Order processing” can mean the system is performing the relevant transaction steps. The label does not by itself specify settlement, dispatch, collection, approval or success. Each product may define processing differently.
In an online shop, “Processing your order” isn’t the same as “Your parcel has shipped.” In an education system, “Processing your registration” isn’t the same as a confirmed place. Preserve that operational distinction.
Completed: Finished According to Which Criterion?
“Task completed” says a defined task reached its completion criterion. It might still be awaiting a supervisor’s inspection, a client’s acceptance or a later integration step. “Test completed” need not mean “Test passed.” A translation that adds passed changes the outcome.
The object of completion matters: draft writing finished, proofreading completed, submission received, lesson attended, payment initiated or refund credited. If the source says a review was completed, don’t claim the document was approved unless that decision is separately stated.
Resolved: Settled Issue, Not Necessarily Customer Happiness
“The issue was resolved” typically suggests a problem has been dealt with or a satisfactory solution reached in the applicable context. A ticketing system may use resolved as a specific internal state even if users still need to confirm the fix. The translation should represent the platform’s actual definition, not a universal guarantee of satisfaction.
A reported login fix doesn’t imply every other service is operational. Scope matters: “The authentication error was resolved” is narrower than “The entire platform is fully restored.”
Closed: Administrative Status Can Differ From Substantive Outcome
“Case closed due to no response” means a process ended administratively because a reply wasn’t received. The underlying fault may remain. “Case resolved and closed” makes two claims. “Complaint closed after withdrawal” reports another reason.
A target that renders closed as all problems fixed can mislead customers and regulators. Read the closure reason and actual remedy before selecting a target status word.
Reopened: A Previous Closure Is Reversed
“Ticket reopened” tells readers the case had reached a closed or resolved state and then became active again. It doesn’t mean the original problem was newly discovered or a second complaint was filed, unless a system says so.
Reopen is also used for businesses and facilities. “The library reopened” is a public availability event; “The case reopened” is a workflow status. Choose wording appropriate to the object.
Approved: An Authorization or Decision, Not Implementation
“Budget approved” indicates a specified decision was made by the relevant authority in context. It does not prove money was disbursed or purchases completed. “Approved for testing” is more limited than “Approved for production.” The target should not expand an approval’s scope.
Legal or institutional review may be needed for exact approval terminology. A manager’s informal agreement can differ from an authorized signature, and translation shouldn’t manufacture one.
Rejected, Denied and Unsuccessful
“Application rejected” reports a negative outcome under a process. “Access denied” reports refusal of a particular operation or permission. “Unsuccessful applicant” describes someone not selected. They are related but may have different procedural grounds.
Where appeals, revision or reapplication are possible, preserve the stated route. Do not turn a denial into a permanent ban if the notice allows reconsideration, and don’t replace a final negative decision with vague pending language.
Canceled: Activity Not Proceeding As Planned
“The event was canceled” states that the original event will not go ahead as scheduled. It doesn’t automatically promise another date, a refund or another venue. “The event was postponed” more strongly points toward a later occurrence, while the new date may be undetermined.
The forthcoming Reschedule vs Postpone vs Cancel guide will focus on time changes. For the present status review, the important principle is that canceled and delayed are not synonyms.
On Hold vs Suspended
“On hold” can signal a temporary pause without necessarily naming authority. “Suspended” may be a specific administrative or formal restriction, such as a membership suspended pending investigation. Its exact meaning depends on policy. “Permanently terminated” is often stronger.
A target should not announce permanent expulsion from an ordinary review hold, nor soften a binding restriction to a casual pause. Keep procedural force and any condition for resumption.
Waiting vs Awaiting a Specific Party
“Waiting for customer response” identifies the customer as owner of the next communication. “Awaiting manager approval” identifies a decision-maker. “Awaiting system sync” describes a technical process. The three may all appear as pending but call for different action.
Preserve the named dependency. A reader who thinks they must reply when the system is actually synchronizing may waste time; a customer who thinks the software is waiting when they need to upload a form may miss a deadline.
No Update: Absence of New Information
“No update yet” indicates nothing new has been communicated in that context; it doesn’t establish that no work has occurred. “Work has not started” is a stronger assertion about activity. A translation that substitutes one for the other may make the team look inactive without evidence.
Likewise “Still investigating” communicates ongoing effort, not necessarily a change of status. Keep actual state and communication frequency separate.
No Change: Scope of the Unchanged State
“No change to the delivery date” preserves one date. It doesn’t say the product price, shipment status or customer details stayed identical. A target “Nothing changed” expands the claim. Qualifiers such as to the schedule, in the symptoms or since yesterday can be essential.
A useful status update names the property. “The date is unchanged, but the venue has moved” contains both stability and change; the translation should not erase the contrast.
At Risk: A Forecast About Status
“The milestone is at risk” suggests a future failure or delay is possible, often without asserting a current miss. “The milestone was missed” reports an actual failure to meet it. “The project is blocked” may identify an existing dependency. These are different operational meanings.
Translators should preserve probability and time, especially in weekly status reports. A red-risk indicator is not itself proof that the outcome already failed.
Needs Attention: Action Required Without Defining Failure
“Needs attention” tells a user that further review or action is warranted. It does not necessarily mean the matter failed. “Action required: verify your address” specifies a concrete task and who should perform it.
If an interface sends a notification, the translated alert should direct the user to the same safe action. Avoid turning a request for verification into a notice of deletion or lockout unless stated.
In Transit, Out for Delivery and Delivered
“In transit” says goods are moving through a supply chain; “Out for delivery” describes a later operational stage in many courier systems; “Delivered” claims the relevant delivery event occurred. A target that equates them can mislead a recipient waiting at home.
Carrier definitions and proof of delivery differ. A delivered scan may not tell the entire story of who received an item, so a translation should not invent the identity of a person who signed for it unless recorded.
Refund Initiated, Processed, Issued and Credited
“Refund requested” describes a customer’s action; “Refund approved” reports a decision; “Refund initiated” describes a process start; “Refund credited” reports a posting or receipt into an account. The timeline can vary by provider and payment method.
Use the service’s defined terminology where possible, and preserve who issued the update. Do not tell a customer money is back in their account if the source only confirms initiation. Financial status is not a matter for stylistic rounding.
Submitted for Review, Reviewed and Accepted
“Submitted for review” describes a handoff. “Reviewed” indicates examination; it may be favorable or unfavorable. “Accepted” reports a decision. “Published” or “released” is an additional public-facing event. These states are especially important when translating academic submissions or content approvals.
A target that jumps from reviewed to published can cause unauthorized release, while one that weakens accepted to under review may mislead an author about editorial progress.
Student Portal: Draft, Submitted, Marked, Returned
An assignment saved as a draft hasn’t necessarily been turned in. Submitted indicates the learner completed the relevant submission action, subject to system confirmation. Marked means a teacher evaluated it; returned may mean feedback became available. Each is a different learning stage.
A student and parent can misunderstand missing homework if these labels are translated poorly. Keep submission evidence, grade visibility and the next action clearly separated.
Status Labels Can Be Short but Still Precise
A dashboard may have space for one or two words, so translators sometimes prefer a generic term such as ongoing. But if the product differentiates “pending approval,” “in progress,” and “on hold,” one label for all three destroys workflow information. Use concise distinct target terms validated in the interface.
A tooltip or explanatory line can provide clarity without filling every badge with a sentence. The governing requirement is that a user can tell whether they must act or wait.
A Status Doesn’t Guarantee Open Now
“Open” can refer to a case, a retail shop, an application period or a ticket state. A case marked open does not prove a physical office is open for walk-in visitors. A product named “open application” may mean submissions are accepted; an open customer-service ticket means unresolved or active.
Keep the domain and object visible in the translation and avoid importing retail opening hours into an administrative workflow.
Timestamp: When Was the State True?
A status can change between the moment a report is created and the moment it is read. “As of Monday, review was pending” is a historical snapshot. “The review is pending” makes a present claim in the source’s narrative time. A translator should not silently update Monday’s status to today’s date.
In localized dashboards, display and time-zone conversions must preserve the actual timestamp and offset. An update time isn’t necessarily the event completion time.
Worked Case Study: One Application Through Seven States
Imagine a student’s bursary application. The portal first says “Saved as draft,” then “Submitted,” then “Received,” “Under review,” “Awaiting documents,” “Approved” and finally “Payment scheduled.” A mistranslation at any stage can change the student’s next step. Submitted does not prove acceptance; awaiting documents may require the family to act; approved does not prove money was paid.
If the final label changes to “Payment completed,” that is another claim about transaction state. A helpful translation should permit an explicit check if the payment has not arrived, while not converting the approval notice into a bank statement.
Worked Case Study: A Support Ticket Closed Without Repair
A user reports a recurring login error. The support portal shows “Received,” “Assigned,” “In progress,” and finally “Closed—customer did not respond.” The final case closure does not necessarily prove the login error was repaired. The translated reason should be visible so a user can decide whether to reopen the ticket or seek further help.
The same workflow might instead say “Resolved—password reset completed,” which makes a specific remedial claim. Closure reason and actual remedy, not the green icon alone, determine what the translation should imply.
Thirty Worked Status Translation Examples
Order submitted
Source status: “The order was submitted at 14:10.” This communicates the following bounded state: The user’s submission event is recorded at a particular time. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A translation saying payment was received invents another stage. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Can fulfillment still be pending? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
Application received
Source status: “We have received your application.” This communicates the following bounded state: The institution acknowledges receipt, not a selection decision. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A target ‘You’re admitted’ is too strong. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Can eligibility review remain? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
Review pending
Source status: “The application is pending review.” This communicates the following bounded state: Review remains outstanding under the workflow. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A target describing final rejection changes status. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Can staff still perform the review? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
Actively reviewing
Source status: “The panel is reviewing the proposal.” This communicates the following bounded state: An evaluation activity is ongoing. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A target ‘panel approved it’ fabricates decision. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Can reviewers still request evidence? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
Approval needed
Source status: “Awaiting director approval.” This communicates the following bounded state: A named authority must decide. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A target claiming director already signed is wrong. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Can deployment remain blocked? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
Approval obtained
Source status: “The director approved the budget.” This communicates the following bounded state: A decision was reported. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A target saying money was transferred is another event. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Can procurement still take place? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
Work paused
Source status: “Development is on hold pending new funding.” This communicates the following bounded state: The activity is paused under a stated dependency. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A target ‘project permanently canceled’ goes too far. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Could funding permit resumption? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
Active engineering
Source status: “The repair is in progress.” This communicates the following bounded state: Technicians are working on it, not necessarily finished. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A target ‘repair completed’ changes user expectations. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Can the problem persist during work? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
Technical blocker
Source status: “Deployment is blocked by missing credentials.” This communicates the following bounded state: A particular dependency prevents proceeding. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A target saying the system cannot ever deploy overstates. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Can providing credentials resolve this blocker? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
Delayed shipment
Source status: “Your shipment is delayed.” This communicates the following bounded state: The shipment is later than expected. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A target ‘package lost’ invents outcome. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Can delivery still occur? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
Out for delivery
Source status: “The parcel is out for delivery.” This communicates the following bounded state: The courier describes a delivery stage. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A target ‘parcel delivered’ is premature. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Can recipient still await arrival? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
Delivered scan
Source status: “The parcel was marked delivered.” This communicates the following bounded state: A carrier status was recorded, with proof details not stated. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A target saying a named person signed invents identity. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Can the recipient still check details? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
Receipt pending
Source status: “The payment is pending.” This communicates the following bounded state: A payment remains in an unsettled or waiting state as defined by provider. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A target ‘payment failed’ is not necessarily correct. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Can transaction still clear? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
Refund initiated
Source status: “Your refund was initiated.” This communicates the following bounded state: The refund process started. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A target claiming funds reached the bank changes stage. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Can crediting still take time? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
Refund credited
Source status: “The refund has been credited to your account.” This communicates the following bounded state: The source claims account credit. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A target saying only a request was filed weakens completion. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Can user review their account record? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
Draft work
Source status: “The essay is saved as a draft.” This communicates the following bounded state: The learner saved work but may not have submitted. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A target ‘teacher received it’ is unsupported. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Can the student still need to submit? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
Assignment submitted
Source status: “The assignment has been submitted.” This communicates the following bounded state: The relevant submission step occurred. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A target ‘assignment graded’ skips marking. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Can teacher evaluation remain future? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
Assignment marked
Source status: “The teacher marked the assignment.” This communicates the following bounded state: Evaluation occurred, but visibility of feedback may differ. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A target saying all students received feedback adds dissemination. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Can feedback release remain separate? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
Case reopened
Source status: “Your ticket was reopened.” This communicates the following bounded state: A previously closed case returned to a working state. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A target ‘new complaint filed’ changes record history. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Can original ticket number remain? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
Case closed without fix
Source status: “Ticket closed due to missing customer response.” This communicates the following bounded state: The process ended administratively due to nonresponse. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A target ‘issue repaired’ misstates result. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Can the user still face the problem? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
Specific resolution
Source status: “The login error was resolved.” This communicates the following bounded state: The source reports fixing or settling a particular issue. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A target ‘all services restored’ broadens scope. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Can another issue remain active? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
No update
Source status: “There is no new status update today.” This communicates the following bounded state: No new communication or state change is reported today. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A target ‘no work was done’ alleges inactivity. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Can staff still be working? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
No change to schedule
Source status: “The date has not changed.” This communicates the following bounded state: One schedule property remains constant. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A target ‘nothing changed anywhere’ is too broad. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Could the venue or speaker have changed? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
At-risk milestone
Source status: “The milestone is at risk of delay.” This communicates the following bounded state: A future delay is possible. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A target ‘deadline missed’ states a completed failure. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Can mitigation still work? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
Missed milestone
Source status: “The milestone deadline was missed.” This communicates the following bounded state: The relevant deadline has already passed unmet. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A target ‘might be late’ weakens status. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Can management accurately record variance? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
Event canceled
Source status: “The workshop was canceled.” This communicates the following bounded state: The originally planned event will not proceed as planned. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A target ‘postponed until Monday’ invents a new date. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Can refund or rebooking remain undecided? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
Event rescheduled
Source status: “The workshop was moved to Wednesday.” This communicates the following bounded state: A new event time/date is reported. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A target saying canceled permanently removes the event. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Can attendees plan for Wednesday? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
Temporary suspension
Source status: “Membership suspended pending verification.” This communicates the following bounded state: A status restriction is tied to a dependency. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A target ‘permanently expelled’ overstates. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Can completion of verification affect the status? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
Application declined
Source status: “The application was unsuccessful.” This communicates the following bounded state: The institution gives a negative selection outcome. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A target ‘awaiting review’ reverses decision. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Can the applicant recognize status and next steps? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
Next action owner
Source status: “Waiting for the applicant to upload ID.” This communicates the following bounded state: The applicant owns a required document action. It does not provide every later event in the workflow. Keep the object, timestamp if present, and which system or speaker is reporting the status.
False inference to avoid: A target ‘waiting for staff’ shifts responsibility. The translator should not substitute a desired outcome for a process stage simply because users prefer good news. A green label can be administratively positive while work remains incomplete; a negative label can describe a temporary dependency rather than a final refusal.
Workflow check: Can the applicant identify the needed step? The target should direct the correct participant to act or wait. Read the next possible status after this one and confirm that the translated language leaves that transition meaningful.
A Release Audit for Workflow States
Read the status in three parts: the object whose state is changing, the state itself, and the condition or next action. Check whether a timestamp marks submission, decision or publication. If the source uses a named authority, keep it. If it uses a passive state with no actor, do not invent an approver.
Test a plausible user response: “What should I do now?” After “Awaiting your documents,” the user should upload them. After “Under review,” they generally wait or follow the given instructions. After “Payment completed,” they may check the account rather than repay automatically. A target that implies the wrong next action has not preserved the workflow.
Frequently Asked Questions
Is pending the same as in progress?
Not necessarily. Pending indicates something remains outstanding, while in progress more directly indicates ongoing work. Product-specific workflow definitions may narrow either.
Is on hold the same as canceled?
No. On hold usually indicates a pause, while canceled says a planned action won’t proceed as planned. The distinction affects whether resumption remains possible.
Does completed mean approved?
No. Work can be finished and still await approval, testing or acceptance. Translate the stated completion criterion.
Does resolved mean closed?
Not always. Resolved often refers to addressing the issue; closed can be an administrative case status. Systems define these differently.
Does payment pending mean payment failed?
No. Pending indicates a waiting or processing state, not necessarily failure. Consult the payment provider’s exact definition.
Can approved mean paid?
Not by itself. Approval is a decision; release, settlement and receipt of funds are separate acts.
Does no update mean no work occurred?
No. It means no update was communicated or recorded in the relevant sense. Work can continue without a new message.
What is the fastest translation check?
Identify the object, current state, responsible next actor and what has not yet happened. Keep all four answers unchanged.
Sources and Related Reading
The Cambridge Dictionary | Pending reference describes waiting for a decision, event or approval, and On Hold describes a paused activity or telephone wait. For an operational distinction between stages, see Master Art of Translation, Short Email Replies and Complaints and Feedback.
Final Principle
A status is a claim about how far a defined workflow has progressed. It is not a vague label for good or bad news. A reliable translation preserves whether someone must act, whether a decision has been made and whether the actual result was delivered. The next step should remain as clear in the target language as it was in the source.