Page 1 of 2

Community Systems Alignment Snapshot

Answer based on your current operating reality

Operational Flow:

How cleanly does work move from request to completion?

Examples: Service requests, violations, board actions, vendor follow-through, etc.

Operational Flow:

A

Clear and predictable

B

Functional but needs follow-up

C

Often stalls, loops, or resurfaces

Reactive vs Proactive:

*

How would you describe day-to-day operations?

Reactive vs Proactive:

A

Mostly proactive

B

Mixed

C

Mostly reactive

Ownership Clarity:

*

How clear is ownership through to completion?

Examples: Who finalizes work, closes projects, ensures follow-through

Ownership Clarity:

A

Clear ownership

B

Some gaps

C

Blurred or shifting ownership

Cross-System Patterns:

*

When issues occur, how often do they involve multiple systems?

Cross-System Patterns:

A

Rarely

B

Sometimes

C

Often

Capital Effectiveness:

*

How well do capital projects resolve issues long-term?

Capital Effectiveness:

A

Results hold

B

Partial improvement

C

Issues persist or return

Admin & Financial Flow:

*

How smoothly do admin and financial processes support operations?

Examples: Invoices, reimbursements, reporting, approvals

Admin & Financial Flow:

A

Smooth

B

Functional with follow-up

C

Delayed or inconsistent

Decision → Execution:

*

How reliably do decisions translate into action?

Decision → Execution:

A

Direct and consistent

B

Some delay or reinterpretation

C

Often slows or loops

Visibility:

*

How clearly can you see what’s happening across systems and operations?

Visibility:

A

Clear visibility

B

Partial

C

Limited / reactive

Overall Experience:

*

How would you describe the overall community experience?

Overall Experience:

A

Consistent and reliable

B

Generally good with some friction

C

Frequent small issues