Operations
Portfolio Command
Portfolio command for owners, managers, vendors, and field work.
Loading this page.
Platform modules
Start with the buyer’s pain: owner clarity, vendor scope, field execution, records, events, or reporting. Each module shows the workflow, proof, and safe expansion path.
Visual module catalog
Portfolio command for owners, managers, vendors, and field work.
Maintenance requests, preventive care, and closeout proof without side-channel chaos.
Give vendors enough context to work, not enough to overshare.
Owner clarity without the operational clutter.
A mobile execution path for the people standing at the property.
Structured compliance workflows with review before sensitive action.
Written notices and offline engagement tied back to the operating record.
Rental and short-term-stay operations connected to property readiness.
Property health, asset signals, and security posture in one governed layer.
Module landing pages describe buyer-facing product workflows and controlled-pilot proof. They do not change billing, permissions, legal advice, emergency monitoring, payments, or live integrations.
Trust boundaries
Buyers can see how each module treats privacy, authority, automation, money movement, and emergency-adjacent work. 198 boundaries are published across these modules.
Read the strongest refusals grouped by theme
Does this software ever hold, move, or charge money?
Financials
The accounting and payments workbench prepares evidence, classifications, export mappings, and payment packets for human review. It does not move money, file taxes, submit 1099s, create live QuickBooks records, or expose internal vendor cost or coordination markup to owners.
Read module contextConcierge
Concierge intake records an owner-safe request for human review. Receipt is not acceptance, dispatch, scheduling, purchasing, or an emergency-response guarantee. Do not submit access or security credentials, payment details, private guest data, vendor wholesale pricing, or raw media identifiers. Quoalis does not store payment instruments or custody client funds here.
Read module contextOperations
Time and cost entries are staff-reviewed operational records only. They do not run payroll, pay vendors, create invoices, charge cards, expose loaded labor rates to owners/vendors, publish raw GPS, or write accounting ledgers.
Read module contextVendor admin
Vendor administration stores business profile, service-fit, compliance metadata, and review posture only. It does not store raw W-9/TIN values, bank details, payment instructions, access/security codes, vendor markups, or evidence object keys.
Read module contextPlatform onboarding
Commercial authorization packets are start-of-service evidence only. They do not create billing-provider customers, invoices, subscriptions, payment methods, financial charges, email, access grants, imports, monitoring, or dispatch.
Read module contextWill it send someone, or act, without a human deciding?
Incidents
Reserve provides issue acknowledgement and property coordination, not emergency dispatch, alarm monitoring, physical security, guaranteed arrival, or guaranteed resolution.
Read module contextMaintenance
Maintenance requests capture property care needs, triage decisions, owner-safe updates, and manual follow-up status. Quoalis does not guarantee emergency response through this portal, store access/security secrets in ordinary request data, expose vendor pricing or markups, process payments/client funds, or automatically dispatch vendors.
Read module contextConcierge execution
Concierge execution coordinates an explicitly scheduled property-team visit. It does not automatically dispatch staff or vendors, promise emergency response or arrival, expose access or security details, or send owner notifications without staff review. Owner views contain only reviewed closeout language and explicitly owner-visible ready evidence.
Read module contextApprovals
The owner approval center centralizes review packets and decision posture. It does not auto-approve, bypass authority policies, send tenant-sensitive notices, execute payments, or dispatch vendors without a valid approval.
Read module contextOperations intelligence
Action links open existing source workflows. They do not automatically dispatch, approve, pay, alter source records, or override required human review.
Read module contextSnow
Snow routes coordinate winter access work only. They do not optimize routes, auto-dispatch vendors, expose access/security details, show vendor pricing, promise emergency response, or guarantee arrival/resolution times.
Read module contextReserve notifications
Reserve notification adapters are release-gate contracts only. This API does not send live email, SMS, WhatsApp, push, emergency, alarm, utility, or dispatch notifications.
Read module contextIs anyone being watched, tracked, or recorded?
Operations intelligence
This is an assignment-only field route packet. It uses synthetic relative context and is not live tracking, route optimization, surveillance, or an emergency-dispatch tool.
Read module contextOperations intelligence
This staff-only preview assembles role-specific map status overlays from authorized records and property markers. A marker is a coarse canvas cell, either projected from the single coordinate a person recorded for the property or, when none is recorded, derived from the property identifier; every marker states which of the two it is. It is not live GPS, route optimization, occupant tracking, camera monitoring, alarm monitoring, emergency dispatch, provider writeback, or automated ticket prioritization.
Read module contextOperations intelligence
IoT signals become reviewable ticket candidates only. This endpoint does not dispatch, notify emergency services, expose device coordinates, publish owner alerts, or create work without an operator review.
Read module contextSystems
Home technology records show reliable status and planned care only. They exclude raw CCTV, continuous telemetry, access or alarm credentials, remote controls, network secrets, drone mitigation, and automated dispatch.
Read module contextSystems
The physical security registry tracks equipment, responsibility, privacy posture, service tier, and maintenance readiness. It does not promise emergency monitoring, police dispatch, live surveillance staffing, or access-code disclosure, and it stores no credential, stream URL, or provider secret.
Read module contextCommunications
Phone records are provider-neutral operational metadata only. Raw phone numbers, live carrier commands, recording files, transcripts, payment data, and secrets are excluded.
Read module contextDoes it decide anything a lawyer or an appraiser should decide?
Compliance
Compliance localization tracks jurisdiction, source, version, review, export, and delivery posture. It does not provide legal advice, jurisdiction-specific legal wording, court filing, eviction authority, or automated notice sending.
Read module contextRentals
Tenant lifecycle workflows organize reminders, checklists, evidence, and review packets. They do not provide legal advice, jurisdiction-specific notice automation, court filing, eviction authority, or payment collection, and they hold no tenant identity.
Read module contextRentals
Unit tenancies record which unit is occupied, by what kind of arrangement, and over what window. They hold no tenant identity, contact details, payment data, lease documents, or screening results, and recording a tenancy neither creates nor terminates a legal agreement.
Read module contextRentals
Valuation-support language is a source-backed narrative only: it may describe history, readiness, amenities, and income-potential support, but it must not guarantee valuation, forecast income as certain, or replace a licensed appraisal.
Read module contextCan anything in here open a door or sign someone in?
QR registry
QR codes are context pointers only. They do not grant sign-in, MFA, property access, owner authority, vendor package scope, payments, access codes, or emergency dispatch.
Read module contextIdentity
Six-digit email codes verify mailbox reachability only. They do not reset provider passwords inside Quoalis, replace MFA/passkey step-up, approve spending, grant property scope, or authorize account changes.
Read module contextIntegrations
Integration records are provider-neutral, account-scoped, and audit-ready. Credentials and private calendar URLs are accepted only through write-only setup, are never returned, and belong only in the server-side vault. Calendar reads store busy windows only. No scraping, payment movement, tax filing, private event detail, or unreviewed external write is performed by these endpoints.
Read module contextVendor work packages
Vendor work packages are purpose-built, expiring assignments. Creating a package does not grant generic property access, confirm vendor availability, approve owner cost, or authorize work before explicit vendor acceptance, assignment, and operator dispatch.
Read module contextPlatform onboarding
Access grant adapter packets are dry-run grant intents only. They do not create account, workspace, property, vendor, field, or owner-decision access rows.
Read module contextNext best step
Can I understand which module solves my first operational problem?
Start with view module or compare with compare pricing. Each path is designed to answer a buyer question before asking for a meeting.Pilot access
The best demo is not a feature checklist. It follows a request from owner intake to manager triage, vendor packet, field evidence, reviewed closeout, and owner-safe reporting.
We respond with the recommended demo route, who should attend, and what production access would require.