Operations / csv-template / v1.0
Follow-Up Sequence Planner
A free CSV and field guide for defining a small, permission-aware follow-up sequence before anyone builds or automates it.Small operators planning a bounded follow-up sequence before choosing or configuring a sending tool. The current license is personal use.
- Status
- Free download
- Access
- Free
- Version
- 1.0
- Support
- Self-serve documentation
- License
- Personal use
- Delivery
- The CSV downloads immediately; the detail page explains its fields, use, and limits.
File manifest / v1.0
Everything included, before download.
- Follow-Up Sequence Planner CSV with clearly fictional examples
- Follow-Up Sequence Planner field and testing guide
- Compatibility
- Excel, Google Sheets, Numbers, Any CSV-compatible spreadsheet app
- Documentation
- The guide defines every field, identifies the fictional rows, explains permission and stop conditions, and provides a manual testing sequence before live use.
- Support
- Self-serve documentation
- License
- Personal use
- Updates
- Material field, status, or documentation changes receive a visible version and dated history entry. Existing downloaded files remain unchanged.
The CSV downloads immediately; the detail page explains its fields, use, and limits. MethodCo does not create an account, start a subscription, or store a copy of your completed file.
Plan the sequence before choosing a tool
A sequence should begin with a real event, a known audience, a useful purpose, and a named owner. The CSV makes those decisions visible before software settings obscure them.
The fictional rows demonstrate an acknowledgement, a human-owned follow-up, and a stop condition. They are examples only and use reserved contact details; they are not MethodCo customers or evidence of results.
Make review and stopping explicit
Every row includes a human-review field and a stop condition. Those fields prevent a timing plan from becoming permission to continue messaging after a reply, withdrawal, error, or other reason to stop.
The guide explains how to replace the examples, test ordinary and exception cases, and keep the planned message honest about timing, scope, and what happens next.
Limitations and responsibility
The files do not send messages, connect to a form, manage consent, or establish that any channel is lawful or appropriate. They are planning documents, not a communication service or a customer database.
A person must approve the audience, permission basis, message, timing, promised action, and stop rule. Apply the legal, contractual, professional, privacy, and accessibility requirements relevant to the real situation.
Method Digital standard
Version, document, and bound every tool; never imply a file is an app, automatic system, or decision-maker.
The detailed public commitments and refusal list live in one place.
Read The Standard