Improve workflows

Where is work getting stuck between your tools?

Find the handoffs in your business that still depend on copying information, remembering follow-ups or chasing people, and get one next action for each gap.

For: Owners and managers who already run two or more software tools and still chase work by hand.

Format: Interactive assessment + printable action sheet
Published: September 9, 2026
Last checked: September 9, 2026
Written by: Dryvn AI editorial
Edited by: Dryvn AI editorial
Reviewed by: Not yet reviewed by a named person
Read as: Editorial (Dryvn's practical method)

Why work goes missing between tools, not inside them

Most businesses that come to us already own decent software. A calendar, a quoting tool, an accounting package, a shared inbox, maybe a CRM. Each one works. The problem is what happens at the edges: a quote is approved in one place and the job has to be created somewhere else, a customer replies by text and the answer has to be typed into a ticket, a crew finishes and somebody has to remember to invoice.

Those edges are handoffs. Every handoff has three parts: something finishes, information moves, and somebody or something picks it up. When any of the three depends on a person's memory or their willingness to re-type, the handoff will eventually fail. Not every time. Just often enough that you cannot fully trust it, which is why you keep checking.

BDC's 2026 research describes execution and digital maturity as the common constraint for Canadian businesses, rather than access to tools [S06]. That matches what we see: the tools are there, the handoffs are not designed.

Three signs a handoff is broken

Copying. Someone reads a value from one screen and types it into another. Every copy is a chance for the detail to drift, and it means the two tools were never told about each other.
Remembering. The next step lives in somebody's head, a text thread or a sticky note. If that person is sick, busy or on site, the next step waits.
Chasing. Work is waiting on a decision, and the person waiting has to go and ask. If you hear "did you ever get back to them?" more than once a week, you have this one.

You do not need to fix every handoff. You need to find the ones that carry money, customer promises or safety, and make those hold. The assessment is a way to look at one piece of work at a time and see which control is missing.

The six controls

These six questions are Dryvn's editorial checklist, built from what we have had to fix in operations work. They are not an industry standard and there is no score. Each one is a control: something that, if present, stops a specific kind of failure.

The six controls and the failure each one prevents
Control	Question it answers	Failure it prevents
Named owner	Who makes sure this gets finished?	Work that belongs to a team belongs to nobody.
Approval authority	Who may decide the price, the date, the refund?	Waiting on decisions; automated steps doing what nobody authorized.
Recorded next step	Where is the next action and its date written?	Follow-ups that depend on memory.
Reliable handoff	Does the receiving side get what it needs without re-typing?	Detail drift, double entry, skipped fields.
Exception route	Where does an item go when it does not fit the normal path?	Silent failure when the customer goes quiet or a part is missing.
Completion evidence	How do we know the outcome happened, not just that a message was sent?	Finding out from the customer that the work never closed.

Why the order matters

When people find a broken handoff, the instinct is to automate it. We would ask you to hold that thought until the first two controls are settled. An automated step still needs an owner when it fails, and it still needs to know what it is allowed to decide. Automating a handoff that nobody owns does not make the failure rarer. It makes it faster and quieter.

Ownership and authority first. Put a name against the work and a name against each decision inside it. This costs nothing and often fixes more than any tool.
Then handoffs and exception routes. Decide which fields move at each handoff and which tool is the source of truth. Define one exception state and who reviews it.
Then completion visibility. Decide what counts as evidence that the work is done and record it. This is what tells you whether the first two fixes worked.

Illustrative example · fictional

A service request across two tools

A fictional plumbing company takes service requests through a shared inbox and schedules work in a calendar app. A tenant emails about a leaking tap. The office manager reads it, checks the calendar, replies with a Thursday slot, and adds the appointment. Nobody records that the tenant has not confirmed. Thursday arrives; the plumber goes; the tenant is at work. The plumber texts the office. The office manager, who is on the phone, forgets to reschedule. Eight days later the property manager calls to ask why the tap is still leaking.

Run the six questions against this one piece of work. Named owner: partly, the office manager owns it while she remembers it. Approval authority: yes, she can offer any open slot. Recorded next step: no, "tenant to confirm" was never written anywhere. Reliable handoff: partly, the calendar entry existed but the tenant's confirmation status did not move with it. Exception route: no, "tenant not home" had no place to go except a text. Completion evidence: no, the appointment being on the calendar was treated as the tap being fixed.

The action sheet for this example would put "record the next step and its date" first among the handoff gaps, because ownership and authority are mostly in place. Before any automation, the fix is a required "next action" and "waiting on" field on every open request, and a Friday review of everything in the waiting state. After that, an automated confirmation request and a reschedule prompt become safe to add, because a person owns the exception.

Run the assessment

Pick one recurring piece of work that moves between people or tools. Answer honestly for that one piece of work. "Partly" is a real answer; so is "Unsure", which gets you a way to find out rather than a guess. Nothing you enter is sent anywhere. When you are done, copy or print the action sheet and take it to whoever owns the work.

What to do with the action sheet

01Take the first gap onlyFix the top item on the sheet this week. Most businesses can settle a named owner and a recorded next step without buying anything.
02Re-run in two weeksSame piece of work, same six questions. If the gap is still there, the fix did not hold. Find out why before moving to the next one.
03Repeat for the next piece of workService requests, estimates, invoices, change orders. The same gaps tend to appear across all of them, which tells you what to design once.
04Then decide what to connect or automateWith owners, authority and exception routes settled, a handoff is safe to automate. The connect existing software checklist walks through that decision.

Worksheet

Printable action sheet (blank)

For working through a piece of work on paper, or with a team, without the interactive version.

Piece of work: One recurring thing that moves between people or tools
Named owner: Yes / Partly / No / Unsure and who
Approval authority: Which decisions, who may make them, any limit
Recorded next step: Where the next action and date are written
Reliable handoff: Which fields move, from which tool, to which tool
Exception route: The waiting state, who reviews it, on what day
Completion evidence: What proves the outcome happened
First action, owner and date: One fix, one name, one date

Questions people ask

Why do I still copy information between business apps?: Because the two apps were never told about each other, and the copy is the handoff. It keeps working because a person is willing to do it. The fix is to decide which app is the source of truth for each field, then either connect them or stop keeping the field in both places.
Isn't this just a process problem, not a software problem?: Yes, mostly. That is the point. Software makes a designed process faster and an undesigned one messier. Settle the six controls on paper, then let software carry them.
Can the assessment tell me what to automate?: It tells you what not to automate yet. Once the gaps are closed for a piece of work, the what to automate first guide helps you pick a bounded experiment.
Do you store my answers?: No. The assessment runs in your browser. The optional work name only appears on your printed or copied sheet. We record that an assessment was completed and how many gaps it found, nothing else.

Connect the software you already use: a handoff checklistPlan a connection between two tools you already run so that records move once, in the right direction, with an owner, a failure route and a way to check it worked.
What should I automate first in a small business?Compare recurring work on six practical measures, sort each task into the right lane, and pick one bounded experiment with a baseline.
Customer requests: track the work until it is actually resolvedRun every customer request through the same nine stages, so nothing is marked done until the customer's problem is gone and you can show it.
What should AI be allowed to do without asking?Decide, action by action, what an AI assistant or automation may do on its own, what it may do inside an approved scope, and what always waits for a person.
BlogWhat’s Your Differentiator? The Question That Made Me Rethink DryvnI am not trying to build another dashboard that gives a business owner more information to monitor. I am building Dryvn toward a harder outcome: reducing the daily effort of coordinating the business, including the effort of operating the software itself.
BlogShould You Hire an Office Manager or Use AI? A Decision Guide for Trades BusinessesHire a person when the business needs judgment, relationships, ownership and capacity across unpredictable work. Use software or AI when the work is repeatable, the record is clear and the result can be checked. If the process is not defined, fix that before doing either.

Sources

Dates are when each source was last checked by the editor. Sources support specific claims; they are not endorsements.

S06Canada's next phase of growth to be driven by AI and digital technologies · BDC · checked September 9, 2026Used for the point that execution and digital maturity, not tool count, are the common constraint. Not used for any revenue or savings figure.
S10How to complete a digital transformation in the age of AI · BDC · checked September 9, 2026Supports starting from proven core software and fixing the process before adding tools.
S15Dryvn Ops: what the operating layer between tools does · Dryvn AI · checked September 9, 2026Dryvn's public description of the gap between tools. Positioning, not evidence of a customer result.

R01 · Published September 9, 2026 · Next scheduled review December 9, 2026 · Teaches process management; not legal, warranty, safety or engineering advice. Examples are fictional unless stated. Part of the Dryvn resource library (17 resources).