Skip to content

Last1.org prompt: certification apply + standards pages

Paste this into Lovable (or your last1.org builder) as the build brief for certification apply / inquiry / standards surfaces.

Role

You are updating last1.org, the nonprofit standards body for Last1 certification.

Tone: institutional, neutral, governance-oriented. Not marketing. No hype CTAs like "Get Certified Today!"

Truth model (do not invent otherwise)

  1. Last1.org grants certification standing after review.
  2. last1.app records the application and the public verification page after standing is granted.
  3. Organizations cannot self-certify in Org Settings.
  4. An application sets standing to pending review. It is not certified yet.
  5. A public verification page (https://last1.app/verify/{slug}) exists only after certification is granted (verified or certified level with active/conditional/paused standing).
  6. Pending applicants must not appear in the public registry as certified.

Required pages / routes

Publish real content (no blank SPA shells that return 200 with empty UI). Prefer these routes:

1. /standards and /standards/certification

Purpose: explain what certification means, status states, and what certification does not do.

Required CTAs: - Primary: Apply in last1.app → https://last1.app/certification/apply - Secondary: Organization inquiry → /organization-inquiry - Tertiary text link: Registry → /registry

Copy constraints: - Say Last1.org reviews and grants standing. - Say last1.app is where the org submits the application and later hosts the public verification page. - Do not promise a live public page at apply time. - No em dashes in user-facing copy. Use periods, commas, or colons.

2. /organization-inquiry (canonical)

Purpose: inquiry form for orgs that are not ready to apply in-app, or want to talk to Last1.org first.

Required fields (minimum): - Organization name - Contact name - Work email - Website (optional) - Requested level: Verified or Certified - Short notes

On submit: - Confirm receipt - State that inquiry does not equal certification - Point them to https://last1.app/certification/apply if they already have a last1.app org account

Also support aliases that redirect to /organization-inquiry: - /inquiry - /apply - /standards/certification/apply (if present)

3. /registry

Keep consuming: - GET https://last1.app/api/public/registry - GET https://last1.app/api/public/registry/:slug

Rules: - Show only organizations returned by the API - Include paused / conditional / revoked when the API returns them - Never invent pending applicants as certified - Link each entry to its last1.app verification page when provided - Do not show EINs or numeric confidence scores

Exact language to use

Use language like this:

  • "Certification standing is granted by Last1.org after review."
  • "Organizations apply in last1.app. Submitting an application places the organization in pending review."
  • "A public verification page is published only after certification is granted."
  • "An inquiry is not a certification decision."

Avoid: - "Self-certify" - "Instant certification" - "Apply via pricing" - "Your public page is live" at application time

Visual / UX constraints

  • Institutional, sparse, document-like
  • No testimonial carousels
  • No pricing tables on standards/apply pages
  • No purple marketing gradients or badge spam
  • Clear hierarchy: title, short explanation, one primary action

Acceptance checks

  1. /standards/certification loads with real content and both CTAs.
  2. /organization-inquiry loads a real form (not blank).
  3. /apply and /inquiry redirect or render the same inquiry flow.
  4. Primary apply CTA goes to https://last1.app/certification/apply.
  5. Copy never claims the org is certified while pending.
  6. Registry does not invent pending orgs as certified.

Out of scope

  • Do not build admin approval tooling in last1.org for this pass.
  • Do not change last1.app APIs.
  • Do not add payment or plan upsell on these pages.