Free Eisenhower Matrix Template, With Examples
Start with your free template
An editable AFFiNE page or a one-page printable PDF.
An Eisenhower matrix template is a four-quadrant grid for sorting tasks by urgency and importance. Use it to decide what to do, schedule, delegate, or eliminate—then give each task an owner and a next action.
Use the AFFiNE template · Download the printable PDF · Go to the blank matrix · See the worked example
The PDF is a one-page A4 worksheet you can print and complete by hand. The tables below can be copied into a document or spreadsheet. Prefer a visual workspace? Open the Eisenhower matrix template in AFFiNE to keep the blank grid, task register, and review checklist together.
Eisenhower matrix template you can copy
Start by writing one goal and a planning horizon. For example: “Prepare a reliable product launch; review work for the coming week.” This gives “important” a meaning beyond whatever feels most pressing.
| Urgent | Not urgent | |
|---|---|---|
| Important | Q1: Do. Task: ____. Owner: ____. Act by: ____. | Q2: Schedule. Task: ____. Owner: ____. Reserve time: ____. |
| Not important to the stated goal or responsibility | Q3: Delegate, batch, or renegotiate. Task: ____. Owner: ____. Check-in: ____. | Q4: Eliminate. Task: ____. Drop it, or record why and when to reconsider. |
Use the urgent-important matrix, sometimes called the Eisenhower box, as a decision aid. It is not a calendar or a project schedule.
For tasks where the answer is unclear, keep a short record beside the grid:
| Task | Evidence | Quadrant | Next action |
|---|---|---|---|
| One task, one verb | What happens if it waits? Which goal or commitment does it affect? | Q1–Q4 | Owner, action, and time or check-in |
Add an exact deadline, expected effort, and review note when needed. You do not need to fill out a large register before sorting a simple personal list.
Choose a format
- Paper: download the PDF and print at actual size on A4, or choose “Fit” for another paper size. Leave enough room to write one action per line.
- Excel or Google Sheets: copy the task register into a sheet and add one task per row. Record the quadrant manually. This page does not currently provide a native Excel workbook or a hosted Google Sheets copy.
- AFFiNE: open the linked template and use its grid, task register, and review checklist on one page. The matrix requires your judgment; it does not automatically assign priorities or schedule work.
The four quadrants: criteria and default actions
Ask two separate questions:
- Is it urgent? What meaningful consequence occurs if I wait beyond the relevant time? Include preparation and dependencies, not just the final due date.
- Is it important? Does it advance a named goal or protect a responsibility, relationship, or commitment that matters?
| Quadrant | Test | What to do next |
|---|---|---|
| Q1: Do | Important, and delay creates a time-sensitive consequence | Assign an owner and act by the required time. Escalate a capacity conflict. |
| Q2: Schedule | Important, with enough time to prepare and complete it safely | Reserve time before the latest safe start; protect that time. |
| Q3: Delegate / batch | Time-sensitive, but low value relative to the stated goal or responsibility | Check whether it needs doing. Delegate with agreement, batch, simplify, renegotiate, or decline it. |
| Q4: Eliminate | Neither important nor time-sensitive | Drop it. Keep a review date only if there is a clear reason to reconsider. |
Being easy to delegate does not make a task unimportant. A critical customer fix remains important when another engineer handles it. The quadrant describes priority; assigning the work is a separate decision.
Likewise, “ASAP” is not a deadline. Ask what will happen, to whom, and by when. If the goal is unclear, use a SMART goal template to make it specific before sorting the list.
Eisenhower matrix example: 12 tasks from a fictional product launch
This is an editorial illustration, not a customer case study or a record of AFFiNE’s launch process. The team, dates, and outcomes are fictional.
On Monday, October 5, 2026, a small team plans the coming week for a launch on October 16 and reviews priorities each morning. In this example, a task is urgent when it needs intervention now or before the next review on October 6; being due later in the week does not automatically make it urgent. Importance means protecting the launch, customers, or an explicit business commitment—not whether a task requires a particular person.
The schedule assumes that preparation and rework fit into the reserved blocks. If that assumption changes, the team must reclassify the task.
| Task | Why it belongs here | Next action |
|---|---|---|
| Q1: Fix a checkout crash | Customers are blocked now; resolving it protects revenue and the launch | Marcus investigates today and confirms a recovery plan by 5 pm |
| Q1: Submit the store listing | Review may take a week; preparing and checking the submission must start October 5 to meet the October 7 submission window | Sam starts preparation today, submits by October 7, and checks the submission status |
| Q1: Confirm launch support coverage | Coordination must start October 5 to allow staff notice and resolve gaps before October 8; missing coverage puts customer response at risk | Priya starts coordination today and confirms owners and backups by October 8 |
| Q2: Write release notes and help content | Needed October 14; a reserved writing block and review buffer remain available | Jordan writes October 8, then routes the draft for review |
| Q2: Test onboarding accessibility | Important for users; the scenario reserves testing October 9 and time for fixes before release | Elena tests on October 9; new blockers trigger a fresh urgency assessment |
| Q2: Prepare the metrics dashboard | Needed before launch; agreed setup and verification time still fit | Priya reserves October 13 and verifies data before October 16 |
| Q2: Prepare an investor update | A real commitment, but the meeting is October 22—not “ASAP” this week | Priya reserves October 19 with time for review |
| Q3: Send an existing logo to an optional community meetup | The organizer wants it tomorrow; there is no customer, contractual, or launch dependency | Sam asks whether Jordan has capacity to send the existing file |
| Q3: Reply to an optional vendor-demo invitation | The RSVP expires tomorrow; the team is not evaluating vendors now | Priya declines in the next admin window |
| Q3: Arrange optional snacks for the retrospective | A booking cutoff exists, but the retrospective can proceed without catering | Jordan handles it if capacity permits; otherwise use a simpler option |
| Q4: Redesign an internal wiki homepage | No current usability problem, deadline, or connection to the launch | Elena removes it from the launch list |
| Q4: Compare three new note-taking apps | No current requirement or problem would justify the work | Marcus drops the task |
The result is 3 tasks to do, 4 to schedule, 3 low-priority requests to handle deliberately, and 2 to eliminate. This is a demonstration of the classification rules, not a measured productivity improvement.
The useful counterexample: an “ASAP” request moves out of Q1
Priya initially treated the investor deck as Q1 because the founder asked for it immediately. Checking the actual meeting date showed that the work was important but did not need to interrupt launch preparation. She moved it to Q2 and reserved time for it.
The reverse can also happen. If testing reveals a checkout blocker before release, an item previously in Q2 may become Q1. Keep the reason for a change beside the task so the next reviewer can understand it.
How to use an Eisenhower matrix in five steps
1. Capture every open task in one place
Collect open actions from notes, messages, and your task list. Describe each with a verb and an outcome. Split large projects into actions that can be classified meaningfully.
2. Define what urgent and important mean this week
Choose the responsibility or goal you are evaluating, then decide whether this is a daily or weekly review. Urgent does not always mean “within 24 hours” or “within seven days.” Use the interval that fits the consequences and lead time of the work.
3. Classify each task and record the evidence
For each task, record why waiting matters and why the outcome matters. Check preparation time, external approvals, and dependencies. A useful planning estimate is:
Latest safe start = deadline − expected work time − review or rework buffer.
This is a scheduling aid, not a guarantee. Use working calendars and dependencies when calculating the actual date. Starting tomorrow can be urgent even if the final deadline is next week.
4. Assign one next action per quadrant
Assign responsibility to Q1 work, reserve a slot for Q2, agree the owner and handoff for Q3, and remove Q4 work. Use a weekly planner for time blocks; the matrix itself does not allocate hours.
Do not give every Q3 task to the same colleague without checking their workload. A delegation is complete only when someone accepts the work and understands the outcome and timing.
5. Review weekly and revise the criteria
Review at an interval that fits the work, and revisit the grid when a deadline, dependency, or goal changes. Check:
- Which important tasks were finished, and which were blocked?
- Did planned Q2 work keep its reserved time?
- Were delegated tasks accepted and completed or followed up?
- Which recurring emergencies could be prevented earlier?
- Which requests can be dropped instead of carried into another week?
There is no universal healthy percentage for each quadrant. Judge whether the mix fits your role and whether important work is getting enough time.
What to do when the matrix feels wrong
Everything looks urgent. Check the actual consequences and latest safe start dates. If the demands are all real, the problem is capacity: renegotiate scope, sequencing, ownership, or deadlines. Changing labels will not create more hours.
You have nobody to delegate to. Q3 still gives you a choice. Batch necessary admin, use a simpler response, renegotiate the request, or decline it where appropriate. Do not neglect an actual obligation simply because it does not advance your main project.
Two important tasks conflict. Compare consequences, dependencies, effort, and available capacity. Escalate incompatible commitments. The matrix does not resolve every trade-off.
Rest keeps ending up in Q4. Recovery, health, and relationships can be important goals in their own right. Do not define “important” solely as paid output. Classify the specific activity in context rather than treating all leisure as waste.
A task is both easy to delegate and critical. Keep its Q1 or Q2 priority and assign an appropriate owner. Delegation is possible in any quadrant.
Eisenhower matrix vs. a decision matrix, Kanban, and a weekly plan
These tools answer different questions:
| Tool | Main question | Typical output |
|---|---|---|
| Eisenhower matrix | What treatment does each task need next? | Do, schedule, delegate/batch, or eliminate |
| Weighted decision matrix | Which option best fits several criteria? | Comparative scores with stated assumptions |
| Kanban board | Where is work in the process? | Visible status and workflow |
| Weekly plan | When can the chosen work happen? | Time blocks that fit available capacity |
Use a weighted decision matrix to compare vendors or options, then sort the resulting actions here. For status tracking, see how Kanban boards and Eisenhower grids work together. If you first need to identify strategic actions, start with SWOT analysis templates and examples.
The American Society for Quality describes the weighted comparison function of decision matrices. The Kanban Guide explains Kanban’s focus on managing and improving flow. Neither tool makes an urgent-important grid a complete project plan.
Keep the matrix and review notes together in AFFiNE
Open the Eisenhower matrix template for a reusable page with a blank grid, task register, and review checklist. Keep each task’s reason, owner, and next action with its card or in an adjacent register.
AFFiNE’s database documentation describes Table and Kanban views. Its template documentation explains how to save reusable page structures. A practical setup is a blank matrix, a short task register, and the review checklist on the same page.
This is a manual workflow. The template does not automatically judge importance, account for dependencies, create reminders, or book time on your calendar. Use your existing calendar or project system for those steps.
Frequently asked questions
Is this Eisenhower matrix template free to download?
Yes. The linked one-page PDF is free to download and print. It is a blank worksheet for handwriting, not an interactive fillable PDF. You can also copy the matrix and task-register tables from this page.
Can I use the template in Excel or Google Sheets?
Yes. Copy the task-register table into a sheet, add one task per row, and enter each task’s quadrant and next action. This page does not currently offer a native Excel workbook, a hosted Google Sheets template, or automatic spreadsheet classification.
How do I distinguish urgent from important?
Urgency concerns the consequences of delay. Importance concerns a goal or responsibility that matters. Record both separately. A task can be important without needing action now, or time-sensitive without deserving a large share of your attention.
What if I cannot delegate Q3 tasks?
Check whether the request needs to be done. For necessary low-value work, batch it, simplify the response, or renegotiate the deadline. Decline optional work where appropriate. A real obligation may need a different importance rating even if it is routine.
Can an important task be delegated?
Yes. Priority and ownership are separate decisions. An urgent customer fix can remain Q1 while being assigned to another qualified person. Do not label it unimportant merely because someone else can do it.
Did Dwight Eisenhower invent the four-quadrant matrix?
The often-cited 1954 speech discusses urgent and important problems but does not present a four-quadrant grid. Eisenhower attributed the saying to a former college president. The later time-management matrix is associated with Stephen R. Covey’s work, including The 7 Habits of Highly Effective People.
Is an Eisenhower matrix the same as a decision matrix?
An Eisenhower matrix sorts tasks by urgency and importance. A weighted decision matrix compares options across several criteria. Use the first to organize actions and the second when choosing among alternatives.
Sources and editorial method
- Eisenhower’s August 19, 1954 address, The American Presidency Project: primary source for the historical quotation and its attribution.
- The 7 Habits of Highly Effective People, Simon & Schuster: publisher’s record for Covey’s book and Habit 3.
- ASQ: Decision matrix and The Kanban Guide: references for the comparison above.
- AFFiNE documentation linked above: references for the described product capabilities.
Written by the AFFiNE Editorial Team. The worked example is fictional and intended to make each classification inspectable. The workflow suggestions are editorial guidance, not results from a customer study or a productivity experiment. AFFiNE publishes this guide and develops the workspace linked in it. See our editorial policy.
