Professional Templates & Tools

Choosing the right minutes format

The three templates below are not interchangeable. Picking the wrong one creates real problems — formal board minutes that read like standup notes will not survive an audit, and standup notes written in board-minute style will not be read.

• Use the formal board template when there is a quorum requirement, recorded votes, or a regulatory or fiduciary record-keeping obligation. The structure is deliberately heavy because what matters is durability and unambiguous attribution.
• Use the standup notes template for recurring internal team meetings where the value is in the running rhythm — what was promised last week, what shipped, what is blocked. Keep entries short; the strength of these notes is comparability across weeks, not depth in any one entry.
• Use the action-items tracker alongside, never instead of, one of the above. Minutes capture the decision; the tracker enforces follow-through. A common failure mode is keeping action items only inside minutes, where they get archived and forgotten by the next meeting.

Before you save anything as a master copy, strip every example name, date, and dollar figure out of the file. Templates that ship with leftover sample data eventually escape into a real meeting packet, where they look careless at best and confidential at worst.

If you are running an actual board or executive committee meeting — not just taking minutes — the formal template is one piece of a much larger logistics puzzle. The full operational playbook for the room itself is in the board meeting logistics guide.

What travel templates do well — and what they don't

A travel itinerary template solves the formatting problem: it gives you a single, scannable document covering flight, hotel, ground transport, meeting times, and emergency contacts. It does not solve the harder problem, which is keeping the document accurate when something changes mid-trip.

Two practices matter more than the template you choose:

• One source of truth. The itinerary lives in one place — a shared file path or a single email thread your executive can find from the airport at 6 AM. Multiple updated versions floating between inbox, phone, and printout is the most common cause of an executive missing a connection.
• An "if something goes wrong" footer. Every itinerary should end with three things: your direct phone number, the airline's status URL or app, and the hotel's main desk. When a flight is cancelled at midnight in a city your executive does not know, this footer is the only part of the document they will read.

The executive travel profile template is the companion document. Build it once per executive and update it twice a year. Frequent flyer numbers, passport expiry dates, dietary restrictions, and seat preferences belong here, not in your head and not in the itinerary itself.

The templates handle the documents. Booking judgement, time-zone handover, and what to do when a flight cancels at midnight are covered separately in the business travel coordination guide.

How to use a communication template without sounding like one

Email and memo templates are useful for the same reason they are dangerous: they remove the work of starting from scratch. A template-driven message that lands in someone's inbox unedited reads as exactly what it is — a fill-in-the-blank that did not warrant a real reply. Three habits keep that from happening.

Edit the opening sentence every time. The standard "I hope this finds you well" opener is the most ignored sentence in business email. A specific opener — referring to the last meeting, a known deadline, or a piece of news — moves the message from automated-feeling to deliberate in one line.

Match the channel to the format. A six-paragraph executive memo is not an email. If the recipient will read it on a phone, the template needs to be cut down before it ships, not lifted wholesale. Memos and letters belong as attached PDFs; emails should fit in a single screen.

Hold a personal phrasebook. The reusable parts of communication — declines, follow-ups, scheduling requests, polite chasers — work best as a private snippet library you maintain in your own voice, drawn from the templates here as a starting point. Over time the snippets stop sounding templated because they sound like you.

Setting up a filing or inventory system that lasts

Office organization templates fail in predictable ways. The inventory tracker becomes outdated within a quarter because nobody owns updates. The filing system collapses because the naming convention turned out to be ambiguous in week three. The vendor database lists three contacts at a company that was acquired last year. None of these failures are template problems — they are operating problems that the template is supposed to make easier, not solve.

Before adopting any of the trackers in this section, decide three things explicitly:

1. Who owns updates. One person is responsible for keeping the file current. If two people share that responsibility, neither of them does it.
2. How often it is reviewed. Inventory and vendor lists need a recurring calendar block — typically monthly or quarterly — or they go stale silently.
3. Where the canonical copy lives. A shared drive path, a SharePoint location, or a wiki page. Local copies on individual machines are the single biggest cause of "which version is the real one" arguments.

The same three questions apply when you build a coverage document for any of these systems — see the desk manual guide for how to record where each tracker lives and who is on the hook for keeping it accurate. If the bigger problem is that the shared drive itself has gone sideways — folders nested too deep, files called "Final Final v3," documents that exist in three places — the fix is in document and file management for administrative assistants.