Turn the request into a defined piece of work
Do not begin by downloading files.
First, write down what the request actually asks for. Confirm who made it, whose record is involved, what date range or type of information they want, and where the finished copy should go. Follow the authorization, consent, identity, and response-time requirements that apply to your practice and location.
A useful request record might include:
- the date you received it;
- the person who is asking;
- the client record or records involved;
- the requested scope and date range;
- the delivery method;
- the person responsible for reviewing and sending it;
- the due date under your practice process.
If any part is unclear, resolve that before assembling the release. A vague request for “everything” may need a short conversation about what the person needs and how you can provide it safely.
Gather one source bundle from the client chart
Once the request is clear, gather the record from its source.
Avoid building the chart from memory or from whatever folders are easiest to reach. The client's record may include more than session notes. Intake answers, consent records, treatment plans, assessments, uploaded documents, appointment history, billing records, and relevant message attachments may all matter to the request.
Use your practice system's chart export when it is available. A single source bundle gives you a dependable starting point and makes omissions easier to notice. It also preserves the relationship between records that can become confusing when each file is downloaded separately.
Keep the source bundle private. Store it only in an approved location, limit access to the people handling the request, and avoid leaving an extra copy in a general downloads folder.
Check the chart before you prepare the release
A complete download can still reveal unfinished work.
Open the bundle and compare it with the client's chart. Check that expected notes are present, signed addenda appear with the right note, and uploaded files open correctly. Look for a draft that should be completed, a document that was attached to the wrong client, or a recent item created after the export.
Use a short review list:
- Confirm the client's name and the date the chart was generated.
- Review the date range against the request.
- Check that the expected note, form, document, and message sections are present.
- Open a sample of the included files instead of trusting their filenames.
- Resolve unfinished or misplaced records through your normal correction process.
- Generate a new source bundle if the chart changes during review.
Do not quietly rewrite a signed record to make the release look cleaner. If a correction or explanation is appropriate, use the addendum or amendment process your practice follows so the history stays understandable.
Separate the source bundle from the release copy
The source bundle is what you review. The release copy is what you are authorized and prepared to send. They are not always the same file.
Follow the scope of the request and your practice's rules when deciding what belongs in the release. Remove duplicate working copies and unrelated administrative material. Check whether the bundle contains information about another person, such as a partner, family member, or someone who wrote a message. Joint and family records deserve particular care because one chart can contain information about more than one person.
Be equally careful with records that have special access rules. A practitioner may be able to open some notes but not others. A message export may include only conversations that person was part of. Treat those boundaries as part of the review rather than assuming every team member can assemble the same release.
If you are uncertain about a record, pause and use the privacy, clinical, or legal review process available to your practice. Guessing is not a useful way to save time.
Give the finished package a simple structure
The recipient should be able to understand what you sent without searching through a pile of unexplained files.
Use a clear folder and filename that identify the client and preparation date without adding unnecessary clinical detail. Include a brief cover note that states the request you are responding to, the date range, the broad categories included, and a contact for questions. Do not turn the cover note into a new clinical summary unless one was specifically requested and appropriately prepared.
Keep the original source bundle unchanged while you work from a separate release copy. That makes it easier to explain your decisions later and prevents a last-minute edit from changing the only copy you have.
Before delivery, have the assigned reviewer check the final package against the request one more time.
Choose the delivery method before the deadline
Do not finish the chart and only then ask how to send it.
Records can be large, sensitive, and difficult to recover once they go to the wrong place. Use the secure delivery method approved by your practice. Confirm the destination through a trusted channel, and do not place private records in ordinary email simply because the attachment is ready.
If another provider is receiving the chart, verify the person and destination rather than relying only on contact details copied into the request. If the client is receiving it, explain how long the link or file will remain available and what they should do if they cannot open it.
Send a short confirmation without repeating clinical details in the message itself.
Record what you released
The work is not finished when the file leaves your computer.
Record the date, the person who reviewed it, the person or organization that received it, the delivery method, and the scope of the release. Keep the request, authorization, and delivery confirmation with the administrative history your practice uses for records requests.
You should be able to answer a later question without reopening every file:
- What was requested?
- What did we send?
- Who approved it?
- When and how was it delivered?
- Was there anything we intentionally left out or handled separately?
That record protects the client from having to repeat the request and protects your team from relying on memory.
Test the process with a fictional chart
Do not wait for an urgent request to learn how your export works.
Create a fictional client with a note, intake form, document, appointment, invoice, and test message. Download the chart and walk through the full review. Confirm that your team knows where the file goes, who can access it, how the release copy is prepared, and which secure delivery method to use.
Repeat the test when your record system or practice process changes. A twenty-minute rehearsal can uncover a missing permission, an unclear owner, or a delivery limit before a real client is waiting.
The best records process is calm and observable. Define the request, gather one source bundle, review the chart, prepare only the authorized release, deliver it securely, and record the outcome.
In Stillpoint, Download chart gathers the parts of a client record you are allowed to open into one ZIP, including readable note PDFs, uploaded documents, relevant message files, and a structured copy of the chart. The download is recorded in the audit log, giving you a clear starting point for your own release review. Explore clinical notes in Stillpoint.
