What’s new

Changes to CarePath247, most recent first — written for the people who use it. Fixes are listed alongside new things, because a list of only wins tells you nothing.

Get these by email

A short note when something changes — new records, fixes, and what is coming next. No more than a few times a month.

Send me CarePath247 product updates by email — what changed, what was fixed, and what is coming. I can unsubscribe at any time using the link in every message. We will email you a link to confirm first. Sent by Paqads Consulting Inc., 30 Focality Crescent, Nepean, ON K2J 6W7, Canada — hello@carepath247.com.

A policy can belong to a programme

Say who has to acknowledge a policy, and outreach gets its paused families their own list.

  • Who has to acknowledge itFixed

    Every active policy had to be acknowledged by everybody, because there was no way to say who one was for. An outreach worker who visits young parents in their own flats was being asked to sign off medication administration, use of physical restraint and serious occurrence reporting — three residential practice policies, and between them the only thing in her inbox. Publishing or editing a policy now asks which programmes it is for. Tick none and it goes to everyone, which is right for conduct and confidentiality and is what every existing policy stays until somebody narrows it on purpose.

  • Paused families have a list of their own

    Pausing a family takes them off every working list, which until now left nowhere to find them again. Outreach now has Families and Paused families side by side in the menu, with the count of each.

Drag a question where you want it

The form builder reorders by dragging, including moving a question into another section.

  • Pick it up and put it down

    Every section and every question now has a handle. Drag a section above another, drag a question up or down its list — and drag a question into a different section, which the arrows could never do: until now that meant deleting it and typing it again somewhere else. Drop a question on a section rather than on one of its questions and it goes to the end, which is how you fill a section that has none yet.

  • The arrows stay

    They are how you do it from a keyboard, they are the only way on a tablet — dragging does not work for a finger — and on a long form they are still the quickest way to nudge one question by one place. Nothing that worked before works differently.

A contact note is saved, not submitted

No approval queue on the contact log — a note is saved to the file and you can keep adding to it.

  • Save it, then add to itFixed

    A contact note used to travel the same road as a shift log: save a draft, finish and submit, review, approve and lock. An outreach pair are their own supervisors, so that was two people sending notes to themselves — and the only reliable result was a locked note they could no longer add to. A note is now saved straight to the file and stays open to its author. Every change is recorded in the audit trail with the name, the time and which parts changed, and a note edited later says so on its face.

  • A colleague’s note stays theirs

    You edit your own notes. On somebody else’s, what you add goes beside it, signed and dated — their account of their visit is not something anyone else rewrites. Notes approved under the old lifecycle stay locked and take corrections the same way: a signed record does not become editable because the workflow around it changed.

  • No moving a family between programmes

    The transfer request is gone from an outreach file. Moving a child between homes is a residential act with an approval behind it; an outreach family is simply on the programme, or paused, or closed.

Outreach keeps the risk assessment, not the care binder

Safety plans and plans of care come off an outreach file — except where the record says somebody may be in danger.

  • No care binder for a family in their own home

    A plan of care and a safety plan are written for a child living in a staffed house, reviewed by the staff who supervise them. An outreach programme has neither the house nor the oversight, and asked for both off the screen. An outreach file now carries the contact log, the risk assessment, school, identity, contacts, the profile and the papers on file.

  • The safety plan comes back when it matters

    One exception, deliberately kept: a safety plan is never hidden once one exists, and it reappears the moment the risk assessment rates the file high or critical — with the file flagged until one is written. A critical self-harm rating with nowhere to record what to do about it would be the worst of both decisions, and the safety plan is on the front-line floor for that reason.

  • The file is chased for what it actually keeps

    An outreach file is no longer marked as needing attention for a care-plan review it does not have. What is chased instead: the risk assessment’s own review date, a family nobody has reached for a fortnight, three attempts in a row, and a high-risk file with no safety plan.

A form’s name belongs to its programme

Two programmes can each keep their own consent form, and a forms manager is no longer blocked by a form she cannot see.

  • Forms are named within their programme, not the whole agencyFixed

    Forms have belonged to a programme since the summer, but the rule about names did not move with them: the first programme to create a “Consent to care and treatment” took that name from every other programme and from the agency. The worst of it landed on the people the builder was made for — a forms manager who looks after one programme was told “a form with that name already exists” while her own list said “no forms yet”, because the form in the way belonged to somebody else and she is not allowed to see it. Each programme now keeps its own, the agency keeps its own, and the message says which.

  • Publishing stops at your own programmeFixed

    Publishing a form retired every published form sharing its name across the agency. A programme publishing its own intake could therefore retire the agency’s form of the same name, or another programme’s, without anyone being told. It now retires only the previous version of that programme’s own form.

An outreach file, shaped like a young parent’s file

The risk assessment asks perinatal questions, school and the people around her stay, and the papers on file show on the profile.

  • A risk assessment that asks the right questions

    A young parent in her own flat was being scored against absconding, fire setting and sexualized behaviour — a page of “none identified” that told a reviewer nothing while missing what is actually dangerous. An outreach programme is now assessed on perinatal mood and anxiety, infant safety, bonding and attachment, pregnancy and postnatal health, relationship safety, housing and income, supports and isolation, before or after the birth. Self-harm and substance use keep their place and their history, so an assessment still compares with itself if somebody moves programme.

  • School stays, because she is often still in it

    The school and day-programme record is back on an outreach file, with young parents’ programmes and adult upgrading added to the list of settings. Who to call at the school is exactly the sort of thing an outreach worker holds.

  • The people around a young parent

    Contacts already covered family, partners, the client’s own children, society and case workers, doctors and schools. Midwife, public health nurse and childcare or daycare are now on the list too — in the first year they are often the three numbers that matter most.

  • Papers on file show on the profile

    A health card, a status card, a signed consent or a returned form now appears on the client’s profile as well as under Documents, with what kind it is, when it was signed and when it expires. They are listed rather than displayed: opening one is an access event, and a page that quietly loaded every image would log a download nobody asked for.

Outreach stops pretending to be a group home

A community or outreach programme now works from the contact log, and loses the residential screens it never used.

  • The contact log, not the shift logFixed

    A worker who visits families in their own homes has no shift to write up — and the whole-house daily log refused her programme anyway, which is why it would not open. Her record is the contact log: every visit, call and unanswered door against the family, with how long since anybody actually reached them, and three unanswered doors in a row shown as what it is. It has its own place in the menu and sits on the family’s file.

  • The screens that are not her job are gone

    For someone whose programmes are all outreach, the eMAR, shift handover, comm book, activity programme, quarterly residential return, staff rota, foster register, policies and reports no longer appear. Her family’s file loses medications, immunisations, school, inventory and progress reports, and stops being flagged for having no daily logs. What is left is the family, the contact log, the plans, and forms.

  • Incidents and serious occurrences are off the outreach screen

    At the agency’s request, an outreach programme no longer shows either. Note plainly what that means: there is now no way to file a serious occurrence report in CarePath247 for a family on an outreach programme, while the duty to report one to the ministry is unchanged. Ask us and we will put the serious occurrence screen back for your outreach programmes.

  • Add a family without a referralFixed

    Outreach has no intake queue to admit from — a young parent with children is not a candidate for a bed. Add the family straight into the programme and start the contact log. Adding someone is also no longer blocked for a worker whose access is scoped to one programme, which is every front-line grant we issue.

  • Pause a family, and bring them back

    Work with a family can stop for a year and start again. Marking them inactive takes them off today’s lists and leaves the file whole; making them active again puts them back with their history intact. It is deliberately not a discharge — discharging starts the retention clock that counts down to destroying the record.

  • Someone re-admitted no longer stays marked dischargedFixed

    A client admitted again after a discharge kept the discharged mark, which meant an active file was sitting on the retention clock. Admitting somebody now returns them to active and clears the discharge date.

  • A corrected name now changes everywhereFixed

    Fixing a misspelling updated the file you typed it in and nothing else — the client list, the record header, every tab and the dashboard kept the old spelling until something else happened to refresh them. It looked as though the correction had not saved. It now reaches every page at once.

  • Remove a file added in error

    A duplicate typed twice, a name against the wrong agency, a test entry from the first week: an administrator can now remove a client file that holds no care record at all, under Admin → Retention. The moment a log, contact, incident, medication, form or plan exists against it, it leaves only through discharge and the retention period, as before. Either way the audit trail keeps the certificate.

  • Take back a file you uploaded

    The person who attached a document to a file can remove it — a wrong scan, a duplicate, somebody else’s page. Nobody else can, a withdrawn consent is never removed this way, and the audit trail keeps the record that the file was there and who removed it.

  • Forms managers can find the form builderFixed

    The builder has accepted a programme-scoped forms manager since the role was introduced, but the menu link asked for agency-wide access — so the people made forms managers for one programme had no way in except by typing the address.

One notification a day, instead of one an event

The bell gathers the day’s routine updates into a single item, and the morning brief stops arriving at weekends.

  • Routine notifications fold into one a dayFixed

    A supervisor rostering a fortnight sent each worker ten separate “you’re on the schedule” notifications; a task assignment arrived as its own, a certification expiry as another. That makes the bell something people stop reading, which is worse than no bell at all — the one notification that mattered sits in a list of twenty that did not. Routine updates now gather into a single item for the day, holding its lines, each still a link to the thing it is about. Opening it marks it read; anything new that arrives afterwards brings it back.

  • What still arrives on its own

    Anything you must see now is never folded in: an on-call alert about a serious occurrence or an incident, and a decision somebody is waiting on. Those behave exactly as before, including by email. Everything else is carried by the day’s summary and the morning brief — one email rather than fifteen.

  • The morning brief takes the weekend off

    The 7 a.m. brief for supervisors — what is waiting for approval, counts only, no names — now runs Monday to Friday. Monday’s carries the weekend with it, so nothing is missed; it just stops landing in anyone’s inbox on a Saturday.

Blank forms download as fillable PDFs

Send a form to a family or a placing agency, and get it back filled in.

  • Every form, as a PDF somebody can type into

    Choose “Fillable PDF” on any form — from the list or from the builder — and you get the whole form as a proper PDF: each section under its own heading, real boxes to type in, tick boxes, dropdowns where the form offers a choice, and signature lines with the date beside them. It opens in anything, including Preview on a Mac, so a family or a placing agency can fill it in on screen and send it back rather than printing, writing and scanning. “Print blank” is still there for the kitchen table.

Intake stops being everybody’s business

Referrals and forms belong to the people who do intake, and to the programme they were taken for.

  • Front-line staff no longer see referrals or fill in formsFixed

    The staff role carried the forms and referrals permissions, so every worker on shift could open your referrals list — every family referred to the agency, names and dates of birth, most of whom never arrive — and fill in any published form. Neither is front-line work. Intake happens before a child is placed, and it belongs to a supervisor, an intake worker, or whoever you have made your forms manager; all three keep everything they had. If somebody front-line does take referrals at your agency, give them the Intake worker or Forms manager role under Admin → Users and they will have it back. One consequence worth knowing: a staff member who filled a form in before today can no longer open it — their supervisor and your administrators still can, so nothing is lost to the agency.

  • A referral belongs to the programme it was referred toFixed

    The referrals list showed everyone the whole agency’s referrals, however their own role was scoped — so a supervisor of one house saw families referred to another. It now shows the programmes you hold, plus any referral you took yourself, and administrators still see them all. Opening one you have no business reading answers “not found” rather than “forbidden”, because a web address should not confirm that a family was referred here. This is the same change made to filled-in forms last week.

A form belongs to a programme, and prints blank

Forms can be handed to the programme that uses them, and you can print an empty one for a family to fill in.

  • Forms belong to a programme

    When you create a form, or adopt one of ours, you now say who it is for: one of your programmes, or the whole agency. A programme’s form is filled in and edited by that programme’s people and appears to nobody else; an agency form stays available to everyone who fills forms in, but only an agency-wide administrator can rewrite it — otherwise one programme could change the consent every other programme depends on. Existing forms belong to the agency, as they always have, and “Who this form is for” on any form moves it.

  • The form builder shows you your own programme’s forms

    Someone who runs a single programme can now be given the form builder without being given the agency. They see their programme’s forms, build and publish them, and nothing else — no client records, no logs. Administrators still see every form, which is how a director keeps an eye on an outreach team.

  • Print a blank form

    Intake happens at a kitchen table as often as at a desk. Choose “Print blank” on any form — from the list or from the builder — and you get an empty copy with ruled lines to write on, the right questions in the right order, and signature lines. Until now the only printable copy was one already filled in, so agencies kept printing the Word document they had before, and the paper slowly stopped matching the form.

A filled-in form is not agency-wide reading

Who can open a completed form now depends on the programme it belongs to, not on holding the forms permission somewhere.

  • Forms belong to the programme they were taken forFixed

    Opening a filled-in form only ever asked whether you fill in forms *somewhere* — so every account at an agency could read every form in it, by clicking the list or pasting a link. For an agency running an outreach programme alongside its houses, that meant a group-home worker could open a young parent’s intake, pregnancy history included. It now asks which programme the form belongs to. Administrators with agency-wide access still see everything, which is how a director oversees a team; everyone else sees the forms of the programmes they work in. “Recent forms” lists the same set, so nothing is shown that cannot be opened, and the buttons on a form now match exactly what the save behind them will allow.

  • A referral that is not attached to a programme yet

    Most intakes are taken before anyone is placed anywhere, so a form often starts with no programme on it. Those stay visible to whoever is filling them in, and to administrators — but not to the rest of the agency. If a team shares the work of an intake, choose the programme when you start the form and everyone on that programme will see it.

Forms you can start from, and somebody to own them

Three residential forms ready to adopt and edit, a role for whoever builds them, and a filled-in form you can print.

  • Three forms for residential programs, ready to adopt

    A residential admission record, consent to care and treatment, and photo, media and transportation consent. Adopt one under Form builder and it is yours to cut about — rename sections, delete what you do not ask, add what you do. They are drafted from what Ontario licensing and the CYFSA expect to find in a file rather than copied from any one agency’s pack, so read them before you publish: they are a starting point, not an approved document. The admission record asks a young person’s First Nations, Inuit or Métis identity and band, because those drive obligations that begin the day they arrive, and a file that never asked cannot show it later.

  • A Forms manager role

    Until now the only people who could build and publish a form were supervisors and administrators — so letting somebody own the intake pack also gave them every child’s record, every log and the audit trail. The new role builds, publishes and fills in forms, takes referrals, and sees nothing clinical. It is on every agency now and assigned to nobody; an administrator gives it to whoever actually does the job, under Admin → Users.

  • Print or share a form that has been filled in

    A consent often has to go back to the worker who signed it, and an intake into the file a reviewer opens. Open any form and choose Print / share. It prints the questions as they stood when the form was submitted — not as the template reads today — with the signatures, who submitted it and when. Opening that view is recorded in the audit trail, which is new: until now only changes to a form were.

Behaviour you can count, and a handover the next shift signs

Two things that were only ever prose: whether a young person is doing better or worse, and what the next shift needs to know.

  • Behaviour, recorded in a shape that adds up

    Behaviour lived in four places — a section on the daily log, a section on the quarterly report, goals on the plan of care, a comm-book category — and all four were free text. None of them could answer the question a plan-of-care review turns on: is this getting better or worse? There is now a behaviour record with the structure your staff are already trained to write — what was happening beforehand, what happened, what staff did, how it ended — and a Behaviour tab on each young person’s file that counts the last thirty days against the thirty before. Recording coping counts too, so the trend can point upward for a young person who is doing better rather than only ever downward.

  • Your safety plan’s own language, on the observations

    Each behaviour type is tagged to a phase of the crisis cycle your safety plans already use — pre-crisis, triggering, escalation, outburst, recovery. A week of records then reads against the plan written for that young person, rather than against a generic scale that means nothing in particular.

  • The quarterly report shows the counts behind the section

    The behaviour section of a quarterly progress report used to ask a supervisor to summarise three months from memory. The period’s counts now sit beside the box as you write, and stay with the finished report — so the narrative is written against evidence, and a reviewer can see the numbers it came from.

  • Shift handover, as a record rather than a note

    You could always write a handover note in the comm book. What you could not do was hand over: there is now a handover per home per shift, gathered from what we already know — medications still due, an incident still open, logs waiting on review, a deadline landing tomorrow, a young person who did not settle — with a box against each young person for what only a person can tell you. The outgoing worker completes it, which freezes the list, and whoever comes on acknowledges it against their name and the time. Shift-gated sign-in already opened the record an hour before a shift so staff could read the handover; now there is one to read.

  • Only what the next shift can act on

    Staff certification deadlines are real, and they are a supervisor’s job rather than something the worker coming on at eleven can do anything about. They stay on the inbox and the compliance report instead of sitting at the top of the handover marked urgent, where three of them would bury the one medication that is.

  • A quiet shift is a real handover

    Nothing outstanding is a perfectly good handover, and it can be completed in one click. Demanding a paragraph would only teach everyone to type “nothing to report” forever, which tells the next shift less than an empty list somebody checked and signed.

The right date after eight in the evening

Screens that asked our server what day it was got tomorrow from 8 p.m. onward. They now go by your calendar.

  • Evening shifts no longer land on tomorrowFixed

    Our servers keep time in UTC, which in summer runs four hours ahead of Ontario. Several screens asked the server for “today” and, from 8 p.m., got tomorrow: a log started at nine was filed under the next day, a deadline read as overdue the evening before it was due, a consent with a day still left showed as expired, and a young person’s age ticked over the night before their birthday. All of them now use your calendar, so the day changes at midnight where you are.

  • After-hours alerts reach tonight’s on-call supervisorFixed

    The one that mattered most. An alert raised after 8 p.m. looked up tomorrow’s on-call roster, so it reached the supervisor coming on in the morning rather than the one holding the phone that night. It now reaches whoever is on call at the time.

  • A report includes the whole of its last dayFixed

    A date range ending on a given day stopped four hours early, which left the evening shift of that final day out of incident and audit reports. Ranges now run until midnight your time.

  • An import with a mistyped date flags that row, not the whole fileFixed

    A spreadsheet with an impossible date in it — 30 February, say — used to make the entire import fail. That one row is now flagged for correction and the rest come in.

Serious occurrences on the ministry’s two clocks

Level 1 and Level 2, each timed from when you became aware — and times that mean your clock, not our server’s.

  • Level 1 and Level 2, each with its own deadlineFixed

    The ministry gives a Level 1 serious occurrence one hour — notify immediately, report within the hour — and a Level 2 occurrence twenty-four. We gave every report twenty-four hours, which meant a death, always Level 1, was shown twenty-three hours it did not have. Each report now carries its level, and the countdown, the dashboard and the deadline badge run on that level’s clock. Choosing a category shows the ministry’s Level 1 tests for it beside the choice, and a death is Level 1 without asking.

  • The clock starts when you became awareFixed

    The ministry times a report from when the agency became aware of the occurrence, or decided an incident was one — not from the moment it happened. An injury found at the morning check now starts its clock in the morning instead of arriving already overdue. The time is asked for when the report is opened, starts at the time of the incident, and can be corrected while the report is a draft. Reports already sent keep the deadline they were held to.

  • Reports record when they went in, and why they were late

    Marking a report as sent now asks when it was submitted to the ministry, so a report filed on time and recorded here twenty minutes later is not marked late. A report that did go in after its deadline asks for the reason, as the ministry asks of every late report.

  • A report you have sent is no longer called overdueFixed

    Once a report was marked as sent, its deadline passed like any other — and the dashboard went on calling it “overdue to the ministry” until the file was closed, which can take weeks of investigation. Only reports still waiting to be sent count now.

  • Times are your timesFixed

    Our servers keep time in UTC, and parts of the app were quietly using that clock instead of yours. The new incident form suggested a time four or five hours ahead of the real one, and times the system stamped itself — when a form was submitted, when a report was approved — were shown four or five hours later than they happened. Every date and time is now read and shown on Ontario’s clock. One thing to check: an incident time that was typed in by hand, rather than left at the suggested time, was saved four or five hours early, and now shows as it was saved. A draft can be corrected directly; an approved report, with an amendment.

Supervisors can use the buttons they were being shown

A permission check that was stricter than the screen it belonged to.

  • Filling in a form works for house supervisorsFixed

    A supervisor responsible for one home was shown Start, Save and Submit on a form, and got an error page on pressing any of them. The screen was asking whether she could fill in forms for her own house; the check behind it was asking whether she could do so across the whole agency. They now ask the same question. This has been wrong since the start of September, and only for people whose role is tied to a single home — which is why nobody administering an agency ever saw it.

  • The same mismatch, everywhere else it reachedFixed

    Recording a referral, admitting a child, discharging one, requesting a transfer, and editing a client’s profile, photo, documents or consents were all wrong in the same way, and are all fixed. Requesting a transfer was the plainest case: that form is only ever shown to people who cannot approve a move themselves, so it was being offered exclusively to the people it then refused. Admitting a child is now checked against the home they are being admitted into — narrower than before, not wider.

A client file you can navigate, and a builder that stops asking

Every part of a record is its own page, and the form builder no longer hands you its bookkeeping.

  • Every part of a client file has its own page

    Placement, medications, daily logs, the contact log, risk, school, contacts, documents — each has its own address now rather than being a stop on one very long page. The back button works, you can send a colleague a link to the part you actually meant, and opening a record to check one medication no longer loads the entire file first. Safety plan and Plan of care open directly, instead of stopping at a summary card that needed a second click.

  • The form builder stopped asking you to fix its own bookkeepingFixed

    Adopting a starter form could greet you with twenty-one errors about “field keys” — internal labels nobody types and nobody sees. There was only ever one correct answer to each, so the app applies it itself now, when a form is adopted, saved, or published. What is left is only what a person can actually decide: a section without a title, a question with nothing written in it. The export column names are still there to look at if you ever need them.

  • The menu no longer highlights two places at onceFixed

    Opening the form builder lit up both Form builder and Fill in a form, because one sits underneath the other. The most specific match wins now — so Clients stays highlighted while you are inside a client’s record, where it is the only honest answer, and hands the highlight over wherever a page has a menu entry of its own.

The starter intake, and a watermark you now choose

Two fixes to forms — both of them ours — and a default turned the other way round.

  • The starter intake can be publishedFixed

    Adopting the young-parent intake produced a draft with twenty-one errors on it, because the questions we shipped were labelled in a style the builder refuses. Anyone who pressed “Use this” got a form they had not written, could not publish, and could not obviously repair. The template is corrected, and the checks the builder runs now also run against every starter form before one of them can ship.

  • Saving a form no longer unwires itFixed

    The fields that carry a child’s name and date of birth onto the client record at admission were being stripped out the first time a form was saved. Nothing failed and nothing was reported — the answers simply stopped arriving, and somebody retyped them by hand on the busiest day. Saving keeps them now, and a mapping that would not work is refused rather than accepted and ignored.

  • The builder repairs keys for you

    Every problem is listed rather than the first eight, each section shows how many of them are its own, and a form whose keys will not publish can be put right in one click. Keys that are already correct keep their exact spelling, so an export somebody built a spreadsheet around still lines up. A field that feeds the client record now says so on the field itself.

  • The name watermark is off unless you switch it on

    Tiling a worker’s name across every screen they open is a decision about how an agency treats its staff, and we were making it for you. It is now off unless you turn it on, under Admin → Organization, and switching it either way is recorded in the audit trail. An agency that had already ticked the box keeps it; one that never opened the setting will find it off.

Safety plans in the shape people are trained to read

The crisis cycle, and a fix to a problem that stopped some plans being approved at all.

  • The crisis cycle on every safety plan

    Five phases — pre-crisis, triggering, escalation, outburst, recovery — each pairing what staff will see with what they do about it. It is the structure CPI, TCI and BMS all teach, and it is how most plans were already written on paper. Plans approved before today keep every word they have; the new fields simply appear, empty, on the next revision.

  • A phase left half-written is flagged

    If a phase describes a behaviour with no intervention beside it, the draft says so before approval. A row that names a danger and not the answer to it is worse than a blank one, because it reads as though the thinking was done.

  • Revising a plan a third time now worksFixed

    Approving the third version of a safety plan or plan of care could fail with a server error, leaving the draft stuck in review. The cause was in how the previous version was found when it was archived. Nothing was ever lost — the drafts were intact and can now be approved normally. If a plan of yours is sitting in review unexpectedly, that is why.

  • Images load fasterFixed

    Photographs were being re-processed on every single view rather than cached. They are now cached properly, which makes client records and the dashboard noticeably quicker to open.

Consents you can rely on, and a form nobody has to build from nothing

For programs that work in the community, and for anyone who keeps signed paper on file.

  • Signed documents that tell you when they lapse

    Upload a two-way consent, a transportation form or home-visit guidelines, and record when it was signed and when it expires. You are warned thirty days out and it joins your compliance list. A consent with no signing date is shown as unproven rather than valid — that mistake is the one this exists to prevent.

  • Withdrawn consent is marked, not deleted

    If a family withdraws consent, record it. The document stays on file, because you may need to prove it existed, but it is clearly marked so nobody relies on it by mistake.

  • A contact log for work that does not happen on a shift

    Home visits, phone calls, texts, and the attempts that reached nobody. Outreach and community programs finally have a record built for episodes of contact rather than a shift somebody worked.

  • Starter forms you can adopt in one click

    A young-parent intake is ready to use — eight sections, thirty-five questions. Adopt it and it is yours: rename it, cut sections, add your own. Names and dates of birth entered at intake carry onto the client record automatically, so nobody retypes a child’s details at admission.

Supervision, risk, and what was offered

Three records that licensing asks about and that most agencies keep in a spreadsheet.

  • Structured risk assessment

    Eight domains, each rated on its own. The overall level is the highest single domain, never an average — averaging away one critical risk is how a risk assessment becomes dangerous. The review date follows the rating: monthly at critical, annually at low.

  • Staff supervision on a schedule

    Supervision sessions with named sections, and the next one scheduled the moment you close the last. Only a regular session moves the clock, so a debrief after an incident does not quietly reset the cycle.

  • Activities and participation

    Record what was offered as well as what was taken up. A cancelled activity is not counted as something the young person declined, and a pattern of declining surfaces before it becomes a review finding.

Your agency’s name on the screen, and on the page

Smaller changes, mostly asked for directly.

  • Watermarks can be turned off

    The reader’s name across printed records is now an agency setting rather than something everyone gets. Printing behaviour was sorted out at the same time, so the watermark appears on paper the way it appears on screen.

  • Install it on a phone or tablet

    Add the site to a home screen and it opens like an app, under your own agency’s name rather than ours. Nothing is stored on the device.

Asked for something?

Most of what is on this page started as a message from someone running a home or a program. If CarePath247 does not do something the way your team expects it to, tell us — that is how this list gets written.

What’s new · CarePath247