Environmental Actions
An environmental action is a measure opened against a significant aspect — the work that brings the aspect under control. Each belongs to one record and has its own flow, so it can be assigned and tracked while the record waits.
The flow
| State | Meaning |
|---|---|
| Draft | Being defined, or being corrected after a rejected performance. |
| In progress | Somebody is carrying it out. |
| Awaiting approval | What was done is with the approver. |
| Completed / cancelled | Closed. Either way the record stops waiting on it. |
Fields
- Code / Name — the measure's identity.
- Definition — what is to be done.
- Responsible — a single user. See below.
- Planned start date / planned end date — the commitment.
- Actual end date — stamped when the measure closes, never typed.
- Perform information — the account of what was actually done.
- Attachments — planning material.
- Perform attachments — the evidence of completion.
The responsible is one person
Everywhere else in the risk modules, the responsible is a collection of identities — users, roles, positions, organization units. A measure is the one deliberate exception: it names a single user.
The reason is that both of the measure's task steps resolve their assignee from that field. A measure is concrete, short-lived and taken on by one person; a collection here would leave the question "who is doing this" unanswerable at exactly the point where it needs an answer.
Measures open at the control step and nowhere else
A measure can only be opened while the record is at its control step. This is checked on the server as well as by the button, because the same operation is reachable from a mobile layout and the API.
Opening one against a draft, or against a record already in force, would produce work with no flow to return to.
Closing the last measure releases the record
When the last outstanding measure reaches a terminal state, the record moves from waiting for measures to verification — pushed from the measure itself, immediately, not found by a periodic scan.
Cancelling counts as closing. A cancelled measure stops the record waiting without claiming the work was done. That is the honest record: the account of why it was cancelled is on the measure, and the verification step is where somebody judges whether what remains was enough.
The completion date is stamped when the closing approval is given, not typed on the form. It appears on the read screens and in reports, and there is no field for it where a measure is defined — so it always records when the work was actually accepted rather than when somebody says it was.
What if no measure is opened?
A band marked requires measure is what should prevent that. If the control step is completed with nothing opened, the record does not park — it is moved straight on, because the waiting state carries neither a task nor a button and would otherwise strand it forever.
That behaviour is a safety net, not a feature. A significant aspect that passes through with no measure and no explanation looks identical in the register to one that was properly controlled. Set requires measure on your significant bands.
If the measures were not enough
At verification the reviewer can send the record back to the control step, where new measures can be opened, carrying the reason. It does not go back to waiting — no measure can be created from the waiting state.