4.4
2,100+ reviews on G2
A report is a structured document that presents what was investigated, what was found and what should happen next, organized under headings so readers can find each part. Use this order unless your reader or format requires another:

What was done, the key findings and what to do.
Background, purpose and how the report is laid out.
Methods, results and analysis, easy to scan.
What the findings mean, and recommendations.
Write it in Evernote. The AI Assistant drafts it from your notes, then you share it for comments.
Write down the question the report must answer and who will read it. A report for a manager deciding on a budget needs different detail than one for a class.
Collect the data, notes and sources, then group them under the headings the reader needs. Keep track of where each fact came from.
Give the background, the purpose of the report and a short overview of its structure. Do not repeat the summary here: they do different jobs.
Put methods, results and analysis under clear headings and subheadings, with tables or charts where numbers are easier to read that way.
Say what the findings mean and what you recommend, each recommendation tied to a finding. Number them so readers can refer to them.
A short summary at the top says what was done, the key findings and the recommendations.
Add the title, author and date, and a table of contents for longer reports. Check numbers and headings against each other before you send it.
Repair wait times at Harbor Bikes, Q3 2026
Average repair wait rose from 5 to 9 days between July and September because phone bookings overfilled Saturdays. We recommend online booking with fixed daily slots.
Customers complained about waits in August. This report looks at 412 repair tickets from July 1 to September 30 to find out why, and what to change.
1. 46% of repairs were booked for Saturdays, against about 9% on an average weekday.
2. 1 in 10 bookings was a double booking.
3. Weekday repair stands were idle about a third of the time.
1. Move to online booking with fixed slots per day (findings 1 and 2).
2. Offer a $10 discount for weekday drop-offs (finding 3).
The business and numbers are made up for this example.
Short reports can merge some of these. Long or technical reports can include all of them.
| Section | What goes in it |
|---|---|
| Title page | Report title, author, organization or course, and date |
| Summary or abstract | What was done, key findings, conclusions and recommendations |
| Table of contents | Main sections and subsections, with page numbers |
| Introduction | Background, purpose and an overview of the structure |
| Body | Methods, results, analysis and discussion, under headings |
| Conclusions and recommendations | What the findings mean and what to do next |
| References and appendices | Sources, and detailed data the body refers to |
Copy it, or save it to your Evernote account and fill it in from your notes.
Title: [what the report is about, with the period or place]
Summary: [what was done] · [key findings] · [recommendations]
Introduction: [background] · [purpose] · [how the report is organized]
Findings: [heading 1] [finding with numbers] · [heading 2] [finding]
Conclusions: [what the findings mean]
Recommendations: 1. [action, tied to a finding] 2. [action]
References and appendices: [sources] · [data tables]
4.4
2,100+ reviews on G2
4.4
8,200+ reviews on Capterra
4.4
73,000+ reviews on App Store
248M
Registered users
Title page, summary or abstract, table of contents, introduction, body (methods, results, analysis, discussion), conclusions and recommendations, then references and appendices.
Write down the question the report must answer and who will read it, gather your information, and sort it under headings. Write the introduction and body first, and the summary last.
The summary condenses the whole report, findings and recommendations included. The introduction gives the background and purpose, and tells the reader how the report is laid out.
Short. A few sentences that cover what was done, the key findings and the recommendations are enough.
A report is organized under headings so readers can jump to what they need, and can end with recommendations. An essay is continuous prose built around an argument.
Yes, where they make lists of findings or recommendations easier to scan. Explanations and reasoning read better in short paragraphs.
Keep the ticket export, the ops sync notes and the customer complaints in one notebook, so the AI Assistant can draft from them.
Ask the AI Assistant what your notes show about repair waits in Q3. It searches your notes and reads the PDFs.
Ask the Assistant to write a short report with findings and a recommendation from those notes. It creates a new note with the draft, which you edit like any other note.
Share the note with the operations director, who reads it, who can edit it. They leave a comment on the exact sentence they want changed, and you see it next to the text.
Keep meeting notes, emails and files in one notebook, let the AI Assistant draft from them, and get comments in the note before you send.
Start for free