What the 2026.08.30 release changes
AuroraPrime RMA 2026.08.30 is an AI writing platform update for life-sciences teams who want more deliberate handling of document details, not just faster drafting. The updates address a familiar kind of friction: an information element that does not live under a stable heading, a TFL that needs more context, a caption controlled by Word, or a project that needs another document instance after work has already begun.
This article is for regulatory, medical-writing, clinical, CMC, and Lay Summary teams. It covers the product changes recorded in this release. It does not cover implementation planning, validation activities, or organization-specific procedures.
The general authoring updates are small but practical. When configuring an information element for AI extraction, users can now leave the section blank; RMA then begins extracting the requested information from the associated document's beginning. Copied content with an unavailable cross-reference is also handled more predictably: RMA resolves it inside the document where possible, or displays it without an unresolved active link.
| Release area | Documented update | Why a team may care |
|---|---|---|
| General authoring | Section selection can be blank for an information element. | Useful when relevant information appears early in a document rather than under a repeatable heading. |
| General authoring | Unavailable cross-references are resolved locally when possible. | Reduces distracting unresolved active links in copied content. |
| CSR | Inserted in-text tables retain tab-based indentation after view edits. | Helps preserve nested-table alignment and avoids unwanted spacing in narrow columns. |
| CSR | TFL mapping uses section-path and study-design context. | Gives reviewers more context when assessing suggested TFL scope. |
| CSR | TFL captions can use Word-managed numbering. | Lets a team keep its existing Word caption-style convention. |
| Lay Summary | TFLs from associated documents can be reused. | Extends a familiar reuse flow to Lay Summary work. |
| CMC | Template-based document instances can be added during authoring. | Supports projects that grow as additional information becomes available. |
More context for CSR TFL work
For teams evaluating clinical study report AI software, the CSR changes are about the objects around the narrative. Tables, figures, and listings carry meaning, but they also bring formatting, captioning, and scope questions into the document. The release does not remove those decisions. It gives the writer and reviewer a clearer place to make them.
First, RMA now preserves tab-based indentation in inserted in-text tables, including after a user edits a view. That matters most in a narrow column or nested layout, where a small spacing change can make a table harder to read. It is a formatting update, but it protects a document detail that reviewers notice quickly.
Second, AI-assisted TFL mapping now considers the section path and relevant study-design content when recommending TFLs for an in-text TFL. The recommendation can include more than one TFL, and Manage TFL shows the number of recommended items before the user proceeds. More suggestions are not automatically better. The helpful part is that the suggested scope is visible for review.
Third, teams that use Word caption styles can select No Label in RMA's Caption Format settings. RMA keeps the cross-reference target on the caption line, while Word manages the current caption number through the mapped caption style. This is a good fit when an existing Word convention, rather than the add-in, is the system of record for caption numbering.
Two reuse and setup improvements
Lay Summary and CMC work often start with a different problem from a CSR: how to bring the right existing material into the project without forcing the project structure to be complete on day one.
In Lay Summary documents, Reuse TFL from Associated Documents lets users select one or more associated documents and reuse their TFLs through the same workflow used for Clinical Summary documents. That creates a direct option for teams whose Lay Summary work needs to draw on material already connected to the project. The release describes the workflow; the team still decides which items are suitable for the intended audience and document.
For AI CMC authoring software workflows, the release allows a CMC writing project to add template-based document instances during authoring. Users can add multiple templates and configured attribute values together. RMA creates missing combinations without overwriting or duplicating existing document instances.
The distinction matters. A project that develops as information arrives should not have to choose between locking every document instance at creation and manually rebuilding structure later. The new option supports a more incremental setup, while leaving the team's document-selection and review decisions intact.
A practical way to review the release
The cleanest way to assess a release is to use one live workflow, not to run every new feature in isolation. Pick the route that matches your team's current work.
For CSR work, choose one in-text TFL. Check its indentation after a view edit, inspect the TFL recommendations, and decide whether Word-managed captions fit the document's caption convention.
For Lay Summary work, select a small set of associated-document TFLs. Review the reused material for the intended audience before treating it as ready for the document.
For CMC work, add one needed template-based document instance after project creation. Confirm that the selected template and attribute values create the expected missing combination.
For general authoring, test a document whose key information is on an introductory page. Configure an information element without a section and review the extracted result in the normal authoring workflow.
That sequence does not promise an outcome. It gives each group a compact way to see whether the changes fit the actual documents and conventions they use.
Frequently asked questions
What is included in AuroraPrime RMA 2026.08.30?
The release documents seven updates across general authoring, Clinical Study Report work, Lay Summary, and Chemistry, Manufacturing, and Controls projects. They include more flexible information-element extraction, cross-reference handling, three CSR TFL updates, Lay Summary TFL reuse, and incremental CMC document-instance setup.
Can RMA use Word-managed caption numbers for TFLs?
Yes. In the 2026.08.30 release, users can select No Label for Caption Format, map Caption to the desired Word caption style, and insert a TFL. RMA retains the cross-reference target while the mapped Word style manages the caption number.
Can Lay Summary documents reuse TFLs from associated documents?
Yes. Lay Summary documents can use Reuse TFL from Associated Documents to select one or more associated documents and reuse their TFLs through the workflow also available for Clinical Summary documents.
Can a CMC project add documents after it has been created?
Yes. CMC writing projects can add template-based document instances during authoring. The release notes state that RMA creates missing template-and-attribute combinations without overwriting or duplicating document instances that already exist.
Turn release changes into working choices
AuroraPrime RMA 2026.08.30 does not make every authoring decision for a team. It gives teams more options at the points where documents often become awkward: locating introductory information, maintaining table presentation, choosing TFL scope, managing caption numbering, reusing connected material, and extending a CMC project.
For an AI writing platform for life sciences, that is the right test. Do the new controls fit the way your writers and reviewers already work? Start with one representative document, test the applicable change, and decide where it belongs in your own process.
To discuss an AuroraPrime RMA workflow for your team, contact AlphaLife Sciences.
