01 / 08EVENT
A new document arrives
Field study notes
- Source document received
- Original retained
- Ready to review
Received
A research document starts the work. The original stays available throughout.
PROPERTY OPERATIONS
Better systems for maintenance, coordination and portfolio visibility.
Property operations often span management platforms, email, phone calls, vendors, spreadsheets and human judgement.
Stacx24 connects those moving parts into more reliable operational systems.
Emergency, safety, legal and sensitive situations always escalate to an authorised person.
- THE MOVING PARTS
- Property management platform, email, phone, vendor portals, owner statements and spreadsheets.
- WHERE IT WAITS
- Missing details, unclear priority, the vendor callback, the owner question.
Architecture sequence: MAINTENANCE REQUEST, then COLLECT MISSING DETAILS, then CLASSIFY, then DETERMINE PRIORITY, then ROUTE, then TRACK, then ESCALATE, then RESOLVE. Stages marked Human pause the flow until a person decides. Status labels update as the event moves.
MAIN ARCHITECTURE · ILLUSTRATIVE SCENARIO · MAINTENANCEILLUSTRATIVE · MAINTENANCEMAINTENANCE REQUEST
Portal, email or phone
READY
COLLECT MISSING DETAILS
Unit, access, photos, when
READY
CLASSIFY
Trade, issue, safety keywords
READY
DETERMINE PRIORITY
Rules: urgency × impact
READY
ROUTE
Contracted vendor for trade + site
READY
TRACK
Vendor accept · schedule · arrival
READY
ESCALATE
Overdue, disputed or sensitive
REVIEW REQUIRED
RESOLVE
Confirmed with tenant · owner informed
READY
ESCALATION BRANCH
- EMERGENCY
- SAFETY
- LEGAL
- SEVERE COMPLAINT
- UNCERTAIN SITUATION
AUTHORISED HUMAN
Property manager · on call
ON CALL
NO AUTOMATED ACTION ON THIS PATH
SCENARIO A · "KITCHEN TAP DRIPPING"PAUSED · PROPERTY MANAGER DECIDES
SUPPORTING SYSTEMS
Four systems around the maintenance core.
Maintenance is where the friction is most visible, so it is usually the pilot. The same records, the same vendors and the same owners feed four more systems that share its data and its escalation rules.
Maintenance recordsVendorsOwnersEscalation rules
Illustrative working previews
RECORDSDRAFTREVIEW
Owner Reporting
Monthly and on-request statements assembled from maintenance, financial and occupancy records, drafted in the owner’s format.
Human: ACCOUNT MANAGER REVIEWS AND SENDS
WORK ORDERVENDOR APIAPPROVE
Vendor Coordination
Dispatch, acceptance, scheduling, arrival confirmation and invoice matching across contracted vendors.
Human: MANAGER APPROVES SPEND ABOVE THRESHOLD
DATAANALYSISDECIDE
Portfolio Intelligence
Repeat issues, vendor performance, cost per unit and response times across the portfolio, explained in plain language.
Human: OPERATIONS LEAD DECIDES WHAT TO CHANGE
EVENTTEMPLATESEND
Routine Communications
Acknowledgements, appointment confirmations, status updates and reminders, from templates your team approved.
Human: ANYTHING NON-ROUTINE GOES TO A PERSON
ESCALATION
Some situations should never depend on autonomous automation.
The system handles the routine: a dripping tap, a broken blind, a vendor who needs chasing. It also detects when a request is not routine. Then it stops, and a person authorised to act takes over. That rule is designed in, logged, and cannot be switched off by configuration.
Property operationsEscalation desk
Illustrative scenario · simulated data
emergency escalation
Immediate contactExample request · Resident portal
There is a strong smell of gas in the second-floor hallway.
Detected by keyword, category or sensor. Immediate call to the on-call manager and emergency vendor. The system does not wait.
- TriggeredComplete
- ProcessingComplete
- EscalatedComplete
- AcknowledgedComplete
Escalation activity
- TriggeredComplete
Gas keyword matched the agreed emergency rule.
- ProcessingComplete
Match the emergency rule and identify on-call contacts. Emergency notification is immediate.
- EscalatedComplete
Immediate calls initiated to the on-call manager and emergency vendor.
- AcknowledgedComplete
Manager acknowledged. Human response now in progress.
Automation does not choose the emergency response.
On-call property managerEmergency vendor · call initiated
Acknowledgedsafety escalation
Human reviewExample request · Resident portal
The entrance lock is damaged and residents cannot secure the building.
Routed to a person before any vendor is contacted. Site visit scheduling is a human decision.
- TriggeredComplete
- ProcessingComplete
- EscalatedComplete
- AcknowledgedComplete
Escalation activity
- TriggeredComplete
Security and access concern flagged for safety review.
- ProcessingComplete
Prepare site and access details for a person to review before vendor contact.
- EscalatedComplete
Request and site details routed to an authorised person before vendor contact.
- AcknowledgedComplete
Manager acknowledged. Safety review now in progress.
Vendor contact and site visit scheduling wait for a human decision.
Authorised property managerVendor contact · awaiting human decision
Acknowledgedlegal escalation
Human reviewExample request · Resident email
I dispute the deductions from my deposit and want a formal explanation.
No automated reply. The message, its context and a suggested category go to the authorised manager.
- TriggeredComplete
- ProcessingComplete
- EscalatedComplete
- AcknowledgedComplete
Escalation activity
- TriggeredComplete
Deposit dispute flagged for legal review.
- ProcessingComplete
Attach the original message and records; keep automatic replies blocked.
- EscalatedComplete
Original message, context and suggested category sent to the authorised manager.
- AcknowledgedComplete
Manager acknowledged. Message and context under review.
No automated reply is sent.
Authorised property managerResident reply · awaiting human review
Acknowledgedsevere complaint escalation
Human reviewExample request · Resident email
I have reported this repeatedly and will raise it with the regulator.
Tone and history are flagged. A person reads the whole thread before anyone responds.
- TriggeredComplete
- ProcessingComplete
- EscalatedComplete
- AcknowledgedComplete
Escalation activity
- TriggeredComplete
Repeat complaint and regulator reference flagged.
- ProcessingComplete
Gather the conversation history for full-thread review before any response.
- EscalatedComplete
The full conversation and history routed to a person for review.
- AcknowledgedComplete
Manager acknowledged. Full conversation review in progress.
A person reads the whole thread before anyone responds.
Property managerResponse · awaiting full-thread review
Acknowledgeduncertain situation escalation
Human reviewExample request · Maintenance request
The request lists two different units and conflicting access instructions.
When the system is not sure, it says so and asks a person. Uncertainty is a route, not a failure.
- TriggeredComplete
- ProcessingComplete
- EscalatedComplete
- AcknowledgedComplete
Escalation activity
- TriggeredComplete
Conflicting details detected; the system cannot confidently proceed.
- ProcessingComplete
Collect the conflicting details and request direction instead of guessing.
- EscalatedComplete
The conflicting information sent to a person for direction.
- AcknowledgedComplete
Manager acknowledged. Clarification now in progress.
The system asks for direction instead of guessing.
Property managerNext action · awaiting human direction
AcknowledgedESCALATION RULES ARE WRITTEN WITH YOUR TEAM AND REVIEWED QUARTERLYTHE ESCALATION PATH CANNOT BE DISABLED BY CONFIGURATION
CORE SYSTEM MODEL
The system is the product. Technology is a component.
- Not every step needs AI.
- Some need rules.
- Some need software.
- Some need edge processing.
- Some need people.
We engineer the right combination.
Research assistance
IN THE OPERATION
A document arrivesFrom the research team
02 / 08CONTEXT
Bring the background together
Document + background
- Source details attached
- Related records found
- Approved labels loaded
Context attached
Existing records, source details and the approved label list give the document context.
03 / 08PROCESSING
Check the details first
Document checks
- Duplicate check complete
- Required details present
- Text ready for review
Checks complete
Software checks for duplicates and missing information before any AI suggestion.
04 / 08INTELLIGENCE
Suggest a label, within scope
Suggested label
- Field study
- Supporting passage highlighted
- Awaiting researcher review
Suggestion only
AI proposes a label from the approved list. It cannot publish the label itself.
05 / 08DECISION
A researcher makes the decision
Label review
- Source passage checked
- Suggested label reviewed
- Field study approved
Reviewed by researcher
The researcher reads the supporting passage and approves or corrects the suggestion.
06 / 08ACTION
Update the research record
Research record
- Label: Field study
- Source linked
- Review retained
Saved to record
Only the approved label enters the record, alongside its source.
07 / 08OBSERVATION
Record what actually happened
Activity record
- Suggestion recorded
- Reviewer decision recorded
- Save confirmed
Outcome recorded
The system records the suggestion, the review and the saved result so the team can inspect them.
08 / 08IMPROVEMENT
Review the labelling rules
Next-cycle guidance
- Review corrections
- Agree guidance changes
- Use approved guidance next time
Feedback to the next event
The team reviews corrections and agrees changes to the guidance before the next document.
Each outcome informs the next cycle.
- 01 · EVENTA new document arrives
A research document starts the work. The original stays available throughout.
- 02 · CONTEXTBring the background together
Existing records, source details and the approved label list give the document context.
- 03 · PROCESSINGCheck the details first
Software checks for duplicates and missing information before any AI suggestion.
- 04 · INTELLIGENCESuggest a label, within scope
AI proposes a label from the approved list. It cannot publish the label itself.
- 05 · DECISIONA researcher makes the decision
The researcher reads the supporting passage and approves or corrects the suggestion.
- 06 · ACTIONUpdate the research record
Only the approved label enters the record, alongside its source.
- 07 · OBSERVATIONRecord what actually happened
The system records the suggestion, the review and the saved result so the team can inspect them.
- 08 · IMPROVEMENTReview the labelling rules
The team reviews corrections and agrees changes to the guidance before the next document.
Everyday operations
IN THE OPERATION
A request arrivesFrom the operating team
01 / 08EVENT
A request starts the work
New work request
- Request received
- Source application linked
- Handoff opened
Received
An incoming request starts a handoff between the tools your team already uses.
02 / 08CONTEXT
Attach the details once
Request background
- Existing record attached
- Current state checked
- Owner identified
Context attached
The system brings together the request, existing records and its responsible owner.
03 / 08PROCESSING
Let the rules route the work
Connected applications
- Request inbox → work queue
- Required details checked
- Work queue → owner workspace
Handoff prepared
Defined rules check the request and pass its details between connected applications.
04 / 08INTELLIGENCE
Rules are enough here
Routing rule
- A required detail is missing
- Exception route selected
- Named owner notified
No AI needed
This example needs no AI decision. Defined rules identify an exception and send it to its owner.
05 / 08DECISION
The owner resolves the exception
Exception review
- Exception opened
- Missing detail supplied
- Owner confirms next step
Reviewed by owner
A named person supplies the missing detail and confirms that the work can continue.
06 / 08ACTION
Complete the handoff
Completed handoff
- Confirmed details transferred
- Next application updated
- Owner notified
Handoff complete
The confirmed information reaches the next application and the work continues.
07 / 08OBSERVATION
Keep the outcome visible
Activity record
- Exception recorded
- Resolution recorded
- Handoff confirmed
Outcome recorded
The system records completion and exceptions so the team can see what happened.
08 / 08IMPROVEMENT
Review the handoff rules
Next-cycle guidance
- Review recurring exceptions
- Agree routing changes
- Apply approved rules next time
Feedback to the next event
The team reviews repeated exceptions and approves rule changes for future requests.
Each outcome informs the next cycle.
- 01 · EVENTA request starts the work
An incoming request starts a handoff between the tools your team already uses.
- 02 · CONTEXTAttach the details once
The system brings together the request, existing records and its responsible owner.
- 03 · PROCESSINGLet the rules route the work
Defined rules check the request and pass its details between connected applications.
- 04 · INTELLIGENCERules are enough here
This example needs no AI decision. Defined rules identify an exception and send it to its owner.
- 05 · DECISIONThe owner resolves the exception
A named person supplies the missing detail and confirms that the work can continue.
- 06 · ACTIONComplete the handoff
The confirmed information reaches the next application and the work continues.
- 07 · OBSERVATIONKeep the outcome visible
The system records completion and exceptions so the team can see what happened.
- 08 · IMPROVEMENTReview the handoff rules
The team reviews repeated exceptions and approves rule changes for future requests.
Connected fields
IN THE OPERATION
A field reading arrivesFrom a connected sensor
01 / 08EVENT
A sensor reads the field
Incoming field reading
- Sensor reading received
- Field identified
- Reading time attached
Received
A new field reading starts the cycle, connecting conditions on the ground to the system.
02 / 08CONTEXT
Put the reading in context
Field background
- Field history attached
- Recent readings loaded
- Current conditions attached
Context attached
Field history and recent conditions help the team interpret the new reading.
03 / 08PROCESSING
Check the signal near the field
Edge processing
- Local checks run
- Incomplete readings flagged
- Relevant readings forwarded
Local checks complete
Local edge checks validate readings before relevant information reaches the monitoring application.
04 / 08INTELLIGENCE
Prepare a suggested response
Response proposal
- Field context considered
- Suggested response prepared
- Sent for agronomist review
Suggestion only
The system uses the checked information to propose a response within its defined scope.
05 / 08DECISION
The agronomist reviews
Agronomist review
- Conditions reviewed
- Proposal checked
- Response approved
Reviewed by agronomist
The agronomist checks the proposal and approves or adjusts it before it reaches the operator.
06 / 08ACTION
Send the approved proposal
Operator work item
- Approved proposal attached
- Instructions available
- Delivered to operator
Ready for the operator
The approved proposal reaches the operator with the instructions they need.
07 / 08OBSERVATION
Keep watching the conditions
Field activity record
- New readings recorded
- Operator reports attached
- Outcome ready for review
Observation continues
New readings and operator reports help the team understand what happened next.
08 / 08IMPROVEMENT
Review the next field cycle
Next-cycle guidance
- Review field observations
- Agree guidance changes
- Use approved guidance next time
Feedback to the next event
The agronomist reviews the observations and agrees guidance for the next cycle.
Each outcome informs the next cycle.
- 01 · EVENTA sensor reads the field
A new field reading starts the cycle, connecting conditions on the ground to the system.
- 02 · CONTEXTPut the reading in context
Field history and recent conditions help the team interpret the new reading.
- 03 · PROCESSINGCheck the signal near the field
Local edge checks validate readings before relevant information reaches the monitoring application.
- 04 · INTELLIGENCEPrepare a suggested response
The system uses the checked information to propose a response within its defined scope.
- 05 · DECISIONThe agronomist reviews
The agronomist checks the proposal and approves or adjusts it before it reaches the operator.
- 06 · ACTIONSend the approved proposal
The approved proposal reaches the operator with the instructions they need.
- 07 · OBSERVATIONKeep watching the conditions
New readings and operator reports help the team understand what happened next.
- 08 · IMPROVEMENTReview the next field cycle
The agronomist reviews the observations and agrees guidance for the next cycle.
Read the complete system model
- EVENT
Something happens in the operation.
- CONTEXT
Records, history and state are attached.
- PROCESSING
Rules, software and integrations do the deterministic work.
- INTELLIGENCE
One bounded AI component, where judgement can be modelled.
- DECISION
A named person decides where it matters.
- ACTION
Something changes in the world.
- OBSERVATION
Telemetry and monitoring record what happened.
- IMPROVEMENT
The loop feeds back into the next event.
SYSTEMS USED · SERVICES
RELATED WORK
photo: maintenance coordinator and vendor on site
WORK · AUTOMATIONCASE STUDY
Operational Automation
Routine operational handoffs connected across applications, with validation at intake, rules for routing, and exceptions routed to the people who own them.
APPLICATION · RULES ENGINE · API · HUMAN ESCALATION
NEXT STEP
Which property operation creates the most friction today?
Maintenance intake, vendor chasing, owner statements, the Monday inbox. Describe it as it runs and we will show you what the system would carry and where a person must stay.
Discuss Property Operations
No technical specification required. Start with the request that waits the longest.