Employee Grievance Appeals: Review the Decision Without Erasing the Original Outcome

An employee case portal should not treat an appeal as an ordinary request to edit a closed record. The employee is asking for a decision to be reviewed. Before commissioning the workflow, distinguish the original grievance outcome, the grounds of appeal, any further investigation and the written appeal outcome. Preserve how those stages relate without implying that lodging an appeal automatically changes the decision.

This guide uses British Acas disciplinary and grievance appeal guidance as a specific procedural reference. It is software-planning advice, not employment-law advice or a complete procedure for any country. Have a qualified adviser approve your organisation's policy, jurisdiction, time limits, responsibilities and employee communications before implementation. Translation into another language does not transfer the Acas framework to another legal system.

Link the appeal to the decision being challenged

Begin with the actual outcome the employee is appealing, not just the employee's name. Preserve the issued decision and its date, then create a related appeal record containing the submitted grounds and supporting material. The original outcome should remain identifiable after the review.

Acas describes appeals as a review of whether a decision should be overturned or changed. Its examples include an allegedly wrong grievance outcome, an unfair procedure and new evidence. Allow the employee to explain the grounds rather than forcing every appeal into “new evidence” or requiring an upload before they can submit.

Keep an initial receipt separate from a decision about the appeal. “We have received your appeal” does not mean it has been upheld. An automated acknowledgement should not promise a changed result or declare the complaint disproved.

Assign a review role, not an automatic manager notification

Decide who assesses and hears the appeal under the approved procedure. A useful custom portal lets an authorised case owner assign the proper reviewer without exposing the full record to everyone in the employee's management chain. Do not assume that the existing line manager is always the appropriate recipient.

Specify access separately for the employee, reviewer, investigator and administrators. A person responsible for arranging the meeting may need dates and attendance details without receiving all witness material. These are proposed access controls, not a claim that a particular portal already implements them or that every document can lawfully be withheld.

Do not promise anonymity. Agree with the responsible advisers what can be shared, what requires review and how an employee obtains the information needed for the procedure. Use fictional cases during demonstrations, never real workplace records.

A hearing can lead to more work

Acas's preparation guidance describes a hearing where the evidence is considered before the final decision. It also explains that further investigation may be needed to examine new evidence, recheck existing evidence or speak to witnesses. A completed meeting is therefore not sufficient evidence of a final appeal outcome.

Represent that branch explicitly. Staff should be able to record that the hearing occurred while investigation tasks remain outstanding. Keep each task's owner and expected next action visible, without presenting an internal target as a statutory deadline or guaranteed completion date.

If further findings concern disciplinary action, have the responsible professional apply the correct procedure. The Acas page distinguishes extra investigation from starting a new disciplinary procedure for new findings, subject to the organisation's policy. Do not build an automatic “increase sanction” action into a grievance appeal workflow merely because an attachment contains more serious allegations.

Preserve the written outcome and its relationship

Acas says the employer should provide the final outcome in writing as soon as possible. For the software brief, define who approves that communication, which decision it confirms or changes and how its issue is recorded. A saved draft is not an issued outcome.

If the original decision changes, keep the earlier issued version and explain its relationship to the appeal decision. Do not silently replace the original letter, making it appear that the reviewed result was always the first decision. Track any agreed operational follow-up separately rather than assuming that publishing the outcome carries out every action it describes.

An employee opening the portal should be able to distinguish “appeal received,” “hearing arranged,” “further investigation” and “written outcome issued” under the approved terminology. A single closed badge conceals too much.

Demonstrate an appeal that does not end at the meeting

Use a fictional grievance with an issued outcome. Submit an appeal on procedural grounds without an attachment, assign the approved reviewer and arrange a hearing. Confirm that submission does not overwrite the original decision and that arranging the meeting does not mark the appeal finished.

Then add a further investigation step, prepare an outcome draft and issue the authorised final version. Verify access through each test account and check that the record preserves both decisions. A normal support-ticket reopening rule is not enough to demonstrate this process.

Bring a blank procedure map and approved communication templates to a private internal-tool discussion. The useful outcome is a traceable review of a decision, not a general inbox carrying sensitive employee allegations.

Sources and boundaries

Acas: what an appeal is explains grounds, review and written outcomes. Acas: preparing for a hearing describes hearing and further-investigation branches. This article does not cover the complete accompaniment rules, dismissal appeals, tribunal rights or statutory deadlines. Those require separate qualified review.