Sample deliverable · 9:00 a.m.

This is what an estate review actually gives you.

This is a full sample of the report you get from a RautingTech estate review. The company, people and numbers are fictional. The format, the level of detail and the way findings are ranked are exactly what you'd receive.

Get one for your estate

Estate review · Sample

Northwind Field Services (fictional)

Environments
Development, Test, Production
Scope
Cloud flows, solutions, releases
Access used
Read-only reader role

Summary

The estate works on most days, but two flows can cause customer-visible damage without anyone being alerted, and the next release to Production will not apply one of its changes. Fixing the top three findings removes most of the risk and takes about four days of work.

Exposed

Verdict: fix findings 1 to 3 before the next release window.

Findings, ranked

Ranked findings
#FindingWhy it mattersFixEffort
1Tier escalation re-triggers itself
It updates the agreement that triggers it.		1,357 runs against one agreement in two minutes; each queued an invoice job.Trigger condition to ignore its own update; re-run billing for affected agreements.0.5 day
2Technician sync hides failures
The Catch scope ends the run as Succeeded.		Customer accounts stop updating and nobody is told.End Catch with Terminate (Failed); alert the support channel.0.5 day
3Hand edit in Test
Site location sync edited over the managed solution.		Saturday's import will not change this flow.Remove the active layer, bring the change back to Development, re-release.1 day
4Four connection references unbound
In the billing and photo upload solutions.		Flows fail on activation after import.Bind to service-account connections in each environment.0.5 day
5Connections owned by one person
Nine flows run on a single user's connections.		They all stop if that person leaves or resets a password.Move to a service account; document ownership.1 day
6No failure alerts
Failures are found by users.		Every failure becomes an incident before anyone looks.Route failures to a monitored channel with record and flow named.0.5 day

Release verdicts

  • Ready Field Ops core 1.3.0.0, Production matches the last release.
  • Needs a decision Northwind Estate 1.4.0.0, hand edit in Test (finding 3).
  • Will fail Billing 2.1.0.0, unbound connection references (finding 4).

Next steps

  1. Fix findings 1 to 3 this week, through Development, Test and Production.
  2. Fix findings 4 to 6 before the next release window.
  3. Install Flow Trace in Production so the next 2 a.m. takes minutes, not hours.
NextGet one for your own estateA fixed-price review with the same detail, on your real environments.