Write a request like an email, track it like a folder

You write plain text, and links become clickable. To ask for something, you add a request from the "Add" button or by typing / in the message. The types are grouped by intent:

• Ask: an answer, documents, a choice, steps to tick off, an approval, information to fill in
• Plan: an appointment, a dated milestone, a place

One post can hold up to ten of them, of different types. Each lives its own life: its status changes when it is completed, and its reminders stop at that moment.

The message can also be spoken: a voice note attaches to the post, from one second up to fifteen minutes, and the recorder stops by itself at the limit. In the text, @ suggests the people on the folder to mention (an internal note suggests the team only), and the person mentioned joins the publication’s people.

Each request is set as you write:

• The recipient: you name a person, or leave the request to the other side. One person is enough to complete it, except for a sign-off, which each person gives for themselves.
• The deadline: optional, it triggers the automatic reminders (two days before the due date, on the day, the day after, then seven days later).
• Who reads it: everyone, or only the people you choose. An internal note stays invisible to clients, and a confidential post is read only by the team and the participants it names.

If you have already typed your list into the message, "Turn the message into…" converts it into a request: the first line becomes the title, the dashed lines become the documents or the options. The draft saves itself, folder by folder, and you find it again on another device: a request started at the office is finished on the phone. Recurring messages are kept as templates.

For a post you want to send later, "Plan for later" (the "Publish" menu, team only) puts what the composer holds into the folder's list of planned posts. It belongs to that folder alone, with no template behind it, and is prepared in one click when the time comes. Like a template, it keeps neither the people named or mentioned, nor a file added by hand.

They open their link, enter the code sent by email on a new device, and land on what is expected of them, with no account to create and no app to install. They work through each request in its own card: filing documents, picking a slot, approving, replying. They can also send you requests of their own.

Building and renovation. One message about the revised quote: the PDF attached, a sign-off addressed to both homeowners, a document request with a deadline, an appointment proposed on site. The client sees four distinct things waiting, and you see which one is missing.

Law and accounting firms. The document request names each document expected, and an internal note tells a colleague that the client has already ruled out an option, without the client reading it. For a decision to make, the choice replaces the question lost in the middle of a paragraph.

The text stays plain, with no rich formatting. Voice notes can be switched off for the whole workspace or for one folder, and their length runs from one second to fifteen minutes. "Plan for later" does not schedule a sending time: the post waits for the team to prepare and publish it. A post holds at most ten requests. After ten minutes, or as soon as someone has answered, a request can no longer be edited: you cancel it (the trace stays) or replace it with a new one. A sign-off is a simple, dated, named approval, with no value as a qualified electronic signature.

• The folder thread, where these requests appear and get answered
• Document requests, for collecting documents
• Folder templates, so you do not rewrite the usual requests