Skip to main content
Chart and diagram generation lets Sofie turn a request into a visual output inside chat. Use it when you want a quick chart, process map, timeline, flowchart, or visual summary without opening a separate editor. This is different from CoSheet charts. CoSheet is best when the chart should stay tied to spreadsheet data. Chart and diagram generation is best when the visual is a chat output that helps you understand or explain a result.
Sofie can create useful visuals from your request and available context, but you should still review labels, groupings, source data, and assumptions before using the visual in controlled work.

​
When to use chart and diagram generation

Use chart and diagram generation when you need to see a pattern, sequence, relationship, or process. Good uses include:
  • A deviation investigation timeline.
  • A CAPA workflow or effectiveness check process.
  • A tech transfer dependency map.
  • A quality risk assessment decision tree.
  • A Gantt-style project plan.
  • A sequence diagram for handoffs between teams or systems.
  • A mindmap for protocol sections, source gaps, or follow-up questions.
  • A horizontal bar chart for top finding categories.
  • A pie or bar chart for percentage breakdowns.
  • A visual summary of a File Studio or CoSheet analysis.

​
Choose the right surface

NeedUse
A quick chart, diagram, flow, timeline, or visual summary in chatChart and diagram generation
Editable spreadsheet data with formulas, pivots, and chartsCoSheet
A downloadable Office file, generated PowerPoint, or code-based file outputFile Studio
Inspection of an existing chart, figure, image, PDF, or slideFile Query
Source-backed narrative around a visualChat with selected sources or Workspace search
If Sofie returns a table when you wanted a visual, say Create this as a chart or diagram in chat.

​
Ask for a chart

Name the chart type, data, grouping, and review goal.
1

Provide the source

Attach the file, select the CoSheet, add the Workspace, or paste the data summary Sofie should use.
2

Name the visual

Ask for a chart type such as horizontal bar, line, pie, scatter, or timeline.
3

Define the grouping

Tell Sofie which fields belong on the axis, legend, labels, or time scale.
4

Ask for a source check

Ask Sofie to list the data used, exclusions, units, and assumptions before or after creating the chart.
Good prompts: 
Create a horizontal bar chart showing deviation findings by category. Use the attached tracker. Include category name, count, and a short note about any grouping assumptions.

Create a line chart of assay result trend by lot. Use the selected CoSheet range. Show the date on the x-axis and result value on the y-axis. List missing or excluded values before creating the chart.

Create a pie chart showing CAPA status distribution from this table. Use Open, In progress, Pending effectiveness check, and Closed as categories.

​
Ask for a diagram

Use diagrams when the order, relationship, or decision path matters more than the numbers. Common diagram requests:
DiagramUse it for
FlowchartProcess steps, review paths, escalation logic, triage workflows.
TimelineInvestigation events, batch milestones, meeting follow-ups, evidence chronology.
Gantt-style planWorkstreams, owners, dependencies, and target dates.
Sequence diagramHandoffs between teams, systems, roles, or review stages.
Decision treeQuality risk decisions, disposition logic, next-check recommendations.
MindmapSource gaps, protocol sections, stakeholder questions, training topics.
Relationship mapLinks between systems, records, documents, teams, or data sources.
Good prompts: 
Create a flowchart for this deviation triage process. Include intake, initial impact assessment, immediate containment, investigation path, QA review, CAPA decision, and closure.

Create a timeline of the investigation events from the attached meeting notes and deviation summary. Mark dates with missing source support as "needs confirmation."

Create a decision tree for whether a CAPA effectiveness check needs additional sampling. Separate confirmed source rules from suggested decision points.

​
Use visuals after analysis

Chart and diagram generation works well after Sofie has already analyzed sources. For example:
  1. Ask Sofie to profile a CoSheet or source file.
  2. Review the findings, exclusions, and assumptions.
  3. Ask Sofie to create a visual from the reviewed result.
  4. Ask Sofie to explain what the visual supports and what it does not prove.
Good follow-up: 
Using the analysis you just completed, create a visual summary with one horizontal bar chart for finding categories and one timeline for major investigation events. Keep unverified events marked as assumptions.

​
Review the visual

Before you use a generated chart or diagram, check:
  • The source file, Workspace, CoSheet, or data range used.
  • Axis labels, units, dates, and category names.
  • Whether counts, percentages, and totals match the source.
  • Whether the chart type fits the question.
  • Whether the visual hides missing values, outliers, or excluded records.
  • Whether the diagram introduces steps, decisions, owners, or dates that were not in the source.
  • Whether the visual needs SME review before it appears in a quality, clinical, regulatory, or controlled-process document.
Ask Sofie: 
Review this chart before I use it. List the source data, included records, excluded records, grouping assumptions, label issues, and anything that needs SME confirmation.

​
Refine the output

Use direct correction prompts.
GoalPrompt
Change chart typeMake this a horizontal bar chart instead of a pie chart.
Clarify labelsUse full category names and include units on the y-axis.
Reduce clutterRemove data labels except for the top five categories.
Show uncertaintyMark unconfirmed dates as "needs confirmation".
Use reviewed data onlyUse only the reviewed table from the previous message.
Separate facts from assumptionsKeep source-backed facts and assumptions in separate sections below the visual.
Create a file insteadUse File Studio to place this visual in a downloadable PowerPoint file.