---
title: "M&A integration blueprint: Why procedures matter more than you think"
id: "20777"
type: "post"
slug: "ma-integration-blueprint-why-procedures-matter-more-than-you-think"
published_at: "2026-02-11T09:46:11+00:00"
modified_at: "2026-02-13T09:27:44+00:00"
url: "https://www.cherryleaf.com/2026/02/ma-integration-blueprint-why-procedures-matter-more-than-you-think/"
markdown_url: "https://www.cherryleaf.com/2026/02/ma-integration-blueprint-why-procedures-matter-more-than-you-think.md"
excerpt: "When two companies merge, the announcement typically focuses on synergies, market share, and shareholder value. What gets far less attention, until it becomes a problem, is the intricate work of actually integrating two distinct organisations into a functioning whole. At..."
taxonomy_category:
  - "policies and procedures"
taxonomy_post_tag:
  - "mergers"
  - "policies"
  - "procedures"
---

When two companies merge, the announcement typically focuses on synergies, market share, and shareholder value. What gets far less attention, until it becomes a problem, is the intricate work of actually integrating two distinct organisations into a functioning whole. At the heart of this challenge lies something seemingly mundane but absolutely critical: policies and procedures.

The integration blueprint for any merger or acquisition must address not only systems and structures, **and also** the fundamental question of how work gets done.

It’s here, in the weeds of operational detail, that many integrations stumble.

The M&A integration blueprint: Why procedures matter more than you think

## The identity crisis in mergers

Mergers trigger a form of organisational identity crisis. Once a company passes the 150 employees mark, it becomes very difficult to put a name to every face. Employees who once worked for Company A now find themselves part of Company AB. Or they discover they’ve been absorbed entirely into Company B’s culture and systems.

The shift goes beyond letterhead and email signatures. It goes to something much deeper: how people understand their role, their value, and their place in the organisation.

When policies and procedures clash, employees face daily reminders that their professional identity is in flux. Company A’s established way of approving expenses conflicts with Company B’s more streamlined process. Two incompatible approaches to client onboarding collide. Employees aren’t quite sure whose rules to follow. They don’t know which standard applies. They can’t tell what “good work” even looks like anymore.

This identity shift becomes particularly acute when policies carry cultural weight. A startup acquired by a corporate giant doesn’t just adopt new expense reporting forms. It grapples with the loss of autonomy, speed, and informality that defined its culture. When a family-owned business merges with a publicly traded company, the shift from handshake agreements to formalised documentation can feel like a betrayal of founding values.

> In 2000, AOL’s fast-moving internet culture clashed fundamentally with Time Warner’s traditional media processes. Even their email systems were incompatible, becoming symbolic of deeper integration failures. Neither company’s procedures survived intact. The $165 billion deal is often called the worst merger in history, destroying enormous shareholder value partly because the identity crisis was never resolved.

## When senior staff don’t know how things work

We were involved with one project where nine government bodies were merged into one new agency. The senior leaders were trying to fix the problem of managing parts of the business they didn’t actually understand operationally.

A CFO who oversaw financial operations at Body A was now responsible for Body B’s finance function as well. But Body B had edge cases that Body A had never needed to address before.

And that isn’t unique to that organisation.

This knowledge gap creates several problems.

### Pitfall 1. Applying your processes in unfamiliar contexts

Senior staff might inadvertently impose familiar processes on unfamiliar contexts. They assume that what worked in one environment will work in another. A procurement policy that made perfect sense for a manufacturing business might be completely inappropriate for a newly acquired software division.

> In 1994, Quaker paid $1.7 billion for Snapple, confident it could replicate its success with Gatorade. But Quaker’s management didn’t understand Snapple’s distribution model. They tried to apply Gatorade’s supermarket distribution approach to a brand that succeeded through small distributors and convenience stores. The procedural mismatch destroyed the business. Quaker sold Snapple for just $300 million three years later.

### Pitfall 2. Applying the wrong process

Leaders might struggle to make informed decisions about which procedures to keep, which to discard, and which to harmonise.

Without deep operational knowledge, they can’t easily distinguish between genuinely superior processes and merely familiar ones.

> In 2011, HP paid $11 billion for Autonomy but wrote off $8.8 billion just a year later. HP’s leadership didn’t understand Autonomy’s business model or revenue recognition practices. This knowledge gap led to allegations of accounting fraud and massive value destruction. Senior executives simply didn’t know what they didn’t know.

The gap becomes dangerous when senior staff don’t realise what they don’t know. Overconfidence in existing approaches, combined with unfamiliarity with acquired operations, can lead to dismantling procedures that were actually critical to success. These procedures might have seemed redundant or inefficient from the outside.

## The critical importance of accurate financial information

When two companies merge, financial visibility often deteriorates before it improves. Different accounting systems must be reconciled. The result can be a fog that obscures the true financial position of the combined entity.

> In 1998, Daimler merged with Chrysler to create Daimler-Chrysler. This $36 billion “merger of equals” struggled with incompatible financial reporting systems from the start. German and American accounting practices clashed. Leadership couldn’t get accurate consolidated financial pictures. The companies never truly integrated their operations or finances. Daimler eventually sold Chrysler in 2007 at a massive loss.

This fog can be fatal. Companies have run out of cash during integration because no one had a clear view of combined cash flows. For example: Working capital tied up in one part of the business wasn’t visible to treasury teams managing the whole; customer payment patterns from the acquired business weren’t properly modelled.

> Sprint’s $35 billion acquisition of Nextel in 2005 shows how financial integration failures cascade into operational disasters. Sprint failed to integrate billing systems and financial operations effectively. Customer churn accelerated as billing errors multiplied. The company lost visibility over combined subscriber economics. Sprint eventually wrote off most of the acquisition value.

The integration blueprint must prioritise financial visibility from day one.

This means:

- Establishing interim reporting structures even before systems are fully integrated.
- Daily cash reporting during critical periods.
- The finance teams from both organisations must work together to create consolidated views, even when the underlying systems remain separate.

Leadership needs to understand where every £, $ and € is:

- What are the combined receivables?
- What payment obligations are coming due?
- What credit lines are available?

These aren’t questions that can wait for the new ERP system to go live in eighteen months.

### Financial procedures deserve special attention during integration

Policies around expenditure approval, purchase orders, invoice processing, and payment authorisation directly affect cash flow. If these procedures break down or conflict, mistakes happen.

For example:

- Duplicate payments happen.
- Discounts are missed.
- Suppliers aren’t paid on time, damaging critical relationships.

The risk is particularly acute in the first 90 days. It’s also when opportunistic fraud is most likely. Clear financial procedures, consistently enforced, protect the business during this vulnerable period.

## Understanding and managing integrated risk

Risks that were manageable in separate entities can become critical when combined.

New risks emerge that neither organisation faced before.

Senior leaders must actively work to understand the all the risks the merged organisation might face.

> In 2008, Bank of America paid $4 billion for Countrywide Financial without fully grasping the legal and regulatory risks in Countrywide’s mortgage portfolio. Senior leadership hadn’t understood the compliance failures embedded in Countrywide’s operations. The acquisition ultimately cost Bank of America over $40 billion in legal settlements and losses.

> In 2007, Royal Bank of Scotland led a consortium to acquire ABN AMRO for €71 billion. RBS didn’t fully understand the risk exposures in ABN AMRO’s trading books. The merger left RBS dangerously over-leveraged just before the financial crisis. The bank required a £45 billion government bailout within a year.

The challenge is that risk knowledge often sits deep in the organisation:

- The compliance manager who understands data protection requirements.
- The operations director who knows which supplier is actually a single point of failure.
- The HR business partner who recognises which key employees are flight risks.

This knowledge needs to surface quickly.

A comprehensive risk assessment should happen early in the integration process.

This goes beyond financial and legal due diligence. It requires understanding operational, reputational, cyber, and strategic risks across the combined entity.

What worked as risk management in Company A might be inadequate for the larger, more complex merged business.

### Policies and procedures are fundamental to risk management

They’re how organisations ensure consistent behaviour and maintain control.

When these procedures are unclear, contradictory, or unknown during integration, risk management falls apart:

- People make decisions without proper authority.
- Controls are bypassed.
- No one quite knows who’s responsible for what.

For example: cybersecurity. Two IT environments must be connected, but each might have different security standards, different access controls, different update procedures. The rush to integrate systems can create vulnerabilities. Clear procedures for how this integration happens, with proper security protocols, are essential.

> In 1996, Daimler-Benz’s acquired Dutch aircraft maker Fokker. Daimler failed to integrate procurement and manufacturing procedures. Different quality control standards and supplier management approaches never harmonised. Daimler shut down Fokker within a year, writing off the entire investment. Procedural conflicts in operational risk management proved fatal to the business.

### Compliance risk multiplies in mergers

The combined entity might now operate across more jurisdictions, in more regulated sectors, with more complex reporting requirements. Leaders who don’t understand these requirements, and don’t have robust procedures to manage them, expose the business to significant penalties and reputational damage.

## Building the integration blueprint

An effective M&A integration blueprint must address policies and procedures with the same rigour applied to financial and legal matters. This requires a systematic, staged approach that brings order to what can otherwise feel like chaos.

### Step 1: Create a record of existing policies and procedures on both sides

Before any integration decisions can be made, you need to know what you’re working with. This sounds obvious, yet many organisations rush into harmonisation without fully understanding what policies and procedures exist across both entities.

Many organisations discover during this inventory process that they have more procedures than they realised. Or that documented policies don’t match actual practice. Or that critical processes have no formal documentation at all.

#### Creating a comprehensive inventory is foundational work

It provides visibility into the operational landscape and prevents critical procedures from being accidentally overlooked or dismantled. This inventory should capture every significant policy and procedure across both organisations.

#### The inventory needs to go beyond simply listing policy names

For each policy and procedure, document several key pieces of information:

- What is the policy or procedure called?
- What function or process does it govern?
- When was it last reviewed or updated?
- What systems or tools does it depend on?
- Are there regulatory or compliance requirements driving it?

#### The inventory must identify the process owner for each policy and procedure

This is the person who understands how it actually works in practice. They’re accountable for its effectiveness. They know its history, its quirks, and its dependencies. The process owner might be a department head, a senior manager, or sometimes a specialist deep in the organisation.

Identifying process owners serves multiple purposes. It ensures accountability during integration. It provides a clear escalation point when conflicts arise. It surfaces the tribal knowledge that exists beyond written documentation. And it helps prevent the common mistake of dismantling procedures that seemed redundant but were actually essential.

#### The inventory should capture which policies and procedures are interconnected

A credit approval procedure might depend on a risk assessment policy. A procurement process might trigger compliance reviews. These dependencies aren’t always obvious, particularly to senior staff unfamiliar with acquired operations. Documenting them prevents breaking critical linkages during integration.

#### Go beyond collecting manuals

It requires understanding the informal practices, workarounds, and tribal knowledge that actually govern how work gets done. The written policy and the lived reality are often quite different.

### Step 2: Create cross-functional integration teams and develop a clear framework for decision-making

Once you have a comprehensive inventory, you need the right people and the right approach to make integration decisions. Cross-functional integration teams bring together the expertise and perspective necessary for sound judgements about policies and procedures.

These teams must include people with deep operational knowledge, not just senior executives. The person who has processed invoices for ten years often understands the procurement workflow better than the VP who approved the policy five years ago.

These teams should be empowered to identify conflicts, evaluate alternatives, and recommend solutions based on actual operational needs rather than organisational politics.

### Develop a clear framework for decision-making about which policies to retain

##### Carry out an inventory

There are typically four options:

- Adopt
  - Choose one organisation’s policy and implement it across the combined entity. This works when one approach is clearly superior or when standardisation is essential.

- Harmonise
  - Blend the best elements from both policies into a new, unified approach. This works when both organisations have valuable practices worth preserving.

- Retire
  - Discontinue a policy that’s no longer necessary or relevant. Mergers often reveal redundant or outdated procedures that can be eliminated.

- Keep as parallel processes
  - Maintain different approaches in different parts of the business. This works when legitimate regional, functional, or business unit differences justify variation.

The framework should specify the criteria for choosing between these options. Consider regulatory compliance, risk management, operational efficiency, customer impact, and cultural fit. Be explicit about the trade-offs. Some decisions prioritise speed over perfection. Others require getting it right even if it takes longer.

The framework must also define who has decision-making authority at each level. Which decisions can integration teams make? Which require senior leadership approval? What’s the escalation path when teams can’t reach consensus? Clear governance prevents paralysis and ensures timely decisions.

### Step 3: Assess the consequences of changing a policy

Before implementing any change, assess its consequences systematically. Changes to policies and procedures create ripple effects throughout the organisation. Understanding these effects before you act prevents unintended damage.

> In 2005, eBay paid $2.6 billion but never successfully integrated Skype into eBay’s marketplace culture. The companies had completely different operational approaches and user bases. eBay’s auction-focused procedures didn’t fit Skype’s telecommunications model. eBay sold Skype for $1.9 billion four years later, taking a substantial loss.

> In 2013, Microsoft paid $7.2 billion for Nokia’s mobile phone business, but the cultures never meshed. Microsoft’s software development approach conflicted with Nokia’s hardware heritage. Different product development procedures and decision-making processes collided. Microsoft wrote off $7.6 billion and eventually exited the mobile phone business entirely.

#### For each proposed change, consider multiple dimensions of impact

What systems or tools will need modification? What training will employees require? How will customers be affected? What compliance or regulatory implications exist? What’s the financial cost of implementation?

#### Consider the human consequences

Perhaps most importantly, the integration blueprint must acknowledge that changing policies and procedures is fundamentally a change management challenge.

It’s not just an administrative one. Every procedure represents someone’s work routine, professional expertise, and sense of competence. Telling employees that their familiar processes are being replaced triggers legitimate anxiety about whether their skills still matter.

- Who will be most affected by this change?
- What skills or expertise might become obsolete?
- How will people’s daily work routines shift?
- What anxieties or resistance might emerge?

These aren’t soft concerns – they directly affect implementation success.

#### Pay particular attention to customer-facing and revenue-generating procedures

This includes:

- How sales teams qualify leads.
- How customer service handles complaints.
- How delivery teams fulfil orders.

These processes directly affect the value proposition that made the acquisition attractive in the first place. Disrupting them without understanding them can destroy value quickly.

#### Assess dependencies and sequencing carefully

Some policies must be resolved before other work can progress:

- You can’t integrate IT systems without agreeing on security procedures.
- You can’t consolidate facilities without harmonising health and safety protocols.

Identify these critical path items to avoid creating bottlenecks.

#### Document the assessment findings clearly

Create a simple impact summary for each proposed change that stakeholders can review and understand.

This becomes the basis for prioritisation and implementation planning.

### Step 4: Prioritise the work and make the changes

Not all policies and procedures need immediate attention. Some can wait. Some need urgent harmonisation. Others might be left separate indefinitely. Prioritisation ensures you focus effort where it matters most.

Several factors should drive prioritisation decisions:

- Risk and compliance
  - Policies governing regulatory compliance, legal obligations, or significant operational risks need immediate review.
  - Data protection procedures, health and safety protocols, anti-money laundering controls, and financial reporting policies can’t be left in limbo. The consequences of getting these wrong are too severe.

- Customer and revenue impact
  - Procedures that directly affect customer experience or revenue generation deserve early attention. Confusion or conflicts in these areas lose customers and cash immediately.

- Financial visibility and control
  - Procedures governing financial reporting, cash management, expenditure approval, and payment processing need immediate harmonisation. Without clear financial procedures, you lose visibility and control at the worst possible time.

- Volume and frequency
  - Procedures used daily by large numbers of people need earlier attention than those used quarterly by specialist teams. High-volume processes create more confusion when unclear. They also offer greater efficiency gains when optimised.
  - Integration dependencies
    - Some policies must be resolved before other integration work can progress. Identify these critical path items and prioritise them accordingly.

#### Once priorities are set, make the changes systematically

Update policy documentation clearly. Ensure version control so everyone knows which version is current. Archive superseded policies but keep them accessible for reference during transition periods.

#### Implement changes in a controlled way

Pilot new procedures with a small group before rolling out organisation-wide. This identifies problems whilst they’re still manageable. It also creates champions who can help with broader implementation.

#### Build implementation capacity carefully

Process owners have day jobs. They can’t spend all their time on integration work. Be realistic about how many changes can be implemented in parallel without degrading normal operations.

The acquired business might already be struggling with uncertainty. Adding excessive change burden makes this worse.

### Step 5: Communicate the change and provide training

Even the best policy changes fail without effective communication and training. People need to understand what’s changing, why it’s changing, and how to work with the new approach.

#### Publish updated policies and procedures in an accessible location and format

Everyone should know where to find current policies. Make them searchable and easy to navigate. Remove or clearly mark superseded versions to prevent confusion.

#### Communication should address multiple audiences with different needs

Senior leaders need high-level summaries of major changes and rationale. Managers need detail on how changes affect their teams and what support is available. Frontline employees need practical guidance on what they should do differently.

#### Explain the “why” behind changes, not just the “what”

People are more willing to adapt when they understand the business rationale. “We’re harmonising expense approval limits to improve financial control and prevent the cash flow problems that nearly bankrupted Company X” is more compelling than “New expense policy effective Monday”.

#### Don’t assume everyone will read the new documents

Provide training appropriate to the complexity and importance of the change. This might be formal classroom training, online modules, team briefings, or one-on-one coaching. Match the approach to the audience and the change.

#### Identify and support the process owners in their role as change agents

They can explain changes to their teams. They can provide context and answer questions. They can identify problems early. Equip them with the materials and authority they need to be effective.

#### Create feedback mechanisms

This is so people can ask questions, report problems, and suggest improvements.

A new procedure that looks perfect on paper might have fatal flaws in practice. Early feedback allows rapid correction before problems multiply.

This is where identified process owners become particularly valuable. They bridge between senior leadership decisions and frontline reality. They can advocate for their people whilst helping implement necessary changes.

### Step 6: Measure, review and iterate

Integration isn’t finished when new policies are published. Effective integration requires ongoing measurement, review, and iteration to ensure changes deliver intended benefits.

#### Define clear success metrics for major policy changes

If you harmonised procurement procedures to reduce costs, measure actual cost savings. If you standardised customer service procedures to improve satisfaction, measure satisfaction scores. Metrics keep teams honest about whether changes are actually working.

Not all outcomes are quantifiable, but all should be observable. Are people actually following the new procedures? Are the predicted problems materialising? Are unexpected issues emerging? Regular check-ins with process owners and their teams surface this information.

#### Establish a review cadence

This must be appropriate to the change’s importance and complexity. Critical policies might need weekly review in the first month. Less critical ones might be reviewed quarterly. The point is to create structured opportunities to assess what’s working and what isn’t.

#### Be willing to iterate

The first version of a harmonised policy rarely gets everything right. You’re learning how the combined organisation actually functions. As you learn, adapt. Sometimes this means refining details. Sometimes it means acknowledging that a parallel process approach would work better than forced standardisation.

#### Document lessons learned systematically

What worked well in integrating procurement procedures? What went wrong with IT security harmonisation? These lessons inform later integration efforts and help other teams avoid repeating mistakes.

#### Pay attention to unintended consequences

A change that solved one problem might have created another. The new expense approval process might have improved control but slowed down business development. These trade-offs need visibility so leadership can make informed adjustments.

#### Remember that real integration takes years, not months

Resist the urge to declare victory after ninety days. Some policies need time to bed in before their true impact becomes clear. Patient, sustained attention yields better results than rushing to completion.

## The human side of procedural change

Throughout this entire blueprint, never lose sight of the human dimension. Changing policies and procedures is fundamentally a change management challenge, not just an administrative one.

Every procedure represents someone’s work routine, professional expertise, and sense of competence. Telling employees that their familiar processes are being replaced triggers legitimate anxiety:

- Will I still be good at my job?
- Will my work still be valued?
- Do I still have a future here?

Effective integration acknowledges these concerns directly. It seeks input from those affected. It recognises that resistance to new procedures often isn’t about stubbornness but about genuine worry. Address the emotional reality alongside the operational details.

#### Leaders must also model the behaviour they expect

When senior executives exempt themselves from new procedures or publicly complain about changes, they undermine the entire integration effort. If the new travel policy is necessary for cost control, executives should follow it too. If the new approval workflow is supposed to improve governance, leaders should use it consistently.

#### Celebrate progress, the successes, and acknowledge effort

Integration work is exhausting. Process owners and integration team members are doing extra work: maintaining normal operations whilst rebuilding how work gets done. Recognition matters.

## Making it work

Successful M&A integration is about thoughtfully creating something new that preserves what worked whilst fixing what didn’t. It doesn’t have to be about imposing one company’s way of doing things on another.

Policies and procedures are the technical infrastructure of organisational culture. They’re where values and priorities become operational reality.

The six-step blueprint provides the structure for this work:

1. Create a comprehensive record of existing policies and procedures
2. Form cross-functional teams and establish a clear decision framework
3. Assess consequences before implementing changes
4. Prioritise systematically and execute changes in a controlled way
5. Communicate effectively and provide appropriate training
6. Measure results, review progress, and iterate continuously

This blueprint transforms an overwhelming challenge into manageable work. It ensures nothing critical falls through the cracks. It brings rigour and discipline to what can otherwise feel like chaos.

The integration blueprint must give this unglamorous work its due. That means adequate time, sufficient resources, and genuine attention from senior leadership. And it means staying humble about what you know and don’t know about how the newly combined organisation actually functions.

The companies that navigate this well don’t just achieve the synergies promised in the deal announcement. They build something genuinely better than what either organisation had before.

Not by accident, but by attending carefully to the detailed, difficult work of integration.

One policy and procedure at a time.

## Cherryleaf can help

Cherryleaf’s expert [policies and procedures writers](https://www.cherryleaf.com/documentation_services/business-document-writing-services/)
 helps create customised documentation that provides staff with a reliable framework to follow.

This reduces ambiguity about responsibilities and expectations, leading to more confidence and control over day-to-day operations.

With clearly written policies as a guide, employees gain the freedom to carry out tasks efficiently.

### Share this:

- [Share on Facebook (Opens in new window) Facebook](https://www.cherryleaf.com/2026/02/ma-integration-blueprint-why-procedures-matter-more-than-you-think/?share=facebook)
- [Share on LinkedIn (Opens in new window) LinkedIn](https://www.cherryleaf.com/2026/02/ma-integration-blueprint-why-procedures-matter-more-than-you-think/?share=linkedin)
- [Share on WhatsApp (Opens in new window) WhatsApp](https://www.cherryleaf.com/2026/02/ma-integration-blueprint-why-procedures-matter-more-than-you-think/?share=jetpack-whatsapp)
- [Share on Bluesky (Opens in new window) Bluesky](https://www.cherryleaf.com/2026/02/ma-integration-blueprint-why-procedures-matter-more-than-you-think/?share=bluesky)
-

### *Related*

### Leave a Reply[Cancel reply](/2026/02/ma-integration-blueprint-why-procedures-matter-more-than-you-think/#respond)

This site uses Akismet to reduce spam. [Learn how your comment data is processed.](https://akismet.com/privacy/)

#### Previous post

[5 reasons why the future of software development is less coding, more documentation](https://www.cherryleaf.com/2026/02/5-reasons-why-the-future-of-software-development-is-less-coding-more-documentation/)

#### Next post

[Indicators that suggest something was written by AI](https://www.cherryleaf.com/2026/02/indicators-that-suggest-something-was-written-by-ai/)

#### Browse posts by month

Browse posts by month Select Month  October 2026 (1)  September 2026 (12)  August 2026 (8)  July 2026 (7)  June 2026 (14)  May 2026 (8)  April 2026 (6)  March 2026 (14)  February 2026 (9)  January 2026 (9)  December 2025 (7)  November 2025 (9)  October 2025 (10)  September 2025 (7)  August 2025 (6)  July 2025 (1)  June 2025 (3)  May 2025 (2)  April 2025 (5)  March 2025 (3)  February 2025 (3)  January 2025 (2)  November 2024 (8)  October 2024 (3)  September 2024 (2)  August 2024 (3)  July 2024 (4)  June 2024 (1)  May 2024 (2)  April 2024 (4)  March 2024 (1)  February 2024 (2)  January 2024 (1)  December 2023 (2)  November 2023 (9)  October 2023 (8)  September 2023 (5)  August 2023 (3)  July 2023 (1)  June 2023 (1)  May 2023 (2)  April 2023 (3)  March 2023 (2)  January 2023 (2)  December 2022 (4)  November 2022 (1)  October 2022 (1)  September 2022 (1)  August 2022 (1)  July 2022 (1)  June 2022 (1)  May 2022 (2)  April 2022 (1)  March 2022 (1)  February 2022 (1)  January 2022 (2)  December 2021 (1)  November 2021 (2)  October 2021 (1)  August 2021 (1)  July 2021 (2)  June 2021 (3)  May 2021 (5)  April 2021 (3)  March 2021 (3)  February 2021 (1)  January 2021 (2)  December 2020 (4)  November 2020 (4)  August 2020 (3)  February 2020 (3)  January 2020 (1)  November 2019 (3)  October 2019 (1)  September 2019 (1)  August 2019 (3)  July 2019 (2)  June 2019 (3)  May 2019 (4)  April 2019 (1)  November 2018 (2)  October 2018 (1)  July 2018 (2)  June 2018 (4)  May 2018 (2)  April 2018 (3)  March 2018 (4)  February 2018 (2)  January 2018 (3)  December 2017 (2)  October 2017 (3)  September 2017 (1)  August 2017 (3)  July 2017 (2)  June 2017 (7)  May 2017 (4)  April 2017 (5)  March 2017 (1)  February 2017 (7)  January 2017 (1)  December 2016 (3)  November 2016 (4)  October 2016 (1)  September 2016 (5)  July 2016 (1)  June 2016 (3)  May 2016 (1)  April 2016 (2)  February 2016 (2)  January 2016 (5)  December 2015 (1)  November 2015 (4)  October 2015 (2)  August 2015 (1)  July 2015 (1)  June 2015 (2)  May 2015 (3)  February 2015 (2)  January 2015 (6)  December 2014 (1)  October 2014 (1)  September 2014 (4)  June 2014 (4)  May 2014 (1)  April 2014 (2)  March 2014 (3)  February 2014 (4)  January 2014 (4)  November 2013 (2)  October 2013 (5)  September 2013 (3)  July 2013 (3)  June 2013 (11)  May 2013 (4)  April 2013 (6)  March 2013 (7)  February 2013 (4)  January 2013 (4)  December 2012 (9)  November 2012 (23)  October 2012 (14)  September 2012 (8)  August 2012 (4)  July 2012 (12)  June 2012 (12)  May 2012 (10)  April 2012 (8)  March 2012 (12)  February 2012 (3)  January 2012 (6)  December 2011 (2)  October 2011 (3)  August 2011 (1)  June 2011 (5)  May 2011 (2)  April 2011 (1)  January 2011 (1)  December 2010 (1)  November 2010 (3)  October 2010 (4)  September 2010 (8)  August 2010 (5)  May 2010 (2)  April 2010 (3)  March 2010 (3)  February 2010 (2)  January 2010 (3)  December 2009 (2)  November 2009 (6)  September 2009 (1)  July 2009 (6)  June 2009 (7)  April 2009 (8)  March 2009 (3)  February 2009 (3)  January 2009 (3)  December 2008 (1)  November 2008 (3)  October 2008 (3)  September 2008 (4)  August 2008 (1)  July 2008 (3)  June 2008 (5)  May 2008 (2)  April 2008 (2)  March 2008 (3)  February 2008 (2)  January 2008 (1)  November 2007 (3)  October 2007 (2)  September 2007 (1)  July 2007 (3)  November 2006 (1)  October 2006 (2)  September 2006 (3)  August 2006 (1)  April 2006 (1)  March 2006 (3)

#### Browse posts by category