Documents & Collaboration · Real-Time Collaboration
People, documents, conversations, meetings, and Lex — working together in the same context.
Built into EdgeLex
Chat✕
Maya Chen
Tunde Okafor
MCMaya Chen
Tightening the intro — watch ¶1.
TOTunde Okafor
Good — I'll take the timeline section.
MCMaya Chen
Use the June 15 order language from the minute order, not our letter.
TOTunde Okafor
Pulled it in. Also flagged their three proposed end dates — they don't even agree with themselves.
MCMaya Chen
That's the closer. Put it last.
Enter your message here
Send
SUPERIOR COURT OF THE STATE OF CALIFORNIA
COUNTY OF ALAMEDA
DEPARTMENT 24
JORDAN HALE,
Plaintiff and Cross-Defendant,
v.
NORTHSTAR LOGISTICS, INC., et al.,
Defendants.
Case No. 26CV004182
Hon. A. Oyelaran, Judge
Hearing: October 6, 2026, 8:30 a.m.
Department 24
PLAINTIFF’S OPPOSITION TO DEFENDANT’S EX PARTE APPLICATION FOR EXTENSION OF TIME TO SERVE SUPPLEMENTAL WRITTEN DISCOVERY RESPONSES
Plaintiff Jordan Hale opposes Northstar’s Ex Parte Application for an extension of time to serve supplemental written discovery responses. The application should be denied because the requested extension rests principally on counsel’s admitted failure to account for his own July travel when the existing deadline was set — after the Court had already granted the additional time counsel requested at the June 15 conference. The resulting delay should not be shifted to Plaintiff.
I. RELEVANT BACKGROUND AND TIMELINE
1. On June 15, 2026, the parties appeared for an Informal Discovery Conference concerning Northstar’s supplemental written discovery responses. The resulting direction established a compliance deadline; the dispute had already been pending for months.
2. The Court initially discussed approximately 30 days for compliance. Counsel requested 45 days, citing commitments then said to be on calendar. The Court granted the additional time — the present September 23 deadline therefore already reflects an accommodation.
3. Counsel now relies on his failure to account for July travel when that period was discussed. The application’s related papers do not identify a single consistent proposed end date — they refer variously to October 28, 29, and 31.
TOTunde Okafor 8/15, 5:42 PM
Lead with the June 15 order instead — stronger opener?
AddCancel
The problem
Collaboration tools each solve one slice — editing, chat, or video — in separate products with separate permissions. Legal work needs them connected, in matter context, on the record.
One document. Several people. One record.
Together. Anchored. Threaded. Guarded. On the record.
The live layer that runs across EdgeDocs, Microsoft Word, and Messages — every screen below is the real product.
01 · Together
Two lawyers, one pleading, live.
Presence shows who's in the document; the in-editor chat runs beside the text; and both people type into the same draft at once — real co-editing in the firm's own document engine, not a copy emailed back and forth with _v7_FINAL in the name.
The editor's full story →Chat✕
Maya Chen
Tunde Okafor
MCMaya Chen
Tightening the intro — watch ¶1.
TOTunde Okafor
Good — I'll take the timeline section.
MCMaya Chen
Use the June 15 order language from the minute order, not our letter.
TOTunde Okafor
Pulled it in. Also flagged their three proposed end dates — they don't even agree with themselves.
MCMaya Chen
That's the closer. Put it last.
Enter your message here
Send
SUPERIOR COURT OF THE STATE OF CALIFORNIA
COUNTY OF ALAMEDA
DEPARTMENT 24
JORDAN HALE,
Plaintiff and Cross-Defendant,
v.
NORTHSTAR LOGISTICS, INC., et al.,
Defendants.
Case No. 26CV004182
Hon. A. Oyelaran, Judge
Hearing: October 6, 2026, 8:30 a.m.
Department 24
PLAINTIFF’S OPPOSITION TO DEFENDANT’S EX PARTE APPLICATION FOR EXTENSION OF TIME TO SERVE SUPPLEMENTAL WRITTEN DISCOVERY RESPONSES
Plaintiff Jordan Hale opposes Northstar’s Ex Parte Application for an extension of time to serve supplemental written discovery responses. The application should be denied because the requested extension rests principally on counsel’s admitted failure to account for his own July travel when the existing deadline was set — after the Court had already granted the additional time counsel requested at the June 15 conference. The resulting delay should not be shifted to Plaintiff.
I. RELEVANT BACKGROUND AND TIMELINE
1. On June 15, 2026, the parties appeared for an Informal Discovery Conference concerning Northstar’s supplemental written discovery responses. The resulting direction established a compliance deadline; the dispute had already been pending for months.
2. The Court initially discussed approximately 30 days for compliance. Counsel requested 45 days, citing commitments then said to be on calendar. The Court granted the additional time — the present September 23 deadline therefore already reflects an accommodation.
3. Counsel now relies on his failure to account for July travel when that period was discussed. The application’s related papers do not identify a single consistent proposed end date — they refer variously to October 28, 29, and 31.
TOTunde Okafor 8/15, 5:42 PM
Lead with the June 15 order instead — stronger opener?
AddCancel
02 · Anchored
Collaboration happens on the text, not about it.
Select a passage and the toolbar offers the whole vocabulary of legal collaboration: comment it for a colleague, turn it into a work-product note, pin it, compare it across versions — or hand it to Lex with the exact characters attached. Nothing anchors to "see my email"; everything anchors to the words.
Chat✕
Maya Chen
Tunde Okafor
MCMaya Chen
Tightening the intro — watch ¶1.
TOTunde Okafor
Good — I'll take the timeline section.
MCMaya Chen
Use the June 15 order language from the minute order, not our letter.
TOTunde Okafor
Pulled it in. Also flagged their three proposed end dates — they don't even agree with themselves.
MCMaya Chen
That's the closer. Put it last.
Enter your message here
Send
SUPERIOR COURT OF THE STATE OF CALIFORNIA
COUNTY OF ALAMEDA
DEPARTMENT 24
JORDAN HALE,
Plaintiff and Cross-Defendant,
v.
NORTHSTAR LOGISTICS, INC., et al.,
Defendants.
Case No. 26CV004182
Hon. A. Oyelaran, Judge
Hearing: October 6, 2026, 8:30 a.m.
Department 24
PLAINTIFF’S OPPOSITION TO DEFENDANT’S EX PARTE APPLICATION FOR EXTENSION OF TIME TO SERVE SUPPLEMENTAL WRITTEN DISCOVERY RESPONSES
Plaintiff Jordan Hale opposes Northstar’s Ex Parte Application for an extension of time to serve supplemental written discovery responses. The application should be denied because the requested extension rests principally on counsel’s admitted failure to account for his own July travel when the existing deadline was set — after the Court had already granted the additional time counsel requested at the June 15 conference. The resulting delay should not be shifted to Plaintiff.
I. RELEVANT BACKGROUND AND TIMELINE
1. On June 15, 2026, the parties appeared for an Informal Discovery Conference concerning Northstar’s supplemental written discovery responses. The resulting direction established a compliance deadline; the dispute had already been pending for months.
2. The Court initially discussed approximately 30 days for compliance. Counsel requested 45 days, citing commitments then said to be on calendar. The Court granted the additional time — the present September 23 deadline therefore already reflects an accommodation.
3. Counsel now relies on his failure to account for July travel when that period was discussed. The application’s related papers do not identify a single consistent proposed end date — they refer variously to October 28, 29, and 31.
TOTunde Okafor 8/15, 5:42 PM
Lead with the June 15 order instead — stronger opener?
AddCancel
03 · Threaded
One conversation follows the document everywhere.
Every document carries a single live conversation — and it's the same thread in the EdgeDocs panel, in Messages, and inside native Microsoft Word through EdgeLex for Word. Ask Lex to catch you up in the thread and it answers in the thread: what happened since you last looked, what the bound document is, and what needs you.
The same thread in Messages →SUPERIOR COURT OF THE STATE OF CALIFORNIA
COUNTY OF ALAMEDA — DEPARTMENT 24
JORDAN HALE, Plaintiff, v. NORTHSTAR LOGISTICS, INC., et al., Defendants.
Case No. 26CV004182 · Hon. A. Oyelaran, Judge · Hearing: October 6, 2026, 8:30 a.m.
PLAINTIFF’S OPPOSITION TO DEFENDANT’S EX PARTE APPLICATION FOR EXTENSION OF TIME TO SERVE SUPPLEMENTAL WRITTEN DISCOVERY RESPONSES
I. RELEVANT BACKGROUND AND TIMELINE
1. On June 15, 2026, the parties appeared for an Informal Discovery Conference concerning Northstar’s supplemental written discovery responses. The resulting direction established a compliance deadline, and the conference was requested in an effort to obtain compliance and move discovery forward.
2. The Court initially discussed approximately 30 days for compliance. Counsel requested additional time, and the Court granted it — the present September 23 deadline therefore already reflects an accommodation previously made at counsel’s request.
3. Counsel now relies on his failure to account for his July travel and family commitments when the 45-day period was discussed. His related papers do not identify a single consistent proposed end date; they refer variously to October 28, 29, and 31, 2026.
4. After the June 15 conference, the parties exchanged communications concerning discovery and deposition scheduling. Plaintiff did not consent to the requested extension.
Page 1 of 7 · 1,771 words · native Microsoft Word
EdgeLex for Word AI-powered legal DMS
‹ ConversationLive · 2 open · 5 total⟳ Sync
Tunde Okafor just now Word
Flagged the timeline section — see my comment on ¶2.
↩ Reply · Resolve
Maya Chen 8/15/2026
@Lex catch me up on this conversation.
↩ Reply · Resolve
Lex 8/15/2026
Since you last looked
– Tunde flagged the timeline section and posted a comment on ¶2.
– You replied with the June 15 framing.
– The bound document is a draft opposition to Northstar’s ex parte request to extend time for supplemental written discovery responses (hearing set for October 6, 2026; current compliance deadline referenced as September 23, 2026).
Needs you
Tunde’s ¶2 comment is waiting on your call.
↩ Reply · Resolve
Maya Chen 8/15/2026
Agreed on ¶2 — keeping the accommodation line, citing the minute order.
↩ Reply · Resolve
Reply in the conversation… ➤
04 · Guarded
Live doesn't mean lawless.
Checkout with a running clock, presence with idle states, and version-level access decide who can touch what, when. Collaboration rides the same access boundary as everything else in the DMS — a co-editor is a permission, not an accident.
🗓 This Month (2 versions) · Group by Date
Verified deliverable from legal graph msa_obligation_register.v1 — every obligation traced to its clause span.
👤 Maya Chen (Attorney) · 301 words · 10 KB
Initial version.
👤 Maya Chen (Attorney) · 294 words · 10 KB
05 · On the record
Every comment, resolve, and edit is on the record.
Comments ride the audited path; anchored excerpts quote the exact text into the matter channel; resolve and reopen events post as governance banners. When someone asks six months later who changed the position and why, the answer is a record — not a memory of a hallway conversation.
The record it lands on →＋ New conversation
Start a direct conversation
Pick two or more colleagues
Open a matter's team channel
Also threads on
📄 Every document — one conversation per document, anchored to the text, shared with EdgeDocs and Word comments.
⚖ Hale v. Northstar — AlamedaMATTER CHANNEL · PRIVILEGED
⏰ Opposition due — 9 court days before the 10/6 hearingSep 23 · CCP § 1005(b)
⏰ Informal discovery conferenceOct 6 · Dept. 24
— Document added · “Notice of Ruling with Exhibit” · Aug 14 —
Tunde Okafor Aug 14, 2:10 PM
“The receiving party may use Confidential Information solely for the Purpose…”
Flagged this clause in the doc thread — @Maya can we take the fallback here?
— Comment resolved by Maya Chen · Aug 14 —
Deadline cards read the matter’s real calendar; activity banners come from the audited event stream — the channel narrates the matter without anyone typing status updates.
The difference
Collaboration that never leaves the record.
Consumer co-editing tools made simultaneous typing easy — and made the record worse: comments in one silo, chat in another, decisions in nobody’s. Here the conversation is bound to the document, the comments anchor to the text, the same thread follows the work into Word and Messages, and all of it is audited. Working together stops costing you the file’s history.
The messaging layer →One thread, everywhere
The document's conversation is the same live thread in EdgeDocs, Messages, and native Word.
Anchored to the text
Comments, notes, pins, and Lex prompts bind to exact passages — never to "see my email."
Audited by default
Comments, resolves, and edits ride the audited path and post to the matter's record.
Capabilities
What it does
Coauthor in real time
Two lawyers in the same EdgeDocs document see each other's cursors, presence, and comments live — on an editing engine your firm hosts.
One version chain, two surfaces
EdgeDocs in the browser and Microsoft Word natively are co-equal surfaces over the same DMS version chain — Save updates in place; Save New Version advances the record deliberately.
The conversation travels with the document
A document's discussion lives in EdgeMessage as a version-aware conversation; margin comments from Word and EdgeDocs bridge into the same thread.
Meet about it, on the record
Pull the document into an EdgeMeet room as an exhibit, annotate it live, and keep the meeting's transcript in the matter.
Lex in the loop
The Lex Document Expert panel works inside the coauthoring session — analysis, citations, clauses, review — proposing edits it can only apply with your approval.
Presence with honest labels
Collaborators are shown by name and surface — editing via EdgeDocs or Microsoft Word — with soft-lock warnings so nobody tramples anyone's work.
In your control
The whole loop — edits, comments, threads, meetings — runs in your deployment under one permission model and one audit trail.
Related
Works with
EdgeDocs
Native document drafting and a full DMS: versioning, redlines, clause library, e-signature with an evidence trail, and freeze-on-signature.
EdgeMessage
One universal inbox across every EdgeLex surface: direct messages, team threads, document conversations, and Lex as an @mentionable teammate.
EdgeMeet
Two solutions in one: the Zoom/Teams replacement on your own infrastructure, and a deposition machine — live Agent Insights, certified transcripts, page:line clips, filed to the matter.
See EdgeLex on your own terms.
We'll walk through self-hosting, model control, and your firm's workflows.