Skip to content

Maintenance Promise Audit

Date: 2026-06-25 Status: Accepted for the first paid pilot. Roadmap item: EP9-T5.

Decision

Launch materials must not imply lease-linked maintenance management.

The paid-pilot promise remains simple in-app issue reporting: a signed-in owner or tenant can send a topic, message, and optional photo so support can triage the case. The product must not sell repair ownership, a repair timeline, contractor routing, work orders, quotes, invoices, responsibility decisions, or service level guarantees.

Audit Result

Surface Result
Landing and tenant invitation copy Already narrowed to "simple issues" and "simple in-app reports".
Mobile role onboarding Service-provider descriptions no longer promise fixing, repairs, or maintenance.
In-app support copy Kept as support/problem reporting, with optional screenshot/photo context.
Web-admin support tools Kept as internal problem-report triage, not a customer maintenance workflow.
Pre-release docs and roadmap Lease-linked repair workflow is post-launch backlog only.

Kept For Launch

  • In-app support/problem report submission.
  • topic, plaintext message, and optional photoAssetId.
  • Admin triage with OPEN, IN_PROGRESS, RESOLVED, and DISMISSED.
  • Final-settlement repair deduction labels, because those describe settlement accounting rather than a repair-management workflow.

Post-Launch Maintenance Backlog

Do not start this backlog until pilot/interview evidence proves maintenance is the wedge and the launch promise is explicitly expanded.

Candidate post-launch scope:

  • lease/property-linked issue ticket;
  • tenant photo and availability/access notes;
  • owner status timeline and tenant-visible updates;
  • responsibility decision capture;
  • contractor or building-admin routing;
  • quote/invoice attachment;
  • cost handoff into final settlement when legally appropriate;
  • retention/export rules for maintenance evidence.

Explicitly out of scope for the first paid pilot:

  • contractor assignment;
  • vendor marketplace;
  • work-order system;
  • SLA engine;
  • automatic responsibility adjudication;
  • legal guarantees about repair liability.

Evidence

  • Mobile guard: language utilities > does not promise repair or maintenance workflows in role onboarding copy.
  • Mobile role copy in English, Polish, and Ukrainian now describes property operations help without repair or maintenance terms.
  • Simple issue reporting promise defines the allowed launch wording and excluded repair-management promises.
  • Admin problem report triage smoke verifies support can triage existing problem reports without direct database access.
  • Strategy scope audit now treats lease-linked maintenance as post-launch backlog, not pre-release scope.

Closeout

This closes the Epic 9 paid-pilot issue-reporting boundary. Any future maintenance workflow must start from a new approved epic after pilot evidence shows the simple support-report surface is insufficient.