Prompt engineering gets you answers from general AI models, but fine-tuning creates an AI that thinks about your workplace's specific issues consistently and reliably across multiple documents. If you're building something you'll use repeatedly across lots of documentation, fine-tuning pays off; if you're solving a one-time problem, prompt engineering is usually smarter.
Fine-tuning and prompt engineering are two fundamentally different approaches to making AI models behave consistently. In workplace documentation, this distinction matters because consistency strengthens your evidence trail and credibility.
Prompt engineering is what most people do: you craft a detailed instruction for a general-purpose model like Claude or ChatGPT every time you need documentation. You describe the task, the constraints, and the output format. It's fast, flexible, and requires no special training. Prompt engineering is stateless—each prompt is independent, and you rely on the model's base knowledge and reasoning.
Fine-tuning is different. You provide training examples (usually dozens to thousands) that demonstrate the exact behavior you want. The model learns patterns from those examples and bakes in that behavior at the parameter level. A fine-tuned model is a new version of the base model, permanently altered by your training data. Fine-tuning is expensive, time-consuming, and requires technical expertise, but it produces deterministic, reproducible outputs.
Consider documentation for retaliation protection. You're creating a record of incidents over time. With prompt engineering, each summary you generate depends on the exact wording of your prompt, the model's current behavior (which can shift between API updates), and the model's interpretation of context. If you later need to defend your documentation, opposing counsel might argue inconsistencies in how you framed similar incidents.
With fine-tuning, you've trained the model on examples of how you want incidents categorized, summarized, and contextualized. Every output follows the same logic because the model has learned your documentation style. This consistency is legally valuable—it demonstrates a systematic, non-adversarial approach to record-keeping rather than cherry-picked framing.
Fine-tuning is impractical for most individual workplace users. You'd need 50-100 carefully annotated examples of incident documentation to start seeing benefits. You'd need API access to fine-tuning (OpenAI offers this; Claude has limited fine-tuning; Google Gemini's fine-tuning is in beta). Costs run $0.03 to $0.10 per 1K tokens for training, plus ongoing inference costs for your fine-tuned model.
Prompt engineering is immediate and free for most platforms. The trade-off is consistency. Each time you use the prompt, you might get slightly different summaries depending on temperature settings, model updates, and context window management.
Most workplace documentation benefits from a hybrid: use rigorous prompt engineering with saved templates. Create a master prompt that documents how you want incidents framed. Save it in Notion or a note-taking app. Use the exact same prompt every time you document a similar type of incident. This gives you consistency without the overhead of fine-tuning. If your documentation is ever challenged, you can show that you used the same methodology throughout.
Only consider fine-tuning if you're documenting very high-stakes matters (ongoing legal disputes, severe harassment patterns) across 6+ months or longer, and you have the technical chops to do it. For most workplace users, meticulous prompt engineering with template reuse is sufficient and more defensible because it's transparent—you can show exactly what instructions you gave the AI.
Try this: Create a master documentation prompt in a text file or Notion database. Write it once, clearly, with all your constraints: "Summarize this incident using only facts from the source material. Preserve the date, people involved, and specific statements. Use neutral tone. Include context about patterns if relevant. Do not interpret or editorialize." Save it. Use it unchanged for every incident you document over the next month. This consistency, combined with transparency about your process, is more valuable legally than a fine-tuned model most workplace users could afford.
Peri can explain this concept, give practical examples, help you decide whether it applies to your situation, or recommend a journey if appropriate.
Explore related journeys or tell Peri what you're working through.