Requests: collecting what you need

What requests are for

Projects often wait on the client: a logo file, page copy, access to a website, a decision on dates. A request is a checklist item for something you need from the client. Requests keep those items visible in one list instead of scattered across emails.

Create a request

1. Open the project at /app/projects/<id> and go to the Requests tab.
2. Under Add request, fill in What do you need? with a short title, such as "Brand guidelines PDF" or "Access to the domain registrar".
3. Add Details the client needs to complete it.
4. Optionally set a Due date, then save the request.

The client sees the request in their portal and receives an email about it, depending on their notification settings.

How clients respond

In the portal, a contact can:

• Write a response, for example a short answer or instructions.
• Attach one or more files they have uploaded to the project.
• Select Mark as done or Send response.

When the client responds, the request moves to Submitted so your team can check it. When you are happy with what you received, select Mark done. If something is missing, select Reopen or add a comment. Files the client uploads are saved to the project, marked as coming from the client.

Statuses

• Open. Waiting for the client.
• Submitted. The client has responded or marked it done, and your team can review it.
• Done. Complete.

Reminders for overdue requests

If a request has a due date and is still open after that date, Clientwharf sends the client's contacts a reminder email, depending on their notification settings. This saves you from writing the follow-up yourself. Make sure due dates are realistic, because the reminder goes out automatically.

Request forms

On Agency plans and above, you can add up to 12 form fields to a request. Each field has a label, a type (Short text, Long text or Link (URL)) and can be required. Forms are useful when you need structured answers, such as a list of social media handles or the details for a domain transfer.

The client fills in the form in the portal, and the answers are saved with the request.

Sensitive information

Requests are only visible to your team and the invited contacts of that client. Even so, we recommend that clients share passwords through a password manager rather than typing them into a request. You can use the request to confirm that access was shared.

Tips

• Create your requests at kickoff, so the client sees everything they need to provide in one place.
• Keep one item per request. It is easier for a client to complete "Hero image" and "About page copy" separately.
• Use comments on a request for back-and-forth questions, rather than opening a new email thread.

Related guides

• Projects, files and versions
• Notifications