← Resources
Business Operations DelegationProcess DesignOffshore Support

The Processes Owners Hold Back Until They Are Settled

About two in five owners we map with keep a process out of a remote hire's role because the business hasn't settled how it works. Which ones, and why.

2 October 2026

Minimalist hand-drawn spirit level with a thin amber bubble at its centre, representing a process that has settled before it is handed over.

When we map the work for a new remote hire, some processes stay out of the role on purpose. Over the past nine months, about two in five owners held at least one process back because the business had not settled how it worked yet, or was about to change it.

The processes held back included a finance routine with no fixed method, a settlements process being rebuilt, invoicing waiting on a new software connection, an automation waiting on a stable manual process, and pricing that existed only in the owner’s head.

A process can be handed to someone once it has been decided. Until then there is no fixed method to pass on, and a new hire brought into it becomes one more person working out how it is meant to go.

What owners held back, and why

In every case below, the owner gave the process being unsettled as the reason for leaving it out.

  • The finance routine and invoicing. One business left both out of the role entirely, because it had no set way of doing either yet.
  • Settlements. The owners described their settlements process as convoluted. It was being rebuilt, so it was deliberately left unmapped.
  • Invoicing during a software change. The business was moving to a field app that connects to its accounting software. Nobody wrote invoicing procedures until that connection was live.
  • Pricing. Prices varied by customer, a seasonal discount applied, and no written price list existed. Invoicing could not move across while the prices lived with the owner.
  • New starter setup. Setting up a new starter stayed with the owner, because the rate calculator the setup depended on was incomplete.

Deciding the process comes before handing it over

Documenting a process means writing down how it runs. For the processes above, the business had not chosen how they would run yet. The business with no set way of doing finance or invoicing had no method to record. Mapping the settlements process as it stood would have documented a process the owners were about to replace.

So the first piece of work sits with the owner: choosing the method, setting the prices, finishing the rebuild. Documenting the process and handing it over come after that decision.

If you have already sorted your tasks into what is ready, what needs documenting and what stays with you, these processes need a separate entry on that list: work the business still has to decide.

Holding a process back while it changes

Settlements and invoicing were both partway through a change.

The settlements process was being rebuilt. Instructions written for the old version would describe a process on its way out, and a new hire would have to learn it twice.

Invoicing was waiting on the connection between a new field app and the accounting software. Procedures written before that connection was live would describe a workflow the business was leaving behind. Waiting lets the procedure be written once, for the system the business will use.

Lead handling went the other way. One business mapped it knowing the intake path could change part way through, because it was still choosing which CRM to use.

Holding an automation until the manual process holds

One business had planned an automation that would create a project as soon as a deal was accepted. It was deliberately not built until the manual process was being followed consistently.

An automation repeats the process it is given. While accepted deals are still handled in more than one way, an automation can only follow a single version. Once the manual steps run the same way each time, the automation has a settled process to copy.

Processes waiting on one missing input

Pricing and new starter setup were each waiting on a single missing input.

Where prices vary by customer, with a seasonal discount on top, and no list is written down, each price is the owner’s call. A written price list turns those calls into something an assistant can apply. Until the list exists, every invoice goes through the owner.

New starter setup depended on a rate calculator. While the calculator was incomplete, setting up a new starter waited on the owner.

In both cases the missing piece was specific: a list of prices, a finished calculator.

Four questions before a process goes into the handover

These questions come from the reasons owners gave for holding processes back.

  1. Does the process run the same way each time? If the method changes depending on who does it, there is a decision to make before there is anything to document.
  2. Is any part of it about to change? New software, a rebuild underway, or a connection between systems that is not live yet.
  3. Does it depend on something only you hold? Prices, rates, discount rules or a calculator that exists in part.
  4. If an automation is planned, is the manual version followed consistently?

A process that fails any of these can still sit on the role’s task list, marked as held back, with the decision it is waiting on written next to it.

Settling processes before the handover

When we map a role with an owner before a new hire starts, we note which processes are ready to move and which are waiting on a decision, along with the reason. That gives the owner a list of the decisions that sit with them, separate from the work the specialist can take on from the first weeks.

You can see how that setup works. If you are planning a handover and some of your processes are still being worked out, book a Role Plan call.

Work with HIPPO

Ready to build
your back office?

Book a call with Dusty. We work out the first role to hire, and afterwards you get your Role Plan in writing.

Book a Role Plan call