OBLYTECH Logo
OBLYTECH Logo
ServiceNow Governance, Risk and Compliance for Professional Services
Home / Guides, Services and Solutions / by Industry / for Professional Services / ServiceNow Governance, Risk and Compliance for Professional Services

ServiceNow Governance, Risk and Compliance for Professional Services

Governance, risk and compliance for a professional services firm is the set of controls, records and reviews that show the firm meets its professional standards on every engagement. The main design choice is keeping firm-wide controls apart from engagement-level obligations.

Governance, Risk and Compliance in a professional services firm has to separate firm-wide controls from engagement-level obligations and keep conflict checking reliable. This page covers professional standards and ethics including conflict of interest programmes, data protection and confidentiality, regulatory auditing, quality assurance and review, where each kind of record should live, an ordered procedure for a new engagement, where conflict checking often breaks, risk ratings that drift, and when formal GRC tooling would outrun the firm’s obligations.

Professional Standards and Ethics

Professional services firms are often required to maintain ethics standards. Accounting firms must comply with accounting standards and ethics codes. Law firms must follow professional responsibility rules. Engineering firms must follow engineering codes of ethics. ServiceNow can track compliance with professional standards: codes of conduct, conflict of interest disclosures, training on ethics and professional responsibility, and incidents or violations.

Firms should implement conflict of interest programs: reviewing client engagements to ensure no conflicts of interest exist, disclosing conflicts where they cannot be avoided, and documenting conflict waivers when clients approve. ServiceNow can automate conflict checking: before an engagement starts, the system checks for conflicts between the client and the firm’s other clients or consultants.

Data Protection and Confidentiality

Professional services firms handle sensitive client data: financial information, technical details, strategic plans. Data protection and confidentiality are critical. Firms must comply with client contracts, applicable laws (like GDPR for European clients), and professional standards. ServiceNow can track data handling requirements by engagement and client, and enforce data protection controls across the firm.

Confidentiality breaches are serious. A firm that inadvertently discloses a client’s information faces liability and reputational damage. Firms should maintain strict data protection practices: limiting access to client data, encrypting sensitive data, and training staff on confidentiality. ServiceNow can help enforce these practices through access controls and audit logging.

Regulatory and Compliance Auditing

Professional services firms are audited by regulatory bodies and professional organizations. Accounting firms are audited by accounting regulatory bodies. Law firms are audited by bar associations. Auditors examine compliance with standards, ethics, and client service requirements. ServiceNow provides audit-ready documentation: engagement records, compliance assessments, training records, and incident documentation. Firms that maintain strong documentation usually pass audits with few findings.

Quality Assurance and Review

Professional services firms implement quality assurance programs: reviewing consultant work before delivering it to clients, checking for compliance with standards, and assessing the quality of the deliverable. ServiceNow can track quality reviews: documenting that the review occurred, who performed it, any issues found, and remediation. This demonstrates to regulators and clients that the firm maintains quality standards.

Challenges in Professional Services GRC

One challenge is the variability of engagements. Each client engagement is different; standard compliance procedures might not fit all engagements. GRC programs must be flexible enough to accommodate diverse engagements while maintaining minimum standards. ServiceNow should provide a framework that allows customization for engagement-specific requirements.

Another challenge is consultant resistance to compliance procedures. Consultants focus on delivering client value; compliance might feel like overhead. Firms should emphasize that compliance protects the firm and the client, and integrate compliance into engagement processes (not as an afterthought) to reduce friction.

Engagement Compliance Checklist

A typical engagement compliance checklist might include: conflict of interest check, engagement letter review, compliance requirements identification, confidentiality and data protection setup, required approvals and sign-offs, quality review procedures, documentation requirements, and post-engagement review and closeout. ServiceNow can automate these tasks, ensuring consistent compliance across engagements.

Separating firm-wide controls from engagement-level obligations

A risk or compliance lead at a professional services firm is responsible for two different kinds of control at once. Some controls apply to the firm itself, such as how staff handle confidential information, how conflicts are declared and how training is recorded. Others apply to one client engagement, such as the data handling rules a client wrote into a statement of work or the review a regulated client expects before a deliverable leaves the building. When these are stored in the same list with the same owner, the engagement rules get lost and the firm-wide rules get diluted. Keeping the two apart is the first design decision, and it is easier to make now than to unpick later.

This section is for risk, compliance and operations leaders in consulting, engineering and accounting firms. It assumes the firm already has a list of its professional obligations and a basic risk register. It addresses how to structure the GRC records so that they can be tested, evidenced and reported without rebuilding them for each audit. The governance, risk and compliance guide is the reference for the general model, and the policy and compliance management guide covers the policy side that feeds these records.

Where each kind of record should live

Record Scope Owner Review trigger
Professional conduct policy and training Firm-wide Compliance lead Annual policy review or a material change in standards
Conflict of interest declaration Individual and engagement Engagement partner Each new engagement and each new affiliate or client relationship
Client data handling obligations Engagement Engagement manager Each change to the statement of work
Engagement risk rating Engagement Risk lead, approved by a partner Scope change, new data type or new regulated sector
Quality review evidence Engagement Reviewer named on the record Each deliverable milestone

The reviewer on the quality review record should not be the author of the work. That sounds obvious, but it is the first thing an external auditor checks, and a record that shows the same person as author and reviewer tends to lead to a finding even when the review was genuine.

An ordered procedure for a new engagement

  1. Run the conflict check against the full client hierarchy, including parent companies, subsidiaries and known affiliates, before any engagement letter is drafted.
  2. Record the client’s data handling obligations as discrete items, each with a source reference in the signed contract, rather than as a general note.
  3. Assign an engagement risk rating using the firm’s criteria and have a partner approve it. Record the reasons for the rating, not only the rating itself.
  4. Set the review points the engagement needs, and name the reviewer for each one. A review point without a name is not a control.
  5. At closeout, confirm that the data handling obligations were met or closed out with the client, and retain the evidence against the engagement record.

Where conflict checking often breaks

A frequent weakness is a conflict check that matches on legal names only. A client that trades under a brand, or a holding company whose subsidiary is the real counterparty, will pass the check and still create a conflict. Maintain the hierarchy as a set of linked records rather than a flat list, and require the engagement team to confirm the ultimate parent before the check is recorded as complete.

A second weakness is a check that runs once, at proposal stage, and never again. A conflict that arises when a second client acquires the first one is missed unless someone reruns the check on a schedule. Set the rerun against events that change the hierarchy, such as a reported merger, and against a periodic review of the active client list.

Risk ratings that drift

Engagement risk ratings tend to rise when a project runs into trouble and fall back when it recovers. Neither movement is recorded as a decision, so the register stops explaining the firm’s exposure. Keep the original rating and add each change as a dated entry with the reason. An auditor who asks why an engagement was rated low at the start and high at the end will then get an answer from the record.

When formal GRC tooling would outrun the firm’s obligations

A firm with a few engagements a year, a single regulated client and a partner group that reads every contract may be better served by a controlled spreadsheet with clear ownership. The formal model earns its cost when the same obligations repeat across many engagements and the firm must show, on request, that each one was checked. It also earns its cost when conflicts arise across offices, because a shared hierarchy is hard to keep in separate files.

Frequently asked questions about compliance in professional services

Can a firm rely on the client’s own compliance certificate for its engagement obligations?

Not on its own. A certificate describes the client’s position, while the firm’s obligations depend on what the firm does with the client’s data and systems. Record the certificate as one input, then record the firm’s own controls and the evidence for them.

Who should approve a conflict waiver when a client agrees to it?

The firm’s designated conflicts or risk partner, not the engagement partner who wants the work. The waiver should be stored with the client’s written consent and the scope it covers. A waiver with no defined scope is hard to defend later, because nobody can say which work it permitted.

How should a regulator’s new expectation be added to the register?

As a new obligation record with its own owner, a start date and a list of engagements it affects. Do not overwrite an existing control, because the earlier evidence may still be needed for work completed before the change.

What evidence convinces an auditor that quality review happened?

A record showing the reviewer’s name, the date, the items reviewed, the findings and how each finding was closed. A tick box on a checklist does not show that a review took place. The record should be complete enough that someone who was not on the engagement can follow the chain.

Frequently asked questions

What compliance standards apply to professional services firms?

Compliance depends on the profession and jurisdictions served. Accounting firms follow accounting standards and auditing standards. Law firms follow professional responsibility rules. Consulting firms might follow industry-specific standards if they work in regulated industries. All firms should comply with data protection laws and professional ethics codes. ServiceNow can track standards applicable to the firm and verify compliance.

How do professional services firms manage conflicts of interest?

Firms maintain a conflicts register identifying all clients and major customers, then before taking on a new engagement, they check whether any firm members have relationships that might create conflicts. Conflicts are documented and disclosed to clients when necessary. Some conflicts can be managed through information barriers or independence procedures. ServiceNow can automate conflict checking.

What are the consequences of compliance failures in professional services?

Consequences vary by profession and jurisdiction but can include: professional discipline, loss of license or certification, civil litigation and damages, regulatory penalties, and reputational damage. Maintaining strong compliance programs and documentation helps prevent failures and provides defense if questions arise. ServiceNow records demonstrating compliance help protect the firm.

Talk to Oblytech

Planning, running or fixing a ServiceNow programme? Tell us where you are and we will suggest a sensible next step.

Contact us