Skip to content
EMPOBase
en

How to monitor projects when staff cannot reach the site

By the EMPOBase team · · 4 min read

Short answer

When staff cannot reach a site, use remote monitoring: phone calls, partner or community reports, photos, third-party monitors and records. Choose methods by risk, check data against more than one source, protect the people who share it, and state the limits in your reports. Remote data is weaker than a visit, so label how each result was verified.

Key points

  • Match the method to the risk: calls, partner reports, photos, community monitors or third parties.
  • Check key results with at least two sources before you report them.
  • Protect the safety and privacy of everyone who shares information.
  • Say clearly in reports which results were verified remotely and how.

What is remote monitoring?

Remote monitoring means tracking a project without staff being present at the site. Access may be blocked by conflict, floods, distance or health restrictions. The project still needs evidence that work happened and that it is helping.

Remote monitoring is not a full replacement for visits. It is a way to keep a reasonable view of the work, while you are honest about what you cannot see.

Which methods can you use?

MethodGood forMain weakness
Phone or message calls to participantsSatisfaction, receipt of goodsMisses people without phones; answers may be guarded
Partner or community reportsActivity progressMay be biased toward good news
Photos and videos with date and placeVisible work such as constructionEasy to stage or reuse; consent and safety risks
Third-party monitorsIndependent checksCost; quality varies
Records such as distribution lists and receiptsDeliveryNeed cross-checking against other sources
Community monitorsOngoing observationTraining, safety and trust needed

No single method is enough. Combine them.

How do you choose and combine methods?

Follow these steps:

  1. List what you must know. Pick the few results that matter most.
  2. Rate the risk. Higher risk, such as cash distribution, needs more checks.
  3. Pick two or more sources per key result. For example, a delivery list plus a phone call to a sample of recipients.
  4. Plan a sample. You may not reach everyone; choose a method that gives a fair spread by place, sex and age.
  5. Set a schedule. Decide how often to check and who does it.
  6. Plan for gaps. Write down who you could not reach and why.

How do you check the quality of remote data?

Remote data needs extra checks. Try these:

  • Triangulate. Compare what two or more sources say. Investigate differences.
  • Look for patterns. Identical photos, repeated answers or numbers that always round the same way are warning signs.
  • Call back a small sample. A second short call can confirm an earlier answer.
  • Review before reporting. A second person should check data before it counts as a result. See how to check field data quality.
  • Record the method. Next to each result, note how it was verified.

How do you protect people?

Remote work can put people at risk. Messages can be read by others, and phone numbers can reveal who talks to you.

  • Collect only what you need.
  • Ask for consent, and explain how the data will be used.
  • Use the safest channel available, and avoid sharing sensitive details over open channels.
  • Do not ask people to take photos if it could expose them.
  • Give people a way to raise a concern or complain.
  • Follow your safeguarding and data protection policies, and check local law.

How do you report honestly?

Say clearly that results were monitored remotely. For each key result, show the method, the sample and the limits. Do not present remote data with the same confidence as visited data. Donors usually prefer an honest limit to a claim that falls apart in an audit. When access returns, do a catch-up visit and note any differences.

What does a simple remote monitoring plan look like?

For a project where staff cannot visit, a one-page plan is enough:

  1. Key results. List the three to five results you most need to verify.
  2. Sources. For each, name two sources, such as a partner list and a sample of phone calls.
  3. Sample. State how many people you will try to reach, and how you will cover different groups.
  4. Schedule. Decide monthly or quarterly checks and who runs them.
  5. Safety. Note the main risks to people who share information, and the steps to reduce them.
  6. Review. Name the person who checks the data before reporting.
  7. Return plan. Note which checks you will repeat on site once access returns.

Review the plan whenever access changes. A plan that is a page long gets read; a long one does not.

Where EMPOBase fits

EMPOBase supports remote reporting through Collection links, which are web forms with a token. New submissions enter a review queue, and only approved ones update indicator actuals. Field reporting is online, so there is no offline capture, and Collection links do not connect to KoBo or ODK. EMPOBase does not verify photos or answers for you, so keep your own checks. See the field-to-results workflow.

Questions people ask

Is remote monitoring as reliable as a site visit?

Usually not. It can still be good enough if you use more than one source and say how each result was checked. Return to site visits as soon as it is safe.

What about people without phones?

Many people will be missed. Use community contacts, partners or a trusted third party, and note who you could not reach.

Do we need consent to use photos?

Yes. Get informed consent, avoid faces where it could cause harm, and follow your data protection policy and local law.