Drafts — drafted for you

Open this screen in Saral/projects/reports/drafts

Every report format your account produces is drafted overnight from the registers people filled — the design progress, the package month pack, the cost and CAI report, the DRS — and waits here. Open one, fix the sections that need you, and Send: from your own Outlook with the Excel or PDF attached, or saved into the folder it always went to. What the draft could not build is said on it, never guessed. Saral keeps draft against final and learns which sections you rewrite.

You enter

Your edits to the sections — a sentence rewritten, a row added or removed, a figure corrected. The draft itself is never rewritten; your version is the final.
How it goes out: your own Outlook (the usual when the format always went by email), the SharePoint or Aconex export folder it always went to, or in-app only.
A reason when you skip a report, and the recipients when the format has none saved yet.

Saral fills in

The draft: every section built by its rule from the registers, the AI's words only where the format says a section is drafted, guided by your last finals.
What is missing — 'no site diary Tue–Wed' — one line per input the draft could not read, and 'data as of' for how fresh last night's reads were.
The produced file in the person's own Excel template (formulas kept, cells filled) or a PDF, ready to download or attach.
After Send: how much of the draft was kept (acceptance) and which sections were rewritten, so the next draft is closer.

It produces

The sent report — in your Sent Items when it left from your Outlook, or the file in the folder — and the draft recorded as sent with what changed.
Per format, over the weeks: the share of the draft people keep and the sections they rewrite most (the Owner's learning board).

What this page is for

The QS, the design team, the project team and the commercial team come in the morning and the initial report is already written. The registers they and their readers filled during the week — drawings, CAIs, RFIs, orders, the site diary, applications, the CVR, the DRS — are read overnight, and every report format that is due is drafted from them into this list. A person's job is to polish and send, not to assemble.

A report format is data

The account keeps a register of the reports its people produce: the name, who owns it, how often, which registers feed it, its sections, whether it is the person's own Excel template, a PDF or in-app, and where it goes. The formats are seeded from people's actual last outputs on SharePoint, never invented. Adding a report is a row, not a release.

Missing is said, never guessed

A section built from an input nobody filled is not filled with a guess and never a zero that looks like a fact. The draft names the gap at the top and in the file. A draft that cannot be built at all is still a row, state Blocked, with the reason — so the morning never finds a report silently absent.

Send goes from you

A report that always went by email leaves from your own connected Outlook — in your Sent Items, replies back to you — with the produced Excel or PDF attached and the recipients the format always had. If your Outlook is not connected yet, Send takes you to connect it and then sends. A report that always went into a folder is saved into that SharePoint folder (or the Aconex export folder, named the way the export feed expects). In-app only records the send without anything leaving Saral.

The command post

Under the sections is one box. Write what to change the way you would say it to a colleague — a section name, a colon, then the change; several on one line separated by commas, or one per line. Rules read the page numbers, statuses, money, references and verbs with no AI spend; the small model turns the rest into operations as JSON, and every operation is shown as a chip (rule, AI, or strong model) with the words it could not place shown back. Nothing is written by a model: the operations are applied by Saral's own editor, saved as your final and the file is re-rendered. 'Improve', 'tighten', 'rewrite' on a paragraph is the one path to the strong model, and its proposal is a diff you keep or discard. Every command is kept with its result; one you give three times on a report format becomes a default pre-applied on the next draft, named on it, switchable off.

Saral learns

Every send stores the draft against your final. Per format the Owner sees how much people keep and which sections they rewrite most; the next draft carries your last finals as examples for the AI sections. The number that matters is the edit distance, week on week.

Where next

Reports hub (/projects/reports) for every output this module produces; Connections (/projects/connections) for the sign-ins the overnight readers use; the Canvas (/projects/canvas), where 'Drafted for you' sits beside 'Ready for you'.

Next screen: /projects/reports

Not what you needed? Inside Saral, ask Kuku (Alt+K) — if it cannot answer, “Ask a human” sends the question to Saral support with the chat attached.