Engagement workspaces, proposal libraries and reusable know-how: SharePoint for professional services firms

Why does a shared drive stop working for a firm that sells expertise?

Because a folder records where a file was saved, not what it is. A proposal, a statement of work and a final deliverable for the same client sit in different trees, nobody can filter by service line or outcome, and the best past work is found only by asking the person who wrote it, if they still work there.

The setup we are asked to fix usually looks alike. There is a drive with a folder per client and another per year, proposals saved in partners’ OneDrive folders, an SOW template that exists in four slightly different copies, client files arriving as email attachments, and a “knowledge” folder nobody has opened since it was created. The work is turning the things the firm already talks about — the client, the engagement, the proposal, the template — into objects the platform understands. In SharePoint that means attributes held as columns and managed metadata from the term store (opens in new tab) rather than words typed into folder names. Our guide to SharePoint folders versus metadata explains the trade-off in more detail.

Which firm documents belong where in SharePoint?

Each document type gets a home matched to how it is looked up and who may see it. Engagement files are found by client and engagement code, proposals by sector and outcome, templates by type, know-how by topic. The table below is the map we scope against, including what we route to a dedicated build.

How is an engagement workspace set up so every project starts the same way?

From one approved template. When an engagement is won, the same structure is created each time: a site or library with the agreed folders kept to a minimum, client and engagement code as required columns, a lead and a status, the team’s permissions, and a shared area for the client if one is needed.

Whether an engagement gets its own site or a library inside a practice site is a scoping decision, not a preference. A long engagement with a client team, several workstreams and guest access usually earns a site; a firm running hundreds of short engagements a year is better served by one library per practice with a document set per engagement. Creation runs from a short request form through Power Automate, so nobody builds a workspace by hand and none are skipped. If your PSA or CRM already marks an opportunity as won, we check during scoping whether a supported connector can start the same flow; if it cannot, the request form stays.

How do proposals and templates stop being copied from last year’s file?

By giving them one governed home. Past proposals and statements of work sit in a library tagged by client sector, service line, year and outcome, so a partner filters for won proposals in a sector instead of hunting. Current templates live in a separate library with an owner, and only the approved version is published.

Two details decide whether people actually use it. First, templates should appear where people start work: SharePoint’s organization assets library can surface approved templates inside Word and PowerPoint where your licenses include that feature, which we confirm during scoping. Second, a change to a template or a proposal above an agreed size should go to a named reviewer rather than straight to the client. Microsoft’s approval workflow documentation (opens in new tab) covers the patterns we use, from a single approver to sequential partner review; each decision, approver and timestamp is written back to the document.

How does a firm reuse know-how without exposing client work?

By separating the engagement record from the reusable lesson. Client files stay in a workspace only the engagement team can open. When work is worth reusing, a reviewer copies a sanitized version into a firm know-how library, tags it by topic and service line, and names an owner who keeps it current.

Search in Microsoft 365 respects permissions, so a consultant searching for a pricing model or a method finds the reviewed know-how version and never sees the confidential original unless they were on that engagement. That separation is what lets the firm share its best thinking without breaking client confidentiality. A firm whose main problem is know-how rather than engagement files — experts nobody can find, methods that exist only in someone’s head — is better served by our SharePoint knowledge management consulting, which builds the knowledge base itself in more depth.

How do clients exchange files with the firm without email attachments?

Through a sharing boundary per engagement: a shared library that only that client’s named contacts and your engagement team can reach, with guest sign-in under the client’s own identity, access that expires, and an audit record of every upload. Files arrive in the right engagement with the right code attached, instead of in somebody’s inbox.

SharePoint controls external sharing at the organization level and then per site, and a site can never be more permissive than the tenant; Microsoft’s external sharing overview (opens in new tab) explains the levels. We set link defaults that do not silently create anonymous links, expiry on guest access, and a short list of which sites may share externally at all. A plain caveat: a configured exchange area is not a branded client portal with billing and e-signature built in; firms that need those features out of the box may still choose a portal product.

What happens to an engagement’s files when the work closes?

Closing becomes a configured step rather than a filing habit. When an engagement is marked complete, guest access ends, the workspace drops to read-only for most staff, a retention label is applied, and the retention period your firm has chosen starts from that point. Nothing is deleted early, and nothing is kept forever by accident.

Microsoft’s documentation on retention policies and labels (opens in new tab) explains how a label keeps content for a set period, deletes it afterwards, or both. Which retention features your licenses include is part of the scoping check. This is configuration work, not legal advice: your firm decides what its schedule says, with its own advisers where client contracts or professional rules apply, and we build the tenant so that decision is enforced.

Should a law firm, accounting practice or design firm start somewhere else?

Often, yes. Law firms and accounting practices share the engagement pattern on this page but add requirements of their own, such as conflict walls, legal hold and the tax-year cycle, so each has a dedicated build. Engineering and architecture practices that run project document control alongside contractors often fit the construction build better.

• Law firms: matter files, ethical walls and legal hold are covered by our SharePoint consultant for law firms engagement, and the firm-facing front door by our SharePoint intranet for law firms.
• Accounting and CPA firms: the client-and-tax-year structure, seasonal access and engagement-close retention are covered by our SharePoint consultant for accounting firms build.
• Engineering and architecture practices: drawing sets, RFIs, transmittals and closeout are covered by our SharePoint document control for construction and design teams build.
• Everyone else who sells expertise by the engagement — management and IT consultancies, agencies, advisory, HR and recruitment firms — starts here. All of these are specialised versions of our wider SharePoint consulting.

What does the engagement cover?

Three shapes cover most requests from professional services firms. Every fee is fixed and put in writing after your free consultation — the table shows scope and typical timeline, because an honest number needs to see your service lines, your current shared drive and your license position first. Our fixed-fee process explains how the number is set.

Whatever the shape, you own everything: the libraries, the flows, the metadata, the intranet and the documentation stay in your Microsoft tenant from the first day, and nothing we build depends on us to keep running.

Which professional services firms is this a good fit for?

Consultancies, agencies, advisory and engineering practices of 20 to 500 people, paying for Microsoft 365 and running engagements off shared drives, personal OneDrive folders and inbox attachments. The usual trigger is a proposal rebuilt from scratch because nobody could find the last one, a client asking how their files are protected, or a partner leaving with the firm’s best work.

It fits badly when a PSA or document platform already holds every engagement file and the team genuinely uses it; adding SharePoint beside it only creates a second place to look. Large firms with many offices, several tenants or complex integration needs usually need a bigger partner than a fixed-fee build. We work with firms in all US states remotely from our Orange County, CA base.