Skip forward into hiring notes
RosterAcorn

Leave and family data in 3 states' employee files

Minnesota marks dependent and personal contact fields in government employee files as private data on individuals, Delaware defines covered people through federal code and creates no accommodation duty for family responsibilities, and Washington's sick-leave findings flag a portability gap for construction workers. Together they tell you how to classify, define, and frame leave and family data in your files.

  • Minnesota: Dependent data, home address, nonemployer phone and email, and date of birth are private data on individuals; union-representative communications are also private.
  • Delaware: Military status and dependent definitions come from federal code (10 U.S.C. § 101 and § 10101 for uniformed forces, 50 U.S.C. § 3911 for dependents).
  • Delaware: No obligation to make special accommodations for family responsibilities, so long as leave, scheduling, absence, performance, and benefits policies apply nondiscriminatorily.
  • Washington: The legislature found sick-leave law a good law from a voter initiative, and found it lacks flexibility and portability for construction workers with multiple employers.
  • Build your file in blocks: a general zone for job data, a private zone for contact and dependent fields, a leave block, a military block, and a multi-employer flag for construction workers.

What this post covers and who it is for

You build onboarding forms and personnel files. You decide which fields exist, what they say, and who can read them. Three states give you specific guidance on leave and family data. Minnesota tells you which fields are private. Delaware tells you how to define dependents and leave for family responsibilities. Washington tells you why sick leave law exists and where it still falls short.

This post walks through each state in plain terms. You will get field-level guidance for forms and files. You will also see where to stop and ask a lawyer or your state contact. The goal is a file you can defend in an audit and a form that does not create privacy risk before the first day.

A quick word on scope. Everything here comes from three official sources: Minnesota statutes on government data, Delaware's family-leave code, and Washington's wage-and-hour findings on sick leave. Where those sources are silent, this post stays general. You will not find guessed numbers, guessed dates, or rules pulled from other states.

Key takeaways

  • Minnesota marks dependent data private. Dependent records in a government employee file are private data on individuals. Treat them like the employee's own sensitive fields, with restricted access.
  • Minnesota also marks contact fields private. Home address, nonemployer phone and email, and date of birth sit in a private-data list for employees of government entities in the state.
  • Delaware ties family leave to specific federal definitions. The law defines who counts as uniformed-force members and who counts as dependents, by pointing to federal code.
  • Delaware does not force special accommodations. Family-responsibility policies must be applied without discrimination, but the law creates no duty to accommodate.
  • Washington's sick-leave law came from a voter initiative. The legislature found it a good law, and also found it lacks flexibility for construction workers.

Those five points become your field design. The rest of this post tells you where to place them, how to word them, and what to watch for.

Minnesota: what counts as private data in the employee file

Minnesota law separates public and private data on individuals inside government employee records. Two clauses matter most to you. The first says dependent data is private. The second adds a list of personal contact fields that are also private.

Read the dependent rule first. A government employer in Minnesota must treat information about an employee's dependents as private data on individuals. That covers names, birth dates, relationships, and any other dependent detail you collect. Your file should carry a privacy mark on every dependent block. Access should be limited to the staff who need it for benefits or eligibility work.

The second clause covers the employee's own contact fields. Minnesota law lists home addresses, nonemployer-issued phone numbers and email addresses, and dates of birth as private data on individuals. It also protects emails or other communications between exclusive representatives and their members, prospective members, and nonmembers.

Those two rules shape your form design in three ways.

  • Label every dependent field. When you add a dependent name, birth date, or relationship, flag it as private in your file system.
  • Separate contact fields from work fields. A work email can stay in a general contact block. A home address or personal phone moves into the private block.
  • Keep communications out of the main record. Union-representative emails belong in a protected folder, not in the general personnel file.

How to place these fields in an onboarding form

Your form should collect what you need and nothing more. For a Minnesota government employer, that means at least two zones on the form: a general zone for job data, and a private zone for dependents and personal contact fields. Make the private zone visually distinct. Confirm with your records officer where the form data lands in the file.

Date of birth is useful for eligibility checks, age-based programs, and payroll. Collect it. Just keep it in the private block. Same with a home address if you need it for mailing or jurisdiction checks.

Dependent data usually arrives during benefits enrollment, not day one. If your form asks for it early, mark it then. If it arrives later through a separate enrollment packet, mark it at intake. Either way, your file system should show a clear line between what is general and what is private.

Who should see what inside the file

Access rules follow data classification. A hiring manager rarely needs a dependent birth date. A benefits administrator does.

Build role permissions around that split. Give your benefits and payroll roles access to the private block. Keep the general block open to supervisors who need job history. Review permissions when someone changes roles. An employee who moves from benefits to recruiting should not keep benefits-level access by default.

One open question your sources do not answer: which non-government employers in Minnesota must follow this exact private-data treatment. Ask your state contact or records officer before you apply the same label to a private employer file.

Delaware: defining the people your leave policy covers

Delaware's family-leave rules point to federal definitions for the people they cover. That matters when you build a file. You need a clean way to record who is a servicemember, who is a dependent, and how that connects to a leave request.

The law names members of the uniformed forces as defined in 10 U.S.C. § 101, including reserve components listed under 10 U.S.C. § 10101. In your file, that becomes a status field on the employee record. When the employee reports military service related to a leave request, record the status against those federal definitions rather than writing your own.

Dependents get their own definition. The law defines a dependent of a servicemember as set out in 50 U.S.C. § 3911. That definition drives dependent-name fields on a leave request and any supporting documents you keep. Store the dependent list attached to the military-status record, so a reviewer can see both at once.

What the law says about family responsibilities

Delaware also sets a clear limit on what your policy must do. The code states that the subsection does not create any obligation for an employer to make special accommodations for an employee with family responsibilities, so long as all policies related to leave, scheduling, absenteeism, work performance, and benefits are applied in a nondiscriminatory manner.

That sentence does two things for your file design. First, it tells you you are not required to build a special accommodation path for family responsibilities. Second, it tells you your existing leave, scheduling, absence, performance, and benefits policies must be applied the same way for everyone.

From a file standpoint, apply your policies evenly. A leave request tied to a family responsibility should move through the same steps as any other leave request. Record the request type, the policy under which it was decided, and the outcome. Keep the family-responsibility detail in a restricted block if your records officer classifies it as sensitive. The decision record shows consistent application without exposing the private detail.

Fields to add for Delaware military-family leave

Build a small set of fields so a reviewer can follow a military-family leave request end to end.

  • Military status. Record whether the employee is a member of the uniformed forces or a reserve component, using the federal definitions the law cites.
  • Dependent list. Record dependents of the servicemember as defined in the federal dependent definition the law cites.
  • Leave request type. Mark the request as military-related or family-responsibility-related so it routes to the right policy.
  • Policy applied. Name the leave, scheduling, absence, performance, or benefits policy used in the decision.
  • Nondiscrimination check. Confirm that the same policy was applied as for any comparable request.

Keep military status and the dependent list in the military block, with the other three fields together in the leave section of the file. A reviewer can then see the status, the people involved, and the policy path without opening other sections.

Here is a compact comparison of how the three states frame leave and family data, built only from the facts in the sources above.

StateCore data rule for the fileWho it defines Key limit or finding
MinnesotaDependent data, home address, personal phone and email, and date of birth are private data on individuals Dependents and the employee's contact fieldsCommunications between exclusive representatives and members, prospective members, and nonmembers are private
Delaware No privacy rule stated in this source; define covered people through federal code Uniformed-force members under 10 U.S.C. § 101 and § 10101, and dependents under 50 U.S.C. § 3911 No obligation to make special accommodations for family responsibilities, if policies apply nondiscriminatorily
Washington No privacy rule stated in this source; findings explain the law's originWorkers covered by sick leave from a voter initiative The law lacks flexibility and portability for construction workers who work for multiple employers

Washington: why sick leave law looks the way it does

Washington's sick-leave findings within RCW 49.46.020 set out legislative findings. Those findings tell you why the law exists and where lawmakers still see a gap. That context helps you design leave fields that will not need a rewrite next session.

The first finding is a straight endorsement. The legislature found that Initiative 1433 is a good law approved by the voters to establish sick leave benefits for workers. Your file should reflect a sick-leave benefit held and tracked by each worker. Build an accrual field, a balance field, and a usage field for each worker.

The second finding names a gap. The legislature found that this new law does not provide for flexibility and portability of benefits for construction workers who may work for multiple employers and who already negotiate wages and benefits with their employers.

That gap matters for staffing coordinators who place people across multiple worksites or multiple employers in the construction trades. Your file should record which employer holds the sick-leave record for a given period. When a worker moves between employers, note the handoff point. Do not assume a balance carries over, because the findings flag portability as an open issue.

Building sick-leave fields for a Washington file

Keep the fields simple and tied to what the findings support.

  • Accrual record. Track sick leave each worker earns for the current employer.
  • Usage record. Track days or hours taken, with the date and the policy used.
  • Employer of record. Name the employer holding the balance for that period.
  • Multi-employer flag. Mark workers who hold concurrent jobs in construction trades so you know portability is at issue.
  • Negotiated-benefit note. Record when wages and benefits are set through negotiation, because those workers sit in the gap the findings describe.

The multi-employer flag is the field most likely to save you later. When a construction worker asks about a balance from a prior employer, you can see the flag, point to the employer of record, and avoid promising a carryover the findings do not support.

Where to stop and ask

Your sources leave one question open in Washington: how a worker's sick-leave balance is handled when they move between employers in the construction trades. The findings name the gap but do not describe the fix. Ask your Washington employment contact or your agency's counsel how to handle a transfer request before you answer a worker's question about it.

Putting the three states side by side in your file system

Your file system probably serves workers in more than one state, or at least travelers who cross state lines. The three states in this post each touch a different layer of the file.

Delaware governs how you define covered people and how far your accommodation duty goes. Washington governs how you frame sick-leave benefits and where you flag open issues.

Think of them as three drawers in the same cabinet.

  • Drawer one, classification. Minnesota's private-data rules tell you which fields need a privacy mark and restricted access.
  • Drawer two, definitions. Delaware's federal references tell you how to record military status and dependent status without inventing your own language.
  • Drawer three, findings. Washington's findings tell you why sick leave exists and where to flag portability risk.

A file that handles all three well looks like this. The general block holds job data, work contact, and supervisor. The private block holds home contact fields, date of birth, and dependent records. The leave block holds request type, policy applied, decision, and accrual or usage records. The military block holds status and dependents when a military-family leave request appears, and those dependent entries carry the same private mark as the private block. A multi-employer flag sits on the leave block for construction workers.

Each block carries its own access level. Benefits staff open the private block. Supervisors see the leave block without the private detail. Payroll opens accrual and usage fields. Review access on a schedule, and tighten it when roles change.

Common mistakes when building leave and family fields

Four mistakes come up often. Each one is avoidable with a clear field plan.

  • Mixing private and general fields. Put a dependent birth date next to a job title, and the whole block inherits the wrong access level. Keep blocks separate and label each one.
  • Writing your own dependent definition. Delaware points to federal code for its definitions. Your form should collect the same facts those definitions require, then store them under that heading.
  • Promising a balance carryover. Washington's findings flag portability as unaddressed for construction workers. Do not promise a transfer until you have confirmed the handling with your state contact.
  • Treating family responsibility as a special path. Delaware's rule means your standard leave, scheduling, absence, performance, and benefits policies apply. Record the request under the normal path and keep private detail restricted.

Fix these before your next batch of onboarding forms goes out. A form that mixes blocks is hard to repair after data lands in the file.

A sample onboarding form structure

Your form can stay on one page if you break it into clear zones.

Zone one, job basics. Full legal name, work contact, position, start date, supervisor. This zone is general data.

Zone two, personal contact. Home address, personal phone, personal email, date of birth. For a Minnesota government employer, mark this zone private at intake.

Zone three, family and dependents. Dependent names, birth dates, relationships. Mark this zone private at intake and collect it during benefits enrollment if you can, not on day one.

Zone four, leave profile. Sick-leave accrual start, any prior-employer balance question, multi-employer flag for construction workers, negotiated-benefit note.

Zone five, military status. Uniformed-force or reserve status using the federal references Delaware cites, plus the dependent list under the federal dependent definition.

Five zones, each with a clear access level. A reviewer opening the file sees the structure immediately.

Handling requests once the fields exist

Fields only help if your process uses them. Walk through the three request types you will see most.

A Minnesota dependent-data request comes from a worker or a third party asking for information in the file. Because dependent data is private, you do not release it broadly. Route the request through your records process, confirm the requester's right to the data, and log the release decision.

A Delaware military-family leave request arrives with a status claim. Record the status using the federal definitions, list the dependents under the federal dependent definition, mark the request type, note the policy you applied, and confirm the same policy applied as it would to any comparable request. Keep the private family detail restricted while the decision record stays visible.

A Washington sick-leave question comes from a construction worker with multiple employers. Open the leave block, read the multi-employer flag and the employer of record, and answer only what the record supports. If the question touches portability, route it to your Washington contact before you reply.

Each request follows the same rhythm: open the right block, apply the right rule, log the decision, restrict the private detail.

Related guides: Check 16 paid family leave rules before you approve · Family leave handoff with 5 worksheet fields · ADA staffing responsibilities: 9 topics to review.

FAQ

Do these rules apply to my private-sector agency?

Minnesota's private-data treatment as described here sits in the state's government-data statutes. Ask your state contact which parts apply to a private employer before you label your file the same way. Confirm with your own counsel how the scope applies to your situation.

What if a worker's family-responsibility request does not fit any policy?

Delaware's rule means you have no duty to create a special accommodation. Apply your existing leave, scheduling, absence, performance, and benefits policies without discrimination. If no policy fits, say so plainly and record the conversation. Do not invent a one-off path that you would not offer to the next requester.

Can I collect a dependent birth date on the first-day form?

You can collect it when you need it. For a Minnesota government employer, mark dependent data private at intake, and confirm whether the same rule reaches a private employer before labeling your file. Many recruiters move dependent fields to the benefits-enrollment packet so day one stays light. Either way, mark the field private at intake.

How do I handle a construction worker asking about sick leave from a prior employer?

Open the leave block and read the multi-employer flag. Washington's findings name portability as an open issue for these workers, so do not promise a carryover. Confirm the handling with your Washington employment contact, then answer the worker with what you have confirmed.

What should I do if my form has no private-data zone?

Add one. Split personal contact and dependent fields into their own block, give the block an access level, and re-check the file's existing records so older entries move into the right block. Your records officer can help you set the labels once; after that, every new form inherits the structure.

Does Delaware require me to track family-responsibility requests separately?

The law does not create a special accommodation duty, but it does require your policies to apply without discrimination. Track the request under your normal leave policy so you can show consistent treatment. Keep private detail in a restricted block, and keep the decision record in the visible leave block.


Use this post as your build sheet. Pull the three drawers together, label every block, and check your open questions with your state contacts before your next onboarding batch goes out.

Sources