What gets checked
Checks cover visible condition and agreed points, not an open list of tasks.
What determines your package?
Choose a service scope that matches how you actually use the property.
See what oversight covers, compare packages, and check the indicative range.
Operating setup
First, establish property use and the operating scope.
The package defines check scope, access rules, owner documentation, and what needs the owner's approval.
Four setup points
Who may enter
Owner, technician, cleaner, or partner entry follows the agreed access method.
What the owner receives
A visit report or other documentation suited to the event.
Owner approvalWhat needs approval
A higher cost or scope change requires owner approval before action.
These points define the package and estimator context.
Package in brief
Choose the service level, then check the range.
The three packages differ by local presence, access handling, and on-site decisions.
Basic Package
Regular local checks, documented visits, and a clear status after each visit.
- Visits:
- min. 1/month
- Access coordination:
- owner arranges
- Emergency decisions:
- Every paid action needs approval
- Owner receives:
- visit report and status; owner still handles entries, technicians, and most decisions
Extended Package
Basic + access, technician, cleaning, and entry coordination within the agreed scope.
- Visits:
- min. 2/month
- Access coordination:
- technicians, cleaning, entries
- Emergency decisions:
- Every paid action needs approval
- Owner receives:
- visit reports and people coordination; owner is not connecting technicians, cleaning, and access remotely
Full Package
Extended + priority response, emergency decisions within the agreed limit, and the strongest local representation.
- Visits:
- min. 3/month
- Access coordination:
- strongest coordination
- Emergency decisions:
- Agreed limit
- Owner receives:
- a local decision layer; less remote coordination from abroad within defined boundaries
Higher cost, scope change, or action beyond the limit returns to the owner's decision.
Package rhythm and limits
The package defines visit rhythm, access scope, response timing, and the limits of autonomous action.
First we establish property use. Then we match the package.
Packages differ in visit rhythm, access coordination, priority, and decision limit.
- Visit rhythm
- Access & coordination
- Decision limit
Cost depends on package, property size, and how the property is used. The estimator shows the exact range.
Estimator handoff
Scope first, then the indicative range.
The estimator does not choose the package for you. It converts the agreed model into an indicative monthly range for the conversation.
- 01Scope
package and what needs approval
- 02Property use
private use, guests, or mixed
- 03Property parameters
size, rooms, and basic context
Indicative monthly range
Check the range before sending an inquiry.
Range after setting the details
approximate monthly range
The result appears after completing the estimator.
After the estimate
After the estimate you know what to confirm next.
The indicative range is a starting point for the conversation, not a binding quote. Three things are enough to talk.
- Starting scope
The package and what needs approval before action.
- Property use
Private, guest stays, or mixed, to be confirmed.
- For the conversation
Location, size, and the property's basic context.
Before start, Sentinel confirms the visit rhythm, access, and limits of autonomous action.
Start qualificationService boundaries
What sits inside the agreed scope.
Direct rules: included, conditional, excluded, or subject to owner approval.
Location eligibilityTorrevieja + 50–70 km radius.
Inside agreed scope
Local oversight
Scheduled condition checks at the rhythm defined by the package.Controlled access
Keys, entries, and third-party presence handled by agreed rules.Owner documentation
Reports and decision requests when required by the event or scope.Operational coordination
Contact with technician, cleaning, or contractor when it fits the agreement.Outside agreed scope
Bookings and platforms
Pricing, licensing, listings, and platform communication require separate agreement.Financial or owner administration
Finances, disputes, owner documents, and decisions outside the agreed model require separate agreement.Personal and lifestyle tasks
Personal errands and tasks without defined responsibility remain outside the service.Unlimited emergency work
Emergency work and costs have package limits; action beyond the limit requires owner approval.Tasks outside the agreement
Work outside the package or current agreement requires separate approval before execution.Owner documents and information
The owner receives a document or record suited to the event.
The scope may produce a visit report, operational record, decision request, or action summary.
See how the process worksDocuments and records preview
Visit report
The agreed check results and property status after the visit.
Operational record
Access events and ongoing coordination retained for the agreed scope.
Action summary
The action completed within scope and its current status.
Decision request
Cost, scope change, or action beyond authority — for owner approval.
The record type does not change the package, agreed response time (SLA), limits, or exclusions.
One-off services outside a package
Limited option
Single actions do not replace a monthly package.
They can be agreed after qualification; they do not include recurring visits, reports, agreed response time, or authority for Sentinel to decide independently.
Possible after agreement
- Key holding
- Cleaning coordination
- One-off access coordination
- Seasonal property prep
What it does not include
- Ongoing oversight
- Cyclic reporting
- Emergency response under SLA
- Decision authority
After reviewing scope
Request a package comparison for your property.
Contact us to compare packages and confirm scope.
Send a short property context; qualification will confirm whether the model fits.
QualificationLocation and property use first.
ScopeYou know what will be checked and when approval is required.
Next stepSend the property context to start qualification.