The scope the client approved
Compare the signed contract with change requests to distinguish approved scope from proposed work.
Review client requirements against delivered work
Connect contracts and client conversations to development tasks, code changes, and tests. See what was agreed, what has been built, and which requests still need a decision.
A passed test may cover only part of the client’s request
The sign-in tests for Northstar’s SSO ticket pass. The client’s security questionnaire also requires departing staff to lose account access within four hours. The team must check the contract and meeting notes to establish whether that requirement was agreed, then examine the implementation to see whether it is supported.
Review project scope alongside contracts and code
The fictional Relay Studio workspace brings together the signed scope, client conversations, architecture decisions, code changes, tests, and release records. Compare the agreed work with the delivered features and identify decisions still needed from the client and team.
The decisions behind the work
Trace client feedback and meeting notes to the decisions the team recorded.
The design and implementation plan
Connect architecture decisions to the relevant systems and the plan for building the feature.
The features actually delivered
Match agreed requirements to completed tasks, code changes, and test results to check what has been delivered.
Check agreed requirements, implementation, and open decisions
Clarify the requirements behind the client’s words.
The client uses “SSO” for both sign-in and revoking account access. Compare that language with the agreed SAML sign-in scope and the later account-management request. A shared label does not make the additional feature part of the signed scope.
A clear distinction between agreed scope and an additional request.
Northstar’s SSO ticket passed testing. Why is the client’s offboarding requirement still unresolved?
Follow the requirement through to the release.
Trace architecture decision ADR-12 through AUTH-81, code change PR-118, test AT-11, and release RC-8. These records support the sign-in feature. The API inventory and AUTH-94, which is excluded from the release, explain why the account-management request remains unresolved.
Delivery status tied to the feature actually tested.
Which Northstar requirements are covered by RC-8’s code and tests, and which are not?
Prepare the decisions behind the next commitment.
Review the tested release, current account-administration runbook, and unsigned change request CR-9 together. Set out the account behavior, acceptance checks, and responsibilities that need agreement before committing to more work.
A delivery review with clear decisions for the client and team.
Draft Northstar’s delivery review with tested scope, the open lifecycle request, and decisions needed next.
Team onboarding, customer support, and proposal preparation
Project onboarding
Bring the project brief, key decisions, owners, and active tasks together so new teammates can get up to speed.
Support investigation
Trace a client issue to the relevant requirement, implementation records, and earlier resolutions.
Proposal preparation
Review similar projects to see what worked, what took longer than expected, and what the next proposal should account for.
EngramRAG
Project decisions and implementation history for handovers
EngramRAG links the client’s language to specific features, recorded decisions, and implementation records. New requests and approved changes stay in the project history, so future reviews can trace both what was built and why.
Connect the client’s words to the feature.
Link the client’s terms to the corresponding features and systems.
Keep approval and delivery status clear.
Distinguish proposed ideas, approved changes, and delivered features.
Preserve the reasons behind decisions.
Carry the rationale and agreed decisions into future project reviews.
Prepare project records for the next review
Bring client records, team decisions, and implementation knowledge into one workspace for the next project review.
