​
Evidence and Review

Evidence is the record that field work happened. It may be a file reference, a link, a field note, a row imported from a CSV file, or another record that supports an activity.

​
Evidence Section

Open Operations, then select Evidence. The Evidence section includes:
  • Field evidence form
  • Evidence list
  • Evidence review queue
  • Field data import

​
Submitting Field Evidence

A user with submission access can submit evidence when activities exist. The form asks for:
FieldMeaning
ActivityThe activity this evidence supports
Evidence titleA short, recognizable name for the submission
Evidence link or file referenceA URL, file reference, or storage reference
Field notesContext about the evidence
After submission, the evidence appears in the evidence list.

​
Evidence Statuses

Evidence can move through these statuses:
StatusMeaning
SubmittedThe evidence has been received and is waiting for review
ApprovedThe evidence has been accepted
Needs correctionThe reviewer needs the field team to correct or clarify something
RejectedThe evidence does not meet the required standard

​
Review Queue

The review queue shows evidence that is waiting for a decision. Reviewers can:
  • Approve
  • Request correction
  • Reject
Use review decisions carefully. The review outcome affects whether evidence can be trusted in project reporting.

​
When to Approve Evidence

Approve evidence when:
  • It matches the selected activity.
  • It contains enough information to verify the field action.
  • The notes are clear.
  • The file reference or link is usable.
  • The submission does not create a data quality concern.

​
When to Request Correction

Request correction when:
  • The evidence is probably valid but incomplete.
  • The activity is correct but the notes are unclear.
  • The file reference is missing or incorrect.
  • More field context is needed.

​
When to Reject Evidence

Reject evidence when:
  • It does not match the activity.
  • It is too incomplete to verify.
  • It duplicates a record that should not be duplicated.
  • It creates a serious quality concern.

​
Field Data Import

The Field data import area lets authorized users paste CSV data for bulk field submission records. Required columns:
  • title
  • activity_id
Optional columns:
  • notes
  • evidence_url
  • field_date
  • latitude
  • longitude
Use import when field data was gathered outside the app and needs to be brought into the workspace in bulk.

​
Import Results

After an import, ProjectDesk shows:
  • Imported count
  • Skipped count
  • Error count
  • Error summary, if applicable
If an import has errors, correct the CSV source and try again.