SIGMA ERRADA Guide consultation 20 June 2018 presentation 2 (ENG)

1. © OECD
Egyptian Guide
to
Good Administrative Procedures
The result of the joint
ERRADA/SIGMA project 2015 - 2018
20 June 2018, Cairo

2. © OECD
2
Introduction to Part III
of the
Egyptian Guide to
Good Administrative Procedures
• Practical (re-) Design of Administrative
Procedures
• Simplification and Effectiveness
of the Administrative Process

3. © OECD
Templates in Administrative Procedures
Why focus on Templates?
• Templates so far are the main tool for ‘ruling’ the
process
• Many of them have unclear status
• Source for improvement and Simplification
• More Citizen orientation
 Transparency, Efficiency & Effectiveness
Lothar HAHN, TEMPLATES acc. to Part III of the Egyptian Guide to Good Administrative Procedures
Guide Ref.: P.III/3 Use of Templates

4. © OECD
General Requirements for Templates
Header Information:
Authority – name & address
• Objective of the Procedure and Legal reference
• Case- / File number, identification…
• Officer in charge of the procedure
• Names and Contacts of Parties involved
• Purpose of the Template within the procedure
 Transparency
Lothar HAHN, TEMPLATES acc. to Part III of the Egyptian Guide to Good Administrative Procedures
Guide Ref.: P.III/3 Use of Templates

5. © OECD
General Requirements for Templates 2
Content:
• Structured in Logical Blocks, ordered by
importance
• Only Legally required Data with explanation for
Plausibility, using Field Numbers for text
references
• Electronic data entry shall be the standard, print
out for manual filling should be allowed
• Manual filling should request printed letter
entries, so to allow Scanning and subsequent
electronic character Recognition
Guide Ref.: P.III/3 Use of Templates

6. © OECD
General Requirements for Templates 3
Design:
• Uniform and Modular Structure, Standardised at
least within an authority (header, layout…CI)
• Field numbers shall serve reference to ‚help texts‘
• Citizen friendly Text, easy to understand in local
language, no legal/administrative ‚jargon‘
• Layout (graphics and text) to be kept separate for
easy change / update management
• Templates to be mailed by post to the authority
shall fit the address for ‚windowed envelopes‘
• Design shall allow print-out on A4 portrait format
 To be compiled and documented in a ‚Style Guide‘
Guide Ref.: P.III/3 Use of Templates

7. © OECD
General Requirements for Templates 4IT Design:
• ALL Template development should in principle respect
IT implementation needs
• IT Tools in use should be standardised if not on
national, then at least on authority level
• Provide ‚Interactive Help‘ function through field
number references
• When PIN Identification is available, ALL Basic Data
shall be filled electronically
• Support to people with disabilities and use of keyboard
for screen / e-template -navigation
• Adapt to individual screen size and allow A4 printout
for documentation
Guide Ref.: P.III/3 Use of Templates

8. © OECD
Checkpoints for Templates
• Template Style Guide in place?
• Part I shall provide all the requirements
related to content, form and IT-suitability
as listed in the General Guide;
• Part II should reflect the authority-related
IT system particularities.
enable a largely automation-supported
generation of HTML templates
Guide Ref.: P.III/3.1 Template Style Guide

9. © OECD
Checkpoints for Templates 2
• Completeness of existing templates – are
all templates covered by legal provisions
and stored in a library of templates?
• Up-to-date-ness & Suitability
 Are templates User friendly and aligned with
Legal requirements?
 No outdated or parallel Versions in use?
 Focal target for overall simplification
Guide Ref.: P.III/3.1 & 3.2

10. © OECD
Thank you for your attention!