Lawned.co.nzLawned.co.nz

Trust & safety

Clear protections from first quote to final closeout.

Lawned combines mapped scope, transparent offer history, completion evidence, and payment controls so both sides share the same facts—reducing confusion and improving accountability.

How protection works

Six-step trust timeline

Each step mirrors what you will see in onboarding, orders, and jobs: identity is checked before paid work, scope is visible early, money follows explicit acceptance, and closeout is anchored to evidence—not side-channel messages.

  1. Step 1

    Identity is checked before paid work

    Anyone can create a contractor account. Quoting, accepting jobs, and payouts stay locked until Stripe identity checks pass — and companies or partnerships also verify their own NZBN, not a parent or franchise brand number.

  2. Step 2

    Scope is mapped before pricing

    Clients define zones, off-limits areas, and access context first, so contractors quote against visible scope.

  3. Step 3

    Offers stay in-platform

    Budgets, offers, counter-offers, and acceptance decisions are tracked in one workflow.

  4. Step 4

    Work is tracked and evidenced

    Assigned contractors submit completion evidence, including after photos, before closeout.

  5. Step 5

    Payment follows completion flow

    In Stripe hold flows, the accepted job price plus booking fee is held on bid acceptance and captured only after client approval.

  6. Step 6

    Issues can be escalated quickly

    Scope, safety, payment, identity, or account concerns can be reported with clear reference history.

Swipe or scroll horizontally to read every step on smaller screens.

By audience

Three lanes, one trust model

Each lane spells out what the product already enforces: homeowners get map-backed clarity, contractors get defensible context, and the platform keeps state, access, and money on the rails.

Homeowners

Client safeguards

  • Contractors must finish Stripe identity checks before they can quote or accept paid jobs.
  • Companies and partnerships must verify their own NZBN — not a parent or franchise brand number.
  • Mapped zones and off-limits boundaries reduce scope disputes.
  • You choose the contractor by accepting the offer you prefer.
  • Live progress and completion submissions are visible in-app.
  • Before-and-after evidence supports quality review before release.
  • Re-quote and cancellation paths exist when job conditions change.

Crews & operators

Contractor safeguards

  • You can join and set up a profile first; payouts stay locked until Stripe clears your identity.
  • Franchisees use their own legal-entity NZBN and can still show a brand as a trading name.
  • Job feed includes mapped scope, service needs, and budget context.
  • Counter-offer support lets you price around real site complexity.
  • Only assigned contractors can submit completion proof for a job.
  • In-platform event history protects against unclear handoffs.
  • Structured cancellation reasons support safer job exits.

Infrastructure

System guardrails

  • Role-based access across client, contractor, and admin views.
  • Transaction gates: quoting, acceptance, and capture require Stripe payout readiness, plus NZBN for companies and partnerships.
  • Tracked state transitions from open job to completion and closeout.
  • Payment records linked to order, job, booking-fee, and payout-fee references.
  • Support-ready audit context across scope, offers, and status updates.
  • Privacy and terms pages for policy-level guidance, including impersonation and account-closure rules.

Escalation

When to reach out immediately

Open any item for a quick checklist of what to include. If someone is in danger, contact emergency services first, then notify us with references when it is safe to do so.

Report categories

Unsafe property access or working conditions

Stop work if needed, note the address and job reference, and contact us immediately with photos if it is safe to take them.

Incorrect mapped scope versus on-site reality

Flag the mismatch before closeout so the team can reconcile metres, services, or access notes against what was agreed.

Disputed completion evidence

Open the job and use Dispute (during the 48-hour review window) or Report a problem (after payment release). Reference the submission time, photos, and job ID so support can review the same timeline visible in your dashboards.

Unexpected payment or release behavior

Include order ID, accepted offer amount, booking fee, and any Stripe receipts so we can trace holds, captures, payouts, and refunds.

Issue noticed after payment was released

Open the job and choose Report a problem. The 48-hour timer is only the automatic payment-release window — it is not a deadline for raising problems. Your statutory rights under the Consumer Guarantees Act and Fair Trading Act continue to apply.

Account, privacy, or data-access concerns

Use the contact flow with your account email; point to the specific property or job if the concern is tied to a listing.

Impersonation or a fake business

Tell us the profile name, NZBN if shown, job or offer ID, and why it looks wrong. We can suspend accounts that use someone else's identity, a borrowed NZBN, or a parent-company number instead of the operator's own legal entity.

For payment disputes tied to marketplace rules, read pricing and the FAQ while you gather screenshots.

Keep exploring

Related pages

These guides use the same language as onboarding and dashboards—jump across whenever you need more depth.

Get started safely

Create an account and run jobs with clear guardrails

Choose a role, map your first property or service area, and keep every offer and payout inside the same workflow.