Support and Maintenance en Doha
How we work in Doha
What left, left
A broken page is fixed and stops being broken for everyone. A file sent in March lives in somebody's inbox, and you cannot reach it there. That is why maintenance here is mostly prevention, plus an agreed protocol: how a wrong document is corrected and who decides.
Keep the file, not the recipe for remaking it
If the system rebuilds the document every time someone asks for it, the one that comes out a year from now will carry next year's template. You store the file that was sent, with its date, and that is the one you consult. Only then do your copy and the client's match.
The library that composes the PDF has a version
An update can change how lines break, how the typeface is embedded or where a table splits, without anyone having touched your code. We pin the version, and when it is raised the sample documents are generated before and after and compared.
A document that never gets made throws no error
Documents are produced in a background process: when it jams nothing visible goes down, there are simply clients not receiving theirs and you find out days later through a complaint. The signal we watch is the age of the oldest document still waiting.
Answering your questions
What people ask us about Support and Maintenance in Doha.
If your question is not here, tell us about the project and we will answer with real context.
Ask us directlyReal work
Projects we have built
Full service · All the detail
Support and Maintenance: stack, process, use cases and FAQs