You have enough information to write the brief. There are meeting notes, a report, a few customer comments, and a previous draft. Yet turning them into a document still feels like a large task.
The challenge is deciding what the reader needs and giving the material a clear order. Research provides a working document inside the Upfyn project, so the draft, sources, and revisions can develop together.
Decide what the document needs to achieve
Start with the reader and the purpose. Is this a proposal for a client, a summary for a manager, or an instruction a colleague will follow?
A useful brief tells the assistant what the reader should understand or decide. It also identifies the material that can support the explanation.
Create a two-page brief for our planning meeting from these customer notes and the product summary. Explain the repeated problems, the supporting evidence, and the decisions still open.
That is more specific than asking to “summarise everything.” It gives the draft an audience and a job.
Bring in the material you already have
Start blank or import an existing document. Research supports Markdown, PDF, DOCX, HTML, and text as starting material.
Before a major rewrite, ask the assistant to identify the main sections and anything it could not read clearly. For scanned PDFs, on-device text extraction can make the material usable. Check important figures and names against the original when the scan is unclear.
Keep source files identifiable so you can return to a passage when a reviewer asks where a point came from.
Build the structure before polishing the sentences
Ask for an outline that matches the reader's needs. A planning brief might begin with the problem, group the evidence, explain the options, and end with open decisions.
Review that order before refining the prose. A beautifully written section still gets in the way if it answers a question the reader does not have.
Once the structure works, draft the sections with source references where appropriate. Ask the assistant to distinguish what the material establishes from what still needs confirmation.
Keep evidence close to the claim
A source list at the end can be useful, but a reader also needs to know which source supports which point. Ask for citations beside factual claims drawn from the material.
If the notes disagree, preserve that difference. “Two customers described different expectations” is more useful than smoothing both comments into an unsupported conclusion.
You can review the evidence first, then the writing. Those are different questions: is the point supported, and is it explained clearly?
Revise the passage that needs attention
Research supports in-place editing and selection rewrites. Select the relevant section and describe the change:
Make this paragraph easier for a nontechnical reader. Keep the examples and the source references.
Or:
Shorten this section by removing repeated background. Preserve the decision and deadline.
Focused revisions help you keep the parts that already work. You can also edit directly when the correction is small.
Export for the person who receives it
Choose a supported format suited to the next reader and inspect the exported result. Check headings, tables, links, and any page layout that matters.
Research autosaves the working document in the project, so you can return when new information arrives. Keep a reviewed export when you need a clear milestone, and update the working version through an explicit request.