Skip to main content

Approve Work

An operator comparing field evidence with notes before approving work
Operator chapter

Review the evidence, choose approve or reject, then sign.

What this helps you do​

Clear a pending work submission in your garden: look at the evidence, approve or reject it, and leave feedback the gardener can act on. Approvals turn into on-chain attestations that should match the assessment frame you set earlier and can later be bundled into an impact certificate.

You can approve work from either the mobile app/PWA or the admin. Use the app when you are already in the garden flow. Use admin when you are clearing a queue across gardens.

Protocol permission

Work approval is operator-only at the contract resolver. Garden owners and operators can approve or reject work. Evaluators can create assessments, but they do not approve or reject work unless they also have owner/operator authority.

Before you start​

  • You are signed in with an address that is a garden owner or operator.
  • There is at least one pending submission in the work queue.
  • You are online — approvals and rejections need a wallet signature.
tip

If you only see the submission details and no approve/reject controls, you do not have approval authority for that garden. Ask the garden owner to add you as an operator.

Step-by-step flow​

Option A: Approve in the app/PWA​

Use this when you are on mobile or already looking at the garden.

  1. Open the Green Goods app and go to Home.
  2. Open the garden that owns the submission.
  3. Open the Work tab and select a pending submission.
  4. Review the media, action, details, and gardener notes.
  5. If the work is valid, tap Approve, add optional feedback, choose confidence, and submit.
  6. If the work needs changes, tap Reject, write specific feedback, and submit.
  7. Sign the transaction and wait for confirmation.

Option B: Approve in admin​

Use this when you are clearing a larger queue or need desktop context.

  1. Open the Hub workspace from the left rail. The default view lands on Work, pending across every garden you can review.
  2. Use the garden picker to narrow the queue when you only want one garden.
  3. Filter to Pending to see what still needs a decision.
Admin work queue filtered to pending submissions

The queue only shows submissions in the Pending state. Approved and rejected items move to the history view.

Open one submission​

  1. Click a submission. The Work Detail surface opens with the evidence on the left and the review controls on the right.
  2. Scroll through the media (photos, audio notes) and read the submission details.
  3. Cross-check the gardener's numbers or notes against the action's requirements.
Admin work detail page with submission evidence and review controls

The status badge at the top of the page says Pending until you act.

Approve or reject​

You'll see the review form on the right (or below, on narrow screens).

To approve:

  1. Add a short verification note if it helps the next reviewer stay consistent.
  2. Click Approve.
  3. Sign the transaction in your wallet when prompted.

To reject:

  1. Explain exactly what is wrong — which field, which photo, which count — and what the gardener should change.
  2. Click Reject.
  3. Sign the transaction.
tip

Be specific in rejection feedback. "Photo is too dark to verify tree count — retake in daylight and resubmit against the same action" will land much better than "insufficient evidence."

Confirm the status update​

  1. After the transaction confirms, the status badge flips to Approved or Rejected.
  2. The submission drops out of the pending queue.
  3. You can check it in the Hub History view if you want to verify.

How to know it worked​

  • The status badge on the submission shows Approved (green) or Rejected (red), with the matching icon.
  • The submission no longer appears in the Pending Hub queue.
  • The gardener sees the new status (and your feedback, on a rejection) in their Work Dashboard.
  • For approvals, an on-chain attestation is recorded linking the work UID to your decision.

Behind the scenes​

The gardener's submission creates a work attestation. Your approval or rejection creates a separate work approval attestation that references the original work UID. Downstream assessments use that linked evidence chain when they package approved work into a reporting statement.

If something goes wrong​

  • No Approve/Reject buttons visible. You are not an owner/operator for this garden. Ask the garden owner to add you as an operator.
  • "Select a garden" style errors. The garden didn't resolve from the submission — reload the page and open the submission from the queue again.
  • Transaction cancelled. You cancelled in your wallet. Nothing happens on-chain. Try again when you are ready.
  • Transaction failed. Check the wallet error. Common causes: insufficient gas, wrong chain, or the garden's permissions contract changed. Switch chain, top up, and retry.
  • Evidence is inconclusive. Reject with a specific request ("add a second photo showing the full bed") rather than guessing. It is faster to let the gardener resubmit than to approve a weak record you will regret at assessment time.
  • You clicked the wrong decision. Approvals and rejections are recorded on-chain and can't be flipped in place. If you rejected valid work, ask the gardener to resubmit; if you approved bad evidence, flag the case to the garden owner so it can be annotated in the next assessment.

Next step​

Next page

Mint an impact certificate

Once the assessment frame and approved work tell a coherent story, package them into the certificate flow.

Mint Impact Certificate