Settings

Evidence-Based Completion

NephAI follows this whenever the situation you described comes up.

On

All your work · must follow

Do not mark an Automation complete based only on an attempted action. Completion requires evidence such as: - email successfully sent; - recipient replied; - invitation accepted; - event created with correct participants; - Task completed by the responsible owner; - required approval recorded; - calling sustained and setting apart completed; - requested document received; or - final outcome confirmed by the appropriate leader. An evidence example is not automatically sufficient for every Automation. The Automation's configured outcome determines which evidence proves completion.

What this rule says

Work this covers

Global - Automations and Tasks

When it kicks in

Completion is assessed or recorded

What NephAI does

Do not mark an Automation complete based only on an attempted action. Completion requires evidence such as: - email successfully sent; - recipient replied; - invitation accepted; - event created with correct participants; - Task completed by the responsible owner; - required approval recorded; - calling sustained and setting apart completed; - requested document received; or - final outcome confirmed by the appropriate leader. An evidence example is not automatically sufficient for every Automation. The Automation's configured outcome determines which evidence proves completion.

When NephAI checks it

  • While it works out what is going on
  • Straight after it acts

Limited to

Automations · Tasks

Your test cases

2 cases you set up to check this reads correctly

If NephAI cannot satisfy it

It holds that piece of work and brings it to you rather than proceeding against this rule.

Try it out

See where this rule would take effect and how NephAI reads the cases you set up. This only shows you the result — nothing is saved, sent, or changed.

Where this rule has been used

Clashes with other rules

0

None. This rule has never asked for something another rule contradicted.

Times NephAI used it

50
  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 10, 2026, 12:39 AM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 10, 2026, 12:39 AM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 10, 2026, 12:35 AM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 10, 2026, 12:35 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:30 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:24 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:23 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:20 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:19 AM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 10, 2026, 12:15 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:15 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:07 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:07 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:04 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:03 AM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 10, 2026, 12:00 AM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 10, 2026, 12:00 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 11:59 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:48 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:46 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:43 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:41 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:33 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:31 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 11:28 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:28 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:25 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:17 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:17 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:15 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:15 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 11:13 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:12 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:12 PM

  • Taken into account · Automation trigger judgment

    while working out who this belongs to

    Sep 9, 2026, 11:09 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:09 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:09 PM

  • Taken into account · Automation trigger judgment

    while working out who this belongs to

    Sep 9, 2026, 11:02 PM

  • Taken into account · Automation trigger judgment

    while working out who this belongs to

    Sep 9, 2026, 11:02 PM

  • Taken into account · Automation trigger judgment

    while working out who this belongs to

    Sep 9, 2026, 11:02 PM

  • Taken into account · Automation trigger judgment

    while working out who this belongs to

    Sep 9, 2026, 11:02 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 11:01 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 11:00 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 10:59 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 10:57 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 10:56 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 9, 2026, 10:56 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 10:53 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 10:46 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 10:44 PM