CEO Executive Assistant
Most executive risks are visible before they become urgent. A supplier is late, an approval is stuck, a key person is on leave, or a commitment was made without a date. The signals are there, scattered across messages and calendars. The chief of staff’s weekly risk scan collects them before they compound.
A risk scan is not a status report. It is a short, structured look at what could break in the next two weeks and who owns the response. It takes thirty minutes and produces a list of three to five items, not fifty.
Start with the next two weeks
Look at the commitments in the next fourteen days: board meetings, client deliverables, launches, travel, and regulatory deadlines. A risk that is far away can wait. A risk in the next two weeks needs a name.
The window keeps the scan focused. A quarterly risk register is useful, but it does not help the chief of staff decide what to raise this week.
List the dependencies
For each commitment, name what it depends on: a person, a document, a payment, a vendor, or an approval. A dependency without a confirmed owner is a risk.
The list should be short. If everything is a dependency, nothing is. Focus on the items that could stop the commitment.
Check the quiet failures
Some risks do not announce themselves. A recurring meeting that no longer produces decisions, a report that is always late, or a promise that keeps slipping are quiet failures. The scan should name them.
The chief of staff can ask one question: what has been true for three weeks that should have changed? The answer often reveals a quiet failure.
Assign an owner and a next action
Every risk needs an owner and a next action with a date. The owner may be the chief of staff, an executive, or a functional lead. The next action should be specific enough to verify.
A risk without an owner is a worry. A risk with an owner and a date is a plan.
Decide what to escalate
Not every risk belongs in the executive’s inbox. The scan should decide which items need the executive’s attention, which can be handled by the chief of staff, and which should be watched.
Escalate the items that need a decision or a relationship. Handle the ones that need coordination. Watch the ones that are outside the team’s control.
Keep the scan short
The output should fit on one page: risk, commitment, owner, next action, date, and status. A longer document will not be read in a busy week.
The chief of staff should bring the scan to the weekly priorities reset and use it to adjust the plan. A risk that changes the week should change the calendar.
Review last week’s risks
Open the scan with the items from last week. Which ones closed, which moved, and which were forgotten? A risk that keeps moving without a change may need a different owner or a different plan.
The review is the accountability part of the routine. Without it, the scan becomes another list.
Protect the confidentiality
A risk scan can contain personnel, legal, and financial details. Keep it in a restricted location and share only the relevant item with the relevant person. Do not circulate the full scan in a broad channel.
The chief of staff should keep the working version and a short summary for the executive. The summary is enough for the weekly conversation.
Keep the scan separate from the status report
The risk scan is about what could break, not what happened last week. A status report looks backward; the scan looks forward. Keeping the two separate keeps the scan short and the conversation focused.
If the team needs a status update, send it separately. The scan should not become a place where every update is relabeled as a risk.
Use a simple rating
A rating of high, medium, or low is enough for most items. The rating should reflect the impact on the next two weeks, not the size of the underlying project. A short note explains the rating.
Close the scan with one decision
End the scan with one question for the executive: which risk needs a decision this week? A single decision is easier to act on than a list of concerns, and it keeps the weekly conversation focused.
Key takeaways
- Scan the next two weeks and name the commitments that could break.
- List the dependencies, including the quiet failures that have persisted.
- Give every risk an owner, a next action, and a date.
- Decide what to escalate, keep the scan to one page, and review last week’s items.
A weekly risk scan is a small habit that prevents large surprises. It gives the chief of staff a structured way to see the next two weeks and a clear basis for the weekly conversation with the executive.
For related workflows, see the weekly priorities reset and the executive assistant services overview.