Beatriz Berbert LinkedIn
Selected work

Analytics & BI

Delivery Planner

Cedar’s customer cutover is booked for Friday. An Implementation specialist is out for eight hours, and the team now needs 13 hours it does not have. What can move without missing the cutover?

Compare delivery plans

See what each plan saves this week and what it adds to next week.

Synthetic data

Scenario

Weekly capacity

Loading sample week…

–Hours of work
–Hours available
–Uncovered hours

Compare the trade-offs
OptionGap this weekCommitted gapAdded gap next week
Work in this scenario
Work itemTeamHoursPlan and consequence

The Friday decision

Implementation has 48 available hours after the absence and 51 hours committed to Cedar. Moving Hilltop onboarding frees ten hours, leaving three still uncovered. Support can cover three with a certified specialist if its help center cleanup moves too. That protects Friday and adds ten uncovered hours across the two teams the following week.

Starter SQL queries SQLite database

Planning assumptions

Which hours can move across teams?

One Support specialist is certified for up to six hours of Implementation access mapping. The comparison transfers only available hours, with a six-hour cap. Automation hours remain with Automation.

Who owns the follow-up?

The Implementation lead confirms coverage with Support before promising Friday. Next week’s view includes the deferred hours. The lead must replan Hilltop’s rehearsal if onboarding will not finish in time. The tool estimates weekly load, not the order of work within a day.