1. IESBA Meeting New York, NY September 17-20, 2018
eCode
Don Thomson, Working Group Chair
Finn Partners, Jeff Nordstedt
IESBA Meeting
New York, NY
September 17-20, 2018

2. Topics for Discussion Objective of eCode initiative
Prototype demonstration
Features and functionalities
Next steps and timeline

3. Objective of eCode Initiative
Innovative web based tool with “app-like” features and functionalities
To enhance accessibility and ease of use
To facilitate learning, compliance and enforcement
To achieve consistent understanding and implementation of provisions in Code
For new/ infrequent users as well as experienced users
Support adoption and implementation of Code

4. eCode versus Print Code
Digital platform will better demonstrate “building blocks” approach and scalability
Interplay of overarching, general and topic-specific requirements
eCode features and functionalities will help guide appropriate application (e.g., filtering, smart search, interactive and dynamic cross-references)
Linkage to tools and other non-authoritative material to explain key concepts

5. eCode
General Features
Design suitable for smartphones, tablets and computers
Home page modeled after the Guide to the Code
Visual and interactive depiction of new architecture
Glossary more prominent
Several ways to easily access the Code
Easier to navigate Parts and Sections of the Code
Cross refer to relevant sections, Q&As, Basis for Conclusions & more
Clickable TOC
Ability to bookmark Share Copy/ print)Get help

6. Search Features Filters
eCode
Search Features
Filters
Auto-correct/ auto-completion; suggested terms to facilitate queries
Boolean search techniques (e.g., "and", "or", "but not“)
Toggling and "breadcrumbs" allow users to retrace steps

7. Next Steps Arrange beta testing and respond to feedback
eCode
Next Steps
Liaise with IFAC regarding user access
Use Board input to refine features and functionalities
Consider opportunities to enhance prototype
Notations/ highlighting and other e-book features
Additional search features/ saved results
Tracking that facilitates enhancements in future phases
Arrange beta testing and respond to feedback

8. Timeline Oct/Nov – Convert prototype into “staged website”
eCode
Timeline
Oct/Nov – Convert prototype into “staged website”
Dec Board meeting – Opportunity to use “staged website”
Dec/Jan – Beta testing
Jan/Feb – Respond to feedback
Mar Board meeting – Consider near-final eCode and matters relevant to its release
Apr/May – Launch eCode

9. Matters for Consideration
IESBA Members are asked for views about
The eCode prototype
The scope and timing for the development of the eCode
Any other matters that might be relevant to the development of the eCode