Back in August, an ad hoc committee of the juvenile justice board in Hillsborough issued a lengthy report on the state of placement instability in their circuit. The report diagnosed the phenomenon of children refusing placement as a major source of that instability.
The committee concluded that “children under the care and custody of Florida’s child welfare system should not have the ability to refuse temporary placements that have been determined to be in their best interest by the parties charged with their care.” The committee recommended a new law to expand the “children in need of services” statute to permit foster children to be placed into staff secure facilities (i.e., 24-hour supervision) if they refused placement, were chronic runners, didn’t go to school, or didn’t comply with the treatment recommended. They could then be placed in a physically secure (i.e., lock-down) facility if they didn’t comply with the staff secure program.
The proposal initially struck me as well intended but misinformed. Foster kids can already be placed in staff secure facilities by DCF without a court order. Any group home can be converted to staff secure by upping the staffing ratio and making sure someone is awake at all times in the home. You don’t need a new legal regime for that — you need money.
Second, foster kids can be placed in physically secure programs through a DJJ commitment, a SIPP placement, a Marchman Act placement, or a Baker Act. All of those placements are extremely expensive and have a limited number of beds. The gatekeepers for those programs have to do constant triage to limit use of the programs to the neediest children. If you want to increase access to secure settings with intensive treatment, it will take money to expand the placement array. Once you have a sufficient array, you can start working with the less extreme cases described by the committee.
The report correctly notes that Florida’s foster care placement system is reactionary. It recommends data collection and analysis to create predictive models for which children will have future placement challenges, because “indisputable data on risk factors is not available and would be beneficial to decision making.” If you know me or have read anything on this blog, you know that I couldn’t pass that challenge up.
It turns out that Hillsborough has been logging when children refuse placement in FSFN since 2017. (This should be required for all CBCs.) There were 49 kids in the most recent version of the public database that had ever refused placement. Me and my team of intrepid students reviewed the complete history of all 49 kids, then the history of their most common placements, and then the whole placement array in Hillsborough. What we learned filled over 150 pages. I have broken it into a main report and an addendum that gives a narrative of the placement history of all 49 children. (The addendum will come out soon — it’s over 100 pages.) This post is a summary.
What we found was consistent with existing research on placement instability in foster care. The refusal children were disproportionately non-white teens with significant time in group home settings; but there were children as young as seven who refused. For the most part they were well-known to the system: the median number of placements prior to refusal was 21 (31 in total), and nearly 70% of their placements prior to refusal (75% in total) ended because the provider requested the child be removed. Being ejected by providers after placement was the most pronounced feature of children who refused placement. Most of the children refused only one or two times; and many spent more time at the agency’s office because no appropriate placement could be found than they did because they refused.
What surprised us was that children were slightly more stable after refusing placement than they were before, at least temporarily. The refusal episodes seemed to elicit an agency response that children’s previous placement instability did not. Usually the added stability was from the agency obtaining therapeutic placements, but sometimes stability came from negative causes, as some kids ran away for extended periods of time or were arrested. In some cases, it appeared that the children refused with a specific placement in mind they wanted to be in.
Speaking of arrest, the committee was mostly composed of DJJ professionals, so it makes sense that they were focused heavily on that population. However, it turned out that the children who refused placements were not any more seriously involved in the delinquency system than other unstable kids in foster care. They did, however, appear to have higher levels of mental health needs.
And that’s where Hillsborough is particularly failing. Our review of the system as a whole found a placement array that routinely played hot potato with high-needs children, bouncing them around in circles often back to placement they were just kicked out of. When I first read the committee’s report, my thought was “you’re describing an STGC — just open one.” Hillsborough has no Specialized Therapeutic Group Care programs, and instead sends children across the state to therapeutic programs. Locally it relies on group homes that rarely keep children more than a month on average and enhanced rate foster homes that keep kids a median of 4 days per placement. The problem isn’t the law; the problem is the array.
Our review disagrees with the committee’s report in another way: instability was in fact highly predictable and often began long before a child refused placement. Existing research shows that a child with 4+ placements has a 70% chance of additional instability, and a child with 6+ daily maladaptive behaviors has a 25% increase in risk of disruption per additional behavior. By reviewing the placement histories we found 131 highly unstable children in Hillsborough since 2017, many of whom had more than 50 placements. Only 38 of them had ever refused a placement, though. Refusal and non-compliance are not appropriate triggers for intervention — instability is.
Where we agree with the committee is this: Hillsborough needs to regain control over its array and create a clear escalation process for children who are serially ejected from placements. This will take a significant effort to change the culture. The burden should not be on the children to accept a 22nd placement failure or risk civil commitment for disobedience. The burden should be on the providers to work with children to never get to that level of instability.
Our full report is linked here. The addendum containing the narratives for all 49 children will be released soon. I hope this is helpful to people on the ground in Hillsborough.
I sat on this post until after National Adoption Month because it seemed like the polite thing to do and because I didn’t have time to finish it until now. It’s about adoption. Not whether adoption is good or bad. My feelings about adoption are whatever my client’s feelings are — and it should be no surprise that some kids want to be adopted and others do not. Instead, this post is about adoption as a policy, a specific tool of the system to accomplish certain goals. It is specifically about how much that tool costs.
The Guardian ad Litem Program started as a scrappy community of advocates and gadflies who sought to bring attention and change to the dependency system. It is now a state agency that’s been appropriated over $600 million in the last 15 years. There has never been a comprehensive study to determine whether the Program accomplishes its goal of improving the lives of foster children. I looked at the Program’s performance numbers, first out of irritation, then curiosity, and ultimately the realization that we need more fact-based information about the “Second DCF” to answer the core questions surrounding its continued funding and structure. The questions explored here are whether the GAL Program is ethical, effective, and good for children? The answer to all three questions, it turns out, is the same.
This post introduces a new public FSFN dashboard on permanency timing in Florida’s child welfare system. If you want to just play with the dashboard, you can find it here. All but one of the graphics in this post come from the dashboard.
Every year, in legislatures across the country, well-meaning people propose bills to speed up permanency for foster kids. Permanency is a psychological concept focused on attachment, belonging, and community. Those are hard to legislate, so people focus instead on procedural definitions. The legal meaning of permanency is to close the court case and get the state out of a family’s life for as long as possible. In the process, hopefully leaving the child better than the system found them.
That closure could happen by returning a child home to a parent, placing the child in a guardianship, or having the child adopted. It could also mean a child aging out. The end result is largely the same to the state: one less case on its docket, and varying ongoing financial obligations depending on the way the child exited care. The path a case takes can change a child’s life.
This post introduces a new public FSFN dashboard: the Placement Provider Info Dashboard. If you want to jump straight there, feel free. You should click the fullscreen button in the bottom right corner. Below is the why and how of it.
There is a well-meaning bill working through the legislature that would exempt the names of foster parents from Florida’s public record laws. (Current law exempts their addresses, financials, and the floorplans of their houses.) The bill cites four “public necessities” to bar access to foster parents’ names: (1) it will help keep foster children’s names confidential, (2) it will prevent “unwanted contact” by the press, (3) it will prevent “unwanted contact” by the child’s relatives [i.e., parents], (4) not doing so would compromise foster parents’ privacy. The reasons don’t really stand up to scrutiny. More importantly, public access to information on foster placements is actually a good thing.
The elephant in the room is named Candi Johnson
Let’s start by acknowledging that Candi Johnson, the mother of two children in foster care, orchestrated the shooting of an elderly foster parent in Miami. She went to the foster home with her teenage son and demanded the children. When the foster parent fought back, the son shot her and fled with Candi Johnson and the kids. The foster parent is a hero for defending the kids even when she had no idea who was after them. The media reports that Candi Johnson had a long history of violence and had absconded with her children before. She is currently pending trial for attempted murder, kidnapping, armed burglary, and interfering with child custody.
The public records exemption would not have prevented Candi Johnson and her son from shooting the foster parent. The list of foster parents in the FSFN database has nearly 68,000 people on it. Candi Johnson’s kids would have aged out before she figured out which provider was caring for her children that way. More importantly, Candi Johnson did not use public records to find the foster home. Everyone in the neighborhood knew the woman was a foster parent. Everyone on the case knew Candi Johnson was violent. The foster mother didn’t know who Candi Johnson was when she banged on the door — or else she wouldn’t have opened it and maybe wouldn’t have accepted the placement. Having foster caregivers meet with parents in a supervised setting when they first take in kids could have actually prevented this. Further increasing the separation between them would not.
The bill isn’t about the kids
Candi Johnson stirred up a lot of latent anxieties that some (but certainly not all) foster caregivers feel about the families of the children they take in. The sponsor of the bill says that DCF received calls from “several” foster parents that they would quit if their names were not protected. I received a comment from one foster parent saying the same. The problem is that the bill doesn’t protect foster parents from the people they (rightly or wrongly) are afraid of. It does, however, make it harder to identify wrongdoing by DCF or other foster parents towards the kids they care about.
Let’s start with the bill’s first goal: protecting children’s privacy. The bill doesn’t actually do that. Having the names of foster parents does not tell me the names of the kids in their homes. If we want to keep foster children’s information confidential then we would also include provisions making it illegal for foster care providers to post about the child online, including pictures and over-sharing facebook posts. That’s how most parents in the system find their kids — a mutual friend spots the pictures and forwards them.
If we were serious about not disclosing a child’s foster care status, the bill would have provisions aimed at school personnel who tell a child’s classmates and protective investigators who question neighbors and disclose more than they should. We would also shut down National Adoption Day and Heart Gallery events where kids are brought to one place with giant signs that say “foster care” and television cameras rolling. Nobody is particularly worried about any of that.
A public records request on foster parents would currently give you a name and maybe a zip code, but nothing on the individual kids. You can get that much from a google search (and more). There is actually a much bigger and more immediate leak of information about foster children: the court hearings are open to the public. I have been in countless hearings where essentially this exchange happened in front of a room full of strangers waiting on other cases:
CLERK: Calling the Case of [insert actual name of the child or parents]. All parties please announce.
[everyone, including the parents and children go around and say their actual legal names]
JUDGE: Are the foster parents here? Please just use their initials.
[nobody mentions that there is no law that says foster parents get to be anonymous in court hearings]
FOSTER PARENT: J.M. Good morning, Your Honor.
JUDGE: Ok, we’re here today for a status on medical treatment. Did the child go to the gynecologist for an STD check? She was sexually assaulted. I am very concerned that you did not take her sooner.
CASE MANAGER: Yes, the child is present and can report. She tested negative.
We accept that the hearings are open because we believe the system is better when it works in public. In that context, foster parents’ names are not more sensitive than a child’s history of abuse. Foster parents are good people who largely volunteer to help kids and families that need it. They do not, however, have stronger privacy interests than the actual children and families in the system. When you sign up for this work, you sign up for it in public.
Second, the bill seeks to limit foster parents’ names because disclosure could lead to “unwanted contact” from the child’s “relatives.” This also won’t work and is actually a bad policy goal. Foster parents, parents, relatives, case managers, guardians ad litem, and therapy dogs all sit outside court together, sometimes waiting hours for the case to be called. In most courthouses it’s impossible to hide. And they shouldn’t want to hide: if foster parents are following the Quality Parenting Initiative co-parenting guidelines, then they use that time to talk with the parents and relatives to get to know them and the children better. I hope this sounds as direct as I mean it: a foster parent who doesn’t want contact with a child’s relatives should look for other ways to help children. Fostering isn’t for you.
There may be times when it’s not safe to engage in co-parenting with the child’s family, such as in Candi Johnson’s case. In those situations, court orders and injunctions directed at the parties on the case are the right remedy. Limiting the public’s access to information about foster care providers doesn’t solve the problem: the child’s family already has the foster caregiver’s identity information, or can easily get it by reading the Case Plan or by waiting in the parking lot for 20 minutes. In cases where there are serious safety concerns, there should be serious security responses. A general public records exemption is not a cure.
Finally, I’m not a First Amendment scholar, but “unwanted contact by the press” is why we have public records laws — the press and other watchdogs are supposed to investigate and sometimes that investigation is unwanted. The foster care system is a billion-dollar-a-year government industry. The fact that it recruits and underpays volunteers to perform some of its essential functions does not insulate it from scrutiny.
Now for why it’s actually good to make this information public.
Public information helps make better decisions
After publishing the Visualizing Foster Care Instability project, I received a lot of comments asking for a dashboard that gives information about the foster care providers. I attended a Florida Youth Shine quarterly meeting where a young person still in foster care said in a session, “There should be some way for us to know about placements before we go there. We should know as much about them as they do about us.” That resonated with me. We wouldn’t stay at a hotel without reading the reviews, but we expect foster kids to just show up at a house in the middle of the night and take it on faith that it will be safe.
So I made something: The Florida Foster Care Provider Dashboard. (I’m not really good at naming things.) The goal is to put everything we know about foster care providers in one place so that advocates and the public can make better decisions on how the system operates.
It’s functional, not pretty. I recommend viewing it in full screen because it has a lot of parts. Here’s what it looks like:
Here’s what you can learn from it:
How long do kids stay with ____? This chart in the top-right shows the distribution of how long a provider’s placements lasted. A provider’s average placement length may be skewed due to a few kids they kept for years. This chart shows the real breakdown. You can set it to measure in days, weeks, months, or years. Above, you can see that this provider had 315 placements in total and 134 that lasted less than a week. The average placement length was 45 days, but the median was only 9 days. This is not a stable placement for most kids who go there.
What kind of placement is this? The two boxes in the bottom left break down DCF’s own designation of the placement type. Above you can see that this provider was almost exclusively a foster care provider (orange bar), but spent 16 days as a relative placement, and 4 as a group home. The Service Type shows that this home was mostly for kids aged 13-17.
Why do kids leave this placement? The third box on the bottom left shows the reasons that placements with this provider ended. You can see above that 101 placements ended “in accordance with the case plan,” which usually means pursuant to a court order, while 61 placements ended because the child ran away. Twenty kids aged out of this home.
How has it changed over time? The box in the bottom right corner show the complete placement history for this provider. You can see that they started fostering in 2003 and had their last placement in 2018. Over time, placements with this provider have gotten shorter and shorter. That’s fairly normal for the long-time placements. The first few placements are usually the longest.
What about some summary stats? Right in the middle are the summary stats that I’ve calculated for the provider: number of children, number of placements, average placement length, median placement length, average miles kids moved from the last placement, and average concurrent kids (meaning how many children were placed there simultaneously on average).
I’ve also created Provider Flags that alert you to certain questions you might want to ask about a placement before putting a child there. They are found in the pink box right in the middle of the dashboard. The flags are based on the objective criteria below.
Death of Child: The provider had at least one placement where the end reason was “Death of Child”.
High Reunification, Adoption, Age Out, or Guardianship: The provider was placement to at least 6 children and more than 50% of them went on to reach the stated permanency goal. This does not mean the children exited care from the provider directly.
High Runaway: The provider had at least 6 placements and more than 25% of placements ended in the child running away.
High Turnover: The provider had at least 25 placements and more than 50% of placements ended in under 30 days.
High Disruption: The provider had at least 25 placements and more than 50% of placements ended because the provider requested a change, the child requested a change, or the placement “disrupted.”
High Concurrency: Children with this provider had an average of 10 or more other children placed there concurrently. This could be either because the provider’s capacity is 10 or more children or because the high turnover rate caused 10 or more children to pass through the provider.
High Mileage: The provider had at least 25 placements and the average child moved more than 50 miles from their previous placement. Miles are calculated from the center of a provider’s zip code region.
High Hospitalization: The provider had at least 6 placements and more than 25% of placements ended due to hospitalization of the child.
First Run Warning: The provider had at least 6 placements and more than 10% of children placed there ran for their first time while with the provider.
Baker Act Warning: The provider had at least 6 placements and more than 5% of placements ended because the child was Baker Acted. Baker Acts were calculated by finding children whose next placements were for “Routine/Emergency Mental Health Services”. Note that for small placements, even one Baker Act will raise this warning.
Arrest Warning: The provider had at least 6 placements and more than 5% of placements ended because the child was arrested. Arrests were calculated by finding children whose next placements were for “Correctional Placement” or whose placement end reason was “Incarceration/Detention”. Note that for small placements, even one arrest will raise this warning.
Night to Night Warning: The provider had at least 25 placements and more than 25% of placements were for 2 or fewer days.
I joked that this would be like Yelp for Foster Care, so I went ahead and added three more tabs to make that a reality:
School Map: This tab allows you to click on a provider and see the greatschools.org map for the school in its zip code.
Walk Score: This tab allows you to click on a provider and see the walkscore.com ratings for the zip code.
Yelp: This tab allows you to click on a provider and see the yelp.com most popular places in the zip code.
What can we learn from this?
The Herald Tribune did a story on the public records bill a few days ago. In it, the sponsor is quoted as saying:
“The foster parents are not the people who have been suspected of doing anything wrong,” Roach said. “It’s the parents themselves. … Those are the people that need scrutiny, not the foster care parents.”
Hold on now, nobody said bio parents shouldn’t be scrutinized — and they are heavily scrutinized, in the form of evaluations, classes, supervised visits, and home inspections. The question is whether a higher-than-zero level of public scrutiny of foster parents is warranted.
Yes, it is.
If we didn’t know who they are, we wouldn’t know that foster parent “Lor. Hic” has taken in 525 kids for 626 placements and asked for their removal 360 times (“High Disruption”, “Night to Night Warning”). If she’s agreeing to be a night-by-night placement, then she’s running a a shelter with a foster care license. We need to talk about that practice.
We wouldn’t know that foster parent “Tif. Gip.” has an average placement length of 29 days, but a median placement length of only 2 days (“High Turnover”). The average child placed with Tif. Gip. would experience over 7.5 roommates during their time there. That’s essentially a group home with a foster home license. We need to talk about that, too.
We wouldn’t know that foster parent “Sha. Rob.” experienced the Death of a Child in 2002, or know whether the teams involved in placing kids there for the next three years were aware of that fact.
We also wouldn’t know that foster parent “Kat. Mel.” had over 10% of her 138 kids run for the first time while in her care (“First Run Warning”). Same for “Pat. Fau.”, “Ann. Gre.”, “Gen. Zie.” and many others. What’s going on in these homes?
If the confidentiality gets expanded to institutional providers, then we wouldn’t know that the Hibiscus Vero Group Home has six flags: Arrest Warning, High Turnover, High Concurrency, High Mileage, First Run Warning, and the Death of a Child in 2012. It may be a perfectly lovely place, but I would want to ask questions about all of those issues before I sent a child there.
I’ve requested the provider payment database from DCF as well, and it’s pending. I plan to add an overlay on how much providers get paid. An earlier version of the payment data that I have showed that there was a foster parent in Miami (Jef. Hor.) that received $15,000 per month to care for one child. That is not a typo. If foster parent info is exempted from public records, we wouldn’t know that. The public has the right to scrutinize how the government spends its money. Fifteen-thousand a month is either excessive or what everyone else should get.
I’m also working on a version that overlays the Florida Sex Offender database. The foster home for “Tra. Dav.” that I used in the first example above is in a zip code with nearly 250 registered offenders. Most zip codes have a fraction of that. Maybe we want to think about that when we place kids there, especially certain kids.
Beyond just risk factors, there’s also the problem of the foster parents who have literally hurt kids. If their names are exempt from public records, we don’t know who they are unless they kill a child. (And kids are placed with providers even after others die, as seen above.) I appreciate what the sponsor is saying, but the statewide Guardian ad Litem Program was created and funded with taxpayer money and then significantly strengthened in response to a foster parent murdering a child. The potential for misconduct with our most vulnerable children warrants constant vigilance regardless of who the caregiver is. Trust should not be blind.
Okay Robert Latham, you’re a hypocrite for not publishing the foster parents’ names
Here is where some astute commenter sends me a pointed note that I have chosen to use initials instead of names. I must, therefore, agree that publishing the names would be dangerous.
I believe that publishing the full names would kick the anthill and close down access to a valuable source of public information. I’m using the initials so that readers can focus on the importance of the information and not the hypothetical problems that can come from releasing it (even though it’s been public literally forever). For the public version, I think the three-letter initials are sufficient to find a specific foster parent you’re looking for if you already know the name. I am happy to share the unredacted version with anyone working directly in the system who could use the information.
Public information helps us make the system better, but we can’t do that if we’re not allowed to know things.
Christopher O’Donnell and Nathaniel Lash at the Tampa Bay Times recently published an outstanding investigative piece on the harmful number of placement changes some kids experience while in foster care. They write:
Foster care is intended to be a temporary safety net for children at risk of neglect and abuse at home. Those children, many already traumatized, need love and stability to recover and thrive, child psychologists say.
But thousands of Florida’s foster children were put at risk of further psychological damage by an overburdened system that repeatedly bounced them from home to home and family to family, a Tampa Bay Times investigation found.
Times reporters analyzed more than one million child welfare records recording the movements or placements of about 280,000 foster children under Florida’s care between 2000 and 2017. They show that thousands of foster children led transient lives, many staying only a few nights in one place before being moved on to the next foster family or group home.
For those of us working in the system, placement instability isn’t news (many professionals are numb to it). But it is news for the rest of the world, whose picture of foster care is based on the heartstrings marketing of charitable agencies or the five o’clock stories of deaths and abuses seen in the news. The daily pains and indignities of foster care are rarely discussed by a public who doesn’t have the information or language to talk about them. I was so happy for the Times article because it gave people a new idea: many foster kids move around a lot and that’s a bad thing.
This blog has a different audience, though. The readers here know about the system, often from deep in the weeds, handling cases or overseeing agencies and programs. We have seen placements disrupt both in 30-person staffings and via unexpected text messages that our client’s been kicked out of a home we thought would last — if not forever, at least for a week. We need no emotional priming on this topic. Short of telling a child he can’t go home, the hardest thing we sometimes have to say to them is they “can’t stay there anymore.”
It’s awful. Hold on to that feeling for these next parts. I want to show you placement instability from a thousand miles up, where the people look like ants. I want to multiply that gut-wrench feeling by 17,000 to break through the numbness and help you remember that this is not okay.
The database that the Times used in its reporting is a public record in Florida. I don’t know that any newspaper had ever written a story using it before, and I commend them for doing so. I also have it. I’ve been reluctant to share it largely because it is 77.8 million data points and completely overwhelming. The article and the discussion around it, though, made me believe that it’s time.
Instead of presenting the data with statistics and aggregates, I’m giving it to you how I first began to really understand it: as maps. Every dot on the map is at least one placement for a child. The colors show what type of placement: blue is foster home, purple is relative, orange is group homes, and so forth. The size of the dot shows the length of time the child spent there, and the lines show the moves from placement to placement. Sometimes there are breaks in the lines when run episodes, visitations, or administrative entries intervene. For the most part, though, it’s one continuous path from a child’s first removal placement to their last.
Here is an example. Below is the child with the second most number of placement entries in the database: 286 lines out of a million. He was removed twice: once in 2009 and once in 2011. He spent 1,211 days in institutions, 678 with relatives, 543 in group homes, and 201 on run. Only 22 days were spent in foster care. This child averaged a new placement every 9.3 days, and was moved over 3,700 miles from placement to placement, back and forth along the I-4 corridor. He had approximately 817 DCF roommates over the years and his last entry in the database was a juvenile facility in Orange County. He’s probably long gone now.
Every subsequent placement dot on the map means another “you can’t stay there anymore.” It means leaving your things behind or taking what you can carry. It means a new house with new people and rules, including other foster kids who may have already staked out their territory. You have to learn a new way to turn on a shower and hope there’s a toothbrush for you if you didn’t bring one. You get a new time to eat dinner, go to bed, and wake up — and if you don’t adjust fast enough then you might get kicked out just for that and start all over again. Imagine if you woke up with a different family every 9.3 days for years. That is not okay.
When I was working on this project last year, I showed a former foster youth his map. It was complicated, with lots of dots and lines crisscrossing Florida. He stared at it quietly for a while, looked up and said, “I remember every one of those places.” He asked me to print it out, and now he keeps it in a folder and takes it out when he wants people to understand what foster care was like for him.
I’m publishing the maps for 17,305 anonymized kids using Tableau. Instead of showing all 280,000 children’s maps, I’ve instead created groups of children by notable categories. For best results, I suggest opening it on a computer or tablet and hitting the full-screen button in the bottom right corner. If you’re interested in the details on each category or the database itself, there are tabs at the top of the Tableau with more information.
Below is a list of the categories you can view using the drop-down menu on the Tableau. I’ll do write-ups on them later, but I hope you will take the time to explore through the maps and imagine what life was like for the kids in these groups. It’s important to note that most kids in foster care have 3 or fewer placements and reach permanency in reasonable times. Those aren’t the kids we’re looking at here.
10+ Baker Acts
10+ Correctional Placements
Incarcerated Over a Year
Substance Abuse Programs
10+ Night-to-Night Placements
Longest time in care
Top Movers – No Admin
Top Movers – Post Privatization
Mom & Baby Placements
Most Non-relative Placements
Went to Camp
Failed Reunifications (<30 days)
Group Home Dwellers
Before I end, there is one more map below that captures what it can mean to be in foster care. Child 310000648701 came into care on February 11, 2005. We don’t know his exact age (or his gender actually), but his placements are marked as “Traditional 0-5” foster homes. (In 2010 he makes the transition to “6-12” homes, so he has to be on the young side of 0-5 in 2005.) By the end of February, five foster parents had kicked him out. He had two placements in March, three in April, two in May, and only one in June — that one was a non-relative placement and lasted 41 days before they kicked him out, too. Then another placement for two days; then one for one day. Then he was placed with a relative who kept him for 918 days — that’s two and a half years — before the placement ended “in accordance with case plan” (which I think means pursuant to a court order) and he went back to foster care.
He bounced around some more through regular and therapeutic foster homes, landed briefly in a group home in 2010 for eight days of “respite” care, and was finally placed (in entry 42) in a non-relative placement that adopted him after 175 days.
This child had 36 placement providers and only one was a group home. Families kicked him out, again and again, and for much of that time he was under the age of five. He was with relatives for two and a half years without permanency, and then removed presumably by a judge. After six or so years, it ended in adoption, which is good. We can celebrate the adoption while simultaneously asking hard questions about his experience with 34 other families who failed to make that connection or possibly even try.
These maps tell stories that placement stability statistics cannot. Over the next few weeks I’ll share examples and more thoughts on the categories above. I hope they will have the same impact on others as they did on me.
A video of a child being forcibly removed from his mother has been in the news lately. It’s brutal to watch. A group of police officers and security guards yank at the one-year-old while another swings a taser wildly around the room at anyone who gets too close. The woman is on the floor. Her sin is apparently trespassing, i.e,. sitting on the floor instead of standing when there were no seats available in the four-hour line. The charges are later dropped because she was trespassing at a government office (to extend daycare for her child) where people are actually allowed to be, and people sit on the floor in airports all the time and nobody rips their kids from them. The harm’s already done to the child, though. Nobody in the crowd intervenes — they don’t want to get arrested, shot, or lose their place in line — but they document it for the world to see.
(For added absurdity and likely thanks to the word “baby” in the title, the video I watched was preambled with an ad for Zales’s Enchanted Disney collaboration wherein a rich-looking white lady finds a diamond ring on a table, puts it on, and imagines she’s become a Disney Princess®. She has no idea whose ring it even is, but it’s hers now (hey she deserves it). Nobody arrests her for theft and wrestles her baby out of her arms. She does not spend a few nights in jail for having the audacity of self-worth. She, in fact, lives happily ever after.)
Children are removed from their parents every day, and it frequently looks just like that video. It is traumatic for everyone (especially the child) and is supposed to be only for very exigent reasons. In Florida, we know that anywhere from 1,000 to 1,500 kids enter the foster care system each month. The video got me thinking about when those removals happen.
I had a lot of assumptions. I’ve heard that removals go up around the holidays, and that they go down in the summers when kids are home. I felt sure that fewer removals would happen on the weekends, but also that there should be no reason for that because kids would be in more danger when not in school. Removals are supposed to happen when they are unavoidable, not when they are convenient to the investigator.
And I thought: how many kids are actually removed on Christmas? That would be horrible.
As part of a project we are working on, our office came into possession of the entire Florida DCF placement database (anonymized and unforgivably massive). This database includes the removal dates and details of 280,839 kids going back to some who entered care in the 1980s. Looking only at the removals from January 1, 2007 to December 31, 2017, we have data on 156,357 kids. Some of those kids came into care multiple times, so the time period covers 181,799 removals. (Caveat: as with all real-world records, the data is only as good as it is. Given the large numbers here, it is reasonable to assume that errors are evenly spread out and not biased in any given direction.)
How many of those removals were on a holiday?
Since we have the dates for all the removals, it isn’t hard to count them. On a normal, non-holiday day, the average number of removals is about 46. For Christmas, the average is six. For Thanksgiving, it’s eight. Only 67 kids were removed on Christmas Day in Florida from 2007-2017.
There are a few takeaways there. First, holidays seem to suppress removal numbers, at least on the day of the holiday itself. The only holiday that appears above average is Columbus Day; but, with year-to-year variations, it — along with President’s Day and New Year’s Eve — is not statistically different than a normal non-holiday. There is no holiday where more kids are removed than average (though there are periods of the year when removals are up, discussed below).
So what about the theory that more kids are removed around the holidays? If you thought (like I did) that there would be a giant spike in removals before or after, say, Christmas — well, there isn’t. In fact, removals bump up slightly and then start dropping off around the week before Christmas (a.k.a. now). The slight bump isn’t enough to call a correction. A glance at DCF’s dashboard on investigations shows that Decembers are usually high points for closing investigations during the year, so these numbers are even more pronounced. Removals don’t pick up again until January when school is back in session.
Here is the year-round chart. This confirms that removals go down in the Summer and rise again in the new school year. If you thought sentimentality was what kept DCF from removing kids on Christmas, think again. You see similar holiday drops on the 4th of July and Veterans Day. The dips would be more pronounced for MLK Day, Labor Day and Memorial Day, except those holidays don’t happen on the same calendar day each year. Kids don’t get removed on holidays because investigators are on vacation.
So that’s the question: if only 15 kids had to be removed on the 4th of July, why did 48 have to be removed on the 7th of July?
What about the weekends?
On average only 14 kids per day were removed on Saturdays and Sundays. The highest day of the week for removals was Thursday — probably because court is held one day after a removal and nobody wants to go to court on a Saturday, for sure. At 14 removals per day, the weekend was on par with the 4th of July.
And, while we’re at it, what about time of day? Kids get removed during business hours. The later in the day, the higher the number of removals. Below you can see three distinct peaks in the following hours: 9:00am, 1:00pm, and 5:00pm. Only 416 kids in this dataset were removed in the 6:00am hour. Maybe children are safer before dawn? (Those 5,580 kids removed at midnight include entries without a valid date — i.e., “00:00:00”. Don’t read into that spike.) I’m not including a graph because it’s messy, but if you look at the whole week the highest rates of removals happened during the 5:00pm hour on Thursdays. No surprise.
So removals happen all the time, except holidays, weekends, and usually not outside of business hours. And they especially happen when investigators first get to work, after lunch, and right before they go home for the day. Something feels very wrong about that. It’s as if “risk” is also a product of convenience, which is not how child protection is supposed to work.
If the averages hold, around six (and up to twelve) kids will be removed on Christmas Day this year. Let those removals be necessary and kind.