Nanny Agency JobsA family-facing profile is a new document with its own purpose and audience. It should not be produced by uploading an entire candidate file and asking AI to make the person sound impressive. Start with material the agency is authorized to use, preserve the meaning of each claim and give a responsible person ownership of the final version.
This guide proposes an agency-side production workflow. It is separate from helping a nanny write a personal bio or explaining what an agency may share. The aim is to create a concise introduction whose facts, permissions and version can be traced before it reaches a family.
Define the introduction before choosing the material
Identify the particular introduction: which role, which recipient and what the family needs to understand at this stage. Decide whether the profile summarizes relevant experience, current availability and selected preferences, or serves another defined purpose. Avoid building a universal packet simply because the agency holds more information.
Confirm the agency's authority to process and share the chosen material, including any applicable candidate agreement and data-handling requirements. Candidate permission for one introduction should not be silently treated as permission for public publication or unrelated uses. Resolve unclear permissions before preparing the profile.
NIST's Generative AI Profile identifies privacy risks involving unauthorized disclosure and use of personal information. NIST's profile. The workflow below applies that concern through a practical question: what does this recipient need, and what material is appropriate for this particular tool?
Prepare a small source packet
Select relevant résumé sections and separately confirmed updates. Date each source. A candidate's newer availability message should not be lost because an older résumé contains a different start date. Where two sources conflict, ask the candidate to clarify before writing a definitive statement.
Keep reference contact details, identity documents, screening records and unrelated personal information outside the drafting packet unless a specifically authorized process requires them. A family profile does not need to become a duplicate of the agency's complete file. Review the tool's approved use and access arrangements before entering candidate information.
Use accurate labels for evidence. “Candidate states” describes an attributed claim; “document checked” records a different action. Do not let either become “fully verified” without a defined basis. The profile can remain clear and useful without overstating what the agency has established.
Keep a claim and permission ledger
Create this original NAJ ledger as an internal review aid. It should reference the authoritative source without copying unnecessary personal data into another location.
- Proposed statement: The specific sentence intended for the family.
- Source reference: Document, section and date supporting it.
- Meaning check: Whether the sentence preserves the original qualification, limit or context.
- Sharing basis: The confirmed permission or applicable agency process for this introduction.
- Candidate correction: Any change requested and how it was resolved.
- Release record: Final version, intended recipient and responsible reviewer.
A suitable drafting instruction is: “Use only the selected facts. Do not add qualities, credentials or responsibilities. Preserve dates and limits. Flag contradictions for review. Do not describe self-reported information as independently verified.”
The ledger is still needed after that instruction. Check adjectives as well as numbers: “experienced with” is not necessarily “specialist in,” and “helped organize” is not “led.” Persuasive wording should not change the candidate's actual history.
Review an inflated credential in a fictional example
Fictional worked example: Morgan's résumé states that Morgan attended an introductory workshop on supporting family routines. An AI draft describes Morgan as a “certified family-routine specialist.” The phrase sounds relevant to the opening, but the source does not support a certification or specialist status.
The recruiter records the draft claim, points to the workshop entry and marks the meaning check as failed. The sentence is replaced with the accurate workshop description if it is relevant to the introduction. Otherwise it is omitted. The recruiter does not ask the candidate to approve an impressive phrase that the source cannot establish.
Morgan also identifies an outdated availability line during review. The recruiter confirms the current date, updates the source packet and checks the final profile again. The release record now identifies the corrected version and the intended family introduction.
This example demonstrates two separate checks: truthful transformation and current information. Candidate approval helps catch errors, but it does not turn an unsupported credential into a supported one.
Obtain meaningful review before sharing
Show the candidate the actual proposed profile through the agency's appropriate process. Explain its purpose, intended audience and how to request a correction. A general invitation to “approve your profile” is less useful if the candidate cannot see the exact wording or does not know where it will go.
Ask the reviewer to focus on employment dates, duties, qualification names, availability and any statement that could materially shape a family's expectations. Allow uncertain items to remain unresolved while the supporting information is checked. Do not pressure a candidate to accept flattering wording that feels inaccurate.
The agency should also review the document independently. Confirm that no private internal comment, reference identity or irrelevant personal detail appears in the draft. Candidate agreement is not a substitute for the agency's own accuracy and appropriate-sharing responsibilities.
Release and correct a specific version
Share the approved version through the intended route and record what was actually sent. “Prepared,” “candidate reviewed” and “shared with family” describe different events. Keep them separate so staff can answer a later question about which version a family received.
If a consequential error is found afterward, pause reuse of the affected profile, identify the recipients and arrange a clear correction. Updating the master document alone does not update attachments already received elsewhere. Record the correction action and its status without claiming delivery or acknowledgement you have not confirmed.
For future introductions, check that availability and role-specific statements remain current. Reuse the factual work where appropriate, but revisit the audience and permission questions. A good profile is a controlled introduction that the agency and candidate can explain, not an automatically polished copy of everything in the file.
Sources
NIST: Generative Artificial Intelligence Profile. The source supports the narrow privacy-risk statement. The ledger, workflow and fictional example are original NAJ editorial guidance; they do not determine legal permission for a particular disclosure.