Saturday, March 30, 2013

What Does the Presidential Directive on Records Management Really Require?

What Does the Presidential Directive on Records Management Really Require?

What Does the Presidential Directive on Records Management Really Require?




March 26, 2013 By Michael L. Miller, director, RIM Consulting, Array Information Technology
The August 2012 Presidential Directive on Managing Government Records is a major achievement for the federal records management community -- and it is the cornerstone for the long-awaited transition to electronic recordkeeping by federal agencies. But what does it really mean?
 
As a former federal records officer and former Director of the Modern Records Program of the National Archives and Records Administration (NARA), I have taken a keen interest in the directive, of which a large number of articles, blogs and columns have appeared about its implications. And I would like to bring my perspective as a federal records manager to the discussion.  
 
My underlying message is that agencies can meet the directive’s targets if they carefully scope their response to its requirements and their agency goals, following a seven-year plan and bringing people, policy and process into the solution mix to supplement technology.  
 
Here are 12 ideas agencies can use to leverage staff rather than money on not only electronic recordkeeping goals, but also other goals that are largely restatements of existing requirements.

1.  Read the directive very carefully.

The directive's wording has been crafted very carefully -- and that applies to what is both said and not said. Part 1, Goal 1, for example, states that agencies “should commit immediately to the transition to a digital government.” Target 1.1, however, only requires agencies to manage all permanent electronic records in electronic format to the extent possible by 2019. In many agencies, especially smaller ones, there may not be many permanent records, so consult your records schedules, then review the Code of Federal Regulations to understand how NARA understands “manage.” Your challenges may be smaller than you envisioned.      
 
 

2.  Identify the problem(s) you are trying to solve.

The directive defines goals and targets; it leaves the means open. Obviously you want to meet the targets, but I’m sure there are numerous agency-specific records and information problems that could be addressed also. Continuing the example above, you are only required to manage your permanent records electronically, but you may choose to manage all of your records electronically because there is a well-defined business case for doing so, such as minimizing the number of records on hand to simplify e-Discovery responses, or maximizing document retention to support knowledge management. Electronic recordkeeping can address either, but your implementations would be different depending on your business case, hence the need to identify the specific problem(s) you wish to solve.
 
 

3. Determine what is a “good enough” records management solution.

Many federal records managers bristle at the thought of a “good enough” records management program – they want to have the best in the federal government. I would argue that they should focus on being the best for their agency – its mission, priorities and budget. That means being “good enough” to meet both internal and external requirements.  For example, the records manager in a small agency may want a records management application, but given the limited number of permanent records, a more manual process might provide a “good enough” medium-term solution at lower cost.
 
 

4. Take a holistic view.

From a holistic perspective, you need to understand four major elements of the ecosystem in which records and other information assets are managed:
  • The records and other information assets your agency creates and maintains, their characteristics and requirements, the rewards and risks associated with their management, and available resources.  
  • The needs and expectations of business process owners and staff who create agency records; the records program that provides RIM policy and services; and the information architecture which provides context and support for the records management.
  • Four agency components that can either facilitate records management or erect barriers:  agency staff, agency culture, agency policies, and the existing and planned IT infrastructure.
  • External forces framing “good enough” records management including the regulatory framework (including the directive), and the expectations of the community, agency suppliers (e.g., contractors), and customers (e.g., the regulated community).
Transitioning to electronic recordkeeping will require an assessment of all ecosystem elements so an appropriate path can be chosen.
 
 

5. Take the long view.

The directive has very specific (and tight) timeframes, so use all of the time alloted. The email management target is the end of 2016 and the permanent records target is the end of 2019. Provided agencies start quickly, these targets allow time for project planning, evaluating the current situation, developing policy and training, budgeting to procure necessary technology, and gradually rolling out solutions.  
 
Another reason for taking a longer view is that successful implementations of electronic recordkeeping are done in stages, often over several years.
 
 

6. Assemble your forces.

Records management doesn’t succeed on its own -- it needs supporters, allies and champions.  
  • Supporters see the benefits from records management such as approved destruction of unneeded records and information products, or the ability to find needed records for audit or litigation.  
  • Allies are other information managers who pursue similar information management goals. 
  • Champions will represent the program at the senior level of the organization. 
Your “forces” should be brought together participate in a Directive Response Team and serve as a steering council for the program and an advocacy group to promote its mission, products and budget requests.
 
 

7. Break the problem into manageable chunks.

The ecosystem review discussed above provides keys to understanding your records and how they can be managed successfully. Breaking the body of records into constituent parts allows agencies to apply appropriate management controls to important categories of records. Program staff are a necessary part of the process because they will only buy into an electronic recordkeeping solution if the records warrant the effort. The initial breakdown is by organization or function. And the easiest solution is to follow the approach used in your records retention schedules. Next identify major record groups – permanent records, records required by statute or regulation, records that document the agency’s statutory mission or are subject to audit or elicit public scrutiny, and so on. Then apply appropriate controls to each grouping.
 
 

8. Assess your records management staff.

A strong records manager is critical to meeting the directive’s goals. However, records managers currently vary greatly in experience, training and skill levels. 
 
Records managers can fill one or more of these roles on the Directive Response Team:
  • Explaining federal recordkeeping to the team.
  • Translating NARA requirements into agency requirements.
  • Assisting in crafting policy and procedural solutions for electronic records management.
  • Assisting in crafting technology solutions.
  • Serving as a leader and/or champion for the records management solutions selected to address the directive’s goals.  
To achieve success, all of these roles must be filled. Currently not all records managers have the requisite, experience, training and skills to participate effectively in transitioning to electronic recordkeeping. Agencies must assess whether their current records staff has the qualifications needed to play their role(s) in addressing the goals laid out in the directive. If not, agencies will need to upgrade their staff via training, hiring or contracting.
 
 

9. Assess your current policy and records schedules.

The biggest challenges in implementing electronic recordkeeping have stemmed from poor policy foundations, not technology. Most of those who are not part of the records management community (and even some of those who are) think records management policy is set in stone. It isn’t. Federal records management principles remain, but what they mean and how to implement them effectively is often radically different today.  
 
The easiest way to simplify the management of all records – but especially electronic ones – is to clearly identify the records “containing adequate and proper documentation of the organization, functions, policies, decisions, procedures, and essential transactions of the agency.”  That is what agencies are required to create and preserve. An agency’s definition of record may be understood more broadly than that, but in most cases, records not required for “adequate and proper documentation” can be disposed of relatively quickly.  
 
Records schedules often contribute to the problem.  Many records schedules do not identify the specific documents needed as part of the “adequate and proper documentation.” When employees are in doubt, they tend to keep everything. Records schedules should identify specific records or categories of records to be included or excluded from the file.    
 
The bottom line? Rrecords management policy and guidance must be simple and clear.  
 
 

10. Managing permanent electronic records – manual, automated or a mix.

When most of us think of managing electronic records we think of an entirely automated solution – an electronic records management application (ERMA) engineered to accomplish specific tasks.
 
An alternative (but more manual) process would be making a specific individual or individuals responsible for electronic filing. In many agencies that is already the case with important records –records that need to be safe from change or deletion, filed so they can be located and preserved so they can be transferred to NARA as required by federal recordkeeping regulations. The only records that need to be managed to meet the directive mandate are the ones identified as permanent. 
 
An ERMA is one solution that may be appropriate for your organization, but it is not required, and for smaller agencies with more simple record-keeping and tighter budgets, it may be overkill. The challenge is finding an acceptable balance between manual intervention and automation. How much are your employees able and/or willing to do to manage their records? The more they can do, the less expensive and complex the automation component.  
 
 

11. Managing email – not all records are created equal.

We all can define a record; it’s tougher to get agreement on whether a specific email or document fits the definition. The actual question is not whether an email is a record, but whether it is necessary for “adequate and proper documentation of agency activities.”  If it is, it definitely needs to be made part of an electronic recordkeeping system. If not, I would argue that it is part of a working file (which I do consider record material) to be maintained separately from the “adequate and proper documentation” file with its own retention.  
 
Directive Target 1.2 requires managing emails in an “appropriate system  . . . for as long as they are needed.” This allows agencies considerable latitude in determining retentions for things like working files, and NARA is working on a “tiered” approach to managing email that should simplify maintenance. The guidance is due out late in 2013.
 

12. Look for outside help.

Agencies aren’t in this alone. NARA has worked hard to collect and make available products developed by federal agencies that can be adapted for use in other agencies, and under part II of the directive, the agency and its partners will provide additional guidance and tools to assist records managers in responding to the directive. 
 
Even more useful in many cases are the personal contacts that agency records officer can make attending NARA-sponsored training and events such as BRIDG meetings.  In the D.C., metro area, there is a wide range of activities where federal records managers discuss common issues. Many federal records mangers who have good solutions don’t have the time to publish their ideas, but are available at in-town professional meetings, or one of the many local training seminars, many of which are free to federal employees. These provide excellent opportunities for learning and information sharing.  Agencies should encourage their records managers, especially the less-experienced ones, to attend these activities. 
 
The transition to electronic recordkeeping will benefit everyone – agencies, the regulated community, citizens and the government as a whole. It will make government more transparent and effective. The real transition isn’t from paper to electronic. It requires a change in how people do their jobs – and that is always difficult.   
 
 

You may use or reference this story with attribution and a link to
http://www.govtech.com/e-government/What-Does-the-Presidential-Directive-on-Records-Management-Really-Require.html

Saturday, January 5, 2013

Records management: A list of 7 resources and applications

Records management: A list of 7 resources and applications

Tuesday, January 1, 2013

Electronic Discovery & Records Management - Tip of the Month: Cloud Computing and Data Privacy

Electronic Discovery & Records Management - Tip of the Month: Cloud Computing and Data Privacy 28 December 2012 Mayer Brown Newsletter Scenario A multinational company is negotiating an agreement with a cloud computing provider to maintain and hold all of the company’s electronically stored information and data. The general counsel of the multinational company is concerned about data privacy and data protection both in the United States and worldwide. What is Cloud Computing? Cloud computing is the use of computing resources, including both hardware and software, that are made available over the Internet by a subscription-based service provider. Because cloud computing is Internet-based, it offers several advantages over more traditional access to a company’s data and software. Cloud-based software and files can be accessed “on demand” from virtually any computer with an Internet connection. For example, when email is stored “in the cloud,” the contents of a user’s email folders may actually be stored in one or more easily accessed Internet-connected servers located around the world. Moreover, because a company that receives cloud computing services does not rely on its own servers, the amount of data that can be stored is unlimited. Finally, because cloud computing services typically are managed by a third-party provider, they have the potential to reduce a company’s IT costs by eliminating the need to acquire and maintain expensive hardware and software. For all of the above reasons, many businesses are seeking to take advantage of this still-evolving technology. Potential Risks: Data Privacy, Data Storage, and E-Discovery Data privacy is an issue of concern for companies, their IT professionals and legal departments, whether files stay on-site or are stored electronically with a cloud computing provider. For companies considering cloud computing options, it is particularly important to carefully evaluate the provider’s policies and procedures to ensure that they provide sufficient safeguards to protect confidential data. The company’s lawyers and IT professionals should develop an understanding of the technology so that they can make informed decisions about whether cloud computing provides the level of protection they require. One specific risk is that electronically stored information (ESI) may be co-mingled with the ESI of another company or of a separate but related corporate entity. Such situations can make it difficult to determine what entity has “possession, custody, or control” of the data and is under an obligation to preserve or produce the data. Moreover, if a cloud computing provider stores data in multiple servers around the world, ESI may be split up among jurisdictions with different data protection and transfer laws, making it difficult to keep track of how to access and retrieve data, and how to keep data private and secure. ESI stored with a cloud computing provider can also present challenges to the discovery process in litigation. For example, the U.S. Federal Rules of Civil Procedure allow a party to request discovery of ESI in the responding party’s “possession, custody, or control.” If a company has contracted with a cloud computing provider to maintain and hold its ESI, the company does not have direct control over, or possession of, the ESI. For purposes of discovery, however, the company still has a duty to preserve and produce that data, as long as it has the practical ability to do so. Tips for Managing Risks The use of cloud computing should not fundamentally change the way a company handles ESI. No matter where the ESI resides, a company is responsible for being aware of the information that it creates and for governing that information in accordance with applicable business and legal requirements. It is important that the company be familiar with and closely monitor how its information is stored, retrieved, retained and disposed of by its cloud provider. A company should also develop effective procedures for auditing such activities by its cloud provider. At a minimum, the company should make sure it is capturing sufficient data when information is created (including what the information is, who created it, and for what purpose) to properly govern it. Before signing a service contract with a cloud computing provider, a company should be sure that the contract contains provisions protecting the company’s interests and its need to comply with data privacy requirements. Consider the following items when negotiating a service contract: Access: The company should have the right to access all ESI “on demand” and in a specified format that is easy to use. Control: The company should have the ability to reasonably direct actions of the provider to preserve and produce ESI. Cooperation: The provider should be willing to comply with the company’s directions regarding its ESI and to comply with any and all legal holds. Speed: The provider should agree to cease any data destruction in a timely manner and to produce data with sufficient speed to meet the company’s obligations. Metadata: The company should inquire as to the form or format in which data will be stored and returned for production during litigation, including whether metadata will be intact. Costs: Beyond the subscription price for the service, the contract should address the costs of potential production, as well as potential indemnification policies and attorneys’ fees should the cloud provider’s failure to comply with the contract terms result in liability for the company. Transparency: The contract should address confidentiality, data integrity and availability issues, including whether data will be commingled with the data of other cloud customers. Jurisdiction: The company should discuss with the provider where the data will be maintained and should consider whether production of the data might require compliance with data transfer laws or international privacy laws. Ownership: The contract should clearly state that the company owns the data. Security: The company should inquire about the security measures that the provider has in place to protect data privacy and attorney-client privilege and whether the company will be informed in the event of a security breach. Policies: The company should determine whether the provider’s policies and procedures could impede the company’s obligations to preserve, collect and produce ESI during litigation. Disaster Recovery: The company should have contingency plans in the event the provider was to suffer a server crash or other data loss or go bankrupt or out of business. The contract should stipulate that its provisions will remain in force if the provider is acquired by another company. The best way to manage the data privacy and security risks associated with cloud computing is to gain a comprehensive understanding of how the company plans to use cloud computing and to establish procedures and contract terms with the cloud computing provider that meet the company’s data security and privacy needs.

Monday, September 3, 2012

The FOIA Ombudsman » Government-wide Records Directive Addresses Electronic Records

The FOIA Ombudsman » Government-wide Records Directive Addresses Electronic Records


Government-wide Records Directive Addresses Electronic Records

Good records management is key to ensuring government actions and decisionmaking is preserved for future FOIA requesters (among others).
By the end of the decade, Federal agencies must digitize management of electronic records—including the millions of emails sent and received each year—according to a new records directive introduced last week.
With a focus on a digital transition, the Managing Government Records Directive issued jointly by the Office of Management and Budget (OMB) and the National Archives and Records Administration (NARA), intends to improve records management policies and practices across the executive branch. Specifically, the August 24, 2012 directive establishes two broad goals coupled with specific steps for agencies to take to achieve those goals.
The first goal, to “Require Electronic Recordkeeping to Ensure Transparency, Efficiency, and Accountability,” sets a 2019 deadline for all agencies to electronically manage their permanent records , with a 2013 cutoff to come up with a plan to do so. It also requires agencies to manage all email electronically by 2016.
The second goal is to “Demonstrate Compliance with Federal Records Management Statutes and Regulations.” Agencies will designate a senior official to oversee review of the existing records management program, ensure records are properly transferred to NARA, establish agency-wide records management training and work with NARA to ensure comprehensive agency-wide records schedules.
Implementing these steps should lead to improved openness and accountability by better documenting agency actions, more effective transfer of permanently valuable records to NARA—OGIS’s parent agency—and cost savings through more efficient operations agency-wide, according to the directive.
The directive, ordered by President Barack Obama in his November 28, 2011 Memorandum on Managing Government Records, was a joint product of NARA and OMB. The Office of Personnel Management will work with NARA and OMB to carry out the stated goals, including establishing a new records management employment series requiring specialized skills and giving records managers a heightened role.
NARA will continue to play a major guiding role in carrying out all aspects of the directive. The agency will review related regulations to incorporate necessary changes to achieve the directive, issue new email guidance, explore cloud-based storage solutions and implement a government-wide analytical tool to assess agencies’ records management programs. The Archivist of the United States, David Ferriero, will convene and work with the senior officials from all 99 Federal departments and agencies to discuss progress and implementation of the directive each agency.
As the directive notes, “Records are the foundation of open government, supporting the principles of transparency, participation, and collaboration.” At OGIS, we couldn’t agree more. We look forward to working within NARA and with other Federal agencies to improve recordkeeping which we hope, in turn, will improve the FOIA process.
For more on the Directive, take a look at Records Express, the blog of our records management colleagues here at NARA.


Tuesday, June 19, 2012

Requirements and Best Practices Checklist

Requirements and Best Practices Checklist http://www.howto.gov/web-content/requirements-and-best-practices/checklists/long http://www.howto.gov/web-content/requirements-and-best-practices/checklists/long

Requirements and Best Practices Checklist

The Federal Web Managers Council developed this “checklist” tohelp you assess how well your agency meets federal website requirements and follows government web best practices.
Click a topic below to skip to a specific section, or scroll down to see the entire list. 
Requirements (Must do)Best practices (Should do)
Site policies page
Common content
Social media
Mobile
Managing content
Usability and design
Collaboration
Management and governance
Promote online services
Homepage link
Jobs
Grants
Regulations

Requirements


Required links/iconsRelevant law, regulation, or policy
Include all required links/icons on your site, in compliance with relevant guidance. Required links include, but are not limited to: privacy policy, FOIA info, USA.gov
E-Government Act of 2002 (Sections 204 & 207)
OMB M-05-04, Policies for Federal Agency Public Websites (PDF, 48 KB, 5 pages, December 2004)

Customer serviceRelevant law, regulation, or policy
Agencies must set service standards and use customer feedback to improve the customer experience. Agencies that provide significant services directly to the public are required to identify and survey their customers, establish service standards and track performance against those standards, and benchmark customer service performance against the best in business.

SearchRelevant law, regulation, or policy
Ensure your website includes a search function, to help the public easily locate government information.  Follow industry standard best practices to ensure your search function is as effective as possible. Write content in Plain Language, using the words of your customers, so they can easily find what they need when searching the web or your website
OMB M-05-04, Policies for Federal Agency Public Websites (PDF, 48 KB, 5 pages, December 2004)
Plain Writing Act of 2010 (PDF, 153 KB, 3 pages, January 2010)


Plain Writing ActRelevant law, regulation, or policy
Requires the federal government [executive branch] to write all new publications, forms and publicly distributed documents in a “clear, concise, well-organized” manner.
Plain Writing Act of 2010 (PDF, 153 KB, 3 pages, January 2010)

Accessibility/Section 508Relevant law, regulation, or policy
Make online information and services fully available to individuals with disabilities; Conduct accessibility testing when making significant changes to your site, or before launching a new site
Designing sites to work well on mobile devices usually also improves overall accessibility
Implementing Section 508 (Section508.gov)


PrivacyRelevant law, regulation, or policy
Provide a link to your privacy policy on every page (can be included in your overall site policies); Conduct a privacy impact assessment of your website; Post a “Privacy Act Statement” that explains your legal authority for collecting personal data and how the data will be used; Translate privacy policies into a standardized machine-readable format
Be aware of and comply with all other existing laws and directives that address the need to protect the privacy of the American people when they interact with their government online


Identity ManagementRelevant law, regulation, or policy
Allow the public and business partners to register or log on to Assurance Level 1 systems using externally-issued credentials
Requirements for Accepting Externally-Issued Identity Credentials - memo from Federal CIO to Executive Branch Agency CIOs (PDF, 166 KB, 4 pages, October 2011) 


FOIARelevant law, regulation, or policy
Your website must have a page that includes certain content as required by the Freedom of Information Act (FOIA)
Freedom of Information Act (FOIA) (PDF, 109 KB, 13 pages, April 2007)


Open Government DirectiveRelevant law, regulation, or policy
In the spirit of transparency, participation and collaboration, agencies are directed to:
  • Publish government information online;
  • Improve the quality of government information;
  • Create and institutionalize a culture of open government; and
  • Create an enabling policy framework for open government
OMB M-10-06, Open Government Directive(PDF, 81 KB, 11 pages, December 2009)

Naming and brandingRelevant law, regulation, or policy
Host the website on a .gov, .fed.us, or .mil domain; Clearly display the name of your agency on every page on the website
OMB M-05-04, Policies for Federal Agency Public Websites (PDF, 48 KB, 5 pages, December 2004)

Prohibition on lobbyingRelevant law, regulation, or policy
Consult your agency’s legal staff for guidance to ensure that your site does not advertise for, or provide preferential treatment to, private individuals, firms, or corporations. Follow the "rule of 3" - when linking to non-government information, show at least three similar examples, to avoid the appearance of endorsing a single source, service or product
Prohibition of Lobbying (Title 18, Section 1913, U.S. Code)


LinkingRelevant law, regulation, or policy
Publish your policy describing how and why you link to other websites, including criteria or guidelines for how your agency selects links to non-federal websites;
Publish and follow a schedule for reviewing the appropriateness and relevancy of external links
Notify visitors when a link on your website will take them to a non-federal-government website, include a disclaimer about content and privacy policies; Refrain from disclaiming content when linking to other federal sites, since to the public, all agencies are part of “the government”
OMB M-05-04, Policies for Federal Agency Public Websites (PDF, 48 KB, 5 pages, December 2004)

Web recordsRelevant law, regulation, or policy
Comply with existing laws and regulations related to the management of public web records.
Create an inventory of content that targeted audiences need or want. Identify categories of information (e.g., press releases or publications), not specific documents. Post the inventory, priorities, and schedule for posting additional content on the website for comment.
Regularly delete or archive content that is obsolete and is not required by law or regulation.


CopyrightRelevant law, regulation, or policy
Inform the public about your policies on digital rights, copyrights, trademarks, and patents. If your organization uses or duplicates private sector information, ensure that the property rights of the private sector source are adequately protected. (These protections apply to any material posted to federal public websites, such as documents, graphics, or audio files.)
Digital Millennium Copyright Act (PDF, 277.66 KB, 60 pgs, January 1999)
U.S. Trademark Law (PDF, 1.48 MB, 260 pgs, March 2010)


Paperwork Reduction ActRelevant law, regulation, or policy
Ensure that information collected from the public minimizes burden and maximizes public utility. Your agency must have OMB approval before collecting information from the public (surveys, forms, etc.), and you much include the OMB control number on the collection. Take advantage of OMB's Fast-Track PRA Review Process to help you collect information in a timely manner
Paperwork Reduction Act (44 U.S.C. 3501 et seq.)

SecurityRelevant law, regulation, or policy
Organizations are required to have security protocols in place to protect government information. Provide general information to the public about your security protocols to protect information on your website.
Guidelines on Securing Public Web Servers (Source: NIST; PDF, 2.13 MB, 142 pages, Sept 2002)

Information qualityRelevant law, regulation, or policy
Your site must comply with section 515 of the Treasury and General Government Appropriations Act for Fiscal Year 2001, Public Law 106-554, to ensure the information you present on your website is current, accurate and authoritative 

Multilingual websitesRelevant law, regulation, or policy
Comply with the requirements of Executive Order 13166, “Improving Access to Services for People with Limited English Proficiency,” based on Title VI of the Civil Rights Act of 1964, which bans discrimination on the basis of national origin.
Federal Agency LEP Guidance (Dept. of Justice)


No Fear ActRelevant law, regulation, or policy
Provide a link to information required by the “No Fear Act.”
The Federal Web Managers Council recommends that agencies determine the most appropriate placement for this link based on their audience (e.g., “About Us” or “Jobs” page)


GPEARelevant law, regulation, or policy
The Government Paperwork Elimination Act requires that, when practicable, federal organizations use electronic forms, electronic filing, and electronic signatures to conduct official business with the public, by 2003. Put as many of your services online as you can


GPRARelevant law, regulation, or policy
The Government Performance Results Act of 2003 requires organizations to make their annual performance plans readily available to the public.

Small Business Paperwork Relief ActRelevant law, regulation, or policy
Designate a single point of contact for small businesses, and to post the contact information on the organization’s website.
Small Business Paperwork Relief Act of 2002


Best Practices


Site policies pageGuidance
Create a page entitled “Site Policies” that includes links to required information and important policies.
Posting website policies

Common contentGuidance
Include the same types of “common content” found on most federal websites (such as contact information and basic information about your agency). Use terminology consistent with other agencies, and within your agency.  Write content using the words of your customers.
Includes "About Us" and "Contact Us" pages, as well as a Site Map or A-Z Index

Social MediaGuidance
Engage with the public via social media.
  

MobileGuidance
Design your site with mobile users in mind, and test your site on mobile browsers to ensure the public can access your information on the go.
Deliver content to mobile devices

Managing contentGuidance
Regularly review your content (at least annually, and more often for popular content), and update or archive as appropriate.
Ensure content is written for the web, using words familiar to the intended audience, so people can easily find what they need (usually via search), and understand what they need to do

Usability and DesignGuidance
Follow the “Research-based Web Design and Usability Guidelines” published by the Department of Health and Human Services
Do regular user testing on your site with real customers, to ensure they can easily and successfully complete their tasks. Design and develop your site for a broad range of visitors and browsers, including mobile devices and those with lower-end hardware and software capabilities
Implement a coherent information architecture (IA) and navigation scheme (including common labels), and use it consistently throughout your site


CollaborationGuidance
Collaborate both within your agency and across government to link to the official source for information.  Avoid creating duplicate content - stay in your “content lane.”
Collaborate internally, to make sure all content across your site describes programs, etc. in the same way. Post “program descriptions” in one central place and link there, instead of reposting the same description in several places.
Consult with the Federal Web Managers Council before creating a new portal site.

Management and governanceGuidance
Document and enforce your agency’s web content policies, procedures and style guide.
Regulary (at least annually) review and improve your site policies and procedures, in accordance with the latest government requirements and industry best practices for managing websites and content.
Develop and test procedures and continengency plans to keep your website running during an emergency, or take your website offline.

AnalyticsGuidance
Collect metrics on: customer focus and experience; quality and compliance; and recognition, in accordance with privacy and other policies.
Make changes to your website based on data, not opinion or "executive whimsy"


Promote online servicesGuidance
Offer easy access to online services, displaying them as prominently as possible, to help the public interact with the government on their terms, and serve themselves at their convenience.
Identify the most commonly requested and commonly used online services, forms and publications on your website and make sure can be easily found
Allow the public to print forms, and also complete and submit them online; provide instructions on how to order forms or publications if they can’t be accessed online 

Homepage linkGuidance
Every page on your site should have a text link back to your homepage (if you use a graphical link, you must also provide a text link).
Linking back to your homepage

JobsGuidance
Offer information about jobs or careers at your agency, even if you are a small agency or your site is managed by multiple agencies.


GrantsGuidance
Provide information about grant and contracting opportunities on your website.
Link to grants.gov and any other federal portal(s) related to grants
Link to fedbizopps.gov and any other federal portal(s) related to contracts.
The President’s Management Agenda of 2001 made this a priority (PDF, 633 KB, 64 pages, August 2001)

RegulationsGuidance
Provide information about regulations, notices and rules:
Posting information about regulations