SECTION 1

Each role starts at a different point in the workflow.

AUDIT TRAIL
Readily records who confirmed each step and when: relevance, notice type, requirements, actions, and dissemination. This creates an audit trail you can reference later.

Set up with Readily during onboarding. An Admin keeps it current.

SECTION 2

Organization Profile describes how your organization is structured. Readily sets it up with you during onboarding; after that, your Admin maintains it. It drives source suggestions, relevance rationale, impacted-department mapping, and dissemination recipients.

Fig. 1 — Organization Profile in the main navigation.

Only an Admin can edit Organization Profile. Update it when a department is renamed, a function moves, a lead changes, or a new line of business starts. New notices pick up the changes.

Fig. 2 — Organization Profile, showing departments and the functions each one owns.

SECTION 3

Sources is the last tab in Organization Profile. It lists every regulator, agency, and accrediting body Readily monitors. Readily suggests relevant sources based on your Organization Profile; turn each on or off. New notices from subscribed sources appear in your queue automatically.

Fig. 3 — The Sources tab. Turn each source on or off.

New notices start in the To review queue. A compliance analyst works each notice through five steps. Informational notices end at dissemination. Actionable notices move to In progress.

SECTION 4

Go to Regulatory Notices. The queue shows all notices from your subscribed sources, grouped by workflow stage. Filter, tag, and prioritize from here.

Fig. 4 — Go to Regulatory Notices to open the queue.

Open a notice from To review to start the five-step workflow (Sections 6–10).

After you subscribe to a source, To review only shows notices released from your subscription date forward. Notices the source released before you subscribed don't appear in the queue.

Fig. 5 — Review opens notices released before your subscription.

Fig. 6 — Add a previously released notice to To review.

SECTION 5

Upload guidance that doesn't come from a subscribed source. It follows the same workflow.

Fig. 7 — Upload new on the Regulatory Notices page.

Fig. 8 — The Upload Custom Documents dialog.

SECTION 6 · STEP 1 OF 5

Each notice screen shows the source document on the left and Readily's analysis on the right. In this step, the right panel shows a summary and the reason the notice applies to your organization, based on your Organization Profile.

Fig. 9 — Step 1: relevance summary and rationale beside the source document.

Your confirmation is recorded with your name and the date.

SECTION 7 · STEP 2 OF 5

This choice sets which workflow the notice follows. Readily suggests a type and explains why; confirm or change it.

Fig. 10 — Step 2: choose Informational or Actionable.

Confirm to continue. Steps 1 and 2 make up triage. Informational notices end at dissemination (step 5). Actionable notices then move to In progress (Part 3).

SECTION 8 · STEP 3 OF 5

Readily breaks the notice into individual requirements and lists them on the right. Each one is highlighted in the source document on the left.

Everything on the panel is editable. Edit summaries, classifications, or departments as needed, then confirm.

Confirm requirements one at a time, or use Confirm all after reviewing the set.

Fig. 11 — Requirement review. Each requirement is editable and confirmed individually or in bulk.

SECTION 9 · STEP 4 OF 5

Step 4 works like step 3, but for actions. An action is anything the regulator requires by a date, such as a deliverable, submission, or attestation. Example: a policy and procedure submission due within 90 days of an APL.

Fig. 12 — Step 4: actions and due dates.

CHECK THE DATES
A notice can have multiple dates, and the effective date may differ from the compliance date, even within one rule. Verify dates against the source document before you confirm.

SECTION 10 · STEP 5 OF 5

Compose and send the dissemination from within Readily. No export or separate email client is needed.

Readily suggests the impacted departments and their recipients, based on your Organization Profile. Add or remove departments and recipients, and enter anyone else under Additional recipients.

Fig. 13 — Recipients and template. Readily suggests departments from your Organization Profile.

Recipients get an email from the sender's name via Readily, with a link to the notice.

Fig. 14 — Attachments. The source document is attached by default.

After dissemination, departments plan and track implementation, and compliance reviews policy impact. When actions and policy work are closed, the notice moves to Completed.

SECTION 11 · FOR DEPARTMENTS

After dissemination, actionable notices move to In progress. The email link opens a department view of the notice for review and planning.

Fig. 15 — Requirements tab. Create action is in your department's section.

On the Requirements tab, choose Create action in your department's section. Then:

Fig. 16 — Creating an action against a requirement.

Each impacted department adds its own actions to the same notice.

Regulator actions from the notice and actions created by departments appear in one list, with owners and due dates, visible to everyone on the notice. Import existing implementation plans from a spreadsheet.

Tagged users get an email with a link to the action.

Fig. 17 — Attaching evidence and tagging a colleague on an action.

SECTION 12

The Policy impact tab compares confirmed requirements to the current versions of your policies in Policy Repo and lists policies with gaps.

Fig. 18 — The Policy impact tab, listing policies with gaps.

Choose Review redlines on a policy to open the current policy in its own template with suggested revisions marked. Each gap appears next to the proposed change.

Fig. 19 — Redline review against the current version of the policy.

Fig. 20 — Accepting or editing a suggested revision.

Accepting a redline is not policy approval. Approval happens in Policy Repo with the policy owner.

SECTION 13

After reviewing redlines, choose one of two routes based on how your organization reviews policy.

Fig. 21 — DOCX download and Submit to repository, top right of the redline view.

The draft keeps the redlines, so the policy owner and approver can see what changed and why. The notice's Policy impact tab then shows the policy as submitted.

SECTION 14

For reporting across modules, use Assistant. It reads data from your entire workspace.

Fig. 22 — Assistant. Past conversations are listed under History.

Assistant saves chat history. Star a conversation to pin it and reuse its context for recurring reports, such as committee and board materials.

QUICK REFERENCE

REMEMBER
Every summary, classification, department, and date is editable. Every confirmation is recorded with the user's name and date.

Readily
​Questions about this workflow? Contact your Readily implementation lead.

READILY · ORGANIZATION PROFILE & REGULATORY NOTICES · USER GUIDE · V1.0