Inputs, skills and effort

Prepare a location list, item categories, a neutral description guide, retention period, staff contact and the venue's real handover rule. A form editor and spreadsheet skills are enough. Allow 60–90 minutes to build and test a small pilot. Store only a preferred contact and avoid identity documents, exact home addresses or public photos of distinctive details.

Copy this starter brief

Design a lost-and-found intake form with REPORT TYPE, DATE, GENERAL LOCATION,
ITEM CATEGORY, NEUTRAL DESCRIPTION, PRIVATE IDENTIFYING DETAIL and CONTACT.
Keep the private detail staff-only. Do not identify people, infer ownership,
publish serial numbers, promise a match or mark an item returned.
Add NEEDS STAFF REVIEW when information is missing or conflicting.

Build the pilot

1. Separate “lost” and “found” reports with conditional fields.
2. Use broad public descriptions and keep one distinctive detail private.
3. Give every submission a case ID and receipt time.
4. Let staff compare category, location, time and the private detail manually.
5. Require the venue's approved proof and two-person handover check.
6. Close, delete or anonymise records according to the stated retention rule.

Worked fictional sample

Case LF-012 reports a blue umbrella near Hall B at 15:10. The private detail is a yellow repair stitch inside the strap. A found blue umbrella from Hall B is a possible match, not proof. Staff ask the claimant for the private detail without revealing it, follow the venue's handover rule and record who approved the release.

The pilot passes when every record has a case ID, public and private descriptions stay separate, possible matches require staff review, handovers have evidence, and expired records follow the retention rule.

Recovery and manual fallback

Use numbered paper slips with the same minimum fields and lock them in a staff area. If the form or photo upload fails, record text only. If ownership is disputed, pause the handover and follow the venue's escalation process rather than asking AI to decide.

Product, feature and pricing pages were inspected on 18 October 2026. No account, form, submission, person, item, match or handover was tested.

Prepare a consented review packet

Use the meeting ID, participant-approved recording or transcript, agenda, existing task list, and the real calendar. Record the meeting's consent and sharing rule before inviting a bot or uploading audio. Allow 30–45 minutes for a small meeting. Exclude side conversations and sensitive details that are not needed for the task.

Use this extraction brief

Extract only proposed actions supported by the supplied transcript.
For each row show EVIDENCE QUOTE, TASK, PROPOSED OWNER and STATED DEADLINE.
Write OWNER UNCONFIRMED or DEADLINE UNCONFIRMED when the meeting did not state one.
Do not invent agreement, priority, feasibility, completion, policy or permission.
Flag conflicting statements for participant review.

Verify before assigning work

1. Check that recording, transcription and sharing were permitted for this meeting.
2. Link every proposed action to a timestamp or exact transcript excerpt.
3. Separate a suggestion from an explicit commitment.
4. Ask the named person to confirm the task and deadline.
5. Move only confirmed rows into the team's task system and preserve the source link.
6. Reconcile completed, changed and cancelled tasks at the next check-in.

Worked fictional sample

At 18:42, a transcript says, “Mali, could you send the revised venue map on Thursday?” This supports a proposed task for Mali with a stated day, but it does not prove acceptance or identify the calendar date. Mark the owner and deadline unconfirmed until Mali confirms the task and the specific Thursday. Do not create a completed task or infer urgency.

The register passes when every task has evidence, suggestions remain distinct from commitments, owners and dates are confirmed by people, and access follows the meeting's sharing rule.

Recover without the recording or tool

Use a four-column note: evidence, task, owner and deadline. Read it aloud before the meeting ends and ask each owner to confirm. If consent is absent or disputed, do not upload or redistribute the recording; use an approved manual note instead.

Feature and pricing pages were inspected on 17 October 2026. No account, meeting, participant, recording, transcript, action item or integration was tested.

Prepare only verified inputs

Collect the complaint ID, the customer's exact request, the verified timeline, the relevant approved policy excerpt, the case owner, the authorised next step and its deadline. Remove personal data that the writer does not need. Keep the customer's account separate from facts confirmed in records. Allow 30–45 minutes for drafting, fact comparison and approval.

Use this bounded starter prompt

Use only the verified case facts below.
Draft a calm reply with ACKNOWLEDGEMENT, VERIFIED FACTS, NEXT STEP, OWNER and DEADLINE.
Do not admit fault, deny responsibility, invent policy, refund, compensation, legal meaning or completed action.
Mark missing facts NEEDS CONFIRMATION and conflicting records CONFLICT.
Keep the customer's words distinct from verified facts.
[PASTE REDACTED CASE FACTS]

Draft, compare and approve

1. Put the complaint ID and exact customer request at the top of the working note.
2. Label each statement as customer-reported, record-verified or still unconfirmed.
3. Draft one acknowledgement without adding blame or an outcome.
4. Preserve the authorised next step, owner and deadline exactly while using Grammarly for clarity and tone.
5. Have a second person compare every factual sentence and commitment with the case record.
6. Save the approved sent version and the evidence used to approve it.

Worked fictional sample

Case C-104 says the customer reported a late parcel. The only verified carrier record is a scan at 16:20. The approved action is a warehouse review owned by Narin, with an update due by 17 October. A suitable reply acknowledges the concern, says which record was checked, and names the review, owner and deadline. It must not promise a refund, blame the carrier or say the review is complete.

The reply passes when every factual sentence has a source, every commitment is authorised, the owner and deadline are visible, and uncertainty remains explicit. Recheck Grammarly's rewrite before sending because a smoother sentence can still change responsibility or certainty.

Recover when the tool or evidence is unavailable

Use a two-column sheet with verified facts on the left and the proposed reply on the right. Escalate safety, legal, financial or compensation questions to the authorised person. If records conflict, send a short acknowledgement with the next verification step instead of guessing.

Feature and plan pages were inspected on 16 October 2026. No account, complaint, customer, reply, remedy or delivery record was tested.

Keep the first form small

Use item ID, borrower display name, approved contact, checkout time, due time, condition-out note, staff initials and acknowledgement. Avoid collecting identity documents or unrelated personal data. Allow 45–60 minutes to build and test the form.

Use this field and logic brief

Create an equipment checkout form using only these approved fields.
Require ITEM ID, BORROWER, CHECKOUT TIME, DUE TIME, CONDITION OUT and STAFF INITIALS.
If damage is observed, reveal a short note and manual escalation instruction.
Do not invent item availability, borrower eligibility, fees, penalties or approval.
Do not mark an item returned from this form; use the separate return check.

Build and test the form

1. Match item IDs to labels on the physical equipment.
2. Make required fields obvious and explain why contact data is needed.
3. Keep damage notes factual; do not ask the form to diagnose repairs.
4. Add a confirmation that repeats the item ID and due time.
5. Test one valid checkout, one unknown ID and one damage report.
6. Reconcile the day's submissions with the shelf and return log.

Worked fictional sample

Item CAM-04 leaves at 14:00 and is due at 17:00. The staff member records “small scratch on battery cover” and initials AB. The form must not infer that the camera is safe, charge a fee or mark it returned. The return check compares CAM-04 and the recorded condition.

The form passes when each submission has one recognised item ID, a supplied borrower and due time, damage triggers the manual route, and staff can match the record to the physical item.

Recover when the form is unavailable

Use a numbered paper sheet with the same fields and enter it later only after reconciling item IDs. If an ID is missing or duplicated, stop checkout and ask the equipment owner. Follow the organisation's real privacy, safety and loss procedures.

Product, feature and pricing pages were inspected on 15 October 2026. No account, submission, person, item or return was tested.

Prepare the source sheet

List each plot ID, approved watering instruction, exception, equipment location, assigned volunteer and escalation contact. Add a field for observed condition rather than a guessed diagnosis. Allow 45–60 minutes to build and test a small log.

Copy this starter prompt

Use only the approved garden plan below.
Create a daily watering log and end-of-shift handoff.
For each plot include ID, approved action, observed condition, time, person and status.
Do not invent water amounts, plant diagnoses, weather, chemicals, permissions or schedules.
Mark missing instructions NEEDS LEAD and conflicting instructions CONFLICT.
Include a paper fallback with the same fields.
[PASTE APPROVED PLAN]

Build and test the log

1. Give every plot a visible ID that matches the source plan.
2. Separate the approved action from the volunteer's observation.
3. Use NOT STARTED, DONE, SKIPPED and NEEDS LEAD as explicit states.
4. Require a reason when work is skipped; never let AI supply it.
5. Test three fictional plots, including one conflict and one missing instruction.
6. Have the garden lead review the handoff before the next shift uses it.

Worked fictional sample

Plot G04 has the approved instruction “Water only when the lead confirms.” The volunteer records “surface still damp at 07:10” and NEEDS LEAD. The system must not convert that observation into “no water needed,” prescribe an amount or mark the plot DONE.

The log passes when every status maps to a plot and person, skipped work has a supplied reason, conflicts remain visible, and the next volunteer can find the escalation contact.

Recover when devices or evidence fail

If the device is unavailable, use the paper sheet and enter it later only after checking plot IDs and times. If a label is missing, stop and ask the lead instead of guessing the bed. For unsafe equipment, suspected contamination or plant-health decisions, follow the garden's real process and qualified advice.

Product and pricing pages were inspected on 15 October 2026. This is a fictional planning exercise; no garden, weather, plant condition or watering action was tested.

Prepare the badge list

Use a reviewed table with badge ID, display name, role, accessibility note and approval state. Collect only information needed on the badge. Allow 45–60 minutes for a small batch, excluding attendee confirmation and final printing.

Use this layout brief

Create a simple event name badge.
Reserve the largest area for DISPLAY NAME and a smaller line for ROLE.
Use high contrast, a plain typeface and generous empty space.
Do not invent names, roles, titles, pronouns, affiliations or sponsor status.
Mark missing or unapproved data as HOLD; do not print it.
Test the longest supplied name before duplicating the layout.

Build and test the badges

1. Lock one badge size and record the paper or holder dimensions.
2. Design with the longest real display name, not the shortest example.
3. Keep decorative elements away from the name and trim edge.
4. Duplicate only after the sample passes the source table check.
5. Export a print PDF and print one sheet at 100% scale.
6. Check readability at conversational distance, trim, role accuracy and one-to-one badge IDs.

Worked fictional sample

Badge B07 uses the approved display name “Narin S.” and role “Registration volunteer.” The sample keeps the name larger than the role and leaves the affiliation blank because none was supplied. It must not expand the initial, add a senior title or infer an organisation.

The batch passes when every badge maps to one approved row, long names stay inside the safe area, the printed sample is readable, and held records remain unprinted.

Recover when printing fails

If text clips, reduce decoration or role size before shrinking the name. If alignment shifts, check scale and printer margins with a plain test sheet. If Canva is unavailable, use a word-processor table with the same dimensions. Keep blank badges and a thick marker for approved on-site corrections.

The Canva product and pricing pages were inspected on 13 October 2026. No real attendee list, printer, order or event was tested.

Prepare a safe source sheet

Collect the shift date, area, completed work, unfinished work, named owner, deadline, location of shared items and escalation contact. Remove personal or sensitive details that the next shift does not need. Allow 30–45 minutes for a small handoff.

Copy this starter prompt

Use only the shift notes below.
Create sections for DONE, NEXT, WAITING and ESCALATE.
For every NEXT item include an owner and due time only when supplied.
Do not invent completion, people, deadlines, causes, permissions or safety advice.
Mark missing facts as NEEDS CONFIRMATION and conflicting notes as CONFLICT.
End with a five-item start-of-shift checklist.
[PASTE REVIEWED SHIFT NOTES]

Build and test the handoff

1. Give each note an ID such as S01 and preserve the original wording.
2. Separate observed facts, reported information and open questions.
3. Draft the four sections without filling missing owners or deadlines.
4. Compare each sentence with its source ID and restore any lost condition.
5. Ask a fictional incoming volunteer to name the first three actions and escalation contact.
6. Have the outgoing lead confirm the record before the next shift receives it.

Worked fictional sample

S07 says, “Two welcome packs remain in cupboard B; Sam will count them by 10:00.” The handoff may place this under NEXT with Sam, 10:00 and cupboard B. It must not say that stock is sufficient or that Sam completed the count. If another note says cupboard C, mark CONFLICT and ask the shift lead.

The handoff passes when every action has a source ID, supplied owner and deadline stay unchanged, the incoming reader can find the escalation route, and unresolved items remain visible.

Recover when notes are incomplete

If an owner is missing, leave it unassigned and contact the shift lead. If the issue concerns safety, safeguarding or access, follow the organisation's real escalation process rather than an AI suggestion. If Grammarly is unavailable, use a four-column DONE/NEXT/WAITING/ESCALATE table and proofread it with the outgoing lead.

Feature and plan pages were inspected on 12 October 2026. This is a fictional planning exercise; no real shift, incident, assignment or completion was independently tested.

Prepare the source pack

Use only the current approved rules. Label them R01, R02 and so on, and record the effective date, owner and contact for questions. Allow 45–60 minutes for a one-page guide. Keep conflicting or incomplete rules out of the public guide until the owner decides them.

Copy this starter prompt

Use only the supplied club rules.
Create a one-page welcome guide and a rule-to-guide mapping table.
For every guide statement, cite its source rule ID.
Keep obligations, permissions and prohibitions distinct.
Do not invent eligibility, fees, penalties, exceptions, approvals or legal meaning.
Mark ambiguous or conflicting wording as NEEDS DECISION.
[PASTE NUMBERED APPROVED RULES]

Build and test the guide

1. Give every source rule a stable ID and preserve its exact wording.
2. Mark each rule as MUST, MAY or MUST NOT before rewriting it.
3. Draft one plain-language sentence and its source ID side by side.
4. Compare the meaning, conditions, people, dates and consequences word for word.
5. Ask three fictional new members to identify the main actions and contact route.
6. Have the rule owner resolve every NEEDS DECISION item before release.

Worked fictional sample

R04 says, “Members must return the room key by 21:00.” The guide may say, “Return the room key by 9:00 p.m. (R04).” It must not soften this to “Try to return the key” or add a late fee. The mapping table records R04, the final sentence and owner review state.

The guide passes when every public statement has a source rule ID, three readers can identify the required actions and contact, and any conflict stops publication instead of being guessed away.

Recover when wording is unclear

If two rules conflict, show both to the owner and publish neither interpretation. If QuillBot is unavailable, use a two-column document with exact rule text and proposed wording. If meaning cannot be preserved in shorter text, link to the full rule and keep the exact wording.

Product and premium pages were inspected on 11 October 2026. This is a fictional planning exercise; no club rule, sanction, legal effect or owner approval was independently tested.

Prepare the interview boundaries

Choose one narrow topic and write who will record, who may listen, where files will be stored, how long they will be kept, and whether any quote may be published. Allow 60–90 minutes for the kit, excluding the interview and speaker review. Use a fictional practice story first.

Copy this starter prompt

Use only the topic and boundaries below.
Draft six open interview questions and a quote-verification table.
Include checkpoints for recording consent, pause/withdrawal, name preference,
quote approval, publication channel and retention decision.
Do not invent memories, dates, names, consent or historical facts.
Mark transcript uncertainty as CHECK AUDIO and factual uncertainty as NEEDS SOURCE.
[PASTE TOPIC AND AGREED BOUNDARIES]

Build and test the kit

1. Explain recording, storage and intended use before asking for consent.
2. Keep consent choices separate: recording, naming, quoting and publication.
3. Ask one question at a time and allow the speaker to pause or skip.
4. Compare candidate quotes with the audio and record a timestamp.
5. Send the selected wording and context to the speaker for confirmation.
6. Publish nothing until the chosen approval and retention steps are complete.

Worked fictional sample

Speaker code P01 says at 08:14, “We moved the market tables after the big flood.” A transcript may mishear “market” as “garden.” The table records CHECK AUDIO, the timestamp and the speaker's corrected wording. It cannot add a flood year or publish P01's name unless those facts and permissions are separately confirmed.

The kit passes when every quote has an audio timestamp, speaker review state and publication permission; uncertain facts stay labelled; and withdrawal or deletion requests have a named manual route.

Recover when consent or evidence is unclear

If recording consent is absent, take no recording and use handwritten notes only with permission. If audio is unclear, paraphrase only after speaker approval or omit the passage. If Fireflies.ai is unavailable, use a local player and manual timestamp table. Follow applicable local law and the organisation's real safeguarding process.

Product and pricing pages were inspected on 10 October 2026. This is a fictional planning exercise; no person was interviewed, recorded, transcribed or asked to approve publication.

Prepare the confirmed inputs

Record the travellers, confirmed dates, transport, accommodation facilities and activities. Each person adds personal requirements themselves. Exclude passport numbers, medical details and other sensitive data from the AI prompt. Allow 45–60 minutes for a four-person sample and a final offline check.

Copy this starter prompt

Use only the confirmed trip details and supplied needs below.
Create two lists: shared items and personal items.
For each shared item, show quantity, one owner, handoff time and confirmation state.
Do not invent bookings, weather, laws, medical needs or safety advice.
Do not assign personal medication or documents to another traveller.
Write NEEDS OWNER or NEEDS CHECK when information is missing.
[PASTE CONFIRMED DETAILS AND SUPPLIED NEEDS]

Build and test the handoff

1. Give every shared item an ID and define what “confirmed” means.
2. Merge true duplicates, but keep personal versions separate when required.
3. Assign exactly one owner and one backup plan to each shared item.
4. Add a handoff time, such as the evening before departure.
5. Run a fictional four-person check: each person states what they own and what remains personal.
6. Export or print the final list and reconcile it at the meeting point.

Worked fictional sample

Item S04 is a four-port charger. Mina owns it and confirms it at 20:00 the night before departure. Arun brings only his personal cable. AI may flag that the charger has no confirmed plug adapter, but it cannot assume the destination socket type or assign Arun's medication to the shared bag.

The plan passes when every shared item has one owner and state, no personal document or medication appears in the shared list, and all four sample travellers can explain their handoff without guessing.

Recover when the list becomes unreliable

If AI merges personal and shared items, process one traveller at a time. If two people believe they own the same item, choose one owner before marking it confirmed. If Taskade is unavailable, use a printed table or group message with item IDs. Recheck official travel, weather and health information separately near departure.

Product and pricing pages were inspected on 9 October 2026. This is a fictional planning exercise; no booking, destination, weather, border, health or safety check was performed.