How to rebuild a job search after a layoff without automating judgment

Andre is a fictional 47-year-old former plant scheduler searching after a layoff in Hamilton, Ontario. Andre’s plant closed a line and his role went with it. He has a severance packet, a benefits deadline, a former colleague offering an introduction, and a spreadsheet of postings that all look equally urgent.

The spreadsheet has status columns. It does not hold what the former colleague actually offered to do, or which roles travel more than the household can take.

A benefits form is due Friday. It currently lives in a paper envelope on the kitchen table while the search lives on a laptop.

In You.one's Superboard view, Andre can give “Run a targeted search for scheduling or operations roles while finishing layoff paperwork and protecting household travel limits” a Board of its own. That Board connects separation paperwork, benefits deadlines, search evidence, travel limits, and applications the person still owns; opening “Choose weekly travel, local, or longer commute” creates a Room for its evidence, discussion, state, and decision.

The mission is specific: Run a targeted search for scheduling or operations roles while finishing layoff paperwork and protecting household travel limits.

The consequential choice is not something a board or an AI should quietly make: Whether to pursue a well-paid role with weekly travel, keep the search local, or use the colleague introduction at a plant that is a longer commute but no overnight travel.

You.one can keep the work, evidence, live dependency, and “Choose weekly travel, local, or longer commute” decision visible through its Superboard view. The Owner boundary stays explicit: Andre chooses the travel constraint, files paperwork, and owns every conversation and application.

The Search after layoff Board gives this mission one durable operating picture. Andre can use familiar language instead of translating the situation into project-management jargon. Its 7 Lists separate the kinds of attention this situation actually requires.

Its Cards deliberately distinguish actions, evidence, a live dependency, and decisions. A Waiting List is useful here only because a named request or outside condition is already in motion. That separation makes the current choice, evidence, and next move easier to scan.

These Card titles come directly from Andre's situation: “Choose weekly travel, local, or longer commute” is the live choice, “Household travel limits and commute times” holds evidence, and “Applied: Westend production planner” names something genuinely in motion outside Andre's control. The point is recognition, not a perfect taxonomy.

Opening the Card gives the visible item durable depth. Stage can hold Search-constraint brief: Place household travel limits, commute times, and the three role-path options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Andre will choose the travel constraint that will govern the search.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Search-constraint brief and this Card Room's visible notes and left “Choose weekly travel, local, or longer commute” with Andre.”

A useful Card Chat request would be: “Using only the context visible in this Card Room, compare the travel role, local-only search, and longer-commute introduction. Do not contact anyone or choose for me.” When live AI is configured, current Ava can respond to an explicit Card mention using supported Room context and can make limited reversible changes inside this Card Room after an explicit request. She uses only supported Room context; she cannot summarize the Board, watch other Lists, or act outside this Card Room. She does not gain authority over the decision merely because the context is organized.

Andre's call remains explicit: Andre chooses the travel constraint, files paperwork, and owns every conversation and application.

These requests use the visible supported context inside the “Choose weekly travel, local, or longer commute” Card Room. They do not imply that current Ava automatically surveys the whole Board or follows up on her own; Andre must provide the relevant facts and check the result.

Current Ava can reply in this Room to an explicit Card mention using supported Room context. She cannot summarize the Board, make the choice, represent Andre, watch other Lists, or act outside this Card Room.

Andre owns paperwork, applications, household decisions, and every conversation. Ava does not file benefits, apply, or contact colleagues.

A search with a governing constraint: Friday’s form is on the Board, travel is a decision, and introductions are specific promises.

• Request idea: using only the context visible in this Card Room, compare the travel role, local-only search, and longer-commute introduction. Do not contact anyone or choose for me.
• Request idea: use only the Search-constraint brief and notes the Owner has placed in this Card Room to separate facts, assumptions, and unanswered questions
• Request idea: name which visible Room note could most change the comparison; do not watch other Lists or follow up autonomously

A job-search spreadsheet is enough when paperwork is done and roles are similar.

It starts to break when a benefits deadline and a travel tradeoff are hiding behind status words.

The Search after layoff Board earns its place only when the familiar tool—a job-search spreadsheet—can no longer keep the reason, Search-constraint brief, conversation, current state, decision, and history connected.

Andre should rename every List or Card that feels artificial. This recipe succeeds when “Choose weekly travel, local, or longer commute” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.

Later, Ava may help this Board notice when a people Card has no next visible step, still leaving every message with Andre.

A future unified You.one experience could carry relevant context from “Choose weekly travel, local, or longer commute” across guidance and the Superboard view. Broad proactive coordination, cross-surface personalized memory, realtime shared editing, and general external execution are not available today. Any future action would still require the applicable capability, connection, grant, and human authority.

• Andre is fictional and is not a customer, testimonial, research participant, or disguised real person.
• This is not employment-law, benefits, or financial advice.
• It does not show Ava applying, contacting employers, or filing government forms.
• It is not a measured time-to-hire or a testimonial about a layoff.