Fieldwork operations
Start with programme status, shopper opportunities and accepted work.
This guided tour uses the synthetic Northstar Fieldwork dataset to explain the RetailHawk operating journey. Use the written chapters now; an approved video version will be added after its separate media review.
Use the chapter guide and written walkthrough below. A video version will be added here after approved synthetic captures, captions and transcript pass review.
Video version: not yet published. The written tour below is complete and usable now; video, captions and transcript remain behind separate media approval.
Start with programme status, shopper opportunities and accepted work.
Show QA as a separate decision from submission and client release.
Move from approved work into the client-facing released result and reporting context.
Extend the same evidence, review and release discipline into assurance without replacing the Mystery Shopping workflow.
Follow the chapter sequence for the video version. Each section describes the current RetailHawk workflow using the synthetic Northstar Fieldwork dataset.
We begin in the agency operating view, using the synthetic Northstar Fieldwork tenant. The overview brings programme status and work requiring attention into one place so coordinators can see the current operational picture before moving into individual assignments.
The client workspace provides the organisational and outlet context around fieldwork. This chapter focuses on the current clients and locations surface; programme setup remains a separate workflow.
From the shopper side, RetailHawk presents eligible opportunities and accepted visits through the responsive application. The workflow keeps assignment context clear while preserving the programme rules that determine who can take the work.
The shopper moves into the RetailHawk mobile questionnaire for the synthetic assignment. The tour stays within current supported questionnaire controls and does not imply unsupported rich-media capture.
Submitted work moves into independent review. Reviewers can assess the submission, return it for correction or approve it, while correction history remains attributable rather than silently replacing the earlier state.
Approval and client release remain separate decisions. Once a result is released, the authorised client audience can inspect the released visit detail and reporting context without being exposed to unreleased work.
The same evidence, review and release model can support assurance work. This chapter uses the reviewed-evidence and result-detail workflow to show how the operating model extends beyond Mystery Shopping.
Tell us how your programme runs and we will focus a live walkthrough on the workflows you need to evaluate.