Sharing client records
Start with the operating question. Share records only after Michael and your business agree on the fields, safeguards, and transfer location.
Start with a business overview
Use the inquiry form or business email to describe your restaurant, the operating question, and the periods or locations involved. Keep that introduction brief. The website and ordinary email are not the agreed intake channels for financial records.
Prepare the approved inputs
The standard scopes can use sales and transaction totals, labor hours and costs grouped by role or daypart, food and operating cost summaries, and redacted supplier records. The final input list depends on the signed scope. Share only records you have authority to provide, covering the agreed fields, locations, and dates.
Remove bank and card details, passwords, SSNs, government identifiers, employee identifiers, guest contact details, health information, and records about minors. Personal payroll, individual performance records, guest profiles, and regulated consumer financial records are outside standard intake. A need for those records requires a separate signed, counsel-reviewed scope and safeguards before transfer.
Small groups, distinctive purchases, and persistent IDs can reveal a person's identity. Review the summaries with Michael before transfer if their anonymity is uncertain.
Confirm the transfer arrangements
Before requesting records, Michael and your business must complete the engagement agreement and data protection schedule. They must name the approved transfer and storage services, people with access, permitted uses, retention dates, and any direct system access.
Michael must verify the agreed controls with the chosen tools before intake begins. He will then provide the approved transfer instructions. Do not send master credentials or substitute a public sharing link. Direct access, if agreed, is read-only, time-limited, and confined to approved aggregate report views.
Keep changes within the scope
If a new location, period, field, tool, or use becomes necessary, agree on the change before sending the additional records. Restricted fields or views need the required separate amendment and safeguards first. If an unexpected restricted record arrives, Michael must pause its use and seek instructions.
Close the engagement
Agree on the return or deletion event before intake. At closeout, Michael follows the signed schedule, removes access, and records active-copy deletion and any lawful retention or provider-backup limits.
Read the data protection overview for the engagement principles, the privacy notice for website information, and privacy requests to raise a concern.