Skip to main content

Make an Assessment

Operators organizing approved work evidence into an assessment packet
Assessment chapter

Set the baseline, reporting window, and evidence frame.

What this helps you do​

Create a standalone EAS assessment attestation for a garden. In the operator path, this is the baseline and reporting frame: it records the domain, title, description, location, reporting dates, selected actions, metrics, evidence, and strategy context that later approval work should line up against.

An assessment can support later impact reporting and impact certificates, but it is created from the admin assessment wizard, not from the public Impact page.

Protocol permission

The assessment resolver accepts attestations from garden evaluators or operators. Owners/operators can manage the garden; evaluators can submit assessments when they have the evaluator role.

Before you start​

  • You are signed in as an operator or evaluator in the garden.
  • The garden has enough context to set a responsible baseline. If you are making a final evidence-backed assessment rather than an initial frame, wait until the related work is approved.
  • You have a rough sense of:
    • The domain you are reporting in (must be one this garden runs).
    • A short diagnosis of the situation you acted on.
    • One to three SMART outcomes you will report against.
    • The domain actions you want to include.
    • The reporting window (start and end date).
tip

If the assessment page says "No permission", you are missing operator/evaluator permission for this garden.

Step-by-step flow​

The wizard has three steps: Domain & Context → Strategy Kernel → Actions & Harvest. Your progress is saved as a draft as you go, so you can close the tab and resume later.

Step 1: Open the assessment wizard​

  1. Open the Hub workspace, switch to the Assess tab, and click New assessment (or go directly to /hub/assess/create).
  2. Pick the garden if you haven't already. The wizard refuses to open without one.

Step 2: Fill Domain & Context​

  1. Pick the Domain this assessment reports against. Only domains enabled on this garden are selectable.
  2. Enter the title — keep it stable enough that you will still recognise it in six months.
  3. Enter a short description of what the assessment covers.
  4. Enter the location (specific enough that a reader can place it on a map).
  5. Click Continue.

Step 3: Build the Strategy Kernel​

  1. Enter the diagnosis — one or two paragraphs on what was happening before the work started.
  2. Choose the Cynefin phase that matches the situation (clear, complicated, complex, chaotic, or confusion). This helps a reader read the assessment with the right frame.
  3. Add one or more SMART outcomes. Each outcome needs a description, a metric, and a numeric target. Keep them honest — "15 trees alive after 6 months" beats "trees planted."
  4. Select only the metrics that match the garden's domain. Don't add metrics just to make the assessment look bigger.
  5. Click Continue.

Step 4: Pick Actions & Harvest​

  1. Select the actions to include in this assessment. The wizard filters actions by the domain you chose in step 1.
  2. Set the reporting period — start date and end date. Make it match the work you selected.
  3. Click Submit assessment and sign the transaction in your wallet.
  4. Wait for the transaction to confirm. The wizard stays on this step until it does.

How to know it worked​

  • A success toast appears: "Assessment submitted — Your assessment has been recorded on-chain."
  • The wizard closes and you return to the assessment list.
  • After indexing catches up, the new assessment appears with its title, domain badge, and reporting date range.
  • If the card exposes an EAS Explorer link, you can open it to verify the attestation independently.

Behind the scenes​

Every assessment submits one EAS attestation to the garden address. The on-chain schema stores title, description, assessment config CID, domain, start date, end date, and location. The richer assessment config on IPFS stores the assessment type, capitals, metrics CID, evidence media CIDs, report documents, linked impact attestations, and tags.

If something goes wrong​

  • "No permission" on the wizard. You are missing operator/evaluator permission. Ask the garden owner to add the right role.
  • Domain field missing options. The garden doesn't have that domain enabled. Fix the garden settings first, or pick a domain the garden actually runs.
  • "Incomplete form" toast. The wizard highlights the failing field — scroll to the red label, fill it in, and retry.
  • "We could not submit the assessment." The form data didn't assemble into a valid payload — usually a missing garden reference. Reload the page and re-enter the wizard from the Hub.
  • Transaction cancelled. You cancelled in your wallet. Click Retry submission.
  • Transaction failed. Check the inline error card. Common causes: wrong chain, insufficient gas, or a stale signer. Fix the cause and click Retry submission. If you need to edit the form, click Edit details instead.
  • "Draft backup unavailable" info toast. Your draft could not be saved to local storage, but submission still works — just don't close the tab mid-wizard.

Next step​

Next page

Keep the review queue clean

With the baseline set, approve or reject incoming submissions against the frame you just created.

Approve Work