Assessment
Repeat usage snapshot
A second measurement of the same app after a release, a model change, or a logging fix — compared against the earlier picture rather than started from a blank page.
Who it is for
Teams who have already completed a Model Vertex Point usage assessment and need to know what changed after they shipped.
What you leave with
A short comparison: which invocation sites grew, shrank, appeared, or went quiet, and whether new logging actually closed the gaps we named last time.
Scope
The same app and the same inventory structure as the prior assessment, over a new window you name.
Included
- Reuse of the prior call inventory as the spine
- A new window reconstruction
- A written delta, not a second full narrative from scratch
- A sixty-minute walkthrough
Not included
- Assessment of a different app
- A first-time inventory
Who does the work
Aisha Rahman, with the same counterpart from the original assessment where possible.
Sequence
- Confirm the spine. We reopen the prior inventory and mark sites that have been added or removed in the release notes you send.
- Read the new window. Same method as before, same honesty about gaps.
- Write the delta. What moved, what did not, what is newly unreadable.
Duration
Seven to ten working days. Faster only when logging is in the same shape as last time.
Where it happens
Led from Petaling Jaya. Walkthrough in person or by call.
What to prepare
The prior report, release notes for the interval, and access comparable to the first assessment.
Limits
Offered only after a Model Vertex Point assessment of the same app. If the app has been rewritten past recognition, this becomes a new assessment.
Fee basis
From RM 4,600. Quoted against the prior inventory, not as a percentage of the first fee.
Next step
Name the app, the prior assessment month, and the new window.