Evidence Validation Flow
Power Automate / SharePoint
Attachment, metadata and naming checks before evidence is accepted into the library.
Evidence validation
Submission received
Form / Power Apps
Attachment present?
Metadata complete?
Naming rule match?
Store to library
Entity / period folder
Exception path
Request amendment
Notify requester
Write audit entry
- Overview
- Validation applied at submission so evidence is complete, named consistently and stored where it can be found again.
- Problem
- Evidence arrived incomplete or inconsistently named, so periodic reviews began with cleanup work.
- System architecture
- Submission → attachment and metadata checks → naming rule → library storage or exception path.
- Workflow
- Receive → check attachment → validate metadata → match naming rule → store or return for amendment → audit entry.
- Tools
- Power Automate / SharePoint
- Role
- Wrote the validation rules and exception handling, and set the storage convention.
- Impact
- Evidence usable as submitted, with exceptions routed back immediately instead of discovered later.
- Implementation notes
- All interfaces shown are representative reconstructions using fictitious sample data. No internal names, documents or confidential metrics are published.