Access, approvals and testing

Before building, we agree what information the system can use, who can take action and how your team will check the results.

What information can it use?

We identify which documents and data the system may use, for what purpose and with whose permission.

Who can see or change it?

We agree who can view information, edit records and trigger actions. Different roles may need different access.

What needs your approval?

We identify what the system can prepare and what must wait for a person to check and approve.

How do we test it?

We test agreed examples, including missing or conflicting information. Your team reviews the source references, results and mistakes.

What happens when it is wrong?

We decide what to record, who corrects mistakes and how to pause the system.

If a required field is missing

In this example, the system holds the record for a reviewer. That person completes or rejects it; only an approved record moves on.

Source document

Record for review

Required detail
Missing

Waiting for a reviewer

  • Complete the record
  • Reject the record
Conceptual exception example — an illustration of a proposed review process. It is not evidence of a deployed system.

Tell us about your requirements

Describe the task, any restrictions on the information it uses and who needs to approve the result.

Discuss a project