Key finding
The study would test whether scope changes are controlled records or verbal expansions that appear after the work.
Question and scope
This is a proposed research protocol, not a report of completed findings. It asks what share of client scope changes are recorded and approved before work starts. The result would describe the control, not the client's intent. Record the exception and the person who approved it. The offshore team should record the local time for both locations. The shift report should show the export time and the system.
The protocol does not measure whether the change was a good idea. It measures whether the team had an approved record before acting. Review the first few notes together before the process expands. Ask whether a new reviewer could act on the record without a conversation. The shift report should show the export time and the system. The review should leave one owner and one date.
Population and unit of analysis
Define the population as scope changes during a stated window. The unit is one change, with the request, the impact, the approval, and the start date recorded. Test the rule on one real handoff before applying it to both shifts. Keep the evidence with the record rather than in a separate log. A handoff that cannot be confirmed is not yet complete. The change note should keep the original brief visible.
Link the change to the original brief so the same change is not counted twice. Name the owner in the same line as the action. Write the deadline as a date and a local time. Test the rule on one real handoff before applying it to both shifts. The offshore team should record the local time for both locations. The shift report should show the export time and the system.
Definitions and measures
Define pre-work approval as an approval dated before the first task on the new scope. Define completeness as the presence of the request, impact, and approval. Separate what was observed from what was assumed. Record the exception and the person who approved it. The shift report should show the export time and the system. The team lead should review the missed handoffs weekly.
Report the pre-work approval rate and the completeness rate separately. A short note with four fields is easier to use than a long narrative. Update the template when the same question appears twice. Record the exception and the person who approved it. The change note should keep the original brief visible. The review should leave one owner and one date.
Evidence standard
Link each change to the request, the approval, and the task record. A note that says client asked is not an approval. Use the same format for every handover so the next reader can scan it. Keep the boundary visible in the place where the work is assigned. The review should leave one owner and one date. The quality sample should link the finding to the source update.
Use the task timestamp to establish when the work started. A later approval should be marked as late. Separate what was observed from what was assumed. Test the rule on one real handoff before applying it to both shifts. The onboarding plan should end with a written readiness decision. The offshore team should record the local time for both locations.
Sampling and collection
Use a census of the changes if the volume is manageable. If sampling is necessary, stratify by client and change type. Record the exception and the person who approved it. Write the deadline as a date and a local time. The review should leave one owner and one date. The team lead should review the missed handoffs weekly.
Pilot the classification on a few changes and compare the reviewers. Clarify what counts as the first task. Update the template when the same question appears twice. Separate what was observed from what was assumed. The capacity plan should use productive hours, not scheduled hours.
Analysis and reporting
Report the pre-work approval rate by client and change type. Show the changes that were approved after the work started. Ask whether a new reviewer could act on the record without a conversation. Record the exception and the person who approved it. The quality sample should link the finding to the source update.
Present the results as a description of the control, not a judgment about the client. Name the step that should be strengthened. Review the first few notes together before the process expands. Separate what was observed from what was assumed. The team lead should review the missed handoffs weekly. The review should leave one owner and one date.
Limits and sources of error
The start date may be unclear if the work was exploratory. State the rule used. Test the rule on one real handoff before applying it to both shifts. Keep the evidence with the record rather than in a separate log. The team lead should review the missed handoffs weekly. The shift report should show the export time and the system.
The approval may have been verbal and recorded later. Mark it as late evidence. Use the same format for every handover so the next reader can scan it. A control that depends on memory is not yet a control. The quality sample should link the finding to the source update. The onboarding plan should end with a written readiness decision.
Review cadence
Repeat the review after a process change or at the same interval each quarter. Compare the same change types. Separate what was observed from what was assumed. A control that depends on memory is not yet a control. The capacity plan should use productive hours, not scheduled hours. A handoff that cannot be confirmed is not yet complete.
Assign the follow-up to the account owner and set a date. The protocol should produce a specific decision about the approval step. Update the template when the same question appears twice. A short note with four fields is easier to use than a long narrative. The team lead should review the missed handoffs weekly. The change note should keep the original brief visible.
Sources
Apply this research to your workflow
Use the protocol to define the records, review owner, and decision boundaries before work is delegated.
Discuss your workflow