Built with the people who use it.

Suggested by Beatriz G. and Isabella H.

The very first feature Clareo had. Before it, tracking post status was done on paper, and with 30 clients that turned into chaos. A centralized system fixed that from day one.

Suggested by Beatriz G.

Shoot dates, meetings, vacations, all scattered across different places. It became a single source, the same calendar everyone can check.

Suggested by Beatriz G.

Centralized vacation requests, reflecting straight into the Team Calendar. Everyone knows who'll be off before they even need to ask.

Suggested by Caroline A.

Born from actual use: bold, italics and text color make written instructions clearer for whoever executes the task.

Suggested by Isabella H.

Born from a very specific problem: everyone rushing out on Friday, forgetting a task was still running, and on Monday a task would show up with 77 hours logged, polluting the whole metric. That doesn't happen anymore.

Suggested by João V.

For when the user switches tasks in real life but forgets to switch in the system. After a while, Clareo asks if they're still on that same task.

Suggested by Beatriz G.

Create a campaign for a specific period, build the items inside it, and each item automatically becomes a task. Complete the task and the campaign marks it done on its own. Uncheck it in the campaign and the task goes back to open. Two-way sync, no manual rework.

Suggested by Julyane A.

Tasks chained by stage: the next one only unlocks once the previous is completed. Guaranteed sequence, without relying on anyone remembering the order.

Suggested by Gabriella D.

Before, whoever created the task would send references, PDFs and media separately over WhatsApp, and something always got lost. Centralized attachments fixed that: everything stays with the task, nothing gets lost along the way.