This is the sequence we use for an inventory application audit. Cycle-count reviews, lineage work, and cut-off examinations follow the same spine, shortened to the window you give us.
You name the site, the inventory application, and the period. We say whether the work fits, what we will not do (implementation, a physical stocktake performed by us, vendor certification), and what access we need. If it fits, we send a letter with fee, timing, and a request list.
You return a map of buildings in scope, a list of applications that post inventory, and a way to obtain movements. Where a count is planned, we agree a freeze for receiving and shipping. Missing documents are noted; we do not invent them.
Sampling is of actual receipts, issues, transfers, and count batches — not a reconstructed demo. We walk a gate posting to a bin, test access around adjustments, and read variances against the batch that posted. Rajesh keeps the request log current so receiving is not answering the same question twice.
Draft findings go to the inventory owner for factual check. The signed letter states the scope, the view of the application for inventory recording in the named period, and a ranked schedule. Adjustment verification is a separate letter after you confirm a fix is live.