Leave List Decay Honest at the Volume Increase Leave List Decay Honest at the Volume Increase Submissions pushed without a defined link budget create pages that appear unusually heavy to anyone reviewing the output. Engine-Fit Check gives list-maintenance specialists a defined way to judge list decay while the campaign is at the volume increase. The engine-fit check is the point at which indexing expectations either earns its place in the workflow or is dropped. Repeats inside an imported list inflate its apparent scale, since the same domain appears under several paths. Writing the layer rules into the project notes supplies the next batch something concrete to follow. Before volume rises, the project needs one comparable measurement to sit against. Time spent hunting targets that no longer respond is time lost, and a maintained list at the campaign quality reference curbs that loss. A verified placement that survives a re-check is worth more evidence than a hundred submissions without a follow-up. Record which engines were switched on at the time of the run, since that detail explains most strange results later. During the volume increase, the question is whether list decay still supports measuring how quickly a pool stops producing after a platform change. Set the Settings Record Against a Baseline No check can prove future survival, since a destination may drop content at any time for its own grounds. A batch of roughly 36 destinations is large enough to expose a pattern in list decay without becoming unreadable. For list-maintenance specialists running a Tier 3 project, measuring how quickly a pool stops producing after a platform change matters more than the raw number of attempts recorded against indexing expectations.