Welcome to Jylo

Bring Jylo's AI directly into Microsoft Word with this quick video demo. The Jylo Word Assistant is a side-panel add-in that lets you chat with any open .docx file — asking questions, requesting summaries and instructing edits as tracked changes — all powered by the AI models enabled on your Tenant.

What You'll Gain:

• How to ask questions about your document and receive answers with paragraph-level citations
• How to generate summaries of a full document or specific sections
• How to instruct the Assistant to draft new content, clauses or paragraphs in context
• How to apply, review and accept or reject AI-generated edits as tracked changes
• How to select your preferred AI model from the model picker

What This Demo Covers: This demo walks you through the core workflows of the Jylo Word Assistant: analysing, summarising, drafting and editing a .docx file directly from the side panel, with particular attention to the tracked changes workflow. The full Jylo Word Assistant Guide and Word Plug-In Deployment Guide are attached for reference. Note that the Word Assistant is currently in Beta, so chat history is not retained between sessions and Playbook connections are not yet supported. This is essential viewing for anyone looking to bring Jylo's drafting and analysis capabilities directly into their everyday Word workflow.

Choosing a model

Choosing the right AI model is less about which one is “best” and more about matching the kind of thinking the model does to the kind of thinking your task needs. Picture a single scale.

At one end is executing instructions: following clear directions on well-defined inputs. Extracting names from documents, classifying support tickets or summarising a meeting transcript. You know exactly what you want, and the model fetches it.

At the other end is reasoning what’s necessary: working out what the right questions are, not just the answers. Reviewing a lease for risks you have not named, or assessing a proposal for problems that surface only in implementation. You know the goal but not the shape of the answer. Reasoning of this kind rests on deep knowledge of the subject—the models at this end of the scale draw on a stronger grasp of the field, which is what lets them spot the issues you did not think to ask about.

Most tasks fall somewhere between the two ends. The further right your task sits, the more judgment it asks of the model—and the more it costs to run.

The scale

■ Recommended default (Sonnet 4.6).  Claude models sit above the scale; GPT models below.

The scale is a continuum, not a set of boxes. Every model reasons to some degree; what changes as you move right is how far the model reasons beyond what you have spelt out, and how deeply it draws on knowledge of the subject. The pairs cluster naturally—Haiku 4.5 and GPT-4.1 toward execution, Sonnet 4.6 and GPT-5.4 around the middle, Opus 4.6 and GPT-5.5 toward reasoning—but each blends into the next rather than stopping at a hard line.

Which model for which task

Toward the execution end — Haiku 4.5 and GPT-4.1

Reach for these when the task is well-defined and the model’s job is to fetch, transform or classify rather than to think. They are fast, inexpensive and capable enough for the majority of high-volume work.

• Extract the parties, dates and key amounts from each of these contracts into a table.
• Classify support tickets as “billing”, “technical”, “account” or “other”.
• Read this email thread and pull out every action item, with the owner if mentioned.
• Summarise this hour-long meeting transcript into five bullet points and a list of decisions.

Around the middle — Sonnet 4.6 and GPT-5.4 (the default zone)

Reach for these when you know what you are looking for and want the model to find and reason about it within those bounds. This is the right default for most professional work.

• Review this employment contract and flag anything that conflicts with our standard handbook terms.
• Compare these three vendor proposals against the requirements I have listed and tell me which best fits, and where each has gaps.
• If there is an overage clause, report on what other clauses and dependencies should be checked throughout the document.

Toward the reasoning end — Opus 4.6 and GPT-5.5

Reach for these when you know the goal but not the shape of the answer. They distinguish themselves by identifying issues you did not think to ask about, weighing trade-offs the brief did not name and reaching judgments under uncertainty. They are noticeably more expensive and should be used selectively.

• Review this lease on the basis that our client is taking an assignment and identify any provisions that could expose them to unexpected liability or restrict their intended use.
• Read this M&A disclosure schedule and tell me what concerns a buyer should raise at the next negotiation session.
• Assess this engineering change proposal for risks that might not surface until implementation, and explain why.
• Read three years of board minutes and identify recurring themes that suggest unresolved governance issues.

How to choose

Start by deciding where your task sits on the scale, then refine with the rules below.

Start with Claude Sonnet 4.6. It handles around nine in ten tasks well, at a moderate cost. The rules below assume Sonnet is your starting point.

Move right (toward reasoning) when:

• Sonnet’s answer is close but not right, and small prompt changes do not fix it.
• The task requires the model to spot risks or implications you have not named.
• The output is high-stakes—going to a client, a board or a regulator.
• The work involves reasoning across many sources, where missing a connection is costly.

Choose between Opus 4.6 and GPT-5.5 based on cost tolerance and your existing platform preferences. Both sit at the reasoning end.

Move left (toward execution) when:

• The task is well-defined and the model is fetching, classifying or transforming rather than reasoning.
• The work runs at high volume, where unit cost matters.
• Latency is the main constraint—real-time chat or an interactive interface.

Haiku 4.5 is the faster and cheaper of the two; GPT-4.1 is a well-established alternative.

Model reference

Cost tiers: £ lowest · ££ low · £££ moderate · ££££ high · £££££ highest. Relative running cost per typical interaction.

A few things worth knowing

Cost depends on how you use the model. The cost rating reflects a typical mixed workload. Long documents, code generation and heavy reasoning all push cost higher. Cost differences compound at scale.

Context length is the input ceiling, not memory. Context length is the amount of text the model can consider in a single request, measured in tokens (roughly three-quarters of a word—1,000 tokens is about 750 words, or two pages of A4). It is not memory: models do not retain information between separate conversations.

Test before you commit for high-stakes work. No card can predict how a model will perform on your specific material. For important workflows, try your shortlisted model on a representative sample before relying on it.

Placements will shift as new models arrive. The positions and cost ratings compare these six models against one another, not against the wider market. New releases will change the picture; this card is reviewed periodically.

Jylo has enhanced the User Preference Prompt feature by introducing Output Style Templates—pre-built configurations that instantly customise how the Assistant responds to your queries.

Previously, users needed to write their own preference prompts from scratch to achieve a particular response style. Now, you can select from five professionally designed templates that match common roles and industries, making personalisation immediate and effortless.

How It Works

The User Preference Prompt is automatically appended to every message you send to the Assistant. By selecting an Output Style Template, you define how you want the AI to communicate with you—whether that's formal legal analysis, friendly guidance, or executive-focused insights.

This personalisation layer ensures that every interaction with the Assistant is tailored to your professional context and communication preferences.

Accessing Output Style Templates

To set or change your Output Style Template:

1. Click your profile icon (showing your initial) in the top-right corner of Jylo
2. Select Edit User Preference Prompt from the dropdown menu
3. The "Edit User Preference Prompt" dialogue will open
4. Click to expand the "Choose from Output Style Templates" section
5. Review the available templates and their descriptions
6. Click Use Template on your preferred style
7. The template will populate in the text field below
8. Click Update Prompt to save your selection

Available Output Style Templates

Jylo currently offers five specialised templates designed for different professional contexts:

Consumer

• Description: Friendly, visual answers with emojis and guided follow-ups
• Best for: General users who prefer conversational, approachable responses with visual elements and step-by-step guidance
• Example use cases: Learning new concepts, general enquiries

Legal

• Description: Precise, cautious legal analysis with structured reasoning
• Best for: Legal professionals requiring formal analysis, citation-heavy responses, and careful consideration of edge cases
• Example use cases: Contract review, legal research, regulatory compliance analysis

Government

• Description: Policy-focused, neutral tone aligned with public sector standards
• Best for: Public sector professionals who need politically neutral, policy-oriented responses that align with governmental communication standards
• Example use cases: Policy development, public communications, regulatory guidance

Real Estate

• Description: Market-aware insights with property metrics and deal implications
• Best for: Property professionals requiring responses that incorporate market data, valuation considerations, and transactional context
• Example use cases: Property valuations, market analysis, lease negotiations

Executive / Business

• Description: Concise, decision-oriented answers for leadership and strategy
• Best for: Senior leaders and business strategists who need bottom-line focused, actionable insights without unnecessary detail
• Example use cases: Strategic planning, board reports, executive briefings

Creating Custom Preference Prompts

While templates provide instant customisation, you may want to create a fully bespoke preference prompt. To write your own:

1. Follow steps 1-4 above to open the User Preference Prompt dialogue
2. Instead of selecting a template, click directly in the text field at the bottom
3. Write your custom instructions describing how you want the Assistant to respond
4. Click Update Prompt to save

Custom prompt examples:

• "Always provide responses in bullet points with no more than 5 key points"
• "When analysing documents, prioritise risk identification over opportunities"
• "Use UK English spelling and legal terminology appropriate for English courts"
• "Structure all responses with an executive summary, detailed analysis, and recommended actions"

Need help? Contact support at support@jylo.ai

A Guide for Microsoft 365 Administrators

Introduction

The Jylo Word Add-In enables users to upload and create docx templates in Playbooks ready to be populated with Flow results. This guide provides step-by-step instructions for deploying the add-in to your organisation through the Microsoft 365 admin centre.

Prerequisites

• Administrative access to the Microsoft 365 admin centre
• Permissions to deploy custom apps in your organisation

Deployment Instructions

1. Access the Microsoft 365 admin centre

Navigate to the Microsoft 365 admin centre at admin.microsoft.com

2. Navigate to Integrated Apps

• In the left navigation menu, click Show All
• Select Settings
• Click Integrated Apps

3, Upload the custom app

Click the Upload custom apps button

4. Select app type

When prompted for App Type, select Office Add-In

5. Provide the manifest file link

Enter the manifest file URL that corresponds to your organisation's region:

6. Configure user access

Select who should have access to the Jylo Word Add-In:

• Specific users: Make the add-in available to individual named users
• Groups: Make the add-in available to all members of specific groups
• Entire organisation: Make the add-in available to all users organisation-wide

7. Deploy the add-in

Click the Deploy button to complete the installation. The add-in will appear for selected users within a few minutes.

Verifying Deployment

To confirm the add-in has been successfully deployed:

1. Open Microsoft Word (desktop or web version)
2. Navigate to the Home tab
3. Click the Jylo button in the right side of the ribbon
4. Sign in using your Jylo credentials

Support

If you encounter issues during deployment or have questions about the Jylo Word Add-In, our support team is here to help. Contact us at support@jylo.ai.

Master creating and managing Projects in Jylo with this comprehensive guide and accompanying video. Projects are the foundation of AI-powered document analysis in Jylo, providing secure collaborative workspaces where teams upload documents, run analyses, and manage workflows.

What You'll Gain:

• How to create new Projects
• How to upload Project files 
• Manage team members and permissions 
• Know where to launch a flow on your documents
• Where to collaborate with the Projects Assistant

What This Guide Covers: This guide describes the concept of project centricity in Jylo, how to create and configure new Projects with appropriate metadata, add team members and manage permissions, detail Project settings and ongoing management options, and provide guidance on notifications and collaboration features. This is essential guidance for any new users to the platfrom. 

A Guide for Jylo Users

Welcome to Jylo

Jylo is an AI-powered platform that allows you to automate your organisational intelligence.

The platform focuses on combining AI capabilities with human expertise, helping you work faster whilst maintaining quality through verification.

It comes in two parts – the AI Assistant, and Playbooks. Assistant is a classic chat-style AI tool. If you have a quick question, want a spur-of-the-moment document review or to perform a redline comparison, the Assistant can help.

Playbooks are automated workflows that use AI to not only extract your chosen data but also perform analysis and transform that base data into something completely different such as a letter or a report.

Everything in Jylo happens within Projects—organised workspaces that contain your files, analysis, team members, and results in one secure location.

Essential Setup

Each Project is typically dedicated to a particular department or initiative. Here, all related files and work are stored and shared amongst individuals chosen to form part of the team.

1. Create Your First Project

1. Navigate to My Projects in the "Me" section of the sidebar
2. Click the blue Plus button in the top-right corner
3. Enter a descriptive Project name
4. Provide a Project description
5. Complete any required metadata fields
6. Click Finish to create your Project

2. Upload Documents

1. Select your Project and go to the Files section
2. Click the blue Plus button
3. Select Upload files from the dropdown
4. Either drag and drop files or click browse to select from your computer
5. Click Upload Files to complete the process

Two Ways to Analyse Documents

Choose the approach that best fits your needs:

Assistant

Assistant is perfect for answering quick questions, analysing various documents at once or having dynamic conversations which develop with every interaction. It's easy to use and can help you:

• Prepare for meetings
• Learn new concepts
• Perform redline analysis
• Compare documents of various types
  • you the overview with prompt labels and descriptions.

To launch the Assistant:

1. Click Assistant in your Project navigation
2. Click the blue plus button to start a new conversation
3. Upload specific documents using the plus button in the input field, or ask general questions
4. Use natural language queries:
   • "Compare the agreement to the issues list"
   • "List the contractual milestones in table format"
   • "Differentiate between completion accounts and the locked box mechanism"
5. Always verify responses when analysing documents by clicking citation numbers to see highlighted source text

Playbooks and Flows

The Assistant provides rapid clarity and analysis whenever you need it. However, to consistently automate larger tasks across one or many documents, Playbooks are the best option. These templates enable users to apply high-quality prompts consistently and at scale. They are typically used to:

• Spot trends across documents
• Analyse documents using proven methodology
• Structure large datasets before separating and storing files
• Identify crucial information quickly from an abundance of data
• Produce bespoke reports for single documents or entire datasets
• Democratise methodology throughout your organisation

To launch a Flow:

1. Go to Flows section in your Project
2. Click blue Plus button → Add Flow
3. Enter a Flow name and description
4. Select your chosen Playbook
5. Select your target documents
6. Click Finish to launch the analysis

Once the Flow is complete, review and verify results:

1. Use the left panel filters to find documents matching specific criteria
2. Click Evidence buttons to see AI reasoning highlighted in documents
3. Approve, reject, or edit responses using the verification controls
4. Use Tasks to assign specialist reviews to team members

Getting Results Out

From Assistant

• Export PDF: Download the entire conversation thread
• Copy the output: Save to Word or other applications
• Continue conversations to refine analysis

From Flows

Click the download icon to access export options:

• Export Spreadsheet: Comprehensive tabular data including verification status and comments for further analysis
• Export with source documents: Complete package including original files
• Generate flow assembly: Bespoke report comparing all documents based on the Playbook template
• Generate document assembly: Individual reports for each document based on the Playbook template

Next Steps

• Add team members: Go to Team in your Project to invite colleagues and assign roles
• Explore more Playbooks: Browse the Marketplace to find analysis templates for different document types
• Create custom workflows: Once you've identified effective prompts in Assistant, consider building custom Playbooks for repeated use

Visit our support portal at support.jylo.ai for comprehensive guides including the User Guide, Playbook Prompting, Assembly Building, and more.

Jylo | Quick Start Guide | Version 2.0
© 2025 Jylo. All rights reserved.

A Guide for Jylo Users

What Are Playbooks?

Playbooks are reusable workflow templates that define how AI analysis is applied to documents within Jylo. They contain specific prompts and logic that determine what information to extract, how to process it, and how to present the results.

Benefits of Using Playbooks        

• Consistency: Apply the same analytical approach across all documents
• Efficiency: Save time by reusing established analysis workflows
• Customisation: Configure complex analyses with conditional logic
• Quality Control: Build verification directly into the workflow
• Collaboration: Share expertise through standardised processes

Working with Playbooks

Playbooks, Flows and Assemblies

It's important to understand how Playbooks fit into the Jylo workflow:

• Playbooks define the analysis pattern (what questions to ask, what logic to apply)
• Flows are where you apply these Playbooks to documents and carry out your human review of the AI process
• Assemblies are how you bring together the AI output and use them outside of Jylo

You'll select which Playbook to use when you create a new Flow within a Project. This is when you'll decide which analytical approach is right for your specific documents.

The Playbook Marketplace

The Marketplace serves as a central repository where you can browse, access, and (with appropriate permissions) manage Playbooks.

To access the Marketplace:

• Navigate to Marketplace in the left sidebar
• Select Playbooks from the submenu

Each Playbook appears as a card displaying basic information. Clicking on a card shows you the overview with prompt labels and descriptions.

Playbook Access Control

Playbooks have specific access controls that determine who can use and modify them:

• Builder permission: Enables a user to clone, edit and modify the Playbook after publication
• Consumer permission: Makes the Playbook visible to users who can deploy it in Flows

Your access to specific Playbooks depends on the permissions assigned to you by the Playbook creator.

Creating Playbooks

You can create custom Playbooks from the Marketplace by following these steps:

1. Access the Marketplace
   Navigate to Marketplace > Playbooks and click the blue plus button in the top-right corner
2. Metadata
   Enter the Playbook Name and Description
3. Prompts
   Set the Label, Description, Question, Answer Type, and Model
   Upload test and source documents using the right panel
4. Assembly
   Use flow assembly to consolidate results from across the dataset
   Use document assembly to create a report for individual documents
5. Testing
   Create a test Flow with the blue plus button
6. Access Control
   Assign Builder or Consumer permissions to specific users
7. Summary
   Review your Playbook overview

Next Steps

Maybe now you you’d like to have a shot at building your own Playbook. For full guides on Playbook building visit our Playbook Prompting and Assembly Building guides.

Jylo | Getting Started with Playbooks Guide | Version 2.0
© 2025 Jylo. All rights reserved.

Discover the transformative potential of Playbooks through real-world success stories. This inspirational guide showcases how organisations across different industries have automated complex workflows and achieved significant productivity gains.

What You'll Gain:

• Inspiration from real-world Playbook implementations
• Understanding of diverse use cases across industries
• Ideas for workflows you could automate in your practice
• Confidence that AI can handle complex, expert-level tasks
• Practical examples of problem-solution-result frameworks

What This Guide Covers: This guide presents anonymised case studies from actual Jylo implementations, including contract reviews, compliance assessments, due diligence processes, building safety case compliance, statements of work generation, and traineeship application reviews. Each success story follows a clear structure showing the challenge faced, the Playbook solution implemented, the results achieved, and practical insights for your own practice. You'll see how organisations have automated everything from simple checklists to complex multi-document assessments, demonstrating that with the right expertise and structure, almost any repetitive analytical workflow can be templatised.