← Back to the Input Firewall · Print with your browser’s Print command. Download the tagged PDF.
Nick Blade · Author as System · October 5, 2026
Input Firewall Worksheet
Classify what arrived. Check responsibility. Choose what it’s allowed to do.
What kind of information is this?
| Class | What you're receiving | What to check |
|---|---|---|
| Feedback | A response to a particular piece of work someone has read or encountered | What did they actually experience, and have they seen enough to judge the issue? |
| Advice | A recommendation about craft, process, publishing, or career | Does it address a problem you have, or a problem the advice assumes you have? |
| Market signal | Verifiable information about readers, sales, formats, platforms, or comparable books | Is the evidence current and relevant to a decision you need to make? |
| Noise | Information with no clear use for this project, decision, or stage | Why is it receiving attention, and does it need to be kept? |
Give the input somewhere to go
| Route | Choose it when | Your next move |
|---|---|---|
| Accept | The input deserves consideration at the current stage | Write the question or action it creates in your own words |
| Defer | It may help, but the project isn't ready for it | Name the date, stage, or condition when you'll review it |
| Test | It sounds plausible, but you don't yet know whether it works | Try one reversible change and decide what you'll look for |
| Reject | It doesn't apply, lacks support, duplicates a resolved issue, or would pull the book away from its purpose | Discard it, keeping a reason only when the working relationship or process needs one |
Accountable review comes first
Agreed editorial feedback, factual or continuity corrections, relevant legal/rights, safety, accessibility, representation, contract/production concerns, and repeated reader problems need a responsible decision. Verify claimed requirements. If the class or authority is unclear, clarify before choosing a final route. Accept means consider, not obey.
This framework organizes decisions. It does not determine truth or replace relevant expertise.
Six inputs to review
Keep confidential manuscript, contractual, legal, health, and identifying details out. Use brief labels. Each row can become a full note below.
| Input / class | Source / status | Review concern | Route or pending review | Next action / trigger / test |
|---|---|---|---|---|
| 1. | ||||
| 2. | ||||
| 3. | ||||
| 4. | ||||
| 5. | ||||
| 6. |
One complete routing note
- Project / stage
- Input / class
- Source / assigned role / requested status
- Accountable review
- Recommended route
- Final route chosen (or pending review)
- Trigger or reversible test / observation
- Author-owned instruction
- Decision note / resolution
Defer: name a date, stage, or condition. Test: keep the original; choose one change and what you’ll observe. Reject: retain a reason only where the process needs one.
nickblade.com/for-authors/input-firewall/ · Version October 5, 2026 · English