A tailored course, built for your situation
Executive visibility on COSO control decisions previously overlooked
A tailored course for senior project managers embedding governance into complex delivery environments
The situation this course is for
Strong project-level control implementation routinely gets absorbed into broader reporting, leaving individual contributions invisible at the leadership level. This creates a ceiling on recognition, even when outcomes are strong.
Who this is for
Senior Project Manager in financial services driving delivery within regulated frameworks, accountable for control integration but not formally responsible for governance reporting
Who this is not for
Junior project coordinators, auditors focused only on test execution, or consultants without embedded delivery experience
What you walk away with
- Control decisions documented with executive-facing clarity
- Structured artefacts that surface into leadership updates
- Increased frequency of direct inquiries from risk and compliance leads
- Recognition as a contributor in formal control reviews
- Ability to point to specific, named decisions in COSO-aligned documentation
The 12 modules (with all 144 chapters)
- COSO Principle 1 alignment at project initiation
- Defining control objectives alongside scope
- Integrating governance timelines with delivery sprints
- Identifying decision points for control embedding
- Documenting assumptions for auditors
- Flagging variances in real time
- Creating decision logs tied to COSO
- Linking RACI to control ownership
- Using change requests to update control design
- Capturing exceptions in governance language
- Version control for audit-ready artefacts
- Handover protocols for continuity
- Positioning controls as risk-informed trade-offs
- Using business impact language
- Translating technical decisions for leaders
- Framing delays as risk reduction
- Highlighting upstream prevention
- Naming the cost of inaction avoided
- Tying controls to client outcomes
- Connecting governance to value delivery
- Contrasting reactive vs proactive design
- Using stakeholder quotes in narratives
- Benchmarking against peer incidents
- Positioning controls as defaults
- Executive summary templates
- One-page control overviews
- Highlighting key decisions made
- Using callouts for visibility
- Formatting for skimmability
- Annotating changes for clarity
- Creating version summaries
- Adding decision rationale boxes
- Linking to broader risk posture
- Balancing detail and brevity
- Using visuals without fluff
- Archiving supporting detail
- Inserting control updates into status reports
- Using standard slide placements
- Claiming ownership in governance dashboards
- Naming contributors in summaries
- Aligning with SOX 404 reporting windows
- Timing submissions for review cycles
- Securing placement in risk committee packs
- Linking project outcomes to control strength
- Using consistent terminology
- Highlighting completed control phases
- Flagging upcoming governance milestones
- Requesting feedback loops
- Anticipating auditor follow-ups
- Preparing supporting evidence
- Using COSO language precisely
- Citing framework sections
- Documenting deviation justifications
- Showing consistency across projects
- Referencing internal policies
- Linking to Macquarie-specific standards
- Handling scope change questions
- Explaining control layering
- Clarifying ownership boundaries
- Responding to control gaps
- Standard decision log formats
- Reusable control narratives
- Template libraries for common controls
- Customising for project type
- Versioning governance artefacts
- Creating modular content
- Building repository structures
- Indexing for searchability
- Adding metadata tags
- Linking to project management tools
- Automating updates
- Sharing across teams
- Setting control expectations in RFPs
- Reviewing vendor control narratives
- Flagging misalignments early
- Requiring COSO traceability
- Holding vendors to documentation standards
- Conducting control walkthroughs
- Documenting vendor accountability
- Managing third-party exceptions
- Using SLAs to enforce compliance
- Creating vendor scorecards
- Handling subcontractor controls
- Escalating unresolved gaps
- Framing recommendations as options
- Using data to de-escalate conflict
- Inviting input to build ownership
- Positioning yourself as facilitator
- Documenting group decisions
- Attributing contributions fairly
- Using neutral language
- Avoiding ownership disputes
- Aligning with enterprise standards
- Escalating only when necessary
- Maintaining neutrality
- Summarising outcomes clearly
- Accessing Macquarie's risk appetite statement
- Mapping decisions to tolerance levels
- Using risk heatmaps
- Aligning with capital planning
- Highlighting risk reduction impact
- Connecting to regulatory expectations
- Showing consistency with past incidents
- Benchmarking against peer firms
- Using tone from the top messaging
- Linking to strategic goals
- Articulating residual risk
- Showing escalation paths
- Anticipating executive questions
- Preparing one-on-one briefings
- Creating defence dossiers
- Rehearsing key messages
- Identifying allies in advance
- Flagging unresolved items
- Using pre-review checklists
- Securing sign-offs early
- Highlighting improvements made
- Positioning lessons learned
- Owning narrative framing
- Following up on feedback
- Sharing templates proactively
- Volunteering for cross-project roles
- Presenting at internal forums
- Mentoring junior staff
- Contributing to standards
- Publishing internal case studies
- Seeking feedback from auditors
- Responding to peer requests
- Building reputation through reliability
- Tracking recognition instances
- Leveraging informal networks
- Cultivating sponsor relationships
- Documenting for onboarding
- Creating knowledge transfer packs
- Using standard nomenclature
- Aligning with enterprise taxonomies
- Building audit trails
- Indexing decisions over time
- Establishing review rhythms
- Creating living artefacts
- Updating for new regulations
- Archiving legacy decisions
- Naming contributors permanently
- Linking to role descriptions
How this maps to your situation
- When starting a new project with COSO implications
- During mid-cycle governance reporting
- Preparing for external audit cycles
- Responding to leadership inquiries on control posture
Before vs. after
What's included with your purchase
- 12 modules with 12 chapters each (144 chapters)
- Downloadable templates and worked examples for every module
- Hand-built implementation playbook delivered alongside course access
- 30-day money-back guarantee
Delivery and format
- Course and learning environment access provisioned within 24 hours of purchase
- Hand-built implementation playbook delivered alongside course access
Format: Text-based modules and chapters in the Art of Service learning environment, plus downloadable templates and worked examples for every chapter, plus the hand-built implementation playbook delivered alongside course access.
Time investment: Approximately 3 hours per module, designed to be completed alongside active project work over 6-8 weeks.
How this compares to the alternatives
Unlike generic compliance courses, this program is tailored to senior project managers in financial services who need to elevate the visibility of their governance contributions without stepping outside their role.
Frequently asked
Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.