IB Analyst Workflow

An analyst's operating system across live deals: one task list, clean folders and versions, a request intake that captures deadlines, a pre-send check, honest status updates and weekends you actually keep.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for IB Analyst Workflow, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

201

Starter tasks

🏦 Investment Banking & Advisory

IB Analyst Workflow

Organising the analyst workload: task lists across deals, version control, staffer requests, checking work before sending and keeping some weekends.

  1. One master task list across every live deal
  2. Deal folder structure on the group drive
  3. File naming and version control convention
  4. Email and chat filing for deal traffic
  5. Contact sheet for every deal team
  6. Sign-off chain before anything leaves the bank
  7. Request intake routine for staffer and senior asks
  8. Reference folder of your best past work
  9. Desk and phone set-up for out-of-hours requests
  10. Morning triage of overnight requests
  11. End-of-night status note to each deal lead
  12. Monday workload snapshot for the staffer
  13. Friday file clean-up and archive
  14. Pre-send check for every email with an attachment
  15. Calendar blocks for focused model and drafting time
  16. Monthly review of the task system
  17. One protected weekend a month
  18. Deal drive permissions and hygiene check
  19. Estimating how long tasks really take
  20. Clarifying questions in one message
  21. Competing deadlines from two senior bankers
  22. Parallel editing of one deck without collisions
  23. Briefing an offshore or research support team
  24. Batching data and information requests
  25. Status updates seniors actually read
  26. Choosing a task tool inside the bank's rules
  27. Reusable email templates for routine requests
  28. One-week audit of where the hours went
  29. Confirming the output format before starting
  30. Mis-send and wrong-version post-mortem
  31. Renegotiating a deadline before it is missed
  32. Working on the move with offline files
  33. First week on a newly staffed deal
  34. The 48 hours before a client meeting
  35. Holiday handover pack for live deals
  36. Catching up on the first day back
  37. Shutting down a deal that dies
  38. Year-end tidy of closed and dead deals
  39. First month as a new analyst on the desk
  40. Boutique analyst without a staffer or support team
  41. Working with a team in another time zone
  42. Covering for an absent teammate's deals
  43. Returning after extended leave
  44. Analyst in a small-market regional team
  45. Passing your system to the new analyst class
  46. Running the workstream tracker for a deal team
  47. Personal how-to notes from every deal
  48. A year of turnaround and error records
  49. Workflow for live deals near signing
  50. Quarterly honest look at the workflow

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

One master task list across every live deal

Analysts on three or four live deals usually keep tasks in four places: the inbox, sticky notes, a notebook and memory, and the missed item is always the one in the fourth place. Moving every open request into one list, grouped by deal with a requester and a due time on each line, is the single change that makes the rest of this area work.

First tasks

  • Scroll the last seven days of email and chat and copy every open request into one list
  • Tag each line with the deal code name, the requester and the due time
  • Ask for a due time on any request that came without one
  • Delete the sticky notes and side lists once everything is in the master list

Deal folder structure on the group drive

When a VP asks for last Tuesday's comps at midnight, the difference between ten seconds and ten minutes is a folder structure you set up once. A standard tree for every deal, with the same subfolders for models, presentations, client materials, research, and an archive for superseded files, means you can find anything on any deal, and so can whoever covers for you.

First tasks

  • Ask your associate whether the group already has a standard deal folder tree
  • Write the tree on one page with a purpose line for each subfolder
  • Move the files on your busiest deal into the new structure
  • Repeat the move for each remaining live deal

File naming and version control convention

Sending v7 when the MD marked up v8 is one of the most common and most avoidable analyst errors. A naming rule with the deal code, the document, a date and a version number, plus a rule that superseded files move to the archive the moment a new one is saved, removes the guesswork about which file is live.

First tasks

  • Write your naming pattern in one line and pin it above your desk
  • Rename the current files on each live deal to the pattern
  • Move every superseded version into the archive subfolder
  • Tell each deal associate the pattern so their files match

Make it yours.

Install IB Analyst Workflow, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.