Client project follow ups

Follow up on a requested scope change

Unblock a client project by making the missing decision or dependency unmistakable. This page focuses on how to follow up on a requested scope change while keeping the message clear, proportionate, and fully refusable.

Write your messageHow it works

Name the impact without exaggerating it

Describe who had to wait, worry, redo work, spend money, or make a choice with incomplete information. For a message about how to follow up on a requested scope change, use this factual base: summarize the deliverable, version, requested input, owner, and effect on the schedule.

Make repair practical

Offer the repair you can actually complete, with ownership, timing, and any limit stated honestly. Give a small set of options and explain which default plan applies if the real deadline passes. Make the immediate next step clear enough that the recipient can answer without reconstructing the entire history.

Let future behavior carry the proof

Do not bury a scope or price change, threaten the relationship, or pretend silence means approval. Use the contract and documented escalation route for legal, payment, privacy, or security decisions. A promise inside a message is weaker than a visible change in what you do after it.

Common questions

People also ask

How do I follow up on a requested scope change?
Summarize the deliverable, version, requested input, owner, and effect on the schedule. Give a small set of options and explain which default plan applies if the real deadline passes. Keep the first message focused on one purpose rather than every unresolved part of the relationship.
What should I include when I follow up on a requested scope change?
Include verified context, the real impact, the decision or support needed now, and any genuine timing constraint. Do not bury a scope or price change, threaten the relationship, or pretend silence means approval.
What if they do not respond after I follow up on a requested scope change?
Complete any repair that does not require contact, then let the recipient choose whether the relationship continues. Use the contract and documented escalation route for legal, payment, privacy, or security decisions.

What Kildr supports now

The full request stays simple. The controls around it are deliberate.

Opening is free

Recipients never pay to open or read a Kildr message. Before opening, they see who is asking when the sender chose to identify themselves and the total amount paid. A sender phone number is shown only when the sender explicitly chooses to share it.

The recipient stays in control

A recipient can decline without opening, block one sender, opt out of Kildr entirely, or report an opened message. A normal sender block can be removed by the recipient later. Declining means that message can never be viewed afterward.

Three optional responses

After opening, the recipient can choose “I need to think”, “Text me”, or “Never contact me again”. The first two can be switched after a 10-minute cooldown. “Never contact me again” is final, and the recipient can permanently block that sender or all Kildr requests.

Themes and read receipts are optional

Senders can choose free themes or buy a premium theme. An active paid theme is added to the visible Amount paid total. A separate read-receipt add-on unlocks Opened and Read status; without it, the sender's lifecycle information stops at Delivered.

Paying creates the request and optional sender features. It never creates an obligation for the recipient to open, respond, unblock, or make contact.

Related situations

All situations
Client project follow ups

Follow up before a project milestone

Unblock a client project by making the missing decision or dependency unmistakable. This page focuses on how to follow up before a project milestone while keeping the message clear, proportionate, and fully refusable.

Read this situation
Client project follow ups

Follow up on a content review

Unblock a client project by making the missing decision or dependency unmistakable. This page focuses on how to follow up on a content review while keeping the message clear, proportionate, and fully refusable.

Read this situation
Client project follow ups

Follow up after a project was paused

Unblock a client project by making the missing decision or dependency unmistakable. This page focuses on how to follow up after a project was paused while keeping the message clear, proportionate, and fully refusable.

Read this situation
Work, business & money

Resolve a client misunderstanding

When a client stops responding after a dispute, clarity beats persuasion. Reconstruct the agreed facts, own what is yours, and present one workable resolution.

Read this situation

Prefer to read around it first? Read the journal or see how Kildr works.