1. Create a property
Choose a recognizable property name and, if useful, a general location label. Avoid access codes and other secrets.
Self-service help
This page is the complete public help resource for Estate Relay. The product does not include concierge, personal onboarding, migration, account management, phone/chat assistance, response-time commitments, or guaranteed individual replies.
Getting started
Estate Relay opens with no sample household in release builds. Create only records that are useful to you; an exact street address is not required.
Choose a recognizable property name and, if useful, a general location label. Avoid access codes and other secrets.
Enter an arrival, departure, and title. Choose the built-in essential tasks for a practical starting point or begin empty.
Edit task wording, phase, zone, due date, criticality, assignee label, notes, and state to match the property.
Use Home and the stay detail to find blocked, overdue, or unassigned items before they become arrival surprises.
Add property-manual entries and service contacts that make recurring work easier to understand.
Create a PDF when a readable brief is useful and a versioned JSON file when you need a restorable local backup.
Guide and common questions
Ordinary tasks count once and critical tasks count twice. Complete tasks and intentionally skipped noncritical tasks earn their weight; open, blocked, overdue, and unassigned tasks do not. A skipped critical task earns no weight and remains a critical exception. Ready requires all task weight and no critical blocked, overdue, unassigned, or skipped item. Attention means at least one exception needs review. The score summarizes entered records; it does not inspect the physical property.
An assignee is a label stored in your local record. It helps organize who is expected to perform work, but it does not create an account, send an invitation, notify that person, verify identity, or synchronize a task to another device.
Mark an item critical when missing it would materially affect the arrival or departure. Critical tasks receive extra weight and remain visible when blocked or overdue. Critical does not mean Estate Relay verifies safety, compliance, or professional completion.
Use skipped only when you have deliberately decided that the task does not apply to this stay. A skipped noncritical task earns its readiness weight. A skipped critical task remains an exception and cannot produce Ready; add a note explaining the decision.
A task can include an optional image selected with Apple’s system photo picker. Estate Relay stores a resized copy in local app storage and includes it in a complete JSON backup. The app does not scan the photo library or upload the image. Remove the photo from the task when it is no longer needed, and protect any backup that contains it.
When creating a stay, you can add a starter set covering common arrival and departure checks. These are editable examples, not property-specific instructions or professional recommendations. Remove, rename, reorder, or add tasks to match the actual property.
Use it for non-secret operating knowledge: system locations, ordinary routines, appliance notes, seasonal reminders, preferred setup, or where a physical document can be found. Do not enter alarm codes, safe combinations, door codes, passwords, payment details, or other credentials.
Store only contact details you have a legitimate reason to keep, such as a name, role, phone number, and concise operational note. Estate Relay does not contact anyone, verify a provider, make referrals, or guarantee a provider’s work.
Open the stay and choose its PDF export action. Estate Relay builds the document on-device and presents Apple’s share interface. Review the PDF before choosing a destination. The app does not upload the document or know where you send it.
A backup contains the Estate Relay records needed for restore, together with a schema version. Treat the file as sensitive: anyone who can open it may be able to read property labels, schedules, tasks, notes, manual entries, contact details, and locally attached information included by the app.
Open Settings, choose the backup action, and select a destination in Apple’s file or share interface. Store the file in a location you control and protect. Estate Relay does not maintain a copy and cannot retrieve a lost backup.
First create a current backup if you may need to return to the existing data. In Settings, choose restore, select an Estate Relay JSON file, review the destructive-replacement warning, and confirm only when the file and date are expected. The app validates supported backup structure before replacing current records.
The file may be incomplete, modified, from an unsupported future schema, not valid JSON, or not an Estate Relay backup. Download or copy the original file again and retry. Never edit the backup by hand unless you are prepared for it to remain unusable. A rejected file should not replace current data.
No. There is no Estate Relay account, automatic cloud synchronization, or live multi-user collaboration. Apple device backups may include app data depending on your Apple settings. JSON backup and restore can move a deliberate snapshot, but it is not continuous sync and can replace newer records on the destination device.
In the app’s local data container on the current device. Estate Relay has no developer-operated backend. iOS and device backups provide their own protections and behavior; protect the device with a passcode and review your Apple backup settings.
When enabled in Settings, App Lock asks iOS to authenticate with Face ID, Touch ID, or the device passcode before showing Estate Relay after it has locked. Biometric matching happens inside Apple’s LocalAuthentication system; Estate Relay receives only success or failure and does not receive biometric data. App Lock supplements rather than replaces a strong device passcode.
Use the relevant edit or deletion control for an individual property, stay, task, manual entry, or contact. Settings also provides a delete-all action with confirmation. Deleting the app removes its local container from that device, subject to copies retained in device backups or exported files you control.
Its associated stays, tasks, manual entries, and service contacts are also removed. Create a current JSON backup first if you may need those records later, then read the confirmation carefully before deleting.
An incomplete task becomes overdue when its due time passes. Verify the device date, time, and time zone; then complete, reschedule, skip, or otherwise update the task to reflect the real decision.
Look for an open, blocked, overdue, unassigned, or critically skipped task. Any unresolved critical exception prevents Ready. A stay with incomplete weighted work also remains below 100 percent. If a noncritical task truly does not apply, mark it intentionally skipped rather than complete.
Free device storage in iOS Settings, remove unneeded exports from their destinations, and retry. Before deleting app records, create a backup if the device has enough space. Estate Relay cannot recover files removed from another app or storage provider.
No. It records user-entered states, times, notes, and any locally attached evidence provided by the user. It does not inspect the property, confirm a person’s identity or location, certify safety, or guarantee task completion.
No. Estate Relay is an organizational utility. It does not monitor a property, dispatch anyone, contact emergency services, provide professional advice, or replace inspections. For urgent safety, security, fire, medical, utility, or property issues, use the appropriate local emergency service or qualified professional.
Use the App Store while signed into the Apple Account that acquired Estate Relay, then open your purchase history and redownload it where Apple permits. The app has no separate purchase account or restore button. See Apple’s current redownload guidance.
Apple processes the purchase and decides refund requests. Use Apple’s Report a Problem service. Dayton Thorpe and Good Little Apps do not receive payment-card details and cannot issue an App Store refund directly.
You may send a concise notice to goodlittleapps.support@gmail.com with the app version, device model, iOS version, and reproducible steps. Do not include property addresses, schedules, access details, contacts, backup files, or other private records. This address is a Developer & privacy contact, not an assistance service; a message does not create a service relationship, response-time commitment, or guaranteed individual reply.
Before sending a developer notice
Most questions are answered above. A defect report should contain only the minimum technical context needed to describe reproducible behavior.