BEHCA Support Documentation

Intervention Lens is the graph view on Analyze → Dashboard that shows which strategies actually work, measured against real outcomes. It answers one question: from the day a strategy first shows up in the dates you picked, did the behavior you are watching happen more often or less often? You pick the strategy, and you pick the behavior category to measure. It counts how many times something was logged (events per day). Duration is not used here. This chart is on the website. Before you start Staff log strategies on the daily Behavior tab, in a strategy category — by default Intervention Strategies. See Logging a behavior. The chart needs at least one strategy logged in your dates. If no strategy category has anything logged in these dates, the page says No strategies logged in this date range. Pick a strategy and what to measure 1. Choose a STRATEGY from the dropdown. Each option is one strategy name (for example Redirected to a quiet area), and you look at one strategy at a time. The list shows how many times it was logged in this range and the first date it appears here — for example Redirected to a quiet area (3x since Aug 4, 2026). Only names logged in these dates are on the list. Switch strategies to compare them. 2. Choose one category under MEASURED AGAINST. That is the category in the big chart. The page opens on Challenging Behavior when that category is available, otherwise Warning Behavior. The smaller charts below cover the other categories. MEASURED AGAINST lists the behavior categories that are not marked as strategies — Desirable, Challenging, Warning, and your custom ones. A manager can hide a category from this list with N/A — not used with Intervention Lens. How the chart splits A vertical line marks the first day that strategy appears in this date range. The tag reads Strategy first logged: plus the strategy name. - Days to the left of the line are before. - The first-logged day and every day after it are after. Later uses of the same strategy do not move the line. Only that first day in the range matters. The bars are the daily count for the measured category. Two horizontal lines show the average events per day on each side of the split. Three numbers sit above the chart: - events / day, before — average for the measured category on the before days - after "…" (first logged …) — the same average from the first-logged day through the end of the range - change in daily frequency — how much that average changed, as a percent Days with nothing logged still count in the average (they are 0 that day). Smaller charts under the main chart use the same split for the other measured categories, each with its own percent. The first-logged day is only this range The split is the first time that strategy was logged in the dates you picked, not the first time it was ever used for this profile. If that first day is the start of your range, there are no before days. The percent shows n/a and no baseline before this date. Start the range earlier so some days sit before that first use. The note under the chart says the same: widen the range for a longer baseline. The percent is also n/a when the before average is 0 (nothing in the measured category was logged on the before days), because a percent change cannot be calculated from zero. To change the dates, see Date ranges. Green and red The percent is colored from Success defined by on the measured category: - Fewer events (decrease) — a drop is green; a rise is red. This is the default for Challenging and Warning. - More events (increase) — a rise is green; a drop is red. This is the default for Desirable. What this chart does and does not tell you It shows what happened before and after a date. It does not prove the strategy caused the change — other things change over the same weeks. Read it alongside the notes in the audit log. A short range on either side of the split makes the percent jumpy. A few days of before data can swing the number a long way. Who sets strategy vs measured against Intervention Strategies is the default strategy category. Managers can mark other behavior categories as strategies too — including custom ones — and you can have more than one. When more than one strategy category has data, the STRATEGY list groups names by category. Managers set this under Organization Settings → Tracking Templates. Open Category settings (the cog) on a behavior category. Under Intervention Lens Graph Settings: - Check Use as intervention / strategy category for categories where the team logs what they did in response. Those names fill the STRATEGY list. - For categories you compare against, set Success defined by to Fewer events (decrease), More events (increase), or N/A — not used with Intervention Lens. Intervention Strategies always feeds the STRATEGY list. Checking the box on other categories adds those as well. Environment and health categories cannot be strategies. If every category is set to N/A, the page says No outcome categories available to measure against. Exporting Export PDF on the Dashboard captures the view you have open, so set the strategy and the measured category first. See Exporting PDF reports. Common questions - It says no strategies logged. — Nothing was logged in any strategy category in these dates. Widen the dates, or log the strategy on the daily Behavior tab. - A strategy I use is not in the list. — It was not logged in these dates. Widen the dates. - The percent says n/a. — There are no before days in this range, or the before average is 0. Start the range earlier than the first day that strategy appears here. - A category is missing under MEASURED AGAINST. — A manager set Success defined by to N/A, or the category is marked Use as intervention / strategy category. - Can I turn off Intervention Strategies as a strategy? — That category still appears on the STRATEGY list. Mark other behavior categories as strategies alongside it. - Can I compare two strategies side by side? — Not in one chart. Switch strategies in the dropdown. Related articles - Dashboard charts - Dashboard overview - Logging a behavior - Date ranges - Organization Settings

Troubleshooting

4. Video upload errors

BEHCA accepts MP4, WebM, and MOV videos up to 100 MB per upload. How video processing works Most videos upload first and are then optimized to 720p by the server. While that work runs, the video row shows Optimization in progress. You can leave the page while it finishes. Videos over 100 MB may be compressed in the browser or mobile app before upload. This can take several minutes. If the compressed file is still over 100 MB, BEHCA will reject it. "Could not be optimized" If optimization fails, the original uploaded video remains available at its original size. Re-uploading retries optimization. If it fails again, try the checks below. Common causes and fixes Unsupported format Supported formats are: - MP4 (.mp4) - WebM (.webm) - MOV (.mov) Convert other formats to MP4 before uploading. HandBrake is one option on a computer. File is too large The upload limit is 100 MB after any pre-upload compression. Trim the video to a shorter clip or export it at a lower resolution, then try again. Connection interrupted Reconnect to a stable network and upload again. Wi-Fi is usually more reliable for large files. App moved to the background On some phones, background restrictions can interrupt a large upload. Keep BEHCA open until the upload finishes. Video codec cannot be processed A supported file extension does not guarantee that the video codec can be optimized. Re-exporting the video as an H.264 MP4 usually resolves this. Temporary processing failure If the video remains in progress for more than an hour, or repeatedly cannot be optimized, contact Support. Mobile troubleshooting If BEHCA closes during an upload: - Update BEHCA to the latest version - Restart the phone - Try a smaller video to determine whether the problem is related to file size If a video appears sideways, rotate it in your phone's video editor and save or export a new copy before uploading it again. Trimming alone does not reliably correct orientation. When to escalate Contact Support with: - The file format - The approximate file size - The time of the failed upload - Whether the video was attached to an Incident Report or Supporting Document Keep the original video in case Support needs it for investigation. Related articles - Adding photos and videos - Uploading large videos - Uploading supporting documents

Troubleshooting

6. “Session expired” errors

A session-expired message means BEHCA no longer has a valid browser session or mobile sign-in token. Browser sessions Organizations can set a browser inactivity timeout from 30 minutes to 24 hours. The default is 90 minutes. BEHCA shows a warning and gives you 15 minutes to stay signed in before logging out. You may also lose a browser session if: - The BEHCA cookie was deleted or blocked - You closed a private or incognito window - Browser privacy settings or an extension removed the cookie Changing MFA settings does not by itself reset active BEHCA sessions. A server restart, device clock, or signing in on another device is not a documented cause of a BEHCA session expiring. Mobile sessions The mobile app sign-in token is valid for seven days. Web and mobile sessions are separate, so being signed in on the web does not sign in the mobile app. What to do Sign in again. If you have unsaved work in a browser tab: 1. Leave the original tab open. 2. Open BEHCA in another tab and sign in. 3. Return to the original tab and try saving. This may recover the save, but it cannot guarantee that unsaved data will remain available. "I keep getting logged out" on the web Check the organization's timeout Ask a Manager or Billing user what browser inactivity timeout the organization uses. Allow BEHCA cookies BEHCA needs cookies for app.behca.com (US) or au.behca.com (Australia). Do not block all cookies for the site. Avoid private browsing Private windows discard their cookies when the window closes. Check privacy extensions If a privacy or security extension clears site data, allow BEHCA or test in another browser. Sign-in loop If signing in immediately returns you to the login page: 1. Clear BEHCA site data and cookies. 2. Close and reopen the browser. 3. Try signing in again. 4. Try another supported browser. Mobile app keeps asking you to sign in - Update BEHCA to the latest version - Force-close and reopen the app - Sign in again - If the problem continues, reinstall the app When to escalate If a fresh sign-in expires again within a few minutes, contact Support with the device, browser or app version, exact message, and the time it occurred. Related articles - Login issues - Logging in - Multi-Factor Authentication

Getting Started

1. Welcome to BEHCA

BEHCA is a behavioral health care platform for tracking, reporting on, and sharing the day-to-day care of the people you support. What you can do with BEHCA There are three things most people use BEHCA for, every day: - Track daily — log behaviors, environment, health, medications, and notes for each person you support. - Log incidents — record incident reports with photos, videos, witnesses, injuries, and follow-ups. - Run reports — see patterns across days, weeks, and months in the dashboard, and export PDFs for clinicians, families, and agencies. Who BEHCA is for - Families caring for a child or adult at home. - Providers — group homes, day programs, in-home support agencies, and clinics. - Schools tracking students with individualized support plans. - The person being supported themselves, when they're tracking their own data (we call this "self-reporting"). You'll see a few different roles inside the app — Billing, Manager, Staff, Guest, and Self-Reporter. We explain each in Understanding roles. Website or mobile app? Both work, and most people use both. - Website (app.behca.com for the United States, or au.behca.com for Australia) — best for setup, billing, managing your team, full reports, and anything you'd rather do on a bigger screen. - Mobile app (iOS and Android) — best for tracking on the go, starting and stopping visits (EVV), and getting push notifications. A few things — like setting up billing or inviting your team — only live on the website. We'll point that out in each article. A note on regions BEHCA runs as a separate service in the United States and in Australia. When you create your account, you choose a region. That choice matters for Australian users in particular because it follows regional data storage requirements — US and AU data stay in their own environments. You can't switch regions later, so pick the one where the people you support actually live. What region does not lock in by itself: - Timezone and imperial vs metric units come from your account preferences (and each profile also has its own tracking timezone based on location). See Account preferences. - Weather is based on each profile's location, not on which regional app you signed into. Common questions - Do I have to pay if I was invited by someone else? — No. If a manager invited you, your account is free. See I was invited — how to accept. - Can I try BEHCA before paying? — Yes, there's a 30-day free trial. A credit card is required to start the trial. See Choosing your plan. - Is my data private? — BEHCA is built for sensitive health information. Only people in your team and people you've explicitly shared profiles with can see your data. Related articles - Choosing your plan - Creating your account - I was invited — how to accept

Troubleshooting

1. Login issues

If you can't get into BEHCA, work through these checks in order. "My password isn't working" 1. Check the region. US and AU are separate. Make sure the region link matches the one you signed up in. 2. Check the email address. Make sure it is the email tied to your account. 3. Try a password reset. Select Forgot your password? and follow the email link. 4. Make sure Caps Lock is off. 5. If your browser or password manager filled the password, try typing it instead. It may have stored an old password. If reset emails don't arrive, see Forgot password not working below. "I signed up with Google or Apple but it's asking for a password" Select Log in with Google or Log in with Apple and use the same email address you used when creating your BEHCA account. You can also set a BEHCA password after signing in, under Account Settings → Change Password. "Forgot password not working" 1. Check spam or junk. Reset emails come from notifications@behca.com. 2. Confirm the email address you entered is associated with your BEHCA account. 3. Wait a few minutes, then request another reset email. 4. Confirm you selected the correct region. If the email still has not arrived after 30 minutes, contact Support. "MFA code isn't working" 1. Check that your phone's date and time are set automatically. Authenticator codes depend on an accurate clock. 2. Use a fresh code. Codes change every 30 seconds. 3. Try a recovery code if you saved one. 4. If you do not have a recovery code, contact Support for help resetting MFA. "It says my account is disabled" A disabled or archived account needs help from your organization's Billing user, Manager, or BEHCA Support. "My session keeps expiring" See “Session expired” errors. Also check that your browser allows cookies for app.behca.com (US) or au.behca.com (Australia), and avoid private browsing for sessions you want to keep signed in. When to contact Support If you have tried the checks above and still cannot sign in, contact Support with: - Your account email address - Your region (US or AU) - The exact message you see - The steps you already tried Related articles - Logging in - Setting up Multi-Factor Authentication (MFA) - Changing your password - “Session expired” errors

Incident Reports

1. What an incident report is

An Incident Report (IR) is a formal record of an event that needs careful documentation — anything from a minor scrape to a serious medication error. They're separate from daily tracking entries because they capture more detail and go through a review before they're considered complete. When to file an IR Common triggers across most organizations: - Injuries — falls, hits, scratches, bites, anything requiring first aid. - Behavioral incidents — significant aggression, self-injury, property damage, elopement. - Medication errors — wrong med, wrong dose, missed dose with consequences. - Allegations — complaints, abuse allegations, neglect concerns. - Near-misses — events that almost caused harm but didn't. - Property damage — significant damage to belongings or facility. - Protective physical intervention — when a physical intervention was used. Your organization will have its own policy about what triggers an IR. When in doubt, file one — it's better to over-report than under-report. What's in an IR The exact fields depend on your organization's setup, but an IR generally captures: - Date and time of the incident (separate from when the report was filed). - Incident type(s) — one or more categories (fall, behavior, medication error, etc.). - Description — narrative of what happened. - Witnesses — anyone present (optional — there's no minimum number). - Injuries — body diagram, severity, treatment given. - Photos and videos — supporting media. - Follow-up actions — what was done, and what's planned next. The IR workflow On the website, each report moves through clear stages you’ll see on cards in Incident Reporting: 1. Draft — the report is still being written. The author can edit freely (most fields save as you change them). 2. Waiting for Reviews — after the author submits (Submit For Review), the report waits for the people chosen as Responsible Parties (reviewers) to finish their review. (In the Status filter on the list page, this lane is labeled Waiting For Review.) 3. Completed — all required reviews are done; you’ll see Completed with the completion date and reviewer on the card. Restricted isn't a separate type — any incident report becomes restricted when it indicates suspected abuse, neglect, or exploitation. A restricted IR shows a RESTRICTED ribbon, and access is limited to supervisors (Managers and those with review permission) plus the report's author. Use the Restricted option in the Status filter to focus on those. Mobile wording can differ slightly, but the underlying states are the same. The Incident Reporting page (web) Open Incident Reports in the top menu (same row as Track and Analyze). The URL looks like https://app.behca.com/ir/{profile-id} — it always applies to the profile selected in the profile switcher. At the top of Incident Reporting: - A date range for which incidents to show (pick dates, then Update). - Status and Author menus — multi-select filters so you can show only certain stages or authors’ reports. - Create New IR — starts a new draft (/ir/{profile-id}/edit). - Subtabs Active and Archived — archived IRs move off the default board into Archived (you can Unarchive from there when allowed). Each IR appears as a card with summary text, reported date/time, author, and status (Draft, Waiting for Reviews, Completed, or RESTRICTED). Completed reports often show a PDF export icon for download. The Dashboard and Audit Log (under Analyze) are separate places to see broader trends and history; this page is the day-to-day IR inbox for the current profile. Who can do what - Anyone with Track IRs permission can create an IR — typically Staff, Managers, and sometimes Guests. - Reviewers are the people you check as Responsible Parties on the report. The list to choose from is your Managers and anyone with IR review permission. - The creator of an IR can also be one of its reviewers — BEHCA doesn't stop you. If your organization wants a separate person to review, make that part of your own process. Notifications When an IR is submitted, BEHCA notifies: - Your Managers (and anyone with IR review permission). - The Responsible Parties you selected, so they know this specific report needs their review. Routine Staff and Guests aren't emailed for every submission. BEHCA does not send notifications to external parties (family, GP, regulators) — that's outside the app and up to your organization's own process. What's not in an IR - Routine behavior tracking belongs in Daily tracking overview, not IRs. Don't open an IR every time someone yells. - Medication administration goes in What MAR is, not IRs. Open an IR only when there's an actual error. - Staff complaints about coworkers (workplace/HR matters) go through HR, not IRs. But if the concern is about harm, abuse, or neglect of a person you support — even involving a staff member — that is an incident report (and will be handled as a restricted one). What the activity log records Each IR keeps an activity log, but it's about the review lifecycle, not every keystroke. It records things like when the report was created and submitted, who was added or removed as a reviewer, reviewer feedback, and when the review was completed. It does not track field-by-field edits (it won't say "Jane changed field 2"). Common questions - Can I retroactively file an IR for a past incident? — Yes. Set the Date and time of incident to when it actually happened. - Do I need to upload photos for every IR? — No. Photos and videos are optional, but recommended for injuries and property damage. - Are IRs visible to families/Guests? — Depends on your organization's settings and the Guest's permissions. Talk to your Manager. - What if I made the IR by mistake? — You can archive it (this works even for drafts). IRs can't be deleted from the app — archiving moves it off your active board while keeping the record. Related articles - Creating an incident report - Submitting and the review workflow - Configuring incident types

BEHCA Support Documentation

Getting Started

Profiles

Documents

Daily Tracking

Medications

Incident Reports

Profile Reports

Scheduling

Electronic Visit Verification

Admin Reports

Managing Your Team

Mobile App

Billing

Your Account

Troubleshooting

Messages

5. Intervention Lens

4. Video upload errors

6. “Session expired” errors

1. Welcome to BEHCA

1. Login issues

1. What an incident report is