Change that governs itself — risk-scored, board-approved, and freeze-aware.

You get a working, governed change process rather than a pile of half-configured settings: the change model and its lifecycle, risk assessment with scored thresholds, the approval routing to your board, and a Change Advisory Board with its schedule and review scope. Everything lands in one reviewable package so it can be inspected and moved as a single unit. The outcome is change governance that's ready to operate.

Yes. She builds change governance the native, upgrade-safe way and steers clear of custom code that reinvents behaviour the platform already provides. If a request would duplicate built-in change capability, she flags it. Your process stays clean, standard, and easy to maintain.

A healthy CMDB helps, because technical approvals and conflict checks draw on the services and infrastructure a change touches. She also reads your existing change configuration first, so she designs to how you actually run change today rather than to out-of-box defaults. The result fits your environment, not an idealised one.

No. Phyllis reviews and proposes; nothing is written until you approve. Every record is staged in a package you can inspect first, and she never completes or activates it on your behalf. You stay in control.

Every finding is cited back to your live instance — the change model, the risk rules, the advisory board, the actual configuration values. She reads what's really configured today rather than assuming, so the plan reflects your environment. You get verifiable evidence, not guesses.