How to Record a Regular Service the Customer Declines This Time

Record an agreed declined occurrence without implying attendance or ending the whole recurring service, with concise outcome and next-date examples.

Daylane week schedule with field Jobs, Customers and service Locations
A real Daylane schedule with sanitised fictional example data.

Record that the customer declined this occurrence, confirm whether the next regular service remains wanted and resolve the affected attendance accordingly. Do not describe work as completed when no service took place. A one-time decline is different from ending the recurring arrangement.

Clarify the extent of the decline

Ask whether the customer means the whole occurrence, one task within it or the ongoing service. The answer determines whether you review the Visit, the Job scope or the future pattern.

Three illustrative declined-service outcomesScroll for more columns →
Customer decisionRecordNext check
No service this weekThis occurrence declined by agreementConfirm next regular date
Omit one task todayRevised agreed scope for this attendanceRecord remaining requested work, if any
Stop regular serviceOngoing arrangement endingReview generation and existing future Jobs

Use factual wording

Example: 'Customer confirmed on 5 September that the 7 September clean is not required. No attendance took place. The next regular Visit remains 21 September.' Use the actual dates and only state the next booking is unchanged after checking it.

Avoid vague notes such as 'missed' when the customer deliberately declined the service. That wording can imply an operational failure or unanswered access attempt that did not happen.

Review the next occurrence separately

Daylane creates separate recurring Jobs, so resolving one occurrence does not shift the rest. Check that the next Job still has the standard scope, correct instructions and an agreed date.

If the gap changes the work likely to be needed next time, review duration and scope before confirming attendance. Do not assume the usual short service remains appropriate simply because the pattern is unchanged.

Choose between skipping and postponing a Visit

Sources and scope

An original operational guide from the Daylane team at Blu Mint Digital. Scenarios, durations and message wording are illustrative planning examples, not customer results or industry benchmarks. Product references were checked against the Daylane implementation on 5 September 2026. Adapt the workflow to your service, customer agreements and working conditions.

How we write and maintain our guides. Free templates and planning tools.

    Back to the guide library

    Put the next Job in a clearer place.

    Start with one user and unlimited manually scheduled Jobs.

    Start 14-day trial