How to size survey crew-days from a change tile worklist

Every national mapping shop has a version of the same spreadsheet: a resurvey cycle that divides the country into quadrants and assigns each one a crew-week allotment, due again in three years, or five, whether or not anything on the ground actually changed. It's easy to build and even easier to defend in a budget meeting, but it spends field time on geography instead of on change.
A change tile worklist flips the math. Instead of staffing geography, you staff change. The question becomes: how many tiles flagged this quarter, and how many crew-days does clearing that list take?
Start with tile count, not acreage
Forget square kilometers for a minute. A worklist built from a change tile index gives you a count: so many tiles with a change score above whatever threshold you've set for "send a crew," with the region's footprint left out of the math entirely. A quadrant that used to take three crew-weeks under the old cycle might produce eight flagged tiles this quarter. The other 400 tiles in that quadrant didn't move, and sending a crew to walk them anyway was always a guess dressed up as a schedule.
Once you have a tile count, the crew-day math is the arithmetic planners already do for any field job: divide total flagged tiles by tiles per crew-day to get crew-days needed. That rate isn't fixed. It depends on drive time between stops, terrain, whether the flags cluster in one district or scatter across three, and whether the change score calls for a full resurvey pass or just a verification visit. A run of high-score tiles along one corridor might clear four or five a day. A handful of isolated flags two counties apart can eat a whole day each once you count the driving.
Weight the list by change score before you staff it
Not every flagged tile needs the same visit. A tile with a high change score, say a new subdivision or a realigned road, earns a full field pass: control, feature capture, the works. A tile flagged for a lower-confidence reason, a seasonal water body or a construction site that could go either way, might only need someone to drive past and confirm before it gets promoted or dropped from the list. Sorting the worklist by change score before assigning crew-days keeps high-value tiles from sitting behind a long tail of low-confidence flags that eat the same calendar slot and deliver less.
Tracked honestly, "crew-days per tile" isn't one number. A shop that tracks it ends up with two or three averages: full-resurvey tiles, verification-only tiles, and a blended figure for planning. Flattening those into a single rate for budget season hides where the time goes.
Budgeting the quarter against the crews you have
Once the worklist is scored and sorted, the budgeting question is ordinary: tiles needed divided by tiles per crew-day equals crew-days required, set against crew-days available this quarter. If the flagged list runs ahead of capacity, the change score ranks which tiles wait until next quarter. A fixed cycle would have postponed the whole region instead. If the list comes in lighter than expected, that spare capacity doesn't have to sit idle until the next cycle date. It can pull tiles forward from next quarter or free crews for other work.
That's the real difference between worklist staffing and fixed resurvey cycle staffing. A cycle staffs the calendar. A worklist staffs the change, so a quiet quarter costs less field time and a busy one gets flagged before the schedule book would have noticed. Pulling that worklist from a change tile index built off continuous high-resolution coverage compared against the current basemap means the crew-day math starts from what moved on the ground this quarter, not from whatever came due next on the shelf.
If a budget season still opens with a region map and a cycle date rather than a tile count, National Change Alerts is built to be the thing you open instead.