Do you want feedback or a decision?
‘What do you think?’ is an invitation to discuss. ‘Do you approve this homepage layout for development?’ asks for a decision. Both are useful, but they support different stages of the work. Decide which one you need before writing the request.
If the work is still exploratory, ask open questions about the goals and trade-offs. If you need permission to take the next step, state that step clearly and provide enough context for a decision.
Name the version and scope
An approval is ambiguous when the client cannot tell which artifact it refers to. Link to the relevant design, document, or proof and name the version or date in the item description. Avoid changing the linked artifact silently after a response has been given.
Define the scope of the decision. Approval of a homepage layout does not necessarily approve the copy, image licensing, mobile behavior, or final launch. A short sentence explaining what is included can prevent a much longer disagreement later.
Use a yes/no item with a place for explanation
A yes/no response gives you a clear decision. Add a separate long-text item when you need the reason for a ‘no’ or specific changes. Tell the client whether that explanation is required for the workflow you have agreed.
Be careful with confirmation checkboxes. They work best for statements the client can verify, such as ‘I confirm these are the approved photos for this project.’ Do not hide contractual terms or broad permissions inside a routine completion checkbox.
Identify the person who can decide
Before sending the request, agree who has approval authority on the client’s side. If several stakeholders are involved, ask one coordinator to consolidate the response. Contradictory answers are a people-and-process issue that a progress bar cannot solve.
Rosfish client links do not require an account. They are useful for collecting a response, but they do not establish the identity of the person who clicked. Use an appropriately verified signing or approval system when the decision requires that assurance.
Close the loop after the answer
When a client approves the work, confirm the next agreed step in your project communication. When they decline, turn the comments into a specific revision plan and explain when they will see the next version. Avoid treating silence as approval unless your separate agreement clearly addresses it.
Keep a record of the relevant materials in your project archive. Rosfish is a collection workspace rather than a document-signing platform or immutable approval ledger. Match your recordkeeping process to the importance of the decision and the terms of your engagement.