The bank must lock a branch deployment design before renovation work closes the physical path.
Physical security protects the launch date while IT security protects credential lifecycle controls.
Who you’d be doing this for
“The builders finish in eighteen days, and my guards are already covering doors that should be live.”
Fadi Erdogan · Head of Physical Security
He is responsible for branch access continuity during the renovation programme.
What is at stake
Nineteen credential-lifecycle answers conflict across the bank's review materials for 214 doors. You have to weigh the branch launch date against controls that IT security can verify and sign.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- branch opening date vs verified credential controls
- construction finality vs pilot learning
- procurement consistency vs deployment flexibility
- machine-summarized evidence vs direct verification
Why Verkada
Verkada Products must earn technical trust in regulated branch environments where cloud security and physical deployment decisions converge.
Written with these in mind
Not your kind of problem? 63 more at Verkada, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.