
GITNUXSOFTWARE ADVICE
Cybersecurity Information SecurityTop 10 Best Conflict Software of 2026
Ranked top 10 conflict software tools for teams and enterprises, covering security and features, with options like CrowdStrike, Precisely, Juro.
How we ranked these tools
Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.
Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.
AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.
Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.
Score: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
If you’re doing repeatable conflict clause review tied to daily matter intake, Precisely is the safest pick, whereas Juro fits teams that want conflict clearance built into draft and approval handoffs with a clear decision trail.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Precisely
Policy-linked clearance tracking that maintains a trace from potential conflict to final clearance decision.
Built for fits when legal operations needs repeatable conflict search with clearance tracking during daily matter intake..
Juro
Editor pickApproval records can capture conflict clearance outcomes and decision notes as part of the same intake workflow.
Built for fits when legal ops needs conflict clearance approvals tied to matter intake and downstream document handoff..
ClauseBase
Editor pickConflict results link directly to document intake artifacts so hit review shows the evidence behind each flag.
Built for fits when conflict checks must tie reviewer decisions to intake and preserved evidence..
Related reading
Comparison Table
Precisely
specialistContract review software focused on identifying mismatched and conflicting clauses in legal documents.
Policy-linked clearance tracking that maintains a trace from potential conflict to final clearance decision.
Precisely is positioned for legal operations that need consistent conflict search logic during matter intake and engagement letter review. The system centers on party and matter records, match rules, and a workflow trail that links potential conflicts to clearance decisions. Name normalization and alias matching are built for entity resolution scenarios where the same person or organization appears with variants.
A tradeoff is that teams can end up tuning conflict search logic over multiple cycles when alias coverage and match thresholds need alignment with internal policy. Precisely fits best for daily conflict report workflows where screening must run on every new intake and where auditability of clearance choices matters.
- +Configurable match rules to control hit review volume
- +Alias and name normalization improve entity resolution accuracy
- +Matter intake workflow keeps clearance decisions linked to records
- +Exported results support reporting and downstream case handling
- –Match logic tuning can take iterative governance cycles
- –Fewer workflow customization knobs than enterprise intake suites
- –Complex multi-firm party role mapping may require process alignment
- –Integration depth can depend on how results are exported
Legal operations teams
Run daily conflict report on intake
Fewer missed conflicts
General counsel and compliance
Standardize conflict search logic
More consistent approvals
Show 2 more scenarios
Outside counsel managers
Screen prior representation for matters
Lower false negative rate
Uses alias and name normalization to locate prior representation and related entities.
Intake coordinators
Triage potential conflicts faster
Reduced review workload
Directs hit review around match rules and maintains context for matter intake.
Best for: Fits when legal operations needs repeatable conflict search with clearance tracking during daily matter intake.
More related reading
Juro
SMBContract automation software that centralizes drafting, approvals, and version control to reduce agreement conflicts.
Approval records can capture conflict clearance outcomes and decision notes as part of the same intake workflow.
Juro’s core fit is workflow control around legal decisions, not only reporting. Matter intake workflows can route submissions to conflict review, collect inputs, and capture the clearance outcome in the same place where the engagement documents are prepared. The automation surface supports branching based on whether the conflict search produced hits, and it can attach those results to the approval record. Juro’s API supports building custom conflict search logic and pushing results back into the workflow for docketing or downstream systems.
A key tradeoff is that Juro does not replace a dedicated conflict-search engine for entity resolution and fuzzy matching, so teams still need their screening data source and logic. Juro works best when the organization already has an adverse party check workflow and wants consistent approvals, audit trails, and document handoff tied to each case intake.
- +Workflow-first conflict clearance with recorded outcomes per intake
- +Automation rules route approvals based on screening hit status
- +API supports syncing conflict results into matter records
- +Integrations help carry decisions into engagement and document steps
- –Requires external screening logic for entity resolution and fuzzy matching
- –Workflow governance needs careful configuration to avoid inconsistent routing
- –Advanced governance reports require setup of form and role patterns
- –Higher configuration effort than single-purpose conflict tools
Legal operations teams
Standardize conflict clearance approvals
Fewer clearance inconsistencies
Law firm intake managers
Triage new business intake requests
Faster intake throughput
Show 2 more scenarios
Corporate legal teams
Link conflict outcomes to engagement letters
Reduced policy exceptions
Recorded clearance status attaches to engagement document workflows to prevent drafting before clearance.
Security and compliance leads
Audit and control conflict decisions
Tighter governance evidence
Configured access paths and stored decision records support reviewable history for each clearance request.
Best for: Fits when legal ops needs conflict clearance approvals tied to matter intake and downstream document handoff.
ClauseBase
specialistLegal drafting platform for standardizing clauses and reducing conflicts across templates and negotiated documents.
Conflict results link directly to document intake artifacts so hit review shows the evidence behind each flag.
ClauseBase is designed for conflict search workflows that start from new business intake and engagement letter conflict inputs, then map parties into a screening process that produces review-ready outputs. The system records screening decisions and preserves an audit trail that links flags to the underlying input data and the reviewer outcome. Integration depth is strongest when intake and matter workflows can push structured party and document metadata into the screening run. Governance is supported through controlled screening logic and retained conflict archive records for repeat reviews.
A key tradeoff is that clause-derived screening depends on the quality of document capture and field extraction, so messy or inconsistent intake metadata can raise the false positive rate. ClauseBase fits teams that run daily conflict report routines and need consistent hit review packaging for attorneys to approve or clear. It also suits organizations that want conflict search logic centralized so different matter teams see the same screening behavior.
- +Rule-driven conflict clearance outputs tied to intake artifacts
- +Conflict archive preserves screening inputs and reviewer decisions
- +Designed for matter-by-matter reviewer workflows and hit review
- +Integrates with intake pipelines and downstream clearance steps
- –Document field quality affects false positive rate
- –Complex screening logic needs careful governance discipline
- –Advanced matching behavior can require iterative tuning
- –Some workflows need custom mapping for party roles
Legal ops teams
Daily screening for new business intake
Faster clearance processing cycles
Conflicts attorneys
Engagement letter conflict review
More defensible review decisions
Show 2 more scenarios
Matter management teams
Matter intake workflow conflict flagging
Fewer missed screening steps
Triggers conflict checks during matter intake and routes flags to the correct reviewer flow.
Enterprise compliance leads
Adverse party checks at scale
Consistent policy enforcement
Centralizes conflict search logic and retains outcomes for recurring refresh and re-checks.
Best for: Fits when conflict checks must tie reviewer decisions to intake and preserved evidence.
Relativity Contracts
enterpriseContract analysis software with conflict identification for legal and compliance workflows.
Conflict-clearance workflow automation built as part of Relativity case processing, tied to Relativity objects and audit history.
Relativity Contracts provides conflict-check workflows tied to Relativity data and case processing, which makes it practical for teams already standardized on Relativity. It supports matter intake and document review workflows inside the same environment, so conflict logic can be run alongside production, tagging, and audit-friendly work.
Automation features cover configurable intake steps and repeatable clearance processes for consistent daily conflict reports. Extensibility through Relativity’s API surface enables custom conflict search logic and integrations with identity and case management systems.
- +Native workflow alignment with Relativity matters and document review operations
- +Relativity API enables custom conflict search logic and intake integrations
- +Repeatable intake and clearance steps reduce variability across teams
- +Audit-friendly configuration supports defensible conflict clearance records
- –Heavier governance is required to keep role mapping and party data consistent
- –Conflict archive retrieval depends on consistent linking between intake and matters
- –Advanced fuzzy matching and entity resolution often require custom configuration
- –Admin effort rises when multiple intake sources feed the same clearance queue
Best for: Fits when Relativity-based legal teams need conflict clearance automation with custom intake and identity integrations.
ContractSafe
SMBContract management software with search, alerts, and review workflows for finding inconsistent obligations and terms.
Matter-linked conflict archive that preserves reviewer decision trails and historical flags for repeat intake checks.
ContractSafe performs contract intake and conflict screening workflow management tied to matter records and participant roles. It centralizes conflict logic outputs such as potential conflict flags and maintains a conflict archive tied to cleared or rejected matters.
The system focuses on operational governance for the screening process, including audit-ready trails for decisions and reviewer actions. Automation hooks support moving screened results into downstream intake steps without manual copy and paste.
- +Ties screening decisions to matter intake so reviewers see role context
- +Maintains a conflict archive to support repeat checks and historical review
- +Supports workflow automation from intake to clearance steps
- +Tracks reviewer actions to support internal audit trails
- –Conflict results are only as reliable as the entered party names and aliases
- –Automation depends on the accuracy of role mapping in intake records
- –Deep integration with docketing systems may require custom configuration
- –Advanced search behavior can increase false positive rates without tuning
Best for: Fits when legal operations needs governed conflict clearance linked to matter intake workflows.
Onit Contract Lifecycle Management
enterpriseEnterprise CLM software that supports clause control, approval workflows, and review of conflicting contract terms.
Workflow-driven contract routing that preserves audit trails across drafting, approvals, and outside-counsel handoffs.
Onit Contract Lifecycle Management organizes contract intake, review workflows, and e-signature routing with configurable stages and approvals. It is distinct for how contract records connect to matter-related work products through shared identifiers and workflow links.
Core capabilities include clause and template management, task assignment with audit trails, and standardized review checkpoints for outside counsel. The system also provides administration tooling for role-based access, policy-driven routing, and change history across contract lifecycle events.
- +Configurable review workflows with role-based approvals and persistent task history
- +Contract templates and clause content can be reused across drafting cycles
- +Audit trail captures edits, status changes, and routing decisions per contract
- +Matter and contract records can stay linked through shared operational identifiers
- –Conflict-specific screening depth depends on integration with the screening workflow
- –Workflow configuration requires governance discipline to avoid inconsistent routing
- –Admin reporting favors contract operations over advanced conflict analytics
- –High-volume intake can need tuned automation to maintain throughput
Best for: Fits when legal teams standardize contract workflows and need audit-grade governance around intake and review.
CobbleStone Contract Insight
enterpriseContract lifecycle management software for tracking obligations, clauses, approvals, and conflicting terms.
Intake-driven conflict clearance workflows that persist the triggering attributes and decision outcomes on the same record.
CobbleStone Contract Insight focuses on contract and matter intake workflows that feed conflict checking with structured party, role, and document data. It distinguishes itself with automation hooks that connect intake events to recurring conflict search logic and clearance workflows.
The system emphasizes traceability from a flagged potential conflict through the resolution outcome stored against the intake record. Integration options center on exporting intake fields to conflict search steps and maintaining an audit trail for what triggered each check.
- +Workflow automation ties intake fields to conflict clearance steps
- +Stored resolution outcomes keep decisions linked to the originating intake
- +Audit trail records which intake attributes drove potential conflict flags
- +Configurable rules support repeatable conflict check patterns per matter type
- –Setup requires disciplined mapping of party roles to intake fields
- –Alias matching coverage depends on configured identity sources and normalization rules
- –Fuzzy matching tuning can increase false positive volume without governance
- –Advanced reporting needs exports when daily conflict report formats are fixed
Best for: Fits when contract and intake teams need automated conflict clearance tied to matter records.
Concord
SMBContract management software with collaborative editing and approval controls that help prevent document conflicts.
Configurable name matching with per-workflow clearance outputs that retain a linked audit trail for later conflict archive retrieval.
Concord is a conflict-check and conflict-search workflow tool used to manage intake, screening logic, and matter-level outputs.
It centers on configurable matching to reduce missed aliases and handle name variations during adverse party checks.
Concord also supports an auditable record of clearance decisions for later conflict archive retrieval.
Admin controls focus on user permissions, shared configuration, and governance around who can mark clearances and run new business intake reviews.
- +Configurable matching logic reduces alias misses in adverse party checks
- +Matter-level clearance outputs stay attached to the intake workflow
- +Audit trails support later conflict archive retrieval for cleared decisions
- +Role-based access limits who can approve conflict clearances
- –Fuzzy matching tuning needs governance to manage false positive rate
- –Indexing and re-screening large historical parties can slow operations
- –Workflow customization requires more setup than template-driven tools
- –API surface is oriented to workflow actions more than deep data mapping
Best for: Fits when mid-size firms need configurable conflict search logic with approval auditability for new business intake.
iManage Work
enterpriseDocument and email management software used by law firms for conflict and matter intake workflows.
Matter-scoped governance with end-to-end audit logging across access and workflow actions for conflict-related reviews.
iManage Work manages legal document and matter workflows with tight controls over records, permissions, and collaboration. It supports conflict check workflows through integrations with matter intake and searchable matter indexes that let users run conflict search logic across names and party roles.
iManage Work also provides audit logging and administrative governance for retention, access patterns, and operational traceability across case activity. Its extensibility and automation options matter most when intake, docketing, and outside-counsel handling must stay consistent across high throughput case volumes.
- +Granular RBAC and matter-scoped permissions reduce cross-matter exposure risk
- +Audit log coverage supports review of access and changes tied to matters
- +Automation hooks fit intake-to-matter routing and conflict workflow consistency
- +Search across matter artifacts supports practical conflict archive workflows
- –Conflict search quality depends heavily on name normalization inputs
- –Workflow configuration for screening steps can require governance discipline
- –Deep integration with external intake systems may need custom mapping effort
- –Some screening automation requires administrator time to tune rules
Best for: Fits when enterprises need governed matter workflows with repeatable conflict screening and audit traceability across intake.
Intapp Conflicts
enterpriseConflict clearance software for law firms that automates intake, search, routing, and approval workflows.
Party role mapping and policy-driven relationship checks that keep hit review consistent across intake and matter events.
Intapp Conflicts is used for legal conflict search and conflict clearance workflows tied to new business intake and case lifecycle events. It combines automated conflict checking logic with a structured conflict matrix view to support hit review and consistent clearance decisions.
The product supports configuration around party roles and representation relationships so the system can apply the same conflict of interest policy across matters. For teams that need governance, Intapp Conflicts provides auditability of decisions and integration hooks for aligning intake and docketing data.
- +Configurable conflict search logic aligned to role-based representation relationships
- +Structured hit review flow supports consistent clearance decisions
- +Audit trail for conflict outcomes supports governance needs
- +Integration hooks help keep intake and matter data synchronized
- –Deep configuration requires disciplined governance to avoid policy drift
- –Setup and mapping of party data can take significant effort
- –Hit review throughput depends on data normalization quality
- –Advanced workflows require administrator involvement for changes
Best for: Fits when law firms need policy-driven conflict clearance with governed decision trails and reliable intake integration.
Conclusion
After evaluating 10 cybersecurity information security, Precisely stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
How to Choose the Right conflict software
Conflict software automates conflict checks and conflict clearance decisions during daily intake and matter processing, so legal operations can keep repeat reviews consistent. This guide covers Precisely, Juro, ClauseBase, Relativity Contracts, ContractSafe, Onit Contract Lifecycle Management, CobbleStone Contract Insight, Concord, iManage Work, and Intapp Conflicts.
The biggest differences show up in how each tool ties screening hits to intake artifacts, how it records approval outcomes for audit traceability, and how much configuration control it exposes for match rules and governance. The evaluation also emphasizes integration depth and an automation or API surface that can carry conflict archive and decision records across matter workflows.
Conflict clearance software that automates conflict checks, hit review, and decision trails across intake workflows
Conflict software runs conflict search logic against party data and produces matter or intake-scoped clearance outputs that record why a flag was raised and what decision was made. Tools like Precisely focus on policy-linked clearance tracking from potential conflict to a final clearance decision with configurable match rules and entity normalization.
Other platforms anchor the workflow differently, such as Relativity Contracts building conflict-clearance automation inside Relativity case processing with audit history tied to Relativity objects. ClauseBase emphasizes traceability by linking conflict results to document intake artifacts so reviewers can see the evidence behind each flag during hit review.
Conflict software features to verify for reliable clearance decisions
Conflict software must connect conflict check outputs to the intake or matter record so hit review can show why a flag appeared and what decision followed.
Tools differ most in how they carry screening evidence, decision outcomes, and archive context through the workflow so repeat intake checks and audit traceability stay consistent.
Policy-linked clearance tracking from potential conflict to final decision
Precisely tracks a full path from potential conflict to a final clearance decision with policy-linked clearance tracking. ClauseBase links conflict results directly to document intake artifacts so reviewers see the evidence behind each flag.
Approval records tied to intake outcomes and decision notes
Juro stores approval records that capture conflict clearance outcomes and decision notes in the same intake workflow. Onit Contract Lifecycle Management preserves audit-grade governance across drafting, approvals, and outside-counsel handoffs with persistent task history.
Conflict archive and evidence preservation for repeat intake and historical review
ContractSafe maintains a matter-linked conflict archive that preserves reviewer decision trails for repeat intake checks. Precisely and ClauseBase both preserve archive context, with Precisely maintaining clearance decision traceability and ClauseBase preserving screening inputs and reviewer decisions.
Workflow automation embedded in a case or matter processing environment
Relativity Contracts builds conflict-clearance workflow automation inside Relativity case processing with audit history tied to Relativity objects. iManage Work applies matter-scoped governance with end-to-end audit logging across access and workflow actions for conflict-related reviews.
Configurable match rules and entity normalization for hit review quality
Precisely offers configurable match rules that control hit review volume and uses alias and name normalization to improve entity resolution accuracy. Concord provides configurable name matching with per-workflow clearance outputs that retain a linked audit trail.
Role mapping and relationship checks that keep decisions consistent across events
Intapp Conflicts uses party role mapping and policy-driven relationship checks so hit review stays consistent across intake and matter events. CobbleStone Contract Insight persists triggering attributes and decision outcomes on the same record to tie clearance steps back to intake fields.
Choose by workflow anchoring, clearance traceability, and configuration control
The right tool depends on where conflict clearance must “live” in the legal workflow and how the system records the decision trail that reviewers rely on during hit review.
The selection hinges on integration depth and automation control over screening logic, approval outcomes, and archive retrieval so governance can be enforced without slowing operations.
Start with the workflow system that must own clearance decisions
If clearance decisions must be created inside a specific matter or case engine, Relativity Contracts aligns conflict-clearance workflow automation with Relativity matters and audit history. If governance must be anchored in enterprise permissions and matter-scoped audit logging, iManage Work provides granular RBAC and matter-scoped permissions for conflict-related reviews.
Select based on how the tool ties a hit to evidence and a decision outcome
If reviewers need evidence attached to the intake artifacts, ClauseBase links conflict results to document intake artifacts so hit review shows the evidence behind each flag. If the workflow must move from potential conflict to a final clearance decision with traceability, Precisely provides policy-linked clearance tracking that preserves the path to the decision.
Pick the configuration style that fits governance maturity
If governance teams can iterate on match logic and tuning cycles, Precisely supports configurable match rules that control hit review volume. If governance requires clear approval routing with configuration discipline to avoid inconsistent outcomes, Juro routes approvals based on screening hit status and keeps approval records with decision notes.
Validate archive retrieval paths for repeat intake and historical review
If repeat intake checks must use a matter-linked history with reviewer trails, ContractSafe maintains a conflict archive tied to matter intake workflows. If the organization expects that archive context depends on linking intake and matters consistently, Relativity Contracts requires consistent linking between intake and matters for conflict archive retrieval.
Confirm entity resolution inputs and role mapping coverage before scaling intake volume
If conflict search quality depends on name normalization and role mapping accuracy, Concord’s fuzzy matching tuning requires governance to manage false positive rate. If policy-driven relationship consistency is required across intake and matter events, Intapp Conflicts focuses on party role mapping and structured hit review flow.
Who benefits most from conflict software that records decision trails
Conflict software fits teams that run daily conflict checks and need consistent conflict clearance decisions across intake, matter processing, and downstream approvals.
The largest gains come when the tool preserves screening inputs, reviewer decisions, and approval outcomes in the record that intake and matter workflows already use.
Legal operations teams running daily intake conflict checks
Precisely fits when repeat intake workflows need policy-linked clearance tracking that preserves trace from potential conflict to final clearance decision. CobbleStone Contract Insight fits when intake teams need conflict clearance tied to the same record with stored resolution outcomes.
Law firms and practice groups standardizing clearance approvals
Juro fits when approval records must capture conflict clearance outcomes and decision notes inside the intake workflow. Onit Contract Lifecycle Management fits when audit trails must persist across drafting approvals and outside-counsel handoffs tied to conflict-governed routing.
Enterprises consolidating conflict review governance and access controls
iManage Work fits when matter-scoped governance and end-to-end audit logging must cover access and workflow actions for conflict-related reviews. Relativity Contracts fits when Relativity-based case processing must own conflict-clearance automation with audit history tied to Relativity objects.
Teams with complex party relationships that must stay consistent across events
Intapp Conflicts fits when policy-driven relationship checks and party role mapping must keep hit review consistent across intake and matter events. ContractSafe fits when governed conflict clearance must connect reviewer decision trails to matter intake workflows for repeat checks.
Common failure modes when buying and implementing conflict software
Conflict software fails when the hit review workflow cannot explain why a flag was raised or when archive context cannot be retrieved later for governance or repeat checks.
Most implementation issues come from mismatch between intake data quality and the configuration used for match rules, identity sources, and role mapping.
Treating conflict archive as a separate system instead of a workflow-linked record
Choose tools that preserve conflict results and decisions in a place reviewers can retrieve later, like ContractSafe’s matter-linked conflict archive or ClauseBase’s conflict archive that preserves screening inputs and reviewer decisions. Avoid setups where archive retrieval depends on inconsistent linking between intake and matters, as seen in Relativity Contracts when those links are not kept consistent.
Letting match rule tuning drift from governance expectations
Precisely’s configurable match rules can control hit review volume but still require iterative governance cycles to keep governance aligned. Concord’s fuzzy matching tuning also needs governance to manage false positive rate when large historical parties must be indexed and re-screened.
Starting rollout without validating entity resolution inputs and field completeness
ClauseBase flags that document field quality affects false positive rate, so intake field standards must be enforced before scale. ContractSafe also notes that conflict results reliability depends on entered party names and aliases, so alias and role mapping accuracy must be tested against real intake records.
Configuring workflow routing without aligning party role mapping and identity sources
CobbleStone Contract Insight requires disciplined mapping of party roles to intake fields and depends on configured identity sources and normalization rules for alias matching. Juro requires external screening logic for entity resolution and fuzzy matching, so the approval routing logic must be validated with real screening hit status inputs.
How We Selected and Ranked These Tools
We evaluated Precisely, Juro, ClauseBase, Relativity Contracts, ContractSafe, Onit Contract Lifecycle Management, CobbleStone Contract Insight, Concord, iManage Work, and Intapp Conflicts using feature depth, workflow fit, and governance traceability. Feature depth accounted for 40% of the score, focusing on conflict clearance tracking, conflict archive linkage, and whether approval outcomes remain attached to intake artifacts.
Ease of use plus value each accounted for 30%, emphasizing configuration friction for match rules, identity normalization, and role mapping that can affect hit review throughput and false positive rate. Precisely led the ranking because its policy-linked clearance tracking maintains a trace from potential conflict to the final clearance decision and its configurable match rules plus alias and name normalization improved entity resolution accuracy while controlling hit review volume.
Frequently Asked Questions About conflict software
How do Precisely and Concord handle name variations during conflict search?
Which conflict tools support approval records tied to the conflict clearance decision?
How does Juro move conflict results into downstream contract or document workflows?
When a team needs clause-level evidence for each flagged hit, which option fits best?
What breaks if a team only tracks parties and ignores document intake artifacts in conflict checks?
How do Onit Contract Lifecycle Management and ContractSafe differ in governance and decision history?
Which tools are practical when the legal team already runs case processing in Relativity?
How do tools like Intapp Conflicts and Precisely support consistent policy application across matters?
How should enterprise teams evaluate audit logging and traceability for high-throughput intake workflows?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Cybersecurity Information Security alternatives
See side-by-side comparisons of cybersecurity information security tools and pick the right one for your stack.
Compare cybersecurity information security tools→