30 Claude prompts for clinic admin, patient comms, and front-office SOPs

You are a clinic scheduling coordinator building a multi-touch appointment reminder sequence. <context> Riverside Family Health Clinic wants a standard 3-touch reminder sequence for upcoming appointments to reduce no-shows. </context> <inputs> - Appointment: Dr. Kim, follow-up visit, one week out - Touch points: 7 days before (email), 2 days before (SMS), day-of morning (SMS) - Info to include: date/time, provider name, one-tap confirm or reschedule link - Clinic policy: mention 24-hour cancellation notice only on the 7-day and 2-day touches, not the day-of message </inputs> <task> Write all three touchpoint messages with the right channel length for each (email can be longer, SMS under 160 characters) and the cancellation policy line only where specified. </task> <constraints> - Keep both SMS messages under 160 characters including the link placeholder - Do not repeat the cancellation policy in the day-of message - Each message must include a one-tap confirm/reschedule link placeholder </constraints> <format> Three labeled messages: "7 days before (email)," "2 days before (SMS)," "Day-of (SMS)." </format>

You are a clinic scheduling coordinator writing a proactive rescheduling request email. <context> Dr. Alvarez has an unexpected schedule conflict and Riverside Family Health Clinic needs to proactively reschedule 8 patients on her Thursday afternoon. You need one email template to send to all affected patients. </context> <inputs> - Reason to give: "an unexpected provider schedule change" (no more specific reason to share per practice manager's instruction) - Options offered: earliest opening with Dr. Alvarez, or a same-day slot with Dr. Nolan if the patient prefers not to wait - Action: reply or call the front desk within 3 business days to pick a new slot, clinic will follow up by phone if no response - Tone: apologetic, brief, no excessive detail </inputs> <task> Write the rescheduling email covering the reason as instructed, both options, and the 3-day response window with the phone-follow-up fallback. </task> <constraints> - Do not give a more specific reason than "an unexpected provider schedule change," per instruction - Present both options as equally valid, don't steer toward one - Keep it under 120 words </constraints> <format> A short email with subject line, brief apology, the two options as a short list, and the response window. </format>

You are a clinic care coordination assistant writing a referral scheduling email to a patient. <context> Dr. Patel referred patient Yusuf Karim to an outside cardiology practice. The referral and reason have already been determined by Dr. Patel; you need to help the patient schedule. </context> <inputs> - Patient: Yusuf Karim - Referred to: Lakeside Cardiology, referral already faxed by Riverside Family Health Clinic - What the patient needs to do: call Lakeside Cardiology directly at [SPECIALIST PHONE] to book, mention Dr. Patel's referral - Timing note from Dr. Patel's office: no urgency flag on this referral, standard scheduling window is fine - Clinic follow-up: Riverside will check in if no cardiology visit is on file within 6 weeks </inputs> <task> Write an email telling the patient the referral has been sent, what to do to schedule, the timing note, and the clinic's 6-week follow-up plan. </task> <constraints> - Do not restate or elaborate on the clinical reason for referral beyond what's given, that's between the patient and the specialist - State the timing note factually, don't add urgency language that wasn't specified - Keep it to one short email </constraints> <format> A short email with the referral confirmation, a clear "Next step" instruction, and the follow-up timeline. </format>

You are a clinic scheduling coordinator writing a waitlist notification script for a suddenly available slot. <context> A same-day cancellation opened an appointment slot with Dr. Kim. Riverside Family Health Clinic wants a fast phone and text script to offer it to the next patient on the waitlist. </context> <inputs> - Open slot: today, 2:15 PM, Dr. Kim, general appointment - Waitlist patient: Priya Chandran, waiting for an earlier slot for 2 weeks - Response window: needs to confirm within 20 minutes or the slot goes to the next patient on the list - Fallback: if no answer, leave a voicemail per HIPAA minimum-necessary practice (no medical detail) and text as backup </inputs> <task> Write a phone script and a text message offering the slot, both including the 20-minute response window and clear next steps. </task> <constraints> - Keep the voicemail HIPAA-conscious, no mention of appointment type or provider beyond "an opening at our office" - The text message can be more specific since the patient replies directly to a known clinic number - Make the 20-minute window unmissable in both versions </constraints> <format> Two scripts: "Phone/voicemail" and "Text message," each short and direct. </format>

You are a clinic patient communications coordinator writing pre-visit preparation instructions. <context> Riverside Family Health Clinic wants a pre-visit instruction message for patients scheduled for a fasting blood panel, sent 2 days before the appointment. </context> <inputs> - Appointment type: fasting blood panel, ordered by Dr. Patel - Prep instructions confirmed by the clinic's lab protocol: no food or drink except water for 10 to 12 hours before the draw, take regular medications unless the provider said otherwise, bring insurance card - Timing: arrive 10 minutes early, draws done at the on-site lab window - What to do if instructions weren't followed: call the office, may need to reschedule rather than draw a non-fasting sample </inputs> <task> Write the pre-visit instruction message covering the fasting window, the medication note, arrival time, and what to do if the patient accidentally ate. </task> <constraints> - Use the exact fasting window given, do not shorten or lengthen it - State the medication note exactly as given, don't add a blanket "stop all medications" instruction - Include the reschedule-rather-than-draw guidance for accidental non-compliance </constraints> <format> A short message with a bolded fasting window, a short instruction list, and a "If you accidentally ate" line. </format>

You are a clinic patient communications specialist who rewrites clinical after-visit notes into plain language for the patient portal. <context> Dr. Patel dictated an after-visit note for patient Sonia Weiss. The clinical content and plan are entirely the provider's, already finalized. You need to rewrite the note into plain language for the portal, not change any clinical content. </context> <inputs> - Provider's finalized note: "Reviewed hypertension management, BP 132/84 today, continue current lisinopril 10mg daily, recheck BP in 4 weeks, discussed reducing sodium intake, no medication changes at this visit." - Patient reading level: general public - Portal format requirement: short sections, no unexplained abbreviations </inputs> <task> Rewrite the provider's note into a plain-language after-visit summary for the portal, preserving every clinical fact and instruction exactly, just removing jargon and abbreviations. </task> <constraints> - Do not add, remove, or reinterpret any clinical content, this is a rewording task only - Spell out "BP" as "blood pressure" and explain any other abbreviation - Flag with [VERIFY WITH PROVIDER] if any part of the source note is ambiguous rather than guessing its meaning </constraints> <format> A short plain-language summary with a "Today's visit," "Your plan," and "Next check-in" section, matching the source note's facts exactly. </format>

You are a clinic administrative assistant who formats discharge instructions the provider has already written. <context> After a minor procedure, Dr. Nolan gave verbal and handwritten discharge instructions for patient Ben Torres. You need to format these into a clean printed handout, not originate any new instructions. </context> <inputs> - Provider's instructions as given: rest for 24 hours, keep the site clean and dry for 48 hours, take the prescribed pain medication as directed on the label, follow up in 1 week, call the office if fever over 101F or increasing redness/swelling at the site - Formatting requirement: large clear print, numbered steps, emergency line highlighted separately </inputs> <task> Format the provider's instructions into a printed discharge handout with numbered care steps and a separately highlighted "Call us if" section using the exact warning signs given. </task> <constraints> - Use only the instructions given, word for word in meaning, do not add or infer additional care steps - Do not change the fever threshold or any other specific number in the instructions - Keep the "Call us if" section visually separated, not blended into the numbered steps </constraints> <format> A one-page printed handout with numbered steps and a highlighted "Call us if" box. </format>

You are a clinic care coordination assistant drafting a referral letter for a provider's signature. <context> Dr. Patel decided to refer patient Grace Liu to an endocrinologist and provided the reason and relevant history to include. You need to draft the letter for Dr. Patel to review and sign, not decide the referral content. </context> <inputs> - Referring provider: Dr. Patel, Riverside Family Health Clinic - Referred to: an endocrinologist (specific practice to be filled in by front office) - Reason for referral, as stated by Dr. Patel: management of thyroid function abnormality identified on recent labs, patient has no prior endocrinology care - Attachments noted by Dr. Patel: recent lab results and current medication list to be attached separately </inputs> <task> Draft a referral letter stating the reason exactly as given by Dr. Patel, noting the attachments, and formatted for letterhead with a signature line. </task> <constraints> - Use the referral reason exactly as stated, do not add clinical detail, interpretation, or urgency level not given - Mark it clearly as a draft pending the referring provider's review and signature - Leave the receiving practice name as a fillable field </constraints> <format> A one-page letter draft with a "DRAFT, PENDING PROVIDER SIGNATURE" header and a signature line at the bottom. </format>

You are a clinic care coordination assistant writing a check-in reminder based on a provider's care plan. <context> Dr. Kim set a follow-up check-in plan for patient Walter Adebayo after adjusting his care plan. You need a reminder message for the coordination team to send at the specified interval, using only what Dr. Kim specified. </context> <inputs> - Provider's plan: check in with patient by phone in 2 weeks to ask about symptom changes and medication tolerance, exact questions specified: "any new symptoms," "any side effects from the new medication," "any trouble getting the prescription filled" - Escalation rule set by Dr. Kim: if patient reports a new symptom or side effect, schedule an earlier visit rather than waiting for the routine follow-up - Documentation: coordination team logs the call summary in the chart </inputs> <task> Write a check-in call script using exactly the three questions specified, the escalation rule for the two trigger answers, and a note to log the summary. </task> <constraints> - Ask only the three questions given, do not add additional clinical questions - Apply the escalation rule only for the two triggers named, not for a general "doesn't feel well" answer - Include the charting reminder at the end </constraints> <format> A short call script with the three questions, an escalation branch note, and a closing charting reminder. </format>

You are a clinic administrative assistant formatting a visit summary for the patient portal. <context> Dr. Nolan finalized a visit note for patient Isabel Marsh. You need to format the finalized note into the structured sections the patient portal requires, without changing any of the content. </context> <inputs> - Finalized note from Dr. Nolan: reason for visit was annual wellness exam, vitals reviewed and normal per provider, no new concerns raised, continue current exercise routine, return in 12 months for next annual exam, no medication changes - Portal sections required: "Reason for visit," "Summary," "Your plan," "Next appointment" </inputs> <task> Format the finalized note into the four required portal sections, preserving every fact from the note exactly. </task> <constraints> - Do not add clinical interpretation beyond what the provider's note states - Keep "vitals reviewed and normal per provider" as stated, do not list specific vital numbers since none were given - Each section should be one to two short sentences </constraints> <format> Four short labeled sections matching the portal's required structure. </format>

You are a clinic administrative coordinator building a new patient intake form. <context> Riverside Family Health Clinic wants a standardized intake form for new patients to fill out before their first visit, covering the fields the front office needs on file. </context> <inputs> - Sections required by practice manager: contact information, emergency contact, insurance information, pharmacy of choice, reason for visit (free text), consent to treat and to bill insurance (checkbox) - Format: fillable form, printable or portal-ready - Note: no clinical history questions in this form, those are handled separately on a clinical intake form </inputs> <task> Build the intake form with the six sections listed, each with the appropriate fields (text, checkbox, or short answer). </task> <constraints> - Include exactly the six sections given, do not add clinical history questions since that's explicitly a separate form - Use clear field labels a first-time patient would understand - Consent checkboxes must have their own line, not be buried in a paragraph </constraints> <format> A structured form with six labeled sections and appropriate field types for each. </format>

You are a clinic billing coordinator building an insurance verification request form for internal use. <context> Riverside Family Health Clinic's front desk needs a standardized form to submit to the billing team when verifying a new patient's insurance before their first visit. </context> <inputs> - Fields needed by billing team: patient name, date of birth, insurance carrier, member ID, group number, subscriber name if different from patient, appointment date/provider - Verification checklist for billing: active coverage confirmed, copay amount confirmed, referral requirement checked, prior authorization needed flag - Turnaround expectation: billing completes verification within 2 business days of receiving the form </inputs> <task> Build the internal request form with the fields listed and the four-item verification checklist billing fills in as a response. </task> <constraints> - Include all fields exactly as listed, in the order given - The verification checklist should be a fillable section for billing to complete, not for the front desk - Note the 2-business-day turnaround expectation on the form itself </constraints> <format> A two-part form: "Front desk submits" fields and "Billing completes" checklist, with the turnaround note at the top. </format>

You are a clinic administrative coordinator building a telehealth visit registration form. <context> Riverside Family Health Clinic offers telehealth visits and needs a short registration form patients complete before their first virtual appointment. </context> <inputs> - Fields required: patient name, DOB, state the patient is physically located in during the visit (for licensure purposes), preferred video platform confirmation, backup phone number if video fails, consent to telehealth checkbox - Policy note: provider must confirm patient's state of residence at time of visit since providers are only licensed in specific states - Technical note: link to a test-your-connection page before the visit </inputs> <task> Build the registration form with the fields listed, making the state-location field prominent given the licensure note, and include the test-connection link. </task> <constraints> - Make the "state you'll be physically located in during the visit" field unmissable, not a minor field, since licensure depends on it - Include the consent checkbox as its own line item - Add the test-connection link near the top, not buried at the bottom </constraints> <format> A structured form with clearly labeled fields and the licensure-relevant state field visually emphasized. </format>

You are a clinic administrative coordinator building a communication consent form. <context> Riverside Family Health Clinic needs a form documenting how a patient wants to be contacted and by whom, to avoid disclosure to unauthorized family members or contacts. </context> <inputs> - Fields required: preferred contact method (call, text, email, portal), preferred phone number, authorization to leave detailed voicemail (yes/no), names of any family members or others authorized to receive information on the patient's behalf, patient signature and date - Policy note: if no one is listed as authorized, staff share no information with anyone but the patient, per HIPAA minimum-necessary practice - Review cadence: form reviewed and reconfirmed annually or when the patient requests a change </inputs> <task> Build the consent form with the fields listed and a short policy statement explaining what happens if no one is authorized. </task> <constraints> - Include the policy statement exactly as given, don't soften it to imply flexibility that isn't there - Make the authorized-persons field a repeatable list (name plus relationship), not a single line - Include the annual review note at the bottom </constraints> <format> A structured consent form with the listed fields, a policy statement box, and a signature line. </format>

You are a clinic administrative assistant building a family medical history data-collection questionnaire. <context> Riverside Family Health Clinic wants a structured questionnaire for patients to fill out listing family medical history, which the provider reviews and interprets separately. This form only collects the information, it does not analyze or flag risk. </context> <inputs> - Relatives to cover: parents, siblings, grandparents - Fields per relative: relationship, living or deceased (and age at death if deceased), known conditions (free text), age of diagnosis if known - Note: form includes an instruction line stating the provider will review this history at the visit, the form itself makes no risk assessment </inputs> <task> Build the questionnaire with a repeatable entry block per relative covering the fields listed, and the instruction line about provider review. </task> <constraints> - This form must only collect data, do not add any risk-scoring, flagging, or interpretive language - Include the instruction line stating a provider reviews this at the visit - Structure it so a patient can add multiple siblings or grandparents easily </constraints> <format> A structured form with a repeatable relative-entry block and the review-instruction line at the top. </format>

You are a clinic operations manager documenting a standard front desk check-in procedure. <context> Riverside Family Health Clinic wants a written SOP for the front desk check-in process so every staff member follows the same steps. </context> <inputs> - Steps confirmed by the practice manager: (1) verify patient identity with two identifiers, (2) confirm or update insurance and contact info, (3) collect any outstanding balance or copay, (4) confirm reason for visit matches the schedule, (5) direct patient to waiting area and notify clinical staff - Exception path: if the reason for visit doesn't match what's scheduled, flag the medical assistant before proceeding - Documentation: log check-in time in the practice management system </inputs> <task> Write a numbered SOP covering the five steps, the exception path for a mismatched visit reason, and the logging requirement. </task> <constraints> - Keep the five steps in the exact order given - Make the exception path clearly separated, not folded into step 4 - Include the logging requirement as its own line </constraints> <format> A numbered SOP with a highlighted "Exception" callout box after step 4. </format>

You are a clinic patient experience manager writing a complaint escalation SOP. <context> Riverside Family Health Clinic wants a documented process for how front-line staff handle and escalate patient complaints. </context> <inputs> - Tier 1 (front-line staff): listen, acknowledge, resolve if it's a scheduling or billing question staff can answer directly, log the complaint regardless of outcome - Tier 2 escalation triggers: complaint about clinical care, a request to speak with a manager, or an unresolved billing dispute over $200 - Tier 2 process: practice manager contacts patient within 1 business day - Documentation: every complaint logged in the patient experience tracker with resolution status </inputs> <task> Write the SOP covering tier 1 handling, the three tier 2 escalation triggers, the 1-business-day response commitment, and the logging requirement. </task> <constraints> - Use the three escalation triggers exactly as given, do not broaden or narrow them - State the 1-business-day commitment as a hard number, not "promptly" - Require logging for every complaint, resolved or not </constraints> <format> A two-tier SOP with numbered steps under each tier and a logging requirement noted at the bottom. </format>

You are a clinic HIPAA compliance coordinator writing an SOP for medical records release requests. <context> Riverside Family Health Clinic needs a documented process for handling patient requests to release records to themselves or a third party. </context> <inputs> - Step 1: patient completes and signs the records release authorization form, specifying what records and to whom - Step 2: front desk verifies patient identity and signature match on file - Step 3: records team fulfills within the state-required timeframe, logs date sent and method - Step 4: if request is from a third party (attorney, other provider), verify the authorization names that specific party before releasing - Fee note: clinic may charge a reasonable cost-based fee per state law, communicated to patient before fulfillment if applicable </inputs> <task> Write the four-step SOP with the identity verification and third-party authorization checks clearly called out, plus the fee disclosure note. </task> <constraints> - Keep the four steps in order, do not skip the third-party verification step even for requests that seem routine - Note the state-required timeframe as a placeholder [STATE TIMEFRAME] since this varies by state - Include the fee disclosure requirement as its own line </constraints> <format> A four-step numbered SOP with a highlighted note for the state-timeframe placeholder and the fee disclosure line. </format>

You are a clinic operations manager writing an SOP for requesting a medical interpreter. <context> Riverside Family Health Clinic wants a clear process for staff to request an interpreter, whether in-person, phone, or video, for patients who need one. </context> <inputs> - Step 1: front desk notes the language need at scheduling or check-in and flags it in the system - Step 2: scheduling requests a phone or video interpreter service through the clinic's contracted vendor, or books an in-person interpreter for visits flagged in advance - Step 3: staff never use a family member as the primary interpreter for clinical conversations unless the patient specifically requests it and it's documented - Step 4: interpreter service used is logged in the visit record </inputs> <task> Write the four-step SOP, keeping the family-member interpreter restriction as a clear policy statement, not just a suggestion. </task> <constraints> - State the family-member interpreter restriction exactly as given, including the documented-exception condition - Keep the four steps in order - Include the logging requirement as its own line </constraints> <format> A four-step numbered SOP with the family-member interpreter policy in a highlighted callout box. </format>

You are a clinic operations manager writing an SOP for communicating an unexpected clinic closure. <context> Riverside Family Health Clinic wants a documented process for notifying patients and staff quickly if the clinic has to close unexpectedly, such as for a weather event or facility issue. </context> <inputs> - Decision authority: practice manager or on-call physician decides on closure, notes the reason category (weather, facility, staffing) and expected reopening estimate - Notification channels: mass text and email to all patients with same-day appointments, phone tree for patients over 65 without email on file, updated voicemail greeting and website banner - Rescheduling: affected patients get priority rebooking, front desk reaches out within 1 business day of reopening - Staff notification: separate internal alert to all staff before the patient-facing notification goes out </inputs> <task> Write the SOP covering the decision step, the notification channels in order (staff first, then patients), and the rebooking commitment. </task> <constraints> - Staff notification must go out before the patient-facing one, keep that order explicit - Include the phone-tree channel specifically for patients without email on file, don't assume everyone gets the text/email version - State the 1-business-day rebooking outreach commitment as a hard number </constraints> <format> A numbered SOP with a "Staff first, then patients" ordering note and a channel list for different patient groups. </format>

You are a clinic compliance coordinator drafting a patient privacy notice for legal review. <context> Riverside Family Health Clinic needs an updated Notice of Privacy Practices draft reflecting the clinic's current data-sharing practices, to be reviewed by legal counsel before distribution. </context> <inputs> - Practices confirmed by compliance officer: uses and discloses health information for treatment, payment, and healthcare operations; does not sell patient information; patient portal data shared only with the patient's authorized account; third-party billing vendor has a signed business associate agreement - Patient rights to include: right to access records, right to request amendment, right to request restriction on certain disclosures, right to file a complaint - Effective date and review cycle: reviewed annually by compliance officer </inputs> <task> Draft the privacy notice covering the practices and patient rights listed, marked clearly as a draft pending legal review. </task> <constraints> - Use only the practices confirmed by the compliance officer, do not add or infer additional data-sharing arrangements - Include all four patient rights listed, each as its own short section - Mark the document "DRAFT, PENDING LEGAL REVIEW" at the top </constraints> <format> A structured draft notice with sections for practices, patient rights, and a review-cycle footer, headed by the draft marking. </format>

You are a clinic operations manager drafting a no-show and late cancellation policy for the practice. <context> Riverside Family Health Clinic wants a written policy the practice owner has approved, to post and hand out to patients. </context> <inputs> - Definitions confirmed by practice owner: late cancellation is under 24 hours notice, no-show is a missed appointment with no notice - Fee structure approved: first occurrence in 12 months is a courtesy warning, no fee; second occurrence is a $25 fee; third occurrence in 12 months may result in a requirement to prepay for future visits - Exceptions: emergencies are reviewed case by case by the practice manager, fee can be waived at the practice manager's discretion - Communication: policy is given to new patients at intake and posted in the waiting area </inputs> <task> Write the policy document covering the definitions, the three-tier fee structure, the emergency exception, and where it's communicated. </task> <constraints> - Use the exact fee amounts and tier structure given, do not adjust them - State the emergency exception as a case-by-case, practice-manager decision, not an automatic waiver - Keep the whole policy to one printable page </constraints> <format> A one-page policy document with definitions, a fee-tier table, and an exceptions section. </format>

You are a clinic compliance coordinator drafting a telehealth consent policy for legal review. <context> Riverside Family Health Clinic needs a telehealth consent policy covering how virtual visits work and what patients are agreeing to, based on the compliance officer's confirmed practices. </context> <inputs> - Confirmed practices: visits conducted over a HIPAA-compliant video platform, recorded only if the patient is told and agrees in advance, technical failures result in a phone fallback or reschedule, providers only see patients located in states where they're licensed - Patient acknowledgment required: understands telehealth has the same privacy protections as in-person visits, understands limitations (e.g. some exams require in-person follow-up), consents to the visit format - Review: annual review by compliance officer, marked as draft for legal review before use </inputs> <task> Draft the telehealth consent policy covering the confirmed practices and the three acknowledgment points, marked for legal review. </task> <constraints> - Use only the practices confirmed, do not add technology or recording claims not stated - Include the licensure-by-state note prominently, that's a compliance-critical detail - Mark the document "DRAFT, PENDING LEGAL REVIEW" at the top </constraints> <format> A structured draft policy with a practices section, an acknowledgment checklist, and the draft marking header. </format>

You are a clinic billing manager drafting a billing dispute resolution policy. <context> Riverside Family Health Clinic wants a written policy describing how patients can dispute a charge and how the clinic resolves it, approved by the practice owner. </context> <inputs> - Step 1: patient submits a dispute in writing or via the portal within 30 days of the statement date, describing the specific charge in question - Step 2: billing team reviews the charge against the visit record and insurance EOB within 5 business days - Step 3: billing responds in writing with the outcome, either a corrected statement or an explanation of why the charge stands - Step 4: if the patient disagrees with the outcome, they can request a second review by the practice manager - Note: patient is not sent to collections while a dispute is actively under review </inputs> <task> Write the four-step policy with the 30-day filing window, the 5-business-day review commitment, and the collections-hold note during active disputes. </task> <constraints> - Use the exact day windows given, do not round or generalize - State the collections-hold protection clearly, it's a patient-protective detail that shouldn't get buried - Keep the four steps in order </constraints> <format> A four-step numbered policy with the collections-hold note in a highlighted callout box. </format>

You are a clinic operations manager drafting a staff code of conduct for patient interactions. <context> Riverside Family Health Clinic wants a short code of conduct document for all patient-facing staff, covering the behavior standards the practice owner wants enforced. </context> <inputs> - Standards confirmed by practice owner: greet patients by name when possible, never discuss one patient's information within earshot of another, use the private consultation room for sensitive conversations, treat every patient with the same standard of respect regardless of insurance type or payment method, escalate any conflict to a supervisor rather than arguing with a patient - Enforcement note: violations reviewed through the standard HR process, this document sets the standard, not the disciplinary procedure - Where posted: staff handbook and new hire onboarding packet </inputs> <task> Write the code of conduct covering the five standards listed, with a closing line noting violations go through the standard HR process. </task> <constraints> - Use the five standards exactly as given, do not add unrelated conduct rules - Keep the tone as a positive standard to meet, not a list of prohibitions - Note explicitly that this document is the standard, not the disciplinary procedure itself </constraints> <format> A one-page code of conduct with five short numbered standards and a closing HR-process note. </format>