The business memo has survived every wave of communication technology - fax, email, chat, collaboration platforms - because it does something no other format does quite as well. It carries weight. The same information delivered through a memo versus an email lands differently, not because the content changes but because the format itself signals intent. A memo says: this is the official version, save it, reference it, treat it as record. For policy changes, organizational announcements, formal requests, and internal documentation that needs to outlive its moment of creation, the memo remains the right tool.
This guide provides eight complete business memo templates covering the situations organizations most commonly need to document: policy updates, organizational announcements, information briefings, internal requests, meeting follow-ups, performance notifications, budget communications, and position statements. Each template includes full structure, realistic sample content, and notes on when to use that format. You will also find comparison tables that show how memos differ from other communication channels, expert commentary on the craft decisions that separate strong memos from weak ones, a common mistakes section drawn from patterns observed across corporate communications work, and a review and distribution workflow that improves readership and compliance.
Every template in this guide is carefully curated from formats used by well-run communications teams, executive assistants, and operations leaders across industries. The writing style is opinionated where opinions matter - we insist on clear header fields, we lead with the message rather than the background, and we treat attribution and dates as mandatory. Use these templates as starting points, adapt them to your organization's voice, and treat each memo as a small act of craft. A well-written memo compounds in value every time someone references it.
What a Business Memo Must Accomplish
Before choosing a template, be clear on what the memo needs to do. A well-written memo accomplishes five things:
- It identifies the audience, sender, date, and subject so the essential context is visible within five seconds.
- It states the purpose in the opening paragraph so a skimming reader understands what this is about.
- It provides enough context and detail that a reader who was not in the original discussion can act correctly.
- It makes clear what, if anything, the reader needs to do and by when.
- It creates a durable record that can be referenced later without additional explanation.
A memo that satisfies only some of these fails in predictable ways. If the purpose is buried, readers skim past it. If the action required is unclear, compliance varies. If the tone is wrong for the audience, the message lands poorly regardless of its content. Every template in this guide is built around these five requirements.
Memos exist because some messages need to be read the same way by many people, at different times, without the benefit of follow-up conversation. That constraint is what shapes the format. The header fields exist so busy readers can triage. The opening paragraph exists so skimmers can get the essence. The structured body exists so readers who need depth can find it. Every convention of the memo format serves the reader rather than the writer.
Memo Format Comparison by Channel
The table below compares memos to the other communication channels they compete with. Understanding the differences helps you pick the right vehicle for each message.
| Channel | Permanence | Formality | Audience Scale | Best For |
|---|---|---|---|---|
| Business memo | High | Medium to high | Multiple or broad | Policy, announcements, formal requests |
| Medium | Low to medium | Any | Conversational, time-sensitive, operational | |
| Chat message | Low | Low | Typically small | Immediate questions and coordination |
| Meeting recap | Medium | Medium | Meeting attendees | Documenting decisions and actions |
| Policy document | Very high | High | Broad or targeted | Formal rules with long retention |
| Company-wide announcement | Varies | Medium to high | All employees | Leadership communication, culture |
When the same content could fit multiple channels, ask three questions: how long does this need to last, how formally does it need to land, and who needs to receive exactly the same version. If answers point to long, formal, and many, a memo is usually right.
Universal Memo Structure
Use this template as the starting point for any memo. The header is standardized; the body adapts to the memo type.
MEMORANDUM
TO: [Recipient or recipient group] FROM: [Sender name and title] DATE: [Month DD, YYYY] SUBJECT: [Clear, specific subject line under 10 words]
[Opening paragraph - one to three sentences stating the memo's purpose. Lead with the point, not the background.]
[Body paragraph one - context and details. Organize by topic with subheadings if the memo is long.]
[Body paragraph two - additional context, data, or examples as needed.]
[Closing paragraph - state required actions, next steps, deadlines, or whom to contact with questions.]
[Signature block - name, title, and contact information if relevant]
The MEMORANDUM heading at the top is traditional and signals the format at a glance. For digital distribution, this heading is still useful even though it may feel redundant.
Template 1: Policy Update Memo
Use this format to announce a new or revised policy that employees need to follow.
MEMORANDUM
TO: All Employees FROM: Rebecca Santos, Chief People Officer DATE: April 14, 2025 SUBJECT: Updated Remote Work Policy Effective May 1, 2025
Effective May 1, 2025, we are updating our remote work policy to require all employees to work from a company office or approved alternative location at least three days per week. This memo explains the change, the rationale, and how to adjust your schedule if needed.
What is changing
The current policy requires two days per week in-office. The updated policy raises this to three days per week. The specific days are selected by each team based on collaboration needs, with a default of Tuesday, Wednesday, and Thursday for teams that do not designate alternatives.
Why
Over the past two years, we have observed that teams meeting in-person three or more days per week produce stronger cross-functional collaboration, faster onboarding of new hires, and higher internal survey scores on connection and belonging. Leadership reviewed the data and decided to align company policy with the conditions that produce these outcomes.
What to do
- Confirm your team's selected in-office days with your manager by April 25.
- Adjust any standing external commitments that conflict with the new schedule.
- If the new policy creates a hardship that cannot be resolved through schedule adjustment, contact your HR Business Partner by April 22 to discuss an accommodation.
Approved alternative locations
If your role does not have a designated company office within commuting distance, approved alternative locations include designated coworking partners listed on the People Ops wiki. Contact your HR Business Partner if you need clarification on your eligible location.
We recognize this change represents an adjustment for many employees, and we appreciate your flexibility. Questions can be directed to your HR Business Partner or to peopleops@[company].com.
Template 2: Organizational Announcement Memo
Use this format for reorganizations, leadership changes, or other significant organizational news.
MEMORANDUM
TO: All Employees FROM: Thomas Reed, Chief Executive Officer DATE: April 14, 2025 SUBJECT: Product Organization Restructure Effective May 5
Effective May 5, 2025, the Product organization will restructure into three business-line product teams, replacing the current centralized structure. This memo outlines the new structure, leadership assignments, and implications for ongoing work.
New structure
Product will operate as three aligned teams under dedicated product leadership:
- Core Platform: Led by Jennifer Adeyemi, VP Product (existing role). Covers the core software platform used by all customer segments.
- Enterprise: Led by newly appointed Marcus Delgado, VP Product. Covers enterprise-specific features and expanded security and administration capabilities.
- SMB: Led by newly promoted Priya Natarajan, VP Product. Covers features and experiences tailored for small and mid-market customers.
All three leaders report to Chief Product Officer Sarah Kim, whose role is unchanged.
Rationale
Over the past year, the single Product team has served customer segments with increasingly different needs. Centralizing all product decisions has produced trade-offs that leave each segment partially served. The restructured organization aligns dedicated product leadership with each segment so prioritization reflects the needs of the customers served.
Team assignments
Individual Product Manager and Designer assignments to the three teams have been coordinated with Sarah and the new VPs. Each affected employee will receive direct communication from their new manager by end of day April 18.
Engineering alignment
Engineering alignment to the three product teams is being discussed separately and will be announced no later than April 30.
Questions
Sarah and the three VPs will host town hall sessions during the week of April 21 to answer questions. Calendar invitations will follow tomorrow. Individual questions can also be directed to your current manager or to Sarah.
Template 3: Informational Memo
Use this format to share information that does not require action but that stakeholders need to know.
MEMORANDUM
TO: Engineering Leadership Team FROM: Carla Nunez, Director of Engineering DATE: April 14, 2025 SUBJECT: Q1 Engineering Performance Summary
This memo summarizes engineering performance metrics for Q1 2025 for leadership visibility. No action is required. A detailed data appendix is posted at [wiki link].
Summary
Q1 delivery met plan across all three products. Platform reliability exceeded targets, and incident response performance improved meaningfully year-over-year. Technical debt indicators continued to trend positively as we invested in the stability initiative launched in Q4 2024.
Delivery metrics
- Committed deliverables completed: 47 of 50 (94 percent) vs 85 percent target
- On-time delivery rate: 89 percent vs 80 percent target
- Average cycle time: 4.2 days vs 5.0 day target
Reliability metrics
- Platform uptime: 99.97 percent vs 99.9 percent commitment
- Average time to resolution (P1 incidents): 38 minutes vs 45 minute target
- Total P1 incidents: 4 vs 6 in Q4 2024
Technical debt indicators
- Open critical-severity technical debt items: 12 vs 24 at end of Q4 2024
- Average age of open items: 38 days vs 62 days at end of Q4 2024
What this suggests
The stability investments are paying off. Cycle time improvements are small but consistent across quarters, suggesting compound benefit. The P1 incident reduction is encouraging but the absolute number remains higher than our long-term target of 2 per quarter.
Q2 focus areas
The team's Q2 plan continues investment in platform stability while adding focus on performance regression monitoring, which has been a leading indicator of future incidents. The full Q2 plan is published at [wiki link].
Template 4: Request Memo
Use this format when you need formal approval, resources, or a decision from a specific audience.
MEMORANDUM
TO: Sarah Kim, Chief Product Officer FROM: Omar Haddad, Director of Product Engineering DATE: April 14, 2025 SUBJECT: Request for Approval - Contract Two Senior Engineers for Portal Redesign
I am requesting approval to contract two senior engineers for the Customer Portal Redesign project. This memo summarizes the need, the cost, and the alternatives considered.
Request
Approval to engage two senior engineers from our preferred staffing partner at a combined fully-loaded cost of $78,000 per month, for an engagement period of four months beginning May 5, 2025. Total expected cost: $312,000.
Why
The Portal Redesign schedule depends on delivering the first customer-visible release by August 15. Current team capacity supports 14 of the 18 engineering weeks required for this release. The shortfall creates schedule risk that internal re-prioritization cannot absorb without deferring other Q3 commitments.
Alternatives considered
- Reduce scope of August release by 25 percent. Rejected because the reduced scope would not meet the enterprise segment commitments we communicated at the January kickoff.
- Delay August release by four weeks. Rejected because the customer rollout is dependent on August alignment with the customer advocacy council timing.
- Reassign engineers from the Billing Upgrade project. Rejected because Billing Upgrade has equivalent Q3 commitments that would then slip.
Budget impact
The requested engagement fits within the existing engineering contractor budget line with $48,000 remaining room versus full-year plan. Approval does not require a budget revision.
Requested decision date
Please approve by April 21 so we can confirm engagement timing and onboarding in early May. Happy to discuss alternatives or constraints in our one-on-one this week.
Template 5: Meeting Follow Up Memo
Use this format to document decisions and actions from a significant meeting where formal record is needed.
MEMORANDUM
TO: Q2 Planning Committee FROM: Jonathan Wright, Program Office DATE: April 14, 2025 SUBJECT: Q2 Planning Committee Meeting - Decisions and Action Items
The Q2 Planning Committee met on April 11, 2025 to finalize quarterly priorities and resource allocation. This memo documents the decisions made and the action items assigned. Full meeting notes are posted at [wiki link].
Decisions
Q2 engineering capacity will prioritize the Portal Redesign project (50 percent allocation), the Billing Upgrade (30 percent), and maintenance and customer escalations (20 percent). This allocation supersedes the draft plan circulated April 4.
The Enterprise Analytics initiative is deferred from Q2 to Q3 due to capacity constraints and dependencies on the Portal Redesign. The product team will communicate the revised timeline to enterprise customer advisory council participants by April 25.
The Customer Success team will receive two additional headcount in Q2 to support anticipated renewal pipeline. Recruiting to begin immediately.
Action Items
# Action Owner Due 1 Publish revised Q2 engineering allocation to team wiki Carla April 18 2 Communicate Analytics timeline shift to CAC participants Jennifer April 25 3 Open requisitions for two Customer Success roles Priya April 17 4 Revise Q2 dashboards to reflect new priorities Jonathan April 22 Next committee meeting: May 9, 2025 at 9:00 AM. Agenda will include April performance against Q2 plan and status updates on each major initiative.
Template 6: Performance or Compliance Notification Memo
Use this format for HR-related communications that require formal documentation.
MEMORANDUM
TO: [Employee Name] FROM: [Manager Name], [Title] DATE: April 14, 2025 SUBJECT: Performance Expectations and Support Plan
This memo documents the performance conversation we had on April 11, 2025 and outlines the expectations and support plan we discussed. The memo is not a formal performance improvement plan but provides a record of the conversation and the agreed path forward.
Summary of conversation
We discussed performance against the goals set at the beginning of the review period. Two areas met expectations: customer communication and documentation quality. Two areas fell short of expectations: consistency of meeting commitments and proactive stakeholder updates. We reviewed specific examples in each area.
Expectations for the coming 90 days
- Deliver on committed dates for assigned work with no more than one exception per month, and escalate any risk to a committed date at least three business days before the commitment.
- Provide weekly written status updates for each active project by end of day Friday, including progress, risks, and requested support.
Support available
- Weekly one-on-one with manager continues on current schedule.
- Additional biweekly 15-minute check-ins during the 90-day period to review written updates and discuss priority adjustments.
- Access to the time management and prioritization course in the learning platform, available for enrollment at any time.
Follow up
We will review progress against these expectations in our one-on-one during the week of July 14, 2025. If consistent progress is not observed by that point, we will move to a formal performance improvement plan as described in the Employee Handbook.
Please sign below to acknowledge receipt. Your signature indicates that you have received the memo, not that you agree with every characterization. You are welcome to submit a written response, which will be added to your record.
[Employee Signature] Date
Template 7: Budget or Financial Memo
Use this format for budget communications, funding decisions, or financial policy updates.
MEMORANDUM
TO: Department Heads FROM: Sarah Kim, Chief Financial Officer DATE: April 14, 2025 SUBJECT: Q2 Budget Envelope and Approval Thresholds
This memo confirms the approved Q2 operating budget envelopes by department and summarizes the approval thresholds for Q2 spending. Please distribute to finance owners in your department.
Q2 Budget Envelopes
Department Q2 Envelope YoY Change Key Variances Engineering $6,240,000 +4% Contractor budget expanded Sales $4,180,000 +8% Two new regional hires Marketing $2,740,000 +2% Campaign mix shift Customer Success $1,860,000 +6% Two additional headcount G and A $1,620,000 +3% Audit fee increase Approval thresholds
- Purchases up to $5,000: Department budget owner
- Purchases $5,001 to $25,000: Department head
- Purchases $25,001 to $100,000: Department head plus CFO
- Purchases over $100,000: Department head, CFO, and CEO
Thresholds are unchanged from Q1.
Forecasting cadence
Monthly reforecast submissions are due by the third business day of each month. Templates and submission process are published on the Finance wiki.
Q2 priorities
Departments should prioritize spending that advances Q2 operating plan commitments. Discretionary spending that does not clearly advance plan priorities should be deferred or discussed with Finance.
Questions can be directed to me or to our Financial Planning Analyst, David Ochoa.
Template 8: Position or Recommendation Memo
Use this format to document a formal position or recommendation on a topic requiring deliberation.
MEMORANDUM
TO: Executive Leadership Team FROM: Priya Sharma, Chief Revenue Officer DATE: April 14, 2025 SUBJECT: Recommendation on Enterprise Pricing Model Change
This memo presents a recommendation to transition our enterprise pricing from per-user to a hybrid user-plus-consumption model effective for new contracts beginning Q3 2025. The recommendation is based on six weeks of analysis and customer research.
Recommendation
Adopt the hybrid model for new enterprise contracts beginning July 1, 2025. Existing contracts remain on current pricing through the end of their current terms. Renewals beginning January 1, 2026 transition to the hybrid model.
Rationale
Three observations support the change. First, customer research with 24 enterprise accounts shows resistance to per-user pricing as team sizes grow, with 16 of 24 accounts naming pricing as a factor in considering alternatives at renewal. Second, our current pricing creates misalignment between our revenue and customer value; customers who use the platform heavily with smaller teams feel they are under-paying relative to light-usage accounts with larger teams. Third, comparable enterprise software companies have moved to hybrid pricing in recent years, suggesting the market is ready for this change.
Expected impact
- Year 1 enterprise ARR: flat to low-single-digit growth vs current model
- Year 2 enterprise ARR: 12 to 18 percent higher than current model based on customer usage projections
- Year 1 churn: expected 2 to 3 percentage points lower based on reduced pricing friction
Risks and mitigations
Risk: Some existing customers may seek to renegotiate before their term ends. Mitigation: Grandfather clause in contract language and clear communication plan from Customer Success.
Risk: Sales cycle length may extend during transition period. Mitigation: Sales enablement beginning May 15 and updated pricing tools by June 1.
Requested decision
Please review and provide input by April 28. Final decision by May 5 would allow Sales, Legal, and Finance to prepare for July 1 launch.
Full analysis
Detailed financial modeling, customer research findings, and competitive analysis are in the appendix package at [link].
Writing Clear Memo Openings
The opening paragraph is the most important paragraph in the memo because it determines whether the rest gets read carefully. Several principles produce strong openings.
Lead with the point. The first sentence should tell the reader what the memo is about. Delay the background, the appreciation, and the context until after the point lands.
State the purpose. Use direct language like "This memo informs," "This memo requests," or "This memo documents." The verb choice tells the reader what to do with the memo.
Preview the structure for longer memos. If the memo runs over one page, the opening paragraph should include a one-sentence preview of how the body is organized.
Keep it under 100 words. Openings that run long usually indicate the writer has not yet decided what the memo is really about.
Weak vs Strong Openings
| Weak Opening | Strong Opening |
|---|---|
| As you may know, over the past several months we have been evaluating our current remote work arrangements in light of feedback from employees and managers. | Effective May 1, 2025, we are updating our remote work policy to require three days per week in the office, up from the current two. This memo explains the change and the support available. |
| I wanted to take a moment to share some thoughts about Q1 engineering performance, which I hope you will find useful. | This memo summarizes Q1 engineering performance for leadership visibility. No action is required. |
| The purpose of this memo is to request consideration for some additional engineering resources that we believe we need for the Portal Redesign project. | I am requesting approval to contract two senior engineers for the Portal Redesign project at a total cost of $312,000 for four months. |
Common Mistakes to Avoid
Buried purpose. If the reader has to read the second paragraph to understand what the memo is about, you have buried the purpose. Lead.
Passive voice. "A decision was made" removes the actor. "The Executive Team decided" carries accountability.
Weak subject lines. A subject line that says "Update" does no work. A subject line that names the specific topic and action helps the reader triage.
Ambiguous attribution. FROM lines that say "Management" or "The Team" dilute authority. Name the individual or the specific group.
Missing deadlines. Any memo requesting action without a deadline leaves the action floating. State the deadline explicitly.
Tone mismatch. A conversational tone for a serious HR notification undermines credibility. An overly formal tone for routine operations creates distance. Match the tone to both content and audience.
Too long. Most memos over two pages would be better split or restructured. If you need to go long, use subheadings liberally.
No attribution of decisions. Memos that describe a decision without naming who made it leave ambiguity about authority and accountability.
Failure to specify what happens next. A memo without a closing paragraph stating next steps or a point of contact leaves readers uncertain about what the memo expects from them.
Attachments as crutch. Memos that rely on attachments to carry the message fail readers who do not open attachments. The memo itself should stand on its own.
The best memo writers I know spend 80 percent of their drafting time on the first paragraph and the subject line. They know that readers will skim, and skimmers need to get the point in the first three sentences. Everything else in the memo is context for the readers who need it, but if the first paragraph does not land, none of the other paragraphs matter.
Review and Distribution Workflow
A well-drafted memo ruined by sloppy distribution produces the wrong outcomes. Follow a consistent workflow.
- Draft. Complete a full draft. Sleep on it if possible; significant memos read differently the next day.
- Stakeholder review. Share with co-signers, subject matter experts, and any party whose cooperation the memo requires. Address feedback visibly.
- Legal and HR review where appropriate. Policy memos, performance memos, and anything with legal implications should be reviewed by counsel or HR before distribution.
- Final edit. One last read focused on clarity, tone, and formatting. Verify all names, titles, and dates.
- Distribution. Send through the appropriate channel. For broad memos, a single email with the memo pasted inline reads better than an attachment. For formal memos, a PDF preserves formatting.
- Follow up. For memos requiring action, track responses and follow up with those who have not responded by the deadline.
- Archive. Save the memo in a location that matches its retention requirements. Policy memos belong in policy libraries. Operational memos belong in team wikis. HR memos belong in employee files.
Frequently Asked Questions
What is the difference between a memo and an email? A memo is a structured document with a defined audience and a sense of permanence. An email is a lightweight communication. Use memos when content needs to be findable later, when formality signals importance, or when multiple audiences need the same version.
What is the standard format of a business memo? TO, FROM, DATE, and SUBJECT fields at the top. Opening paragraph stating purpose. Body with context and detail. Closing paragraph with next steps or actions. The four-part header has been standard for decades.
How long should a memo be? Most memos fit on one page, roughly 300 to 500 words. Longer memos up to two pages are appropriate for complex topics. Beyond two pages, consider splitting into a cover memo plus a detailed document.
Who should sign a memo? The FROM line names the sender. For policy memos, the head of the function issuing the policy signs. For operational memos, the team lead signs. Avoid ambiguous attributions like "Management."
Should memos include attachments? The memo itself should stand on its own. Attachments provide depth for readers who need it but should not carry the main message.
How formal should the tone be? Match the audience and content. Formal for legal, financial, or policy matters. Conversational for routine operational matters. Avoid extremes in either direction.
Can memos be delivered by email? Yes. Most modern memos are delivered by email with the memo content pasted inline or attached as a PDF. The format persists even though the delivery channel has changed.
Conclusion and Next Steps
Memos are a craft that rewards attention. The format looks simple because the conventions are old and familiar, but writing memos that actually land requires thinking hard about purpose, audience, and sequence. The eight templates in this guide are starting points; the real work is customizing each one to the specific situation and writing with the reader in mind.
Your next steps are practical. First, identify the next memo you need to write and match it to one of the eight templates above. Second, draft the full memo, leading with the purpose in the first paragraph. Third, read it aloud to catch passive voice, buried leads, and generic language. Fourth, run through the stakeholder review and legal or HR review if the content warrants it. Fifth, distribute through the appropriate channel and archive a copy where the right people will find it later.
The memo that works is the one that respects the reader's time, states the point clearly, and makes the required action unmistakable. Write to those standards and your memos will be read, remembered, and followed.
Frequently Asked Questions
What is the difference between a memo and an email?
A memo is a structured internal document with a consistent format, a defined audience, and a sense of permanence. An email is a lightweight communication channel. The same content can travel through either vehicle, but memos carry more weight because of the format itself. A policy change announced as a memo reads as official; the same content in an email thread can feel casual and get lost. Memos also tend to be saved, reread, and referenced later in a way that most emails are not. Use memos when the content needs to be findable weeks or months later, when multiple audiences need the same version, or when the formality signals importance. Use email when the content is conversational, one-off, or time-sensitive enough that a formatted memo would create unnecessary friction.
What is the standard format of a business memo?
Standard business memos follow a predictable four-part header: TO, FROM, DATE, and SUBJECT. Below the header, the body is typically structured with an opening paragraph that states the memo's purpose in one or two sentences, body paragraphs that provide context and detail, and a closing that states next steps or actions required. The header convention dates to the pre-email era when memos were distributed on paper, but the format persists because it makes the essential information immediately visible. A reader should be able to tell within five seconds who sent the memo, when, to whom, and what it is about. Modern variations sometimes add a PRIORITY or CLASSIFICATION field for sensitive content, but the core four-part header is nearly universal.
How long should a business memo be?
Most effective memos fit on one page, which translates to roughly 300 to 500 words. Shorter memos are common and appropriate for simple announcements; a memo notifying the team of a policy effective date may be three paragraphs. Longer memos up to two pages are appropriate for complex topics like quarterly updates or policy revisions that require context. Memos beyond two pages usually mean you should have produced a different kind of document - a policy document, a report, or a proposal - with a cover memo that announces and summarizes it. Forcing long content into memo format strains the convention and tends to produce documents that are neither concise enough to read nor detailed enough to serve as reference material.
Who should sign a business memo?
In most organizations, memos are sent rather than signed in the traditional sense, but the FROM line carries equivalent weight. The FROM field should name the individual or the role that is responsible for the content. For policy memos, the appropriate signer is usually the head of the function issuing the policy - the Chief Financial Officer for finance policies, the Chief People Officer for HR policies. For operational memos, the team lead or department head usually signs. For announcements from leadership, the CEO or executive sponsor signs. Avoid ambiguous From lines like 'Management' or 'The Team' which dilute accountability. When a memo represents a collective view, name the committee or working group and specify the chair. Clear attribution matters because it tells readers who they can approach with questions and whose authority the memo carries.
Should memos include attachments or appendices?
Memos can reference attachments and appendices, but the memo itself should stand on its own. A reader should be able to understand the purpose, context, and action required from the memo alone, with the attachments serving as supporting detail for those who need depth. This matters because many readers will skim the memo and never open attachments. If the key message depends on the attachment, either summarize the attachment in the memo body or rework the memo to carry the full message. When you do include attachments, name them explicitly - 'see Attachment A: Q2 Budget Detail' - and mention what the reader will find. Avoid generic references like 'attached for your review' that do not tell the reader why the attachment matters.
How formal should the tone of a memo be?
Tone should match both the audience and the content. A memo to all employees announcing a major organizational change should be formal, clear, and unambiguous. A memo to the engineering team about a coding standard update can be conversational while still professional. Generally, use formal tone when the content has legal, financial, or policy implications, when the memo will be retained as official record, or when the audience spans many levels of the organization. Use more conversational tone when the audience is a specific team, when the content is operational rather than strategic, and when the memo serves a practical rather than ceremonial purpose. In all cases, avoid both extremes - academic jargon that obscures meaning and slang that undermines professionalism.