The day a project is handed over is not the end of the work — it is the beginning of its use. Our experience across dozens of projects shows that the biggest hidden cost organisations carry is "walking knowledge": the one manager who understood the panel, the team that files a ticket for every small change, and documentation that was never written. PBDP's training and documentation service seals that leak — user and technical manuals, training videos and specialist workshops — so your team stands on its own feet without the contractor. The more self-sufficient your people, the lower the support bill and the faster the organisation moves.

Why documentation is the invisible return on investment

Written knowledge performs three jobs at once. First, it shrinks support tickets — a user who has an FAQ entry and a "how to publish a news item" video does not phone us the next morning. Second, it compresses onboarding of new staff from weeks to hours; in enterprise portals with dozens of roles and permission tiers, that is the difference between "project delivered" and "chaos delivered". Third, it is an institutional asset — architecture maps, data flows and hosting guides that stay citable even when we are gone. The same logic rules in hardware: production documentation, as in our technical documentation and manufacturing prep service, exists precisely so a product stays buildable without its designer in the room.

What you get delivered

• Role-based user manuals: a separate guide for every role (clerk, manager, super-admin) with screenshots and numbered steps, as PDF and web edition.
• Task-based training videos: short films recorded on your real system environment, with Persian voice-over; ready to host in the site's learning section or the organisation's LMS.
• Technical documentation: deployment, architecture and API documentation for whatever development team inherits the system after us.
• Live workshops: in-person or online sessions with a pre-test, hands-on exercises and a completion certificate.
• Knowledge base / help centre: searchable, always-current FAQs and step-by-step guides, inside the WordPress panel or a bespoke CMS.
• System administrator handbook: the map of accounts, credentials, domains and services in a confidential handover package — the thing nobody usually writes down.
• Tests and exercises: a practice file for every task plus a short end-of-course quiz, so the impact of training stays measurable rather than anecdotal.
• In-service training calendar: quarterly refresh sessions that prevent forgetting and introduce newly added capabilities.

How the work is delivered

1. Audience analysis: roles, digital literacy levels and each group's repetitive tasks are mapped into a training matrix.
2. Knowledge extraction: structured interviews with the development team while technical decisions are still fresh and nobody has left.
3. Production: manuals written, videos recorded and the knowledge base assembled, all reviewed by you before publication.
4. Training delivery: workshops in small groups using your organisation's real scenarios and real data.
5. Assessment and refresh: post-training tests, gap reports and documentation updates; in products built on a design system, the interface guide stays current automatically.

Live training, video or knowledge base? All three

Each format has its job. Live workshops win acceptance and answer the questions nobody dares to type; videos win repetition and access at the moment of need; the knowledge base wins the quick lookup. The full project delivers all three — and where budget is limited, we prioritise: daily and error-prone tasks first, rare procedures later. When training is part of a wider digital transformation programme, we treat staff resistance as a real workstream: training without management sponsorship ends up as archived PDFs. For a small change, even one compressed two-hour session, filmed, becomes the organisation's safety net. In our experience, organisations that start documenting from the first week of a project end up paying clearly less for second-year support; a video, likewise, is produced once and watched thousands of times, which makes it the most economical option for teams with high staff turnover. For senior managers we also prepare a one-page summary — the kind that genuinely works in a board meeting.

Frequently asked questions

How long does a training course take?

For a typical admin panel, two two-hour sessions suffice: orientation and daily tasks in the first, administrative and safety operations in the second. For larger systems, role-specific tracks are designed across three to five specialist sessions.

Do we own the video files?

Yes, with full ownership — no forced watermark and free to host on internal systems. On request we publish the same videos in your site's learning section so your customers benefit from them too.

Will you document things for our in-house programmers?

Yes: architecture, data-flow diagrams, staging environment guide, testing guide, endpoint documentation and error contracts are all part of the technical package, so your team can continue development without depending on us.

To receive a proposal for your team's training and documentation programme, contact PBDP — in a short first meeting we measure your organisation's knowledge gap free of charge.