How it works
- 1Upload your Word form and approve it as the master.
- 2Click to issue a fresh copy every time you need one, and fill it in.
- 3Every entry from every copy becomes structured data you can trend in Docufen Studio (beta).
Problems because of paper
01
Trends spotted too late
Every paper form issued traps its data until someone retypes it somewhere else. By then a trend may have crept up unseen, and you only find out at an excursion or out-of-spec result you could have caught earlier.
02
Transcription costs time and adds errors
Turning paper entries into digital data means retyping them and checking them by hand: slow, and a source of new mistakes.
Two types of digital forms (compared to digital systems)
Going digital doesn't have to mean a digital transformation.
| Rebuilt eForms | Word forms (Docufen) | |
|---|---|---|
| Your documents | Rebuilt from scratch in a form builder | Your existing Word forms, used as they are |
| What changes | Every form rebuilt, then validated and maintained | Nothing: same forms and procedures as paper |
| Users | Learn new eForms | Fill in the form they already know |
| Adoption | Slow: a build for every form | Fast: start with the forms you have |
| Setup | Every rule and limit configured up front, before anyone can fill it in | Fill in straight away, since the rules stay on the form; add limits and checks later in Docufen Studio (beta) |
Cost and implementation
What it takes to go live, and what your cost grows with.
| Rebuilt eForms | Word forms (Docufen) | |
|---|---|---|
| Implementation time | Months | 5.7 working weeks, validated. See the case study |
| Licensing cost | Per user (varies by vendor) | $0 per user (unlimited users). You pay per page completed. |
Ask your vendor what happens to your price when you add 20 more users.
Not just forms
The same approach works for other GxP documents. Logbooks have their own page.