Governance and collaboration

Administrative escalation

ArkanERP Escalation raises every document that has waited past its time, or that someone escalates with the Escalate button, to the people authorised to act on it: the company's authorised staff, the cost center's supervisor and its group's manager. Each escalation keeps its record: who caused the delay, who took it, the person's statement and the outcome it closed with.

  • Automatic escalation when time is up
  • An Escalate button on any document
  • Higher levels for what no one takes
  • The person's statement with a deadline

What Escalation does

  • Where escalations come from

    A voucher waiting past its hours in the review and posting cycle, an approval step whose time is up in any flow, and the Escalate button anyone can press on any document.

  • Who it goes to

    To the company's authorised staff, the cost center's supervisor and its group's manager, as the settings allow.

  • One escalation per document

    A document has one open escalation per source; escalated again, it gains the new people instead of a duplicate.

  • Levels and reminders

    An escalation no one takes in hand climbs the settings' levels, and open ones are re-sent every so many hours.

  • Actions

    The person takes it, asks whoever is concerned for a statement by a deadline, forwards it to another authorised person, or closes it with an outcome: resolved, verbal notice, no action, or a warning or violation when the violations system is on.

  • Who caused the delay

    The people concerned are those the document was waiting on, or whoever the person escalating names.

  • Closing as the document moves

    When the document moves on, that is written on the escalation, and it closes as resolved when the settings say so.

  • Visibility and notices

    Its recipients, the person who raised it, the person concerned when the settings allow, and the authorised of their company see it. System managers get an email for each escalation alongside the in-app notice.

How the work flows

  1. 1

    Delay

    A document passes its time, or someone presses Escalate.

  2. 2

    Raising

    The escalation is made, sent to the authorised, and the person concerned named.

  3. 3

    Taking it

    Someone takes it in hand, or it climbs to the next level.

  4. 4

    Statement

    The person concerned is asked for a statement by a deadline and their answer kept.

  5. 5

    Closing

    It closes with its outcome, which may become a warning or a violation.

Questions about Escalation

When is a document escalated automatically?

When it passes its hours in the review and posting cycle, or an approval step's time runs out in its flow; the hours are set in the settings.

Can an escalation become a violation?

Yes. With the violations and penalties system on, an escalation can close as a warning or a violation against the person concerned, which then starts its own cycle.

Who sees an escalation?

Its recipients, the person who raised it, the company's authorised staff, the person concerned when the settings allow, and the general and system managers, each within their company.

Do escalations arrive by email?

Yes for system managers, with an in-app notice for every recipient, repeated for open ones every so many hours.