In this article
Before asking someone to correct an offer, establish its current stage, the exact proposed change and who can authorize it. “Please update it” leaves the most important questions unanswered.
The documented distinction
The official corrections guide distinguishes pre-accepted from post-accepted offers. It describes broader editing before acceptance, while post-acceptance changes are limited to the start date and adding new allowances, not editing existing allowances. It also describes employee change requests and in-flight corrections. These are product capabilities, not a statement that a particular change is contractually or legally appropriate.
Start with a bounded request
A useful internal request identifies the intended engagement, the current stage as observed in the authorized system, the detail in question, the proposed decision owner and what has already been communicated. Keep private particulars in the approved system. A public planning tool should never ask for a real offer, rate or worker identifier.
Separate “the source was entered incorrectly” from “the underlying agreement changed.” The first is an accuracy question; the second may require a new decision. They can look similar on a screen while carrying different implications. Route the distinction to the appropriate authorized person rather than deciding from a brief message.
Fictional case: a changed start date
A coordinator receives a message that a department will begin later. The coordinator first asks whether this is a confirmed engagement change or a provisional scheduling idea. Only after the authorized decision is clear does the operator consult the current product instructions. The existence of an editable date field does not settle the underlying decision.
Keep four moments separate
- The change is proposed.
- The authorized decision is made.
- The appropriate product action is performed.
- The required recipient review or follow-up is completed.
A planning board can show which moment remains open. Do not mark the entire issue resolved merely because an operator saved a change. Equally, do not assume that a delayed response means the change was rejected. Use observed facts and the official record.
When the desired edit is unavailable
Do not manufacture a new workflow by copying an offer, removing a record or changing someone’s access just to make the screen permit the action. Ask the official support or production payroll route to clarify the supported procedure for that situation. Preserve the question and avoid making an irreversible change based on a guess.
The coordinator’s contribution is a clear handoff: what needs to change, why the authorized decision requires it, what the current workflow permits and what remains unresolved. See additional documents when the issue is an omitted form, and the exception brief when the next owner is unclear.
Evidence & scope
Public documentation checked October 25, 2026. Product facts are attributed below; planning methods and fictional examples are independent editorial analysis, not an official procedure or a private-account test. Availability depends on role and project. This is not legal, employment or payroll advice.