Internal Memo

\documentclass[11pt]{article}
\usepackage[T1]{fontenc}
\usepackage[utf8]{inputenc}
\usepackage[letterpaper,margin=1in]{geometry}
\usepackage{xcolor}
\usepackage{array}
\usepackage[hidelinks]{hyperref}

\pagestyle{empty}

\begin{document}

\begin{center}
  {\Huge\bfseries MEMORANDUM}\\[0.3em]
  \rule{\linewidth}{0.8pt}
\end{center}

\vspace{1em}

\noindent
\begin{tabular}{@{}>{\bfseries}p{3.5cm} p{\dimexpr\linewidth-4cm}@{}}
TO:      & All Engineering Staff \\
FROM:    & First Last, VP of Engineering \\
DATE:    & \today \\
SUBJECT: & New Code Review Policy Effective Monday \\
\end{tabular}

\vspace{1em}
\hrule
\vspace{1em}

\section*{1. Summary}
Starting Monday, all pull requests merging to \texttt{main} require at least
two approvals --- one from a senior engineer and one from a teammate on the
code's owning squad. This replaces the previous single-approval rule.

\section*{2. Rationale}
A recent internal review of production incidents found that 63\% could have
been caught by a second reviewer. The new policy balances velocity against
the cost of outages, which have been trending upward over the past quarter.

\section*{3. Timeline}
\begin{itemize}
  \item \textbf{This week:} Team leads inform their squads; update internal docs.
  \item \textbf{Monday:} CI enforces the two-approval rule.
  \item \textbf{End of month:} VP Eng reviews effectiveness and gathers feedback.
\end{itemize}

\section*{4. Exceptions}
Hot-fix merges during an active incident may proceed with a single senior
approval, but must be reviewed within 24 hours.

\section*{5. Action Items}
\begin{itemize}
  \item Team leads: confirm team acknowledgement by Friday 5~PM.
  \item Platform team: update GitHub branch protection rules.
  \item Docs team: update the Engineering Handbook.
\end{itemize}

\vspace{1em}
\noindent Please direct questions to me or to your team lead.

\end{document}