myITprocess Alignment Reviews
Overview
An alignment review is how an MSP measures a client against its own technology
standards. In myITprocess an engineer answers the review first, then the vCIO
completes it and turns gaps into findings and recommendations. This skill covers
the review side of that loop: what is due, what is late, and what to review
next. See api-patterns for filters, paging and the
rate limit.
Every tool used here is a Conduit read tool. None is admin-gated, and none
can change a review: status, assignee and due dates are edited in the
myITprocess UI.
Anti-triggers
- What the review found, and what to do about it (findings,
recommendations, budget) — use roadmap.
- A brief for one client's upcoming QBR — use qbr-prep.
Key Concepts
Review status (myitprocess_reviews_list)
| Status |
Meaning |
Who owns the next step |
New |
Created, not started |
Engineer |
EngineerInProgress |
Engineer answering |
Engineer |
EngineerComplete |
Engineer done, waiting on vCIO |
vCIO |
VcioInProgress |
vCIO reviewing |
vCIO |
Complete |
Finished |
- |
Each review carries engineerDueDate / engineerCompleteDate,
vcioDueDate / vcioCompleteDate, assignedEngineer.fullName,
assignedVCIO.fullName, client.id / client.name, createdDate and
lastUpdatedDate. The tool returns active reviews only.
Overdue categories (myitprocess_reviews_overdue_categories_list)
myITprocess schedules each standards category on a review cadence. This tool
lists, per client, the categories that are up for review or overdue
(client.id, client.name, category id, name, fullName). It is the
direct answer to "what should the next review for this client cover?"
Client signals (myitprocess_clients_list)
alignmentScore, lastReviewDate, lastAssignedMemberActivityDate,
isActive, createdDate, deactivatedDate. A low score or an old
lastReviewDate marks a client that needs attention even when no review is
open.
Common Workflows
Prepare the next alignment review for one client
- Resolve the client:
myitprocess_clients_list with a name contains
filter. Confirm the match with the user if more than one client comes back.
Note alignmentScore and lastReviewDate.
myitprocess_reviews_overdue_categories_list filtered by client.id. This
is the scope of the next review.
myitprocess_reviews_list filtered by client.id to see whether a review is
already open and where it sits.
- Optional context:
myitprocess_findings_list filtered by the last completed
review's review.id, to show which gaps from last time are still open
(finding type UnassignedReviewFinding means a gap never turned into a
recommendation).
- Report: client, score, last review date, open review (if any) with owner and
due date, and the list of overdue categories grouped as the reviewer will
work them.
Reviews behind schedule (portfolio)
myitprocess_reviews_list filtered status notEqual Complete, sorted by
engineerDueDate ascending. Page until you have totalCount.
- Classify each open review against today's date:
- Engineer late: status
New or EngineerInProgress and
engineerDueDate in the past.
- vCIO late: status
EngineerComplete or VcioInProgress and
vcioDueDate in the past.
- Stalled:
lastUpdatedDate older than about 14 days, whatever the due
date.
- Group by
assignedEngineer.fullName and assignedVCIO.fullName to show
whose queue is the bottleneck.
- Report counts per bucket, then the late reviews oldest first: client, review
name, status, owner, due date, days late.
Do the date comparison yourself on the returned items unless a date filter
clearly works; date filter formats are not documented in the spec.
Clients due for a review (portfolio)
myitprocess_clients_list filtered isActive equal true, sorted by
lastReviewDate ascending.
myitprocess_reviews_overdue_categories_list (no filter, paged) and count
categories per client.id. The response does not say which categories
are merely due and which are overdue, so report the count as "categories
due or overdue".
- Rank clients by number of categories due or overdue, then by age of
lastReviewDate; show alignmentScore alongside. A client with no open
review in myitprocess_reviews_list and many overdue categories is the one
to schedule first.
vCIO / engineer workload
Join open reviews (myitprocess_reviews_list) to staff
(myitprocess_users_list: firstName, lastName, roleName,
lastLoginDate) by name. A reviewer with many late reviews and an old
lastLoginDate usually means the work has been dropped, not that it is
in progress.
Gotchas
- Client names are free text. Use
contains, then confirm; two clients can
share a prefix.
- Rate limit. A full portfolio sweep is three or four list calls plus
paging. Do not loop per client when one unfiltered, paged call answers the
question (50 requests per minute, shared with other integrations).
- No write path. If the user asks to reassign, re-date or close a review,
say that this connector is read-only and the change is made in myITprocess.
1---2name: myitprocess-alignment-reviews3description: >4 The myITprocess alignment-review pipeline: review status stages (New through5 Complete), engineer and vCIO due dates, standards categories that are up for6 review or overdue per client, and client-level staleness signals (last review7 date, last assigned-member activity, alignment score). Covers preparing the8 next alignment review for a client and a portfolio sweep for reviews that are9 behind schedule. Read-only.10when_to_use: >-11 When planning or preparing an alignment review, checking which reviews are late12 or stuck with the engineer or the vCIO, finding clients whose standards13 categories are overdue, or ranking clients by alignment score or review14 staleness. Use when: alignment review prep, overdue reviews, overdue15 categories, review backlog, stale clients, alignment score, or vCIO workload.16metadata:17 source: https://skillmd.com/skills/wyre-ai/myitprocess-alignment-reviews18---1920# myITprocess Alignment Reviews2122## Overview2324An alignment review is how an MSP measures a client against its own technology25standards. In myITprocess an engineer answers the review first, then the vCIO26completes it and turns gaps into findings and recommendations. This skill covers27the review side of that loop: what is due, what is late, and what to review28next. See [api-patterns](../api-patterns/SKILL.md) for filters, paging and the29rate limit.3031Every tool used here is a Conduit **read** tool. None is admin-gated, and none32can change a review: status, assignee and due dates are edited in the33myITprocess UI.3435## Anti-triggers3637- **What the review found, and what to do about it** (findings,38 recommendations, budget) — use [roadmap](../roadmap/SKILL.md).39- **A brief for one client's upcoming QBR** — use [qbr-prep](../qbr-prep/SKILL.md).4041## Key Concepts4243### Review status (`myitprocess_reviews_list`)4445| Status | Meaning | Who owns the next step |46|--------|---------|------------------------|47| `New` | Created, not started | Engineer |48| `EngineerInProgress` | Engineer answering | Engineer |49| `EngineerComplete` | Engineer done, waiting on vCIO | vCIO |50| `VcioInProgress` | vCIO reviewing | vCIO |51| `Complete` | Finished | - |5253Each review carries `engineerDueDate` / `engineerCompleteDate`,54`vcioDueDate` / `vcioCompleteDate`, `assignedEngineer.fullName`,55`assignedVCIO.fullName`, `client.id` / `client.name`, `createdDate` and56`lastUpdatedDate`. The tool returns active reviews only.5758### Overdue categories (`myitprocess_reviews_overdue_categories_list`)5960myITprocess schedules each standards category on a review cadence. This tool61lists, per client, the categories that are **up for review or overdue**62(`client.id`, `client.name`, category `id`, `name`, `fullName`). It is the63direct answer to "what should the next review for this client cover?"6465### Client signals (`myitprocess_clients_list`)6667`alignmentScore`, `lastReviewDate`, `lastAssignedMemberActivityDate`,68`isActive`, `createdDate`, `deactivatedDate`. A low score or an old69`lastReviewDate` marks a client that needs attention even when no review is70open.7172## Common Workflows7374### Prepare the next alignment review for one client75761. Resolve the client: `myitprocess_clients_list` with a `name` `contains`77 filter. Confirm the match with the user if more than one client comes back.78 Note `alignmentScore` and `lastReviewDate`.792. `myitprocess_reviews_overdue_categories_list` filtered by `client.id`. This80 is the scope of the next review.813. `myitprocess_reviews_list` filtered by `client.id` to see whether a review is82 already open and where it sits.834. Optional context: `myitprocess_findings_list` filtered by the last completed84 review's `review.id`, to show which gaps from last time are still open85 (finding type `UnassignedReviewFinding` means a gap never turned into a86 recommendation).875. Report: client, score, last review date, open review (if any) with owner and88 due date, and the list of overdue categories grouped as the reviewer will89 work them.9091### Reviews behind schedule (portfolio)92931. `myitprocess_reviews_list` filtered `status` `notEqual` `Complete`, sorted by94 `engineerDueDate` ascending. Page until you have `totalCount`.952. Classify each open review against today's date:96 - **Engineer late**: status `New` or `EngineerInProgress` and97 `engineerDueDate` in the past.98 - **vCIO late**: status `EngineerComplete` or `VcioInProgress` and99 `vcioDueDate` in the past.100 - **Stalled**: `lastUpdatedDate` older than about 14 days, whatever the due101 date.1023. Group by `assignedEngineer.fullName` and `assignedVCIO.fullName` to show103 whose queue is the bottleneck.1044. Report counts per bucket, then the late reviews oldest first: client, review105 name, status, owner, due date, days late.106107Do the date comparison yourself on the returned items unless a date filter108clearly works; date filter formats are not documented in the spec.109110### Clients due for a review (portfolio)1111121. `myitprocess_clients_list` filtered `isActive` `equal` `true`, sorted by113 `lastReviewDate` ascending.1142. `myitprocess_reviews_overdue_categories_list` (no filter, paged) and count115 categories per `client.id`. The response does not say which categories116 are merely due and which are overdue, so report the count as "categories117 due or overdue".1183. Rank clients by number of categories due or overdue, then by age of119 `lastReviewDate`; show `alignmentScore` alongside. A client with no open120 review in `myitprocess_reviews_list` and many overdue categories is the one121 to schedule first.122123### vCIO / engineer workload124125Join open reviews (`myitprocess_reviews_list`) to staff126(`myitprocess_users_list`: `firstName`, `lastName`, `roleName`,127`lastLoginDate`) by name. A reviewer with many late reviews and an old128`lastLoginDate` usually means the work has been dropped, not that it is129in progress.130131## Gotchas132133- **Client names are free text.** Use `contains`, then confirm; two clients can134 share a prefix.135- **Rate limit.** A full portfolio sweep is three or four list calls plus136 paging. Do not loop per client when one unfiltered, paged call answers the137 question (50 requests per minute, shared with other integrations).138- **No write path.** If the user asks to reassign, re-date or close a review,139 say that this connector is read-only and the change is made in myITprocess.