A spoken daily pass that turns a scattered list into ranked next actions.

Voice Commands for Triage only help after the ranking rules are explicit. Decide how many levels you need, usually four: critical, this week, this month, and later. For each level, write the condition that qualifies an item, in words you would say aloud to a colleague. Critical means a commitment is already broken or a person is blocked. This week means a dated commitment inside seven days. This month means a dated commitment later in the month with no current blocker. Later means everything else. Say the rules once, record them on a card, and keep the card beside the list you rank.
Speak the rule set in your own words before you use it. Read the four conditions aloud and test each one against three items from last week. If an item fits two levels, the rules are not finished. Add a tie-breaker rather than relying on mood: an existing external commitment beats an internal idea, a blocked person beats an unstarted task, and a reversible decision beats an irreversible one. Say the tie-breakers in the same order every time. A rule set you can speak without reading is a rule set you will actually apply on a busy morning when the list is long.
Name who can change a priority and how. In a solo setup, that is you, and the change is a note beside the item. In a small group, one person owns the list each day, and anyone else can request a change with a reason and a new date. Write the request phrasing on the card: move item four to critical because the customer meeting moved to tomorrow. A change with a reason is auditable; a change without one is a preference. Make the override path visible so nobody has to escalate through a side conversation that leaves no trace in the list.
Finish the rule card with an expiry date. Priority rules drift as the work changes, and a card without a review date quietly becomes fiction. Set a monthly review and write it on the card. At the review, test the four conditions against the last two weeks of items and count how often you had to override a rule. Frequent overrides mean the rules no longer match the work. The deliverable for this stage is one page: four levels, their conditions, the tie-breakers, the override phrasing, and a monthly review date. Write the review date on the card itself, not in a calendar note.
Keep one list and give every item the same five fields: the item, the impact if it slips, the date, the owner, and the next action. Speak them in that order so each entry arrives complete. A typical line sounds like: renewal notice, blocks the contract signature, due Thursday, owner Priya, next action send the corrected page today. Say the fields without stopping to format them; the list will be cleaned in a later pass. One list with equal fields is easier to rank than five lists with different shapes. Sorting happens after capture, never during it. Keep the field order fixed across every item.
Capture in batches of five and pause between batches. Speaking ten items without a break produces a blur where a field is missing or an item is repeated. After five, read the batch and mark the gaps. If you notice an item is missing a date, say the correction immediately rather than carrying the gap forward. Keep the capture pass separate from the ranking pass, because mixing them makes you debate priority while the item is still incomplete. The capture pass is about completeness; the ranking pass is about order. Separating them keeps both fast. Two short passes beat one long one.
Rank by speaking moves against a visible list. Say move the renewal notice to the top, move the audit request above the draft, or move item six to later. Confirm each move on screen before the next one. Spoken moves work best when the list is short and the anchors are exact, so rank in small rounds rather than one long monologue. After the first round, read the top five aloud and check that each one still belongs there. If two items keep swapping places, the tie-breaker rule is missing a condition. Fix the rule rather than forcing an order.
Close the list with a backlog rule. Items that will not be touched this month belong in a named later section, not at the bottom of the active list. Speak the move explicitly: move the vendor comparison to later. Keep the active list short enough to read in one minute. A long active list hides the real top three and makes every morning feel like a fresh emergency. The deliverable for this stage is one list, five fields per item, an active section ranked by voice, and a later section that is reviewed monthly rather than daily. Move the backlog items before you close the list.
Every active item needs exactly one owner. Unassigned is not a state; it is a decision that has been postponed. Say the owner name as part of the item line, and say it again when you rank the item, so the assignment survives the move. If two people share the work, name the one who acts next and put the other in the item text. Shared ownership is how items quietly stop moving. When the owner is not in the room, the next action includes telling them, and that message is part of the work rather than an afterthought. Name the owner before you name the work.
Write the next action as a verb, an object, and a date. Send the corrected page today, confirm the meeting time by Wednesday, approve the budget line before Friday. Vague actions like look into it or follow up cannot be checked and will be rewritten tomorrow. Speak the action slowly and read it back. If the action needs more than one sentence, it is probably two items. Splitting it now is cheaper than discovering the split three days later when the first half is done and the second half is invisible. If the verb needs a helper, write the helper as a separate item.
Use a waiting-on state for anything that depends on someone else. Say waiting on finance for the approval, due Thursday, so the list shows both the dependency and the date. A waiting item still needs an owner: the person who checks whether the dependency arrived. Review waiting items at the start of each pass, because they are the ones most likely to go silent. When a dependency clears, say the new next action in the same breath, so the item never returns to the list unowned. Dependencies are normal; invisible dependencies are the problem. Review waiting items before you review active ones.
Confirm assignments where the work already happens. Speak the assignment into the shared message or task field your group already uses, and include the date. Do not create a second tracking place just for triage. When an owner disagrees with an assignment, the disagreement is recorded against the item with a reason and a date, not settled in a side channel. The deliverable for this stage is a list where every active item has one owner, one checkable next action, and a visible state for anything waiting on another person. Speak the assignment once and confirm it on the screen.
Run the pass at the same time every day and keep it to fifteen minutes. Open the list and the message window you already use, then speak the new items into the list before you rank anything. Before the first week of the new routine, download the current version of Voiskey on the computer you use for triage, so a behavior difference reflects your phrasing rather than an old build. Bring items yourself from wherever they arrived; the pass is about deciding, not about collecting. A fixed time and a fixed order turn triage from a reaction into a habit that survives a busy morning.
Begin by reading yesterday's top three aloud. For each one, say whether it moved, stalled, or disappeared. A stalled item gets a smaller next action, not a louder priority. Then rank today's list with a single round of spoken moves and stop. One round is enough when the fields are complete and the rules are explicit. If you find yourself ranking for the third time, the problem is upstream: an owner is missing, a date is wrong, or the item is not really one item. Fix that instead of reshuffling. Then rank only what remains, and write the parked items down.
Protect the pass from becoming a work session. When an item needs real thought, say park this for the afternoon and add a next action that names the first step. The pass decides order and ownership; it does not do the work. Keep a short parking list beside the active list and review it at the same time tomorrow. Without a parking rule, the first complex item swallows the fifteen minutes and the rest of the list goes unranked. The discipline of stopping is what makes a daily pass sustainable on a day with interruptions. A parked item still gets a date.
End the pass with three checks. Does the top item have an owner and a date you can meet? Is anything waiting on someone without a follow-up date? Is the active list short enough to read in a minute? Say the answers aloud and correct one thing before you close the list. Keep a one-line note of what changed, so the weekly audit has something to compare. The deliverable for this stage is a fifteen-minute pass with a visible before and after, a parking list, and a one-line change note. Then close the list and start the day.
Audit the list once a week, not once a quarter. Read every active item and count its age in days. Anything older than two weeks is either not important or not defined well enough to finish. Ask which of the two it is, and act: delete the item or split it into a smaller next action. Also count how often each item was deferred. An item deferred five times is a decision you are avoiding, and the audit should name it rather than letting it drift into a sixth week. Aging counts are the cheapest signal a priority list can produce.
Compare what you planned with what actually moved. Read last week's top three and the change notes, then write one sentence about the gap. If the top items moved but the list still feels behind, the intake is too large rather than the ranking being wrong. If the top items did not move, the ranking rules need a tie-breaker or the owners need a smaller first step. Keep the sentence short and specific, because a vague audit produces a vague adjustment. One accurate sentence per week is enough to steer the next month. Keep the sentence in the audit note.
Look for owner overload before you add more items. Count active items per owner and compare the counts with the dates attached to them. One owner with eight dated items this week is a plan that will fail quietly. Move ownership, change dates, or move items to later, and say the change into the list so it is recorded. A team plan adds shared vocabulary and workflows, which helps when several people rank and assign from the same rules. The audit is the moment to notice that the rules are producing an impossible distribution. Say the change aloud as you make it.
Close the audit with one rule change and one list cleanup. Change a condition, a tie-breaker, or an override phrase, and test it against the last two weeks of items. Then delete finished items, move stale ones to later, and archive the week's note. Before the audit, download Voiskey on the computer you use for the list and confirm the same version is running where the pass happens, so the test reflects the current behavior. The deliverable is a shorter list, one changed rule, and a dated note that explains why. Then start the next week with a clean list.
Choose four levels and write the condition for each in words you would say aloud. Add tie-breakers for items that fit two levels, name who can change a priority, and write the override phrasing. Test the rules on three items from last week, then set a monthly review date on the card.
Give every item five fields: the item, the impact if it slips, the date, the owner, and the next action. Speak them in that order so the entry arrives complete. The next action should be a verb, an object, and a date. Keep one list with equal fields rather than several lists with different shapes.
Start at the same time, speak new items into the list first, then read yesterday's top three aloud. Rank with one round of spoken moves and stop. Park anything that needs real thought. Finish with three checks: the top item has an owner and a date, nothing is waiting without a follow-up, and the active list reads in a minute.
Count the age and deferrals of every active item, then compare last week's top three with what actually moved. Write one sentence about the gap. Count active items per owner before adding more, and close with one rule change and one cleanup. Keep a dated note so next week has something to compare against.

Download Voiskey for Mac and Windows and run your first spoken triage pass tomorrow.
Use it across macOS, Windows, iOS, and Android