Templates & team workflows
All articles
11 October 2026 ยท template.fyi
Choose a template your team will actually use
Choose a team template around a real recurring task. Check the preview, format, ownership and workflow before adopting it.
Meeting notes that separate decisions from discussion
Turn meeting notes into decisions, owners and next actions. Use a short working example and check unresolved questions.
Plan content capacity before filling the calendar
Estimate production hours, review time and dependencies before committing to a content calendar.
A support tracker with clear response definitions
Define first response, resolution, priority and exceptions before measuring customer support performance.
Client intake questions that each have a purpose
Build a short intake questionnaire around goal, current process, constraints and the next decision.
A content brief built around one reader question
Write a useful content brief with a reader question, verified message, sources, boundaries and a clear review owner.
Prioritise customer feedback without losing context
Compare feedback using impact, frequency, effort and evidence. Preserve the original problem before choosing a change.
An event staffing schedule that shows coverage gaps
Map event tasks, time periods, skills and breaks before assigning staff. Make uncovered work visible early.
Test a small business continuity plan with one scenario
Use one realistic disruption to test essential work, responsibilities, fallback steps and a controlled recovery.
Keep a shared template current with an owner and log
Manage a shared template with a clear owner, version, change record and review date. Retire obsolete copies.
An async status update that makes blockers visible
Write a short asynchronous update with completed work, the next step, evidence and a specific request for help.
Write a procedure with a clear exception path
Document a repeatable task with inputs, completion evidence and a safe route when the normal steps do not apply.
Set a decision deadline around the missing input
Plan a team decision with required information, an accountable owner and a clear response when evidence is still missing.
A launch retrospective grounded in real evidence
Review a product launch by separating the original plan, actual events, measured outcomes and one improvement to test next.