Request timestamps, assignment records and escalation history.
Potential cause
Unclear responsibility between the office and external vendors.
Measure next
Time to assignment and the number of overdue requests.
THE WORK YOU TAKE AWAY
Four outputs. One practical improvement plan.
Explore sample excerpts. Every accepted pilot defines its evidence requirements and deliverables before work begins.
01 / Operational Health Score™
Understand the operating picture.
ILLUSTRATIVE EXCERPT · NOT A CLIENT RESULT
51.3 /100Reactive · 78.8% evidence confidence
ILLUSTRATIVE ASSESSMENT · SYNTHETIC DATA
Where operational weaknesses concentrate.
Four lowest-rated capabilities per dimension, ordered by rating then item ID. View the full sample for all 100 items.
0 Absent1 Ad hoc2 Repeatable3 Defined4 Managed5 OptimizedEvidence gapNot assessed
Cells show raw item maturity (0–5), not evidence-adjusted dimension scores. Color is supported by a numeric rating. Gray cells distinguish missing evidence from missing ratings.
People
Process
Technology
Data
Automation
Select a capability to see its assessment details.
100 of 100 items rated · No evidence-level-0 items · No critical-failure triggers in this dataset. A critical item is not automatically a failed control.
Select a step to see the work, the client’s role and the output.
ILLUSTRATIVE PROPERTY-MANAGEMENT WALKTHROUGH · NOT A CLIENT RESULT
01Define the scopeAgree what we will assess.+
STEP 01
Scope makes the assessment useful.
Assessment boundary
One property-management team and its maintenance intake-to-assignment workflow.
Included
Request intake, triage, assignment, vendor handoffs and escalation.
Excluded
Other departments, system implementation and professional compliance opinions.
Client responsibilities
Name a sponsor and coordinator, arrange interviews and provide the agreed de-identified records.
OUTPUT Agreed assessment scope
02Examine the evidenceCheck how work happens in practice.+
STEP 02
A finding needs more than an opinion.
Sources to review
Interviews, workflow instructions, de-identified request timestamps, assignment records and escalation logs.
What assessors check
Compare stated responsibilities with records of how requests were actually handled.
When evidence is missing
Record the gap and its effect on confidence. Do not treat an unverified claim as a confirmed finding.
Assessment limits
Material gaps can limit conclusions or require withholding a headline score.
OUTPUT Evidence-backed findings
03Prioritize improvementsDecide what deserves attention first.+
STEP 03
Connect the gap to a practical decision.
Sample finding
Maintenance requests depend on manual routing and local judgment.
Operational impact
Unclear ownership can delay assignment and leave urgent requests unresolved.
Urgency and dependencies
Review urgent-request escalation first. Confirm categories and accountable owners before introducing automation.
Recommended action
Agree a common triage standard, name escalation owners and measure time to assignment.
OUTPUT Ranked improvement priorities
04Agree the next actionsGive every action an owner and measure.+
STEP 04
Make the next step accountable.
Action and owner
Property Operations Lead: agree and pilot a common maintenance triage standard.
Illustrative target
Within 30 days of action-plan approval, subject to agreed capacity and access.
Progress measures
Time to assignment, overdue unassigned requests and escalation exceptions. Establish the baseline before setting targets.
Review checkpoint
Review pilot results with the sponsor after two weeks. Confirm changes, outstanding risks and the next decision.
OUTPUT Accountable action plan
A timeline matched to your scope. Proposed pilots range from 3–4 weeks for a focused team to 6–8 weeks for a larger, bounded operation. Enterprise and complex scopes are confirmed after discovery.
Planning estimates only. The assessed team, workflows and evidence readiness determine the final schedule.
Bert brings enterprise IT project and program experience across infrastructure modernization, cloud, cybersecurity, financial systems and data governance.
He founded VistaVetta to help leaders understand the operating conditions behind performance and make better decisions about what to improve.
M.S., Geographic Information Systems · Johns Hopkins University
What is the difference between the Snapshot and the pilot?
The free Snapshot asks 20 questions and produces a preliminary self-reported profile. The paid pilot examines supporting evidence, diagnoses operational gaps and delivers a prioritized plan.
How long does the pilot take?
Proposed ranges are 3–4 weeks for a focused team or department, 4–6 weeks for a business unit or smaller company, and 6–8 weeks for a larger, bounded operation. Enterprise or complex scopes are confirmed after discovery. These are planning estimates, not guarantees. Timing starts after scope approval, kickoff and access to the agreed minimum evidence. See scope boundaries and timeline conditions.
What information will we need to provide?
Depending on scope: workflow instructions, de-identified operating records, reports and interviews with responsible staff. Evidence requirements and handling arrangements are agreed before collection. Do not submit client, tenant, case, tax or confidential financial records through this website.
Does the fee include implementation?
Pilot pricing is confirmed after scope review and covers the assessment and deliverables agreed in your proposal. Configuration changes, integrations and implementation are separately scoped and approved.
START WITH YOUR OPERATION
Find your starting point.
Explore your operational practices, then discuss the workflow that needs attention.