← Alchemy Loop portfolio

Client requirements + department procedures

SLAQuery

Know what applies. Know when it applied.

SLAQuery turns client guidelines, SLAs, bulletins, operating instructions and internal department procedures into a governed knowledge system your staff can actually ask questions of.

GOVERNED ANSWERAPPROVED

What applied when this work happened?

CLIENTClient ADEPARTMENTAccountingPRACTICEForeclosureEFFECTIVEMarch 1, 2025
AUTHORITATIVE SOURCEClient Guidelines v8.2 · Section 7.4

Firm procedure ACC-104 is stricter and governs the internal workflow.

VIEW SOURCEPREVIOUS VERSIONWHAT CHANGED?
Effective-date awareHuman-correctableSource-traceableRuns inside your environment

Product demonstration

See governed knowledge in action.

Watch how SLAQuery brings client requirements, department procedures, effective dates and source-backed answers into one controlled workflow.

SLAQUERY PRODUCT DEMONSTRATIONOpen video ↗

The problem

The answer is rarely just “in the PDF.”

Years of revised guidelines, bulletins, email instructions and firm procedures can contain the right words while still producing the wrong answer.

Which version was effective?
Which practice and department does it govern?
Did a newer bulletin change the rule?
What did the client require when the work happened?

What your people would ask

Questions that should not require finding the right person—or the right PDF.

01

What does this client require us to redact on escrow statements?

02

What does Accounting have to include before submitting this client's invoice?

03

What are the first 24-hour requirements after a foreclosure referral?

04

What procedure do we follow when this servicer rejects an expense?

05

What did this client require on March 1, 2025?

06

Did the latest guideline change our bankruptcy proof-of-claim procedure?

07

Does our internal procedure impose a tighter deadline than the client SLA?

08

Where exactly does this requirement come from, and who approved our interpretation?

Not just document search

Indexing finds words. SLAQuery determines what applies.

AI helps interpret, retrieve and explain. Authority, effective dates, version status, corrections and overrides remain governed.

Typical PDF searchSLAQuery
Finds semantically related passagesFilters by the client and context that actually apply
May mix old and new documentsSeparates current, historical and future versions
Treats every document similarlyTracks approved, superseded, future and rejected sources
Regenerates an interpretation each timePreserves corrections, rules, overrides and trusted answers
Can blur firm procedure and client requirementKeeps external requirements and internal procedures distinct
Shows a citationShows source, version, effective date, section and approval path

Client rules + how your firm works

Different departments can follow different procedures for the same client.

SLAQuery does not overwrite the client rule with the firm procedure. It preserves both and explains which one governs the question.

Accounting

Billing requirements, fee limits, invoice backup, expense approval, rejected-charge handling and client-specific submission procedures.

Foreclosure

Referral intake, title, first legal, service, publication, sale, postponements, reporting and escalation procedures.

Bankruptcy

Proofs of claim, motions, deadlines, referral handling, document review and client reporting requirements.

Operations / Compliance

Internal controls, audits, exceptions, redaction requirements, approved interpretations and quality-control procedures.

Time-aware by design

Current. Historical. Future. Never silently mixed.

A document uploaded today may not govern until next month. SLAQuery keeps the approved timeline explicit.

NOWCurrent

Uses the approved requirement and procedure currently in force.

THENHistorical

Answers from the versions effective on the date you specify.

NEXTFuture

Tracks approved upcoming changes without making them current early.

How it works

A controlled knowledge layer your staff can actually maintain.

  1. 01
    Ingest

    Load the client guidelines, SLAs, bulletins and procedures you already use.

  2. 02
    Review

    An authorized person confirms what is authoritative before new material becomes trusted knowledge.

  3. 03
    Ask

    SLAQuery narrows the question by client, department, date, practice and approved sources.

  4. 04
    Correct

    Preserve a correction, standing rule, override or trusted answer instead of fixing the same issue repeatedly.

Teach the system without retraining a model

When your experts know better, SLAQuery keeps the decision.

Approved corrections stay visible, reversible and auditable rather than becoming an invisible change to a black-box model.

Correct an interpretation

Fix what a requirement means while preserving the original source text and history.

Add a standing rule

Define a reusable interpretation for a client, department, practice area or jurisdiction.

Create a firm override

Keep the client requirement visible while recording the firm's approved procedure when it is stricter or different.

Approve a trusted answer

Lock down a frequently asked answer after review and flag it when the underlying source changes.

Correct it once. Keep the correction governed, visible and auditable.

Nothing important should be a black box

Every material answer can point back to the evidence.

Users can see what applies, the period it governed, the original source and the approved firm procedure alongside it.

Source document and sectionVersion and effective periodAuthority and approval pathPrevious version and change history

Controlled deployment

Keep the knowledge base where the firm controls it.

SLAQuery is designed to run inside the firm environment with local document storage and search. Deployment policy controls whether AI processing stays local or uses an approved external provider.

Local document repositoryLocal version and date logicHuman approvalsAuditable corrections

Questions buyers ask

SLAQuery, plainly explained.

Is SLAQuery just a PDF chatbot?

No. SLAQuery is designed to determine which approved requirement or procedure applies based on client, department, practice area and effective date.

Can SLAQuery answer historical questions?

Yes. Superseded versions retain their effective periods so users can ask what requirement applied on a specific date.

Can we add our own internal procedures?

Yes. Internal procedures remain distinct from client requirements so users can see both what the client requires and how the firm has approved carrying it out.

What if an interpretation is wrong?

Authorized users can correct it, create a standing rule, add a firm override or approve a trusted answer while preserving history.

Does SLAQuery replace the original documents?

No. Original documents remain the evidence. SLAQuery adds governed metadata, approved interpretations and controlled knowledge on top of them.

Product brief

Review the SLAQuery datasheet.

A concise two-page overview of the product model, questions, governance and deployment approach.

Download the datasheet ↓

Stop asking, “Which PDF is right?”

Give every department one governed place to ask what applies.

Talk to us about SLAQuery