DELANEY FRANCES CRANE

About Delaney

I am DELANEY FRANCES CRANE, the home cook and lunch-prep writer behind Workday Salads. I keep this site focused on quick workday meals, packed salad systems, simple dressings, and lunches that still make sense after they sit in a container.

I write from the practical problem I care about most: lunch should be easy to pack, easy to carry, easy to open, and still worth eating when the workday gets busy.

I also keep the claims narrow. If a page uses a nutrition estimate, a generated visual, a source link, or a personal note, I want the wording to say exactly what the page can support and nothing stronger.

Read the personal story of why I started making workday salads.

You can follow my updates on X.

What I write about

I write about the same questions I would ask before closing a lunch box: can this be packed ahead, should the dressing stay separate, what ingredient creates moisture, what needs to stay dry, and what can wait until lunch? The goal is useful lunch planning, not perfect restaurant plating.

Container fitI explain whether a shallow box, jar, bowl, side cup, or separate topping bag makes the lunch easier to carry and finish.

Moisture controlI call out cucumbers, tomatoes, fruit, warm proteins, wet dressings, and damp greens before they damage the container.

Lunch timingI separate what can be packed during Sunday prep from what should wait until the morning or the lunch break.

Reader contextI label estimates, visual assets, and outside references so the page does not overstate what it can prove.

My practical specialty

I keep this author profile limited to the site's real scope: home-cooking lunch prep, packed meal structure, dressing timing, container decisions, and refrigerator context. My public author social account is DELANEYFRANCES_ on X.

Packing order: I separate wet, heavy, sturdy, tender, and crunchy parts instead of treating a salad as one pile.
Lunch setting: I write for desk lunches, commutes, limited prep time, shared fridges, and containers that may be opened hours later.
Clear labels: I describe nutrition, images, and personal-experience details only as specifically as the page supports.

What I cover

The current library is salad-based, but the editorial problem is broader: quick healthy workday meals that fit real containers and ordinary lunch breaks. Start with make-ahead workday meals, protein-focused lunches, dressing cups and sauces, and workday lunch guides.

My content map

I organize Workday Salads around a few repeated lunch problems. That helps me make each page more specific instead of writing another general salad paragraph.

Moisture: cucumbers, tomatoes, fruit, wet beans, warm proteins, and loose dressings can change the whole container.
Cold texture: pasta, grains, potatoes, steak, tofu, eggs, and creamy dressings often need a different plan after chilling.
Dressing timing: some sturdy bases can take dressing early, while tender greens need a side cup and a final toss.
Crunch timing: nuts, seeds, chips, croutons, crackers, and crispy potatoes are treated as a lunch-step decision, not a decoration.
Correction logic: if a lunch fails, I want the page to help identify the first fix instead of replacing the whole recipe.

How I add depth to a page

I do not want an article to be long only because it repeats itself. A useful Workday Salads page should help with decisions: what to pack first, what to hold back, what can get watery, what container makes sense, and what one change would improve the next lunch.

That is why many pages discuss soggy greens, leaking dressing, crowded containers, toppings losing crunch, cold pasta getting firm, or yogurt dressing thickening after chilling. Those details are more useful than another generic paragraph about a salad being easy or delicious.

How I review a page

Before a recipe or guide is treated as ready for readers, I check for a specific lunch use case, a packing sequence, a likely failure point, a storage or cold-holding reminder, and any source context readers should know.

I also check whether the page has enough supporting detail for the claim it is making. If the page only supports practical home-cooking guidance, I do not turn that into a stronger testing, nutrition, or product-ranking claim.

Nutrition and calorie notes

When a recipe page shows calories, I mark those numbers as estimates for a practical serving. They are not medical advice, weight-loss promises, or lab-tested labels. Exact nutrition depends on brands, weighed portions, and the dressing amount used in the actual container.

Source standard

For more detail, read the Workday Salads process. The process explains how I handle general lunch guidance, source links, images, estimates, and reader corrections.

Health and safety limits

I am not a doctor, registered dietitian, certified nutritionist, food safety specialist, or professional chef. Workday Salads does not publish detox claims, weight-loss promises, disease advice, or medical nutrition guidance. When I mention protein-rich ingredients or food storage, it is general food information for home cooks.

Corrections

If you spot an unclear step, a broken link, a confusing ingredient note, or a food storage concern, email contact@workdaysalads.com. I review meaningful corrections and change page update dates when the published content changes in a way readers should know about.