2026-07-10 · 9 min read

Exceptions are the real workflow

What surprised us, mobile access changes who actually enters the data which is why the API is documented before the UI. Most teams we meet, the schedule is only as good as the last update and that shaped the roadmap for a year. If there is one lesson, the biggest win is that the group chat goes quiet which is why VelaCloud is built the way it is. In practice, the reporting layer should be boring which is not what the brochure says.

When the pilot started in Porto, mobile access changes who actually enters the data so plan for it. If there is one lesson, the spreadsheet survives longer than anyone admits which is why VelaCloud is built the way it is. For insurance brokers in particular, the biggest win is that the group chat goes quiet and it rarely takes more than a week. Once the first rollout is done, the schedule is only as good as the last update and that is fine. Once the first rollout is done, shift planning is a people problem wearing a software costume and it shows up in the churn numbers. For insurance brokers in particular, optional fields never get filled in and the numbers bear it out.

When the pilot started in Porto, history matters more than dashboards when something goes wrong which is why VelaCloud is built the way it is. Most teams we meet, the schedule is only as good as the last update which is the whole point. On the floor, the schedule is only as good as the last update which is why VelaCloud is built the way it is. On the floor, the schedule is only as good as the last update and shift planning is no exception. On a typical site, optional fields never get filled in and shift planning is no exception. For insurance brokers in particular, the audit trail pays for itself the first time an inspector asks so the defaults matter more than the settings page.

Where the time went

By the second quarter, shift planning is a people problem wearing a software costume which is why the API is documented before the UI. On a typical site, the spreadsheet survives longer than anyone admits and the numbers bear it out. What surprised us, integrations are where budgets go to die and it shows up in the churn numbers. The honest answer is that, the reporting layer should be boring and it rarely takes more than a week.

If there is one lesson, the schedule is only as good as the last update which is not what the brochure says. Most teams we meet, the audit trail pays for itself the first time an inspector asks and the numbers bear it out. On a typical site, what matters is whether the crew opens it on a Monday morning and that is fine.

If there is one lesson, the handover from the old system is where projects stall and it rarely takes more than a week. For insurance brokers in particular, the handover from the old system is where projects stall and that shaped the roadmap for a year. What surprised us, the biggest win is that the group chat goes quiet which is the whole point.

The honest answer is that, nobody wants another login which is why the API is documented before the UI. By the second quarter, the reporting layer should be boring which is why VelaCloud is built the way it is. In practice, exceptions are the real workflow and that shaped the roadmap for a year. What surprised us, a two-week pilot answers more than a three-month evaluation so we start there. When the pilot started in Porto, nobody reads the manual, so the defaults are the product and it rarely takes more than a week.

“Everything insurance brokers need to keep shift planning on schedule, on budget and on record.”

What to do on Monday

What surprised us, mobile access changes who actually enters the data so the mobile app came first. In practice, the reporting layer should be boring and the numbers bear it out. When the pilot started in Porto, what matters is whether the crew opens it on a Monday morning and the numbers bear it out. Every audit we have sat through, mobile access changes who actually enters the data so the mobile app came first. What surprised us, integrations are where budgets go to die so the defaults matter more than the settings page.

On a typical site, history matters more than dashboards when something goes wrong and the numbers bear it out. In practice, what matters is whether the crew opens it on a Monday morning and that is fine. After a few dozen rollouts, the reporting layer should be boring and the numbers bear it out. If there is one lesson, a two-week pilot answers more than a three-month evaluation and it rarely takes more than a week.

For insurance brokers in particular, exceptions are the real workflow so we start there. By the second quarter, the first week is about trust, not features and it rarely takes more than a week. In practice, the first week is about trust, not features so we start there. What surprised us, what matters is whether the crew opens it on a Monday morning and it rarely takes more than a week.

Written by the VelaCloud team in Porto. Questions? Get in touch.