Skip to content

Review a Visit

After a visit has been submitted, authorized reviewers can examine the information collected before making a final decision.

The review process helps ensure monitoring data is complete, accurate and supported by appropriate evidence before it becomes part of the organization's official records.


Opening a Visit

  1. Navigate to Visits.
  2. Open the submitted visit you want to review.

The visit displays:

  • Visit details
  • Monitoring responses
  • Uploaded evidence
  • Current status
  • Activity history

Review all available information before making a decision.


Review Visit Details

Begin by confirming the basic information is correct.

Verify:

  • Program
  • Project
  • Site
  • Visit Date
  • Monitoring Template

Ensure the visit has been recorded against the correct location and monitoring activity.


Review Monitoring Responses

Carefully review the responses provided by the field officer.

Look for:

  • Missing information
  • Inconsistent responses
  • Data entry errors
  • Unusual values
  • Incomplete observations

Responses should accurately reflect the monitoring activity that took place.


Review Supporting Evidence

Open any uploaded evidence associated with the visit.

Depending on the file type, evidence can be viewed directly in your browser or downloaded for further review.

Consider whether the uploaded evidence supports the monitoring findings and observations.


Review Visit History

FieldOps maintains a complete history of the visit.

Reviewers can see:

  • When the visit was created
  • Status changes
  • User activity
  • Monitoring responses
  • Supporting evidence

This history provides additional context during the review process.


Approve the Visit

If the visit is complete and meets your organization's quality standards, approve it.

Once approved:

  • The visit becomes part of the organization's official monitoring records.
  • It is available for reporting and Business Intelligence.
  • The visit status changes to Approved.

Reject the Visit

If corrections are required, reject the visit.

Common reasons include:

  • Missing monitoring information
  • Incorrect responses
  • Insufficient supporting evidence
  • Data quality issues

After the necessary changes have been made, the visit can be submitted again for review.


💡 Best Practices

A consistent review process helps maintain high-quality monitoring data.

We recommend that reviewers:

  • Verify all required information.
  • Review supporting evidence alongside monitoring responses.
  • Check for unusual or inconsistent values.
  • Apply the same review standards across all visits.
  • Provide clear reasons when rejecting a visit.

Consistent reviews improve reporting accuracy and strengthen organizational accountability.


➡️ Next Step

Continue to Visit History and Audit Trail to learn how FieldOps records every significant action performed on a visit, providing a complete history for reporting and compliance.