Prepare
Define the report scope and required sections.
Workflows and reports
Carry findings into owned, reviewable work.
Action Center and report building preserve the decision trail.
Assign findings, track review status, package evidence, and support recurring stakeholder reviews from the same operating context.
- Owners and priority
- Decision notes
- Report builder
- Scheduled review support
Lineage workflow is a product-level review mechanism, not a universal replacement for enterprise ITSM, project management, or records-management systems. Integration and retention requirements are assessed per customer environment.
Action Center
Implemented capabilityPreserve context when a review creates follow-up.
A validated change, cost, risk, or identity finding can move into Action Center with its operating context. The team can see what needs review, who owns it, and how the disposition changes over time.
- Finding and source context
- Owner, priority, and status
- Comments and decision record
Accountability
Implemented capabilityMake the disposition explicit.
Status and review notes help teams distinguish a new signal from validated work, deferred work, accepted context, or a completed follow-up. The exact governance process remains a customer operating decision.
- 01
Triage
Qualify the signal and identify the evidence still needed.
- 02
Own
Set accountable ownership and a visible priority.
- 03
Decide
Record the outcome and supporting rationale.
Review output
Implemented capabilityBuild stakeholder material from the investigation context.
The report builder supports structured report content drawn from Lineage review surfaces. Operators can prepare recurring or one-time output without reducing the report to disconnected screenshots.
- Structured report sections
- Selected operational findings and context
- Review before delivery
Recurring operations
Implemented capabilitySupport a repeatable review cadence.
Where configured, report schedules and delivery controls support recurring review workflows. Successful delivery depends on account configuration, mail infrastructure, recipients, and operational monitoring.
Schedule
Set the intended cadence and delivery configuration.
Monitor
Review execution and delivery status where exposed.
Governed paths
Implemented capabilityKeep write-class execution outside ordinary review workflow.
Azure Write and Deployment Mode are distinct advanced capabilities where enabled. They add identity, permission, policy, approval, execution, verification, and audit steps; an Action Center assignment alone does not authorize an Azure change.
- Separate analysis from execution
- Require configured controls and customer authorization
- Retain execution and verification records
Service and advisory
Service and advisoryMap Lineage to the operating process that already exists.
Swaves can help define review states, ownership, report cadence, and handoff points to external systems. Custom integrations, records obligations, and managed operations require separate scope and are not inherent in the standard public experience.
- Define the decision and ownership model
- Identify ITSM, reporting, and records boundaries
- Test the workflow with a real recurring review
Evaluate Lineage
Bring one recurring review workflow.
Map the finding, owner, decision, and report output to see where Lineage removes manual handoffs.