Approved tools and data
Use only firm-approved systems, permissions and data categories.
Platform fit guide
Spellbook can fit a contract team that already has, or is evaluating, the needed licenses and wants counsel-approved drafting, review, Ask, playbook, or Associate workflows checked by people before attorney release. Remote Legal Team LLC does not sell licenses or act as a reseller. We scope the operating work around the client’s permitted account, feature set, access rules, and review queue, then prepare synthetic tests and handoff steps so lawyers keep judgment, negotiation positions, and final approval.
Custom pricing. Scope and price confirmed in writing.
Legal support outsourcing should begin with role fit. Review the proposed specialist’s education, relevant experience, writing and practical work against the task. LL.B., LL.M., J.D. and paralegal training describe different pathways; they do not establish U.S. attorney licensure.
Use a synthetic exercise that requires source checks and handling an unclear answer. Agree the review owner and permissions before a person or tool receives access.
Explore education and vetting ↗Public materials describe Review, Draft, Ask, Playbooks, and Associate for contract work as of October 23, 2026.
Our role is to assess which documented functions match the firm’s matter types, reviewer habits, and approval path, then define a controlled operating scope around the licensed account.
ReviewDraftAskPlaybooks releaseAssociate
We can turn attorney-supplied rules, fallback positions, clause sources, issue labels, and routing instructions into a versioned review packet. Public materials describe saved review instructions, tracked playbook changes, rule results, and questions with document references.
Counsel sets the legal position. Our scoped work is source cleanup, exception logging, synthetic test sets, reviewer notes, and handoff.
Any work inside Spellbook depends on the client’s own permitted licensed access and firm approval. Public terms limit use to specified users, prohibit shared logins and resale, and do not make outside operator access automatic.
Public install and pricing materials also show that entitlement depends on the selected account and order, not just SSO setup or a general subscription description. Before work starts, we confirm named-user rules, enabled features, document locations, and matter boundaries. If access is unavailable, we can scope approved preparation outside the vendor system for firm handoff.
Privacy review should examine actual collection, use, storage, disclosure, oversight, and external transmission controls in the selected setup. California’s revised 2026 practical guidance is useful current jurisdiction-specific guidance on verification, confidentiality diligence, access controls, and human review.
Platform retention and any underlying model or provider retention are different questions. The public terms do not support a platform-wide no-storage claim, and ABA model guidance leaves reasonable efforts and supervision with the lawyer.
California practical guidance PDFCalifornia ethics resourcesTerms of serviceABA Rule 1.6ABA Rule 5.3 comment
Vendor output needs checking. Our acceptance work uses synthetic examples to test missing fallback language, conflicting precedents, defined terms, cross-references, unsupported citations, and incomplete source access.
We keep a clear queue for approve, reject, revise, and escalate. No suggestion, answer, or draft is treated as sent, signed, filed, or committed until attorney approval identifies the authorized version.
Integrations, Google Docs behavior, and workspace features need account-level confirmation before scope is set. Public integration pages describe available connection types, but setup depends on enabled features, admin choices, and permissions.
Compare routes to market benchmarking by deal context, not document-version diff. Public materials also mark market-backed redline insertion as Coming Soon, Google Docs help conflicts on redlining behavior, and ACM remains early access.
IntegrationsSlack integrationiManage integrationGoogle Drive integrationMarketSpellbook homeGoogle Docs helpACM
For a pilot or rollout, we can prepare the operating materials around the licensed workflow: approved source inventory, clause and fallback register, test matrix, reviewer checklist, escalation notes, and handoff instructions.
Typical fit questions are whether the account has the needed features, which document sets are in scope, where reviewers want source anchors, and which issues must always go back to counsel.
This page covers Spellbook fit, access checks, playbook setup, implementation artifacts, test criteria, and approved operator support within a client-owned licensed environment.
For vendor-neutral pre-signature preparation, see Contract drafting and review. For executed agreements, see Contract abstraction. For broader readiness work, see Workflow audit. For licensed-account operating help, see Managed AI operator.
Spellbook licensing is separate from Remote Legal Team LLC project fees and any approved operator time. Public pricing describes custom vendor pricing and notes that entitlement is controlled by the order.
Our AI work is custom and affordable by written scope. Some simple staffing workflows may be included at no additional charge only when that inclusion is expressly agreed in writing.
| Topic | Software role | Human support | Firm decision |
|---|---|---|---|
| Draft, Review, Ask | Licensed Spellbook features may suggest draft language, issue flags, comments, or source-backed answers in supported surfaces. | We prepare approved source sets, prompt structure, exception logs, and a checked handoff within the permitted account. | The responsible attorney decides whether any suggestion is correct, useful, and ready to send. |
| Playbooks | Licensed Spellbook playbooks may apply saved rules and fallback logic in supported review paths. | We organize attorney-supplied rules, versions, test cases, and review notes. | Counsel sets risk positions, allowed exceptions, and final wording. |
| Associate and Market | Associate is described for multi-document work, and Market compares terms by deal context rather than document-version diff. | We set document inventory, source anchors, and review steps if those licensed features are enabled. | The firm decides whether to rely on those outputs for the matter. |
| Access and release | Use depends on the client’s licensed account, enabled features, permissions, and vendor terms. | We confirm named-user access, folder scope, and handoff steps, or prepare outside-platform materials for firm use. | The firm approves operator access, confidentiality choices, and attorney release. |
A person remains accountable
Use only firm-approved systems, permissions and data categories.
Label every AI output as a draft and route it to a named human reviewer.
Keep a source link or document/page reference for every extracted fact.
Log missing evidence, conflicting inputs and failed steps. Never silently fill gaps.
AI never makes legal decisions or gives advice. Nothing is sent to a client, court or opposing party without attorney approval.
Remote Legal Team LLC states SOC 2 Type II security. Confirm report scope, period and covered services during diligence; it does not certify every proposed tool or make a workflow automatically compliant.
Only if the vendor terms, the customer’s order, and the firm’s approval allow named-user access for the specific person doing the work. We do not use shared logins, resell licenses, or assume outside operator rights. If that access is not available, we can scope preparation and handoff outside Spellbook instead.
Not from the public pages reviewed here. Compare routes to Market benchmarking by deal context, which is different from document-version diff. If market-backed redline insertion matters, public materials mark that item Coming Soon, so current availability should be confirmed before scope is set.
We treat those items as account-specific checks. Public help on Google Docs redlining conflicts, integrations depend on enabled features and admin setup, and ACM is still labeled early access. The fallback scope is synthetic testing, playbook preparation, and reviewer handoff, not a promise of feature parity or access.
Checked October 23, 2026. Product access depends on the current account, plan and configuration.
Remote Legal Team LLC is an independent service provider and is not affiliated with, endorsed by, or a reseller of Spellbook. Spellbook licensing, access, availability, and terms remain separate from our written scope. Work inside a client account depends on vendor-permitted licensed individual access and firm approval. If access is unavailable, scope is limited to approved preparation and handoff outside the vendor system. Attorney judgment, negotiation positions, confidentiality decisions, and release remain with the firm. Fact checked October 23, 2026.
LET’S PLAN YOUR ORGANIZATION’S SUPPORT
Describe the workflow, approved systems, expected draft output and review owner. We will confirm the scope and custom pricing in writing before work starts.
We’ll discuss relevant education and experience, workload, coverage, commercial terms and your review process.
Describe the workflow, expected outputs, review owner and preferred timing. Business requirements only; do not include confidential documents or personal data. Required fields are marked *. Read our Privacy Policy and Website Terms.
Discuss spellbook workflow support, your team’s workload and the next steps for your organization.