> ## Documentation Index
> Fetch the complete documentation index at: https://www.docusnap.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Documenting Evidence for Controls

> Back every execution of a control with a piece of evidence, and set recurrence and due date for recurring controls.

Every control carries the *Evidence* tab, one-time and recurring alike. It
lists the control's executions, newest first, each with effectiveness and
result.

## Record evidence

*Evidence* opens a dialog with four required fields: *Performed On* (defaults
to today, no future date allowed), *Performed By*, *Effectiveness*
(*Effective*, *Partially Effective*, *Ineffective*), and *Result* as free
text.

<Note>
  After saving, Docusnap365 automatically sets the control's status to
  *Implemented*, records the execution as *Last Performed*, and sets the next
  due date for recurring controls.
</Note>

<Warning>
  The move to *Implemented* is a consequence of recording evidence, not a
  decision of its own. Whether the control served its purpose is a separate
  question, answered by the evidence's *Effectiveness* — the status alone does
  not confirm it.
</Warning>

## Edit or delete evidence

Recorded evidence stays editable: you edit it in the sidebar of its row,
with the same four required fields as when recording it.

<Warning>
  Deleted evidence is removed permanently and cannot be restored.
</Warning>

## Set the recurrence

When creating a control, or in edit mode of the *Recurrence & Due Date*
section, you set *Recurring* with *Interval* and *Unit* (*Days*, *Weeks*,
*Months*, *Years*). What the date field means depends on the control's state:

| State | Label | Value |
| - | - | - |
| never performed | *Due Date* | freely chosen date |
| recurring, performed at least once | *Next Due Date* | last performed + interval |

Docusnap365 suggests the next due date after every change to recurrence,
interval, or unit — editable, not enforced. Month and year intervals clamp to
the end of the month (Jan 31 + 1 month yields Feb 28).

<Note>
  Without a prior execution there is no anchor for the suggestion; the due date
  then stays unchanged until you set it by hand.
</Note>

With *Recurring*, *Interval* and *Unit* are both required — if either is
missing, Docusnap365 blocks saving.

## Related

[Manage Controls](/docs/en/isms/controls) covers creating a control. For a
complete example, see the tutorial
[Carrying a Risk Through to Monitoring](/docs/en/isms/tutorial-risk).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.