Import an Existing Restaurant SOP Library Without Starting Over
A restaurant that already has good, current SOPs should not have to rewrite them just to use Gravity. Foundry can be used as the control, training, revision, publishing, and employee-access system around procedures the restaurant already trusts.
Four valid starting paths
- Use Gravity masters. Customize the 525 controlled starting procedures.
- Import your existing SOPs. Bring in the restaurant's current library and manage it through Gravity controls.
- Create a blank SOP. Type a new procedure directly.
- Use a mix. Keep strong existing SOPs and use Gravity masters where gaps exist.
What import does—and does not do
Import creates a working Draft. It does not approve, publish, certify, or declare the procedure correct. Managers still review the actual restaurant process, choose the training requirement, approve the revision, and deliberately publish it.
Supported intake
Gravity handles structured/text formats such as Gravity transfer/JSON, CSV, TSV, TXT, RTF, HTML, DOCX, XLSX, ZIP/folder batches, and copy/paste. PDF, legacy XLS, and image formats can enter the Review Intake, but managers must confirm or transcribe the procedure before saving because visual/document extraction should not be treated as infallible.
Duplicate handling
When an imported title/station appears to match an existing working SOP, choose deliberately: Skip, Replace matching working copy, or Keep both. Replacing a controlled working SOP should preserve revision history rather than silently destroying the prior version.
The control path
Upload → Extract/Map → Review → Save as Draft → Manager Review → Approve → Publish → Train/acknowledge as required.