Three formats cover nearly every sales report title: formal for archives and management, descriptive for busy readers who need the angle up front, and punchy for team channels and standups. The SalesScript generator produces all three. Here is when each fits — and when it backfires.
Formal
Pattern: [Report Type] — [Period], with an audience tag where needed. Example: "Quarterly Sales Report — Q3 2026, Management Review". This is the default style in the generator and the right choice for anything archived, shared with management, or presented to executives. It is unambiguous, sortable and professional — the title equivalent of a pressed shirt. Formal titles age well: "Weekly Sales Report — Week Ending Oct 16, 2026" means exactly the same thing when opened in 2028. One caution: formal titles can feel stiff in a team channel. That is a feature, not a bug — stiffness is what makes them trustworthy in the archive.
Descriptive
Pattern: [period] [report type] — [angle]. Example: "October 2026 pipeline report — deal health and stalls". Use this for internal summaries and email subject lines where the reader benefits from knowing the report's angle before opening. The angle should name the question the report answers: stalls, quota attainment, top sellers, coverage. A descriptive title that promises an angle the report never delivers is worse than a plain one — match the title to the contents. Descriptive titles also make excellent email subject lines: the recipient triages the inbox without opening the attachment, which is exactly what a busy manager wants from a weekly cadence.
Punchy
Pattern: [Hook] — [topic] ([period]). Example: "Sales Pulse — Weekly Recap (Oct 16)". Punchy titles work in team channels, standup docs and Slack threads where energy matters and everyone already knows the context. They backfire the moment they leave that context: a punchy title in the archive ("The Numbers — Q3") is unsearchable six months later, and a punchy title in a board deck reads as unserious. Rule of thumb: punchy for the team, formal for everyone else.
Choosing between them
- Archived, shared upward, or presented? Use formal. The title must stand alone.
- Internal summary for busy readers? Use descriptive. Put the angle in the title.
- Team channel or standup? Punchy is fine — context does the rest.
- Unsure? Default to formal. It is never wrong.
One more rule: never mix registers in one series
A single report can be any style; a series must be one style. The weekly series that alternates "Sales Pulse", "weekly numbers" and "Week Update" trains nobody to recognize it, and it breaks every saved search and email filter built on the old titles. Pick the register when you start the series — punchy for the team standup series, formal for the management series — and let the generator on the homepage keep producing matching titles every cycle.
Keep the chosen format consistent across the cadence: a weekly "Sales Pulse" should not alternate with "weekly sales numbers" and "Week Update". Consistency is what makes a year of reports searchable. And match the period vocabulary to the cadence: week-ending dates for weeklies, month names for monthlies, quarter labels for quarterlies. Mixing them ("October Weekly Report") confuses the sorting. Browse examples by report type or read the full title guide.