The windows are included, but they are not due today
Imagine preparing Monday’s visit sheet for an apartment building. The agreement includes window cleaning once a month, on the first Wednesday. An assistant receives every task and returns a polished list showing the windows as pending on Monday. It has preserved the task but changed when it is due. Both need checking before the list reaches the team.
This guide proposes a trial of AI for turning agreed service conditions into a per-visit draft. Using an invented building, we separate two questions: “Is this due on this visit?” and “Has it been done?”. Not due today does not mean completed; included does not mean repeated every day. The person responsible reviews the draft before use.
Prepare the existing rules rather than asking for an invented plan
Gather an identified copy of the accepted scope, frequencies, visit days and confirmed exceptions. Keep requests that have not been accepted separate. For the trial, write those documents yourself using fictional data: no real agreement or address is needed to test the method.
Limpia Pro’s guide distinguishes planned frequency from execution records. That provides context, not recommended frequencies for your building. The trial here is about preserving supplied conditions rather than asking AI to decide how much cleaning is needed.
- One reference per rule: area, task, literal frequency and source document. “Windows” without the surface or scope may need clarification.
- A specific visit date. “Next week” is insufficient to check a calendar rule.
- Separate exclusions from pending requests. A building manager’s request is not automatically an accepted change.
- Execution records, if available and authorised. Their absence must stay visible rather than being replaced by a guess.
- Access conditions relevant to the visit. Do not include access codes, key details, residents’ phone numbers or security instructions in the trial.
Fictional building C-024: test Monday and then Wednesday
These notes are invented, not a recommended agreement. R1: “Visits on Mondays and Wednesdays; clean the entrance lobby floor on each visit”. R2: “Clean the stair handrail on Wednesdays”. R3: “Accessible interior lobby windows once a month, on the first Wednesday”. R4: “Garage excluded”. R5, a request not yet accepted: “Could you also give the shared storage room a clean now and then?”. No records of completed work are supplied.
Prepare the visit for Monday 2 November 2026. This table is an editorial interpretation for checking the exercise, not observed AI output or an approved work order. Scope and frequencies are fictional inputs only; they do not prescribe what a real building needs.
| Area and source | Applies to this visit | Execution and review |
|---|---|---|
| Entrance lobby floor · R1 | Included; due on this visit | No execution record; do not mark completed |
| Stair handrail · R2 | Included; not scheduled this Monday; rule: Wednesdays | Does not mean completed or excluded |
| Interior lobby windows · R3 | Included; next date under the rule: Wednesday 4 November | Do not add as pending on Monday; execution unknown |
| Garage · R4 | Outside the supplied scope | Do not create a task for this visit |
| Shared storage room · R5 | Pending request, without accepted scope or frequency | Clarify the request and seek acceptance; do not assign |
A trial instruction that does not expand the service
“Use only fictional notes R1–R5 pasted below and the visit on Monday 2 November 2026. Prepare a review draft, not an approved order. Separate included tasks, exclusions and unaccepted requests. For each included task show the area, literal task, source, literal frequency, whether it is due on this visit and why. Keep execution in a separate column: no records are provided, so mark nothing completed. Do not turn monthly into every visit. Calculate dates only where the supplied rule determines them and show the rule so a person can check the calendar. Ask if a date, frequency or acceptance is missing. Do not add products, methods, durations, prices or commitments. Finish with open questions. Notes: [paste R1–R5]”.
Then request a second draft for Wednesday 4 November. All three included tasks are due under the example’s rules that day; none becomes completed just because the date changes. Check the calendar yourself. If you replace R3 with “once a month, day unspecified”, the response should leave the date unresolved rather than choose the first Wednesday out of habit.
Anthropic’s documentation explains that Claude can produce incorrect or context-inconsistent responses. It recommends restricting answers to supplied documents and checking claims. This prompt is a proposed trial: its performance has not been measured and it does not guarantee correct rule interpretation.
Review the list as the service supervisor
Read the draft beside R1–R5. First look for scope expansions: an included garage, an accepted storage-room request or windows repeated every visit. Then check for losses, such as the handrail disappearing because it is not due on Monday. The plan retains the rule even when that visit’s sheet does not include the task.
Check execution separately. “Scheduled” is not “done”, and “not due today” is not an incident. If a scheduled task could not be completed, record the reason using the normal process and ask how it should be rescheduled; do not let the assistant change the agreed frequency. A team observation should not become a service change either.
This trial organises administrative information. Products, techniques, access, risk prevention and work acceptance remain with professionals and applicable procedures. Do not ask the assistant for mixtures, dosages, manoeuvres or decisions about surfaces or installations.
Is a spreadsheet enough, or does the process need connecting?
If the scope is clear and only the columns need separating, a spreadsheet may be enough. CleanManager documents task types for organising planning and notes that available information depends on modules and settings. This is the vendor’s description, not our functional test or verification of compatibility with your software.
The manual trial ends when you copy invented inputs into an assistant and review the result. Connected automation would need to read an authorised source, retain the plan version and propose a date-appropriate list while preserving human acceptance. Before adding AI, assess whether a spreadsheet and a calendar using the agreed rules are enough for your process. If they are not, describe the reading or classification problem you need to solve and test it separately.
Adaris can assess custom software, CRM or integration for that workflow. A first scope could cover one plan format, a per-visit draft, references to original rules and a history of accepted changes, with agreed permissions, export and recovery. Actual connection options would need checking. This is a case-by-case proposal, not an existing proprietary cleaning app. Invoicing, automatic assignment and order dispatch would need separate assessment.
A pilot that detects changes in meaning
First write a human answer key for both dates. Add a monthly rule without a day, a cancelled visit and a scope change that has not been accepted. Compare preparing the sheet manually with reviewing an AI draft. Count altered frequencies, added tasks, omitted tasks, requests treated as accepted and invented completions. Also record the full review and correction time. These are proposed measures, without demonstrated results or savings.
If the draft includes the garage or marks the windows completed, do not use it as an operational sheet: correct the interpretation and examine which information or instruction failed. Before extending the pilot, decide which errors prevent use and who must approve the draft.
Start with entirely fictional data. Do not paste real agreements, addresses, names, residents’ photos or commercial information without authorisation and appropriate terms. Acelera pyme recommends reviewing terms of use and generated content. A conversation does not replace the business archive of plans and visit records.
Related services
Sources
Does the agreed plan reach each visit clearly?
Tell us in Spanish where you keep service conditions and how you prepare visit lists. With a fictional example, we can assess scoped development or integration, with agreed scope, permissions and checks. Commercial communication is in Spanish.