{"id":76837,"date":"2024-03-28T11:12:12","date_gmt":"2024-03-28T10:12:12","guid":{"rendered":"https:\/\/www.veeva.com\/eu\/?p=76837"},"modified":"2026-01-22T11:25:11","modified_gmt":"2026-01-22T10:25:11","slug":"global-approach-to-core-packages-simplify-to-speed-up-submissions-and-variations","status":"publish","type":"post","link":"https:\/\/pantheon.veeva.com\/eu\/blog\/global-approach-to-core-packages-simplify-to-speed-up-submissions-and-variations\/","title":{"rendered":"Global Approach to Core Packages: Simplify to Speed Up Submissions and Variations"},"content":{"rendered":"

Changing regulations, supply chain requirements, and challenges with staff continuity make local submissions preparation increasingly complex. Left unaddressed, this will lead to longer preparation timelines and more work for regulatory teams.<\/p>\n

There will always be a need for localized submission dossiers. Even submissions that apply to several markets require local content and generate specific health authority (HA) questions, which result in divergence from the core dossier. Nevertheless, by automating the dispatch and update cycles from core packages to local submissions, regulatory teams can achieve faster lifecycle variations.<\/p>\n

Traditional formats aren\u2019t effective<\/h2>\n

The core package format describes a set of documents prepared by headquarters and used in local market submissions. Initially intended to streamline and accelerate submission preparation, most formats used today result in tradeoffs between global and local teams.<\/p>\n

Core packages typically appear in two styles \u2014 and neither is perfect. The first is a comprehensive dossier based on the framework of a specific HA (usually in the U.S. or EU), which is adjusted for local divergence. Although this package is easier for global teams to manage, it\u2019s a heavier lift for the local affiliates responsible for reviewing content and submissions: they are required to deliver against specific local content requirements despite only globally common elements being available to them.<\/p>\n

The second style creates a core package for a subset of countries with similar requirements and links to content in common. Although it involves less effort for local offices, this approach quickly creates headaches for global teams, which monitor and adjust to changing local regulations.<\/p>\n

A hybrid core package approach that combines the positive aspects of each format can simplify review and approval cycles. For this to happen, global teams would create a single core package that ingests registered content, and then dispatch market-relevant documents for review [Figure 1]<\/strong>.<\/p>\n

Figure 1: Requirements for good core package management<\/strong><\/p>\n

\"\"<\/p>\n

Bringing global and local closer together<\/h2>\n

Rather than sequential processes, a more effective alternative is for global and local teams to work in parallel [Figure 2]<\/strong>.<\/p>\n

Following this approach, headquarters assesses submission documentation upfront and creates the global content plan before sharing it with local affiliates for review. Once received, local teams fill in missing information, prepare local documents, and initiate translations. Meanwhile, headquarters finalizes global documents (e.g., by pulling in registered documents into content plans) before notifying local offices that approved content is ready and dispatching it.<\/p>\n

Figure 2: Keeping parallel processes on track<\/strong><\/p>\n

\"\"<\/p>\n

Source: Veeva Business Consulting<\/em><\/p>\n

Local affiliates \u2014 whether outsourcing partners or internal regulatory teams \u2014 waste valuable time if required to locate and work with the correct document version. Technology underpins effective global-to-local collaboration by alleviating local teams\u2019 workload as they prepare, distribute, and submit to HAs.
\n\u2003<\/p>\n

When global and local teams use Veeva RIM<\/a>, they can:<\/p>\n

    \n
  1. Develop content plans more efficiently.<\/strong> Global content plans are generated automatically from templates, and include placeholders, while content is collected from different markets. <\/li>\n
  2. Ensure requirements are met on time.<\/strong> Section owners are assigned responsibilities and due dates, while real-time tracking means it\u2019s easy to identify which information is missing.<\/li>\n
  3. Identify changes in registered content.<\/strong> Features such as document auto-matching help teams locate approved content or lock specific document versions. Relevant groups (e.g., clinical, medical writing) view and use content in a controlled environment.<\/li>\n
  4. Share specific documents or sections.<\/strong> Local teams can partially or fully preview global content plans, which are dispatched iteratively.<\/li>\n
  5. Make comparisons with submission content plans.<\/strong> Submission content plans are automatically created from (and can be compared with) global content plans. Local teams can accept or reject proposed updates.<\/li>\n<\/ol>\n

    Simplify with each cycle<\/h3>\n

    As organizational understanding grows, global and local teams generally go through fewer review cycles. This means that despite regulatory complexity, the processes underpinning submissions will simplify over time \u2014 leading to faster submissions and fewer HA questions.<\/p>\n

    Register<\/a> to attend Veeva R&D and Quality Summit, Europe, to learn more about regulatory transformation.<\/p>\n","protected":false},"excerpt":{"rendered":"

    Preparing local submissions is increasingly complex. Regulatory teams can achieve faster lifecycle variations by rethinking the approach to core packages.<\/p>\n","protected":false},"author":377,"featured_media":76998,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"product":[1019],"area":[976],"coauthors":[1661,1627],"class_list":["post-76837","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","product-submissions","area-regulatory","blog-area-rd","blog-product-content-management","blog-html-content-yes"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/pantheon.veeva.com\/eu\/wp-json\/wp\/v2\/posts\/76837"}],"collection":[{"href":"https:\/\/pantheon.veeva.com\/eu\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pantheon.veeva.com\/eu\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pantheon.veeva.com\/eu\/wp-json\/wp\/v2\/users\/377"}],"replies":[{"embeddable":true,"href":"https:\/\/pantheon.veeva.com\/eu\/wp-json\/wp\/v2\/comments?post=76837"}],"version-history":[{"count":9,"href":"https:\/\/pantheon.veeva.com\/eu\/wp-json\/wp\/v2\/posts\/76837\/revisions"}],"predecessor-version":[{"id":92954,"href":"https:\/\/pantheon.veeva.com\/eu\/wp-json\/wp\/v2\/posts\/76837\/revisions\/92954"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pantheon.veeva.com\/eu\/wp-json\/wp\/v2\/media\/76998"}],"wp:attachment":[{"href":"https:\/\/pantheon.veeva.com\/eu\/wp-json\/wp\/v2\/media?parent=76837"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pantheon.veeva.com\/eu\/wp-json\/wp\/v2\/categories?post=76837"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pantheon.veeva.com\/eu\/wp-json\/wp\/v2\/tags?post=76837"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/pantheon.veeva.com\/eu\/wp-json\/wp\/v2\/product?post=76837"},{"taxonomy":"area","embeddable":true,"href":"https:\/\/pantheon.veeva.com\/eu\/wp-json\/wp\/v2\/area?post=76837"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/pantheon.veeva.com\/eu\/wp-json\/wp\/v2\/coauthors?post=76837"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}