6.3 Conflicts-Check Systems, Docket Automation & Electronic Document Processing

6.3 Conflicts-Check Systems, Docket Automation & Electronic Document Processing

[!NOTE] NALS PP Exam Blueprint Focus: The Part 2 technology outline lists conflicts check systems as its own numbered topic, separate from the ethics material in Part 3. That placement is deliberate. Part 3 asks whether a conflict exists as a matter of professional responsibility; Part 2 asks whether the office system would have found it.

What a Conflicts-Check System Is

A conflicts-check system is a searchable database of names, maintained firm-wide, capturing every person and entity the firm has encountered in any matter. It is not the same thing as a client list. A client list contains clients. A conflicts database must contain everyone whose presence could disqualify the firm.

At minimum it captures:

The last three categories are the ones firms most often omit, and each of them is a disqualification path.

When a Search Must Run

A conflicts search is not a one-time intake formality. It runs at every point where the universe of relevant names changes.

1. Initial contact, before confidential information is received. This is the critical timing point. Once a prospective client has conveyed confidential information, the firm may owe duties even if it never opens the matter.
2. At engagement, before the engagement letter goes out.
3. When any new party appears — a counterclaim defendant, a third-party defendant, an intervenor, a newly identified corporate affiliate.
4. When a lateral attorney, paralegal, or staff member joins, run against that person's prior-matter list.
5. On corporate transactions closing, because a merger can make a current client's new subsidiary an existing adverse party.
6. Periodically on open matters, because parties and affiliates change over the life of a long case.

Name-Variant Searching

A conflicts system returns only what the search string matches. The single largest cause of a missed conflict is a search that was run correctly against an incomplete set of name forms.

Good practice is to search on the shortest distinctive root with wildcards rather than the full formal name. Searching Whitc catches Whitcomb, Whitcombe, and Whitcome; searching Whitcomb Industries, Incorporated catches exactly one string and misses the other three.

Resolving a Hit

A hit is not a disqualification. It is a question that must be answered and documented.

1. Identify the prior matter and the firm's role in it.
2. Determine whether the matters are substantially related and whether the interests are materially adverse.
3. Determine what confidential information the firm holds from the earlier engagement.
4. Decide the outcome: clear the matter, obtain informed consent confirmed in writing where the conflict is consentable, screen the affected individual where screening is permitted, or decline.
5. Document the analysis and the decision in the conflicts record. An undocumented clearance is indistinguishable from no check at all when a disqualification motion arrives eighteen months later.

The Lateral Hire Workflow

When a paralegal moves from one firm to another, the paralegal brings imputed knowledge with them. The system workflow is specific:

1. Before the start date, the incoming employee provides a list of matters worked on at the prior firm — parties and matter descriptions, not confidential details.
2. The list is run through the conflicts database against the hiring firm's open and closed matters.
3. Where an overlap appears, the firm decides whether an ethical wall (screen) is required.
4. If a wall is erected, it is implemented before the employee's first day of file access: system permissions denying access to the walled matter, physical file restrictions, written notice to all personnel, and an acknowledgment signed by the screened employee.
5. Compliance is monitored and documented for the life of the matter.

The timing is what the exam tests. A wall built after the new paralegal has already opened the file is not a wall.

Document Assembly and Automation

The same matter database that supports conflicts checking drives the rest of the office's automation, which is why data hygiene at intake pays off everywhere downstream.

• Document assembly merges matter data — party names, addresses, matter numbers, court and case number — into templates, producing pleadings, engagement letters, and closing documents without rekeying. The characteristic failure is a merge field that pulls a stale address because intake data was never updated.
• Calendar and docket automation computes deadlines from a triggering event using a rules engine keyed to the applicable court rules. The paralegal still verifies the computed date against the actual rule, because a rules engine configured for one jurisdiction produces confidently wrong dates in another.
• Electronic filing transmits documents to the court through a portal, returns a filing confirmation, and in most systems effects service on registered participants. The filing confirmation is the record and belongs in the matter file; a document that was uploaded but never accepted has not been filed.

Document Processing Controls for Filings

Three controls prevent the most common filing failures:

1. Start from the firm template, never from another client's document. Recycling a prior filing is how another client's name ends up in a caption.
2. Check local rules before formatting, not after. Margins, typeface, point size, line spacing, page or word limits, and line numbering are mandatory and vary by court.
3. Assemble the complete package: the document itself, the certificate of service, any required proposed order, exhibits with tabs or slip sheets, and the signature block in the form the court requires for electronic signatures.