What we need from your company

How to use this worksheet

Complete this worksheet with your Bridgewerks implementation lead before technical configuration begins. It gives both teams one shared record of the decisions, owners, and source systems needed for a successful launch.

You do not need every answer on day one. Mark an owner for anything still open and agree on a decision date.

Share credentials only through the secure method provided by your implementation lead. Never put passwords, application secrets, access tokens, or private keys in this worksheet, email, a deal note, or a support message.

Company and implementation owners

Item	What to provide
Company identity	Legal company name, customer-facing name, primary office location, and website domain
Executive sponsor	Name and email of the person accountable for the implementation
Implementation owner	Day-to-day decision maker and primary Bridgewerks contact
IT owner	Identity, email, security, and connected-system administrator
Security or compliance owner	Contact for security review, retention, DPA, and access-control decisions
Workflow owners	Leads for originations, underwriting, closing, servicing, and finance
Support contact	Person who will coordinate questions and incidents after launch
Target dates	Configuration start, user acceptance testing, training, and go-live dates

Workspace and access

• Approved company name, logo files, accent color, and default time zone.
• Email domains that should be allowed to sign in.
• Preferred identity provider: Microsoft Entra ID or Google.
• Initial administrator and user list, including each person's email and business role.
• Any access restrictions, separation-of-duties requirements, or required approval steps.
• Joiner, role-change, and offboarding owners.

Deal intake and communications

• The shared mailbox or email alias that receives broker opportunities.
• The person authorized to create and test an email-forwarding rule.
• Which messages should become deals and which should remain outside Bridgewerks.
• Preferred collaboration system: Slack, Microsoft Teams, or neither.
• For Slack, the workspace administrator and proposed channels for deal updates, approvals, tasks, closings, and support.
• Escalation rules for urgent deals, approvals, and production issues.

Data and documents

• Current systems of record for deals, contacts, loans, tasks, and documents.
• Sample exports or templates from your loan origination system, CRM, spreadsheets, or file shares.
• Initial active deals and loans to load, including the agreed historical cutoff date.
• Capital sources, credit criteria, routing rules, and approval roles.
• Standard LOI, teaser, IC memo, underwriting, and reporting templates.
• Data owner for duplicate resolution and final reconciliation.
• Document retention, deletion, data residency, and legal-hold requirements.

Future integration planning

Tell the implementation team about these needs now so they can be included in your rollout plan:

• SharePoint sites or libraries that may become approved knowledge sources, including each site owner.
• Microsoft Teams channels and workflows that should eventually mirror Slack-style notifications or actions.
• Excel users, operating systems, security restrictions, and a proposed pilot group for the Bridgewerks Excel add-in.

SharePoint knowledge sync, full Microsoft Teams workflows, and the Excel add-in are planning inputs—not generally available setup steps in this help center. Your implementation lead will confirm availability and scope before including any of them in a launch plan.

Security and commercial readiness

• Required security questionnaire, vendor-risk, insurance, and procurement contacts.
• DPA, retention, breach-notification, and audit-log requirements.
• Approved support channel and named people who may authorize configuration changes.
• Training audiences and any required internal operating procedures.

Next: Follow the implementation checklist.