Legal Services Offshore blog
Set a matter reopen review that records why the file came back
A reopen review that names the trigger, checks access and conflicts, and records who approved the new work before the file is active again.

Key takeaways
A reopened matter is a new work event, not a reversal of the closing entry. Record the trigger, the requesting person, the date, and the first new task before anyone changes the file status. That record lets a later reviewer see why the firm returned to a matter it had closed. A second reader can catch a gap that the first reader no longer sees.
Access should be restored only to the people and systems needed for the reopened task. A broad reopen can quietly restore old permissions that were removed for a good reason. Compare the current access list with the closing record and name the person who approved each addition. Keep the language neutral and avoid conclusions the record does not support.
The reopen decision belongs to the responsible lawyer or firm owner, even when the administrative trigger is simple. Support staff can gather the file, check the conflict record, and prepare the work list. They should not decide that a closed matter has become active again. Ask the named owner when the instruction is unclear instead of guessing.
Close the reopened matter with the same discipline as the first close. Record what the new work produced, whether the file is complete, and which access was removed again. A second closing note that points to the reopen reason keeps the history readable. A brief exception note is more useful than a silent correction.
Why a reopen needs a reason field
A matter can reopen because a client sends a new question, an appeal arrives, a payment dispute surfaces, or a court issues a later order. Each trigger carries a different risk and a different review path. A single status change labeled reopened hides those differences from the next reader. The person who performs the check should be able to explain the result.
Write the reason in plain language and tie it to a source. A client email, a court notice, an insurer request, or a partner instruction can all be valid triggers. Attach the source and record the date it was received. A reason without a source is only a recollection.
Distinguish a correction from a reopen. If the earlier close was entered in error and no new work happened, record a correction instead of a new matter event. Mixing the two makes the close history look unstable. The named owner should choose the label before the file changes.
Record the first new task in the same entry. A reopen without a task tends to sit in an ambiguous state while people guess what to do next. The task gives the reviewer a clear endpoint and shows why access is needed now. Store the evidence where the team already looks for the matter record.
What to record before the file is reactivated
Capture the matter identifier, the prior close date, the reopen date, and the person requesting the work. Add the client or party who raised the issue and the channel used. These fields let the firm answer a later question without reconstructing the event from memory. If the answer depends on a legal rule, route the question to the lawyer.
List the documents that triggered the reopen and where they are stored. If the client sent a new document, record the file name, the date received, and whether it is an original or a copy. If a court notice arrived, record the case number and the issuing court. A small sample review can show whether the step is working.
Note any deadline that comes with the reopen. A new filing date, a response window, or a hearing date should go to the calendar owner with the source attached. Support staff can flag the date, but the responsible lawyer confirms the legal deadline. Keep the original source unchanged and record any correction as a new entry.
Record the billing or engagement question at the same time. A reopened matter may need a new scope confirmation, a supplement, or a fresh budget. The firm should decide that before work expands, not after the invoice is prepared. That simple step makes the handoff easier to audit without adding a second system.
How to check access and conflict status at reopen
Compare the people who need access now with the people who had access before the close. Restore only the accounts required for the new task and remove any that are no longer justified. Record the compare date and the person who approved the change. The review should be dated so a later reader knows which version was current.
Check whether the conflict record has changed since the matter closed. A new party, a new affiliate, or a new adverse entity may create a question that did not exist before. Send the updated names to the conflict owner rather than deciding the result yourself. The note should stand on its own without a call to the person who wrote it.
Review the document permissions as well as the matter status. A closed folder may have been restricted or moved, and reopening the matter may not restore the intended path. Test one document before telling the team that access is ready. Keep the source path visible so the document can be opened again.
Keep the access change with the reopen record. A later reviewer should see why each account was added and when it was removed again. That history is more useful than a general note that access was restored. Name the person who completed the check and the date it was finished.
Who approves the reopened work
Name the responsible lawyer and the person who can approve the first new task. If the original lawyer is unavailable, record the covering lawyer and the scope of that coverage. A reopen without a named approver invites work to start without a clear owner. The control should be tested on a small set before it is applied to every matter.
Set the limit of the reopened scope in writing. The approval can cover a single client question, a document review, or a defined filing task. A broad approval to reopen the matter is harder to supervise and harder to close again. The note should be short enough to complete on a busy day.
Route any new legal question through the same review path used for active matters. A closed file does not make an old assumption safe, and a new fact may change the analysis. Support staff should prepare the facts and stop at the judgment line. Review the entry before the file moves to the next stage.
Record the approval date and the instructions received. If the scope changes later, add a new entry instead of editing the first approval. The sequence shows how the reopened work grew and who allowed each step. Ask the reviewer to confirm the entry before the deadline, not after it.
How to close the matter again
Write a closing entry that refers to the reopen reason and lists the work completed. Note the documents added, the questions resolved, and any item left open. A reader should be able to connect the second close to the event that started it. That record also helps when the same issue appears in a later matter.
Remove temporary access and confirm that shared links no longer work. Check the matter folder, the document system, and any messaging channel used for the reopened work. Record the date and the person who completed the check. Separate the administrative step from the legal decision in the written record.
Update the retention date if the new work changed it. A reopened file may need to be kept longer than the original schedule allowed. The records owner should confirm the new date and the reason. The process should identify the owner before it identifies the tool.
Tell the client or the requesting person that the matter is closed again, using approved language. Record what was sent and when. The final message should describe the process and the next contact point without promising a legal outcome. If the process changes, record the change and the date it took effect.
A supervised support lane can keep the reopen record, access check, and closing note together while the lawyer decides the legal scope. case file management support.
Sources
- American Bar Association, Model Rules of Professional Conduct
Used for supervision, confidentiality, competence, and communication boundaries in legal support work.
- U.S. Courts, Federal Rules of Civil Procedure
Used for the litigation, service, and production workflow context that these controls support.
- GAO, Standards for Internal Control in the Federal Government
Used as a general reference for documented ownership, review evidence, and exception handling.
- NIST Cybersecurity Framework 2.0
Used for access control, monitoring, and recovery language around shared legal records.