1
Work on one section, not the whole document
Forty pages rarely need forty pages of work. One part needs a specialist. Another needs sign-off from someone who will not read the rest. A third is already fine as it stands. Editing it as one file means every change risks the parts nobody asked you to touch, and it is hard to notice when that has happened.
A section here is more than a heading. It is the thing everything else attaches to: the reference material for that part of the document, the people allowed to see or change it, the notes still to be addressed, and the suggestions waiting on a decision. Sections sit inside the document without depending on it.
Several people can work in different sections at once without colliding. A change made in one place stays in that place, and you can see what happened to a section without reading the whole document to find out.
2
Give a section only the context it needs
The material behind a document is rarely one pile. A funding call’s eligibility rules matter to one section. A safety policy matters to another. Hand someone all of it and they read around the problem. Hand them none of it and they invent. This gets worse when the work is done by an agent, which will use whatever it is given.
Context attaches at three levels: to your organisation, to a document, and to a single section. A section holds its own uploads, its own links and its own notes. Reusable topics, such as your company or a product you make, are set up once and switched on for the documents where they apply.
Whoever works on a section, person or agent, sees the material for that section and not the rest. Narrower context means drafts that address the actual requirement, and you stop re-explaining the background every time the work changes hands.
3
Turn the requirements into a list you tick off
Requirements for these documents arrive scattered. A must-cover clause in the funding call. A point your director asked for in a meeting. A paper someone insists you cite. They end up in email, in comments and in your head, and the only way to check they have all been addressed is to read the finished document and hope you remember.
Notes attach to the section they apply to, and every note is something to be done rather than a remark. “Must cover the data protection policy.” “Make the point about regional inequality.” You tick a note off once the draft addresses it.
The section shows you what is left. At submission you are checking a list with nothing outstanding rather than re-reading the whole submission for omissions, and anyone picking up a section inherits its requirements along with it.
4
Share a section without sharing the document
You need one paragraph from a specialist who has no interest in the rest of it, and often no business seeing it. The usual choices are both bad. Share the document and they have all of it. Copy the section into an email and you have taken on the job of merging their reply back in by hand.
Access is granted a section at a time. You add someone to a section’s share list and they get a link to that section. They enter their email address, receive a one-time code, and work on the part you gave them. That is the whole access model.
Getting a specialist’s contribution costs one link. Commercially sensitive and personal material stays in the sections it belongs to, which matters when the finished document is going to a funder or an auditor.
5
Nothing changes until you accept it
A document with several contributors drifts. Someone rewrites a sentence that was worded carefully for a reason. An assistant tidies a paragraph and quietly changes what it claims. By the time anyone notices, it is hard to reconstruct what the original said or why it was changed.
You are the only person who edits directly. Everyone else, human or agent, submits a suggestion, and human contributors give a reason for each sentence they change. You accept or reject. Rejected suggestions move to a list instead of disappearing. Where two suggestions touch the same text they are shown together, with both versions and a merged version, so you make one decision instead of untangling a conflict.
The document only ever says what you agreed it should say. You can see who proposed each change and why, which is the record you need when a claim is queried months after submission.
6
Fits the documents you already have
The material you need is already written down somewhere, and the finished document has to end up somewhere specific. Neither place is likely to be a tool you have just adopted. Anything that asks your organisation to move its writing in order to work on one document is not worth the trouble.
Material comes in from where it already lives: Confluence, Google Docs, Notion, uploaded files, or a URL that is read when you add it. When the document is finished it goes out as a PDF or a DOCX, or straight back into Confluence, Notion or Google Drive.
Section Draft is where the document is worked on, not somewhere it has to live. Your existing pages stay where they are and stay useful, and the finished version arrives in the format whoever asked for it expects.
Built for grant applications, ISO documentation, SOPs and R&D tax credit submissions.