Usable.software

Approvals

Some things nobody should decide alone: a large order, blocking a customer, going public. Request decisions here, approve or reject — and every decision remains on record: who, when, why.

M53 · Core · System core

your-address.usable.works
SubjectKindStatusRequested byRequested on
Item 4DoneIn progressWolf Spedition07/06/2026
Entry 5ReviewedDoneRoth Handel18/06/2026
Record 6OpenReviewedMeyer GmbH29/06/2026
Item 7In progressOpenKraus Logistik10/07/2026
Entry 8DoneIn progressBauer & Co.21/07/2026

Requesting a decision

On any record you can request a decision — from a specific person or from everyone allowed to decide. The answer and its reasoning are documented. This enforces nothing; it keeps the record.

Enforcing approvals

For status changes your organisation can set rules: this step needs an approval — or a four-eyes principle where the same person never both requests and approves. The database enforces this, not the UI; technical skill does not get around it. A de-minimis threshold exempts small cases.

The worklist

Open requests that concern you live here: what you can decide, what you requested yourself, what has been decided. Rejecting always requires a reason. If a record changes before it is decided, the request expires — nobody approves what they never saw.

What's inside

  • Approvals
  • Request
  • Approve
  • Reject
  • Withdraw request

Other blocks from the same area.