Format
In-house and customised. Delivered onsite at your office or live online.
Duration
1 day (8 hours) or 2 days (16 hours), depending on the documents you need covered.
Batch size
15 to 30 participants per batch. Multiple batches can run on consecutive days.
What you take home
A rewritten sample of your own document, plus templates and a house style checklist.
Certificate
Certificate of completion issued to every participant who finishes the workshop.
Turn your team's technical knowledge into documents people can actually follow
Most documentation problems in Philippine organisations are not English problems. They are structure problems. The engineer knows the process. The QA lead knows the standard. The system administrator knows the fix. What gets written down, though, is a wall of paragraphs that a new hire cannot follow, an auditor cannot verify, and a client keeps sending back for clarification.
Technical writing is the discipline of turning specialised knowledge into documents a specific reader can act on. It covers how you plan a document, how you organise information for the person using it, how you write instructions that cannot be misread, and how you review and edit before release.
This is an in-house programme. We do not run generic public seminars for this topic. Before the workshop we look at the documents your team already produces – your SOPs, incident reports, user manuals, technical proposals, or turnover documentation – and build the sessions around fixing those. Participants leave with a rewritten version of a real document from their own workload, not a textbook exercise.
We deliver across Metro Manila, Cebu, Davao, and provincial sites, and run the same programme live online for distributed teams.
What Your Team Will Be Able to Do
By the end of the workshop, participants can do the following with their own documents.
- Identify who will read a document, what they need to do with it, and what they already know before writing a single line.
- Structure a technical document so a reader can find the one thing they need without reading all of it.
- Write instructions and procedures in steps that cannot be performed two different ways.
- Replace vague and padded sentences with plain, specific language that holds up under audit.
- Use tables, diagrams, screenshots, and callouts where they carry information better than prose, and label them properly.
- Apply one consistent format and style across a document set so different authors produce comparable output.
- Edit and proofread their own and each other’s drafts against a defined review checklist.
- Use AI writing tools for drafting and editing without introducing errors into technical content.
Course Outline
The core programme runs eight modules. We adjust the depth of each one after the training needs analysis, and drop or extend modules to match the documents your team is responsible for.
- Technical writing compared with business writing, academic writing, and marketing copy
- The five traits we assess every document against: clarity, accuracy, conciseness, accessibility, and audience fit
- Where documentation failures cost money: rework, downtime, failed audits, repeated support tickets, disputed deliverables
- Walkthrough of a strong and a weak version of the same document
- Profiling the reader: technical peer, non-technical decision maker, new hire, client, regulator, auditor
- Writing for mixed audiences without writing two documents
- Defining the purpose of a document in one sentence before drafting
- Working with subject matter experts: what to ask, and how to capture answers you can write from
- Scoping: what belongs in the document, what belongs in an annex, what belongs in a different document entirely
- Organising by task, by sequence, by system, or by exception, and how to choose
- Chunking: headings, sections, and the length a reader can hold in one pass
- Writing headings that tell the reader what is inside them
- Summaries, overviews, and executive sections for readers who will not read the whole document
- Navigation aids: numbering, cross-references, tables of contents, and indexes
- Plain language: shorter sentences, active voice, concrete verbs
- Removing padding, hedging, and redundancy without losing precision
- Defining technical terms once and using them consistently
- Ambiguity that causes real errors: unclear pronouns, stacked modifiers, undefined conditions, unstated assumptions
- Grammar and usage refresher focused on the mistakes that appear in technical documents
- Writing a step so it can only be performed one way
- Preconditions, tools, safety notes, and expected results
- Branching, exceptions, and troubleshooting sections
- Warnings, cautions, and notes: when to use each and where to place them
- Testing a procedure by having someone else follow it exactly as written
- Progress and periodic reports: what stays constant, what changes each cycle
- Incident and investigation reports: sequence of events, findings, root cause, recommendations
- Technical proposals: problem statement, approach, scope, assumptions, exclusions
- Specifications and requirements: writing testable, verifiable statements
- Recommendations that decision makers can approve without a follow-up meeting
- Choosing between prose, a table, a list, a flowchart, or a screenshot
- Labels, captions, figure numbering, and referring to visuals in text
- Page layout, typography, and white space in technical documents
- Building or applying a house style guide and reusable templates
- Version control, document numbering, revision history, and approval blocks
- Citing sources, handling confidential material, and respecting third-party content
- The three-pass edit: structure, then clarity, then correctness
- A review checklist your team can apply to any document
- Peer review that improves the document without stalling it
- Handling SME feedback and conflicting comments
- Practical use of AI drafting and editing tools, and the checks that must stay human
Documents We Cover
Bring the documents you are struggling with. We build the workshop exercises around them.
Process and operations
- Standard operating procedures
- Work instructions and job aids
- Process manuals and playbooks
- Turnover and handover documentation
- Checklists and forms
Reporting and compliance
- Progress and accomplishment reports
- Incident and investigation reports
- Audit and compliance documentation
- Quality and inspection reports
- Policies and procedures
Product and client facing
- User manuals and product guides
- Technical proposals and bid documents
- Specifications and requirements
- Knowledge base and help articles
- Release notes and system documentation
Who Should Attend
This programme is built for people who write technical documents as part of a technical job, not for full-time writers only.
Roles
- Engineers and technical supervisors
- Quality assurance, quality control, and compliance officers
- IT, software, and systems teams
- Operations and process improvement teams
- Project managers and project engineers
- Technical sales and pre-sales staff who write proposals
- Customer support and knowledge base owners
- HR and training teams who document processes
Industries we work with
- Engineering and construction
- Manufacturing and industrial operations
- IT, software, and technology companies
- BPO and shared services
- Banking, insurance, and financial services
- Healthcare and pharmaceuticals
- Energy, utilities, and telecommunications
- Logistics and supply chain
Specialist Technical Writing Tracks
Four specialist tracks built on the core outline. Choose one, or combine modules across tracks.
Technical Writing for Engineers
For engineering and construction teams who write for clients, regulators, and non-technical approvers.
Focus modules
- Translating calculations, findings, and site conditions into language a client can act on
- Technical proposals, scope documents, and variation orders
- Inspection, testing, and incident reports
- Method statements, work instructions, and manuals
- Writing recommendations that survive review by both engineers and finance
Typical length: 2 days. Pairs well with presentation skills training for teams who also defend their reports in person.
Digital Documentation
For teams publishing to intranets, portals, help centres, and knowledge bases rather than to print.
Focus modules
- Writing for readers who scan and search rather than read front to back
- Help articles, FAQs, and troubleshooting content that reduce support tickets
- Structuring content for reuse across platforms and devices
- Screenshots, annotated visuals, and short instructional video scripts
- Keeping a knowledge base current: ownership, review cycles, and retirement of old content
Typical length: 1 to 2 days. Often combined with digital marketing training for teams handling both internal and customer-facing content.
Documentation for Quality and Compliance
For manufacturing, healthcare, and service organisations working to a management system standard.
Focus modules
- Writing procedures that an auditor can trace from policy to record
- Document control: numbering, revision history, approval, and distribution
- Corrective and preventive action reports
- Keeping a document set consistent across departments and authors
- Writing so that a procedure survives staff turnover
Typical length: 2 days. Frequently run alongside our ISO training and root cause analysis training.
Business and Technical Communication
For teams whose written output is mostly email, memos, and internal reports rather than formal documentation.
Focus modules
- Structuring email and memos so the ask is clear in the first three lines
- Writing for senior management: brevity, decisions, and options
- Communication styles and how they affect written tone, using the YOUnique DISC framework
- Writing across teams and cultures in shared services and multinational setups
- Meeting notes and minutes that people actually use afterwards
Typical length: 1 day. Draws on our business communication training and cross-cultural communication training.
Delivery Formats and Pricing
Every programme is quoted per batch, not per head. What moves the price is the number of days, the number of batches, and where the training is held.
What a quotation includes
- Training needs analysis and pre-workshop document review
- Customised materials built around your document samples
- Facilitation for one batch of up to 30 participants
- Workbook, templates, and a house style checklist for every participant
- Certificates of completion
- A post-training summary for the training sponsor
Rates depend on days, batches, and venue. Send us your headcount and preferred dates and we will send a written quotation within two working days. For general budgeting across programmes, see our corporate training prices in the Philippines.
How We Build Your Programme
Five steps from first call to post-training review. Nothing is delivered off the shelf.
1. Training needs analysis
A working session with your training sponsor and a few document owners to define the gap and the outcome.
2. Document review
You send five to ten real documents. We identify the recurring problems and build exercises from them.
3. Programme design
We confirm the module mix, the schedule, and the deliverable each participant will produce.
4. Workshop
Short input, then practice. Participants rewrite their own documents and review each other’s drafts.
5. Follow through
A sponsor report on what we saw, plus an optional clinic where the team brings documents written after the training.
How the Sessions Run
Roughly a third of each day is input. The rest is writing, rewriting, and reviewing.
- Document clinics. Participants bring a real document and rewrite it in stages across the day.
- Before and after teardowns. We take a weak passage from your own material and fix it live, explaining each decision.
- Instruction testing. One participant follows another participant’s procedure exactly as written. The gaps become obvious in about ninety seconds.
- Peer review rounds. Structured review using the same checklist your team will keep after the workshop.
- Templates you keep. SOP, incident report, and technical proposal templates, plus a one-page style checklist.
Sessions are delivered in English, with Filipino used freely in discussion and coaching where it helps participants think through their drafts.
Writing Technical Documents in the Age of AI
Most teams are already drafting with AI tools. The risk is not that they use them. It is that a confident, fluent draft hides a wrong step, an invented specification, or a procedure nobody verified.
This module covers where AI genuinely helps and where it must not be trusted:
- Using AI to outline, condense, and reformat rather than to supply technical facts
- Prompting with your own source material so the tool works from your data, not its assumptions
- Verification: what a human must check before any AI-assisted document is released
- Confidentiality: what should never be pasted into a public tool
- Keeping a consistent house voice when several people draft with different tools
Teams looking at broader adoption can extend this into our AI training programme.
What Clients Say About Rainmakers Training
Training sponsors and participants on what changed after the workshop.
Companies We Have Worked With
Teams from these organisations have trained with Rainmakers.
Why Technical Writing Is Worth Training For
Four places where documentation quality shows up on the operations side of the business.
Fewer repeated questions
When a procedure is written so it can be followed without interpretation, the same question stops coming back to the same senior person. Supervisors get their time back, and new hires reach independent output faster.
Less rework and fewer errors
Ambiguous instructions produce wrong parts, wrong settings, and wrong site work. Precise documents remove the guesswork that turns into rework, warranty claims, and disputed deliverables.
Knowledge that survives turnover
In teams with high attrition, undocumented process walks out the door with the person who held it. Written procedures keep operations running through resignations, transfers, and shift changes.
Audits and client reviews go faster
Auditors and clients look for a traceable line from policy to procedure to record. Consistent, controlled documents shorten that conversation instead of extending it.
Technical Writing Training Philippines FAQs
The questions training sponsors ask us most often before booking.
One day for teams focused on a single document type, and two days where the team writes several kinds of documents or needs extended practice on procedures and reports. Delivered online, the same content runs as four half-day sessions of four hours each. Some clients add a half-day clinic three to four weeks later, where participants bring documents written after the training for review.
We quote per batch rather than per participant, so cost is driven by the number of training days, the number of batches, and whether the venue is your office, an external venue, or online. A quotation covers the needs analysis, customised materials, facilitation, participant workbooks and templates, and certificates. Send us your headcount, location, and target dates and we will send a written quotation within two working days.
Fifteen to thirty participants per batch. Below fifteen the peer review exercises lose value, and above thirty the facilitator cannot give every participant feedback on their own document. Larger groups are split into batches, usually run on consecutive days.
Technical writing is delivered in-house only. The programme works because the exercises use your own documents, which is not possible in a mixed public class. If you have a small number of people and cannot fill a batch, contact us and we will point you to a suitable option.
It is a short working session with your training sponsor and a few document owners, plus a review of five to ten documents your team currently produces. It tells us whether the real gap is structure, clarity, formatting, or review discipline, and it tells us which modules to deepen and which to compress. It also gives us the raw material for the workshop exercises. It takes about an hour of your team’s time and there is no separate charge for it.
Yes, and it usually is. Engineering teams spend more time on inspection reports, method statements, and proposals. IT and software teams spend more time on knowledge base articles, release notes, and system documentation. Quality and compliance teams spend more time on procedures, document control, and corrective action reports. The core modules stay the same. The examples, exercises, and templates change.
Each participant works on a real document from their own workload and leaves with a rewritten version of it, reviewed by a peer and by the facilitator. They also take home the templates used during the session and a one-page review checklist their team can standardise on.
Yes. Every participant who completes the workshop receives a certificate of completion from Rainmakers Training and Consultancy.
Onsite anywhere in the Philippines, including Metro Manila, Cebu, Davao, and provincial plant or project sites, and live online for distributed teams. Travel and accommodation for out-of-town delivery are itemised separately in the quotation.
Materials and written output are in English, since that is what the documents are written in. Discussion and coaching move between English and Filipino, which helps participants think through a draft before committing it to English.
Yes. We cover where AI tools genuinely speed up drafting and editing, what has to be verified by a person before release, and what should never be pasted into a public tool. Teams planning wider adoption often extend this into our AI training programme.
Business writing focuses on everyday correspondence: email, memos, and internal updates. Technical writing focuses on documents that someone has to act on or verify, such as procedures, manuals, specifications, and reports, where an ambiguity has an operational cost. Teams that need both usually take our business communication training first, then this programme.
We normally need two to three weeks between the needs analysis and the workshop to review your documents and build the materials. Tighter timelines are sometimes possible. Tell us your target date when you enquire.
Related Training
Programmes teams often pair with technical writing.
- Business communication training – email, memos, and reporting to management
- Effective communication skills training – clarity in spoken and written exchanges across teams
- Presentation skills training – for teams who present the reports they write
- ISO training – for organisations formalising a documented management system
- Root cause analysis training – for teams writing investigation and corrective action reports
- Corporate training programmes – the full in-house catalogue
Send us the documents your team keeps rewriting
Tell us your headcount, your location, and the kind of documents your team produces. We will review a few samples, recommend a one or two day design, and send a written quotation within two working days.
Roselle, Training Operations Lead – Viber +63 976 668 6033
venchito@rainmakermastery.com
