For freelancers and designers

Keep the missing client input separate from your own promise.

You can have work ready to do and still be waiting for a logo, a decision or one final piece of information. Give each unfinished interaction a clear next step.

Name what is actually blocking you

“Website for Nisha” describes a project, not a useful follow-up. “Get the final logo files” tells you exactly what is missing and whom to ask. Keep that item on Waiting on them.

You might also owe Nisha a revised layout. That belongs on Your turn as a separate Follow-up. The two records can share a Person without sharing the same outcome.

Agree a checkpoint, not a cycle of vague nudges

Before you follow up, check whether the input arrived in the agreed channel. If it has not, ask for the specific missing item and a realistic checkpoint. Choose that Target date in SaathKaam if it helps.

A Reminder is optional and separate. It can prompt you to check the situation; SaathKaam does not send the request to the client or import replies from their messages.

Leave enough context for your next session

Post an update when a partial input arrives. Record the actual outcome when the final file or decision arrives. If a new action belongs to you, change the responsibility or create a separate focused Follow-up.

For design work, distinguish receiving feedback from understanding it. An unclear change request may first need a clarification; only then does making the revision become Your turn.

Keep delivery tools where they belong

Keep design files, invoices, client communication and project schedules in their existing tools. SaathKaam keeps the follow-up context; it is not a file repository, project board or invoice generator.

Start with one item you currently keep in your head. Add more only when having a person, next step and history together would make the next conversation clearer.

Try the model

Get the final logo files

You are building Nisha’s website. She has sent the photographs but not the final logo. “Website project” is too broad to tell you what to ask for.

Conceptual example for Nisha: Get the final logo files; Waiting on them; follow up, record the result, then resolve the specific request.
Conceptual explainer using the synthetic example below—not an app screenshot.
Who
Nisha
Follow-up
Get the final logo files
Whose turn
Waiting on them
Planned next action
Ask for the approved logo files through the existing file-sharing channel.
Target date / Reminder
Agree a checkpoint with Nisha and set that Target date. Add a Reminder independently if useful.
What changes in the Timeline
Post an update when the photographs arrive; keep this request focused on the missing logo. Record the outcome when the correct files arrive.
What Done means
The final logo files needed for the website are available in the agreed external location.

Choose one unfinished interaction.

Think of someone you are waiting for—or a promise you still need to keep. Add that Person and one clear Follow-up. Leave optional details until they are useful.

Try SaathKaam on Web