Skip to main content
DigitalSanctum.
Menu
Workflow improvement

Repeated data entry

Enter it once.
Use it where it’s needed.

A repair request, customer order or new-client form can set off work in several places. Explore how checked information could move between them with less repeated handling.

Three small-business examples

One request. Several places to update.

Choose an example to explore. Each comparison follows the same request and keeps the same business systems. See where repeated handling can disappear and independent work can move together.

01Plumbing: a property maintenance work orderA property manager emails a repair request.

The request: A property manager emails a PDF work order for a non-urgent repair at a rental property. It includes the property address, onsite contact, work-order reference and access instructions.

Before: repeated handling

Pass it on.
Type it again.

Each handoff needs someone to move the details.

Work-order inboxPerson
Read email and PDF

Read the email and PDF. Find the address, contacts and reference.

Job recordPerson
Re-enter request details

Type the property, job and contact details into the job system.

Dispatch calendarPerson
Copy address and arrange visit

Copy the address and instructions while arranging a visit.

Technician’s job cardPerson
Forward instructions; chase updates

Send the instructions separately and chase notes or photos afterwards.

The technician completes the job.

Collect the time, materials and completion notes before billing.

Accounting invoicePerson
Re-enter completion and billing

Gather the completion details and re-enter billing information.

Read the manual steps
  1. Work-order inbox.Read the email and PDF. Find the address, contacts and reference.
  2. Job record.Type the property, job and contact details into the job system.
  3. Dispatch calendar.Copy the address and instructions while arranging a visit.
  4. Technician’s job card.Send the instructions separately and chase notes or photos afterwards.
  5. Accounting invoice.Gather the completion details and re-enter billing information.

After: shared details, parallel preparation

Check once.
Move work together.

Reuse checked details. Prepare independent work together. Keep the decisions that matter.

Work-order inboxOriginal request
Job recordPerson
Check the shared details

Check the property, contact, work requested and billing details once.

PropertyContactsWork-order ref
Prepared in parallel

After the request details are checked

Dispatch calendarPerson
Arrange the visit

Confirm the plumber’s availability and property access.

Technician’s job cardLinked
Prepare the job pack

Reuse the checked address, instructions and work-order reference.

Booking confirmed. Job pack ready.

The technician completes the work and adds time, materials, notes and photos.

Accounting invoicePerson
Review the invoice

Prepare it from the completed job, then review before issue.

One linked job, from request to reviewed invoice.

Repeated work this design removes
  • Re-entering the property address
  • Forwarding the same job instructions
  • Re-typing the work-order reference
Read the improved steps
  1. Keep the original request.Preserve the incoming details and attachments.
  2. Check the shared details.Check the property, contact, work requested and billing details once.
  3. Prepare independent work in parallel.Arrange the visit: Confirm the plumber’s availability and property access. Prepare the job pack: Reuse the checked address, instructions and work-order reference.
  4. Booking confirmed. Job pack ready.The technician completes the work and adds time, materials, notes and photos.
  5. Review the invoice.Prepare it from the completed job, then review before issue.
Carry the property, contact and work-order details forward. Add the technician’s findings as the work progresses. Independent preparation runs in parallel; completion, permissions and approvals still control when later work can proceed.
When a person needs to step in.

Missing access details, unclear billing instructions or extra work outside the agreed scope go back to a person.

Flow reference diagrams

Explore the process.

Compare the same request and business systems. These diagrams are illustrative and do not run a process. What can be connected depends on your tools, permissions and checks.

Open the full before and after reference →

Manual handoffs: static diagram and text

Approved unpublished draft 354516da-a6a0-4cee-8b25-80b54b4bcf59. Source BPMN SHA-256: 875ce81bf891458b43efd3c96f414e40de7e2ade84a74806cee0a66250554d31. Reference BPMN SHA-256: e01c38f9f0dc4bf52dad01f5bd07e917ece1330ea4b7295c82d9d6cb131daddd. Native publication findings remain recorded on the full reference.

Manual handoffs BPMN overview; its activities and connections are listed below.

Open the full-size overview · Download BPMN snapshot

Collaboration_1: activities and connections
  • Work order received (start, Work-order inbox)
  • Request not proceeding (end, Job record)
  • Copy details and arrange visit (person's task, Dispatch calendar)
  • Copy job instructions (person's task, Technician’s job card)
  • Re-enter completion and billing details (person's task, Accounting invoice)
  • Issue reviewed invoice (person's task, Accounting invoice)
  • Work order invoiced (end, Accounting invoice)
  • Review original request (detailed phase, Job record)
  • Ready to proceed? (decision, Job record)
  • Review billing evidence (detailed phase, Accounting invoice)
  • Complete authorised repair (detailed phase, Technician’s job card)
  • Checked property, contacts and work-order reference (information)
  • Completed job evidence (information)
  • Work order received → Review original request
  • Copy details and arrange visit → Copy job instructions
  • Copy job instructions → Complete authorised repair
  • Re-enter completion and billing details → Review billing evidence
  • Issue reviewed invoice → Work order invoiced
  • Review original request → Ready to proceed?
  • Ready to proceed? → Request not proceeding: Not confirmed
  • Ready to proceed? → Copy details and arrange visit: Confirmed
  • Review billing evidence → Issue reviewed invoice
  • Complete authorised repair → Re-enter completion and billing details
  • Property manager → Work order received: Original request
  • Re-enter completion and billing details uses Completed job evidence
  • Review original request creates Checked property, contacts and work-order reference
  • Complete authorised repair creates Completed job evidence
Review original request: activities and connections
  • Phase started (start, Job record)
  • Read request and re-enter details (person's task, Job record)
  • Request usable? (decision, Job record)
  • Clarify request with sender (person's task, Job record)
  • Proceed with clarified request? (decision, Job record)
  • exclusiveGateway (request-ready) (decision, Job record)
  • Needs owner decision (end, Job record)
  • Phase ready (end, Job record)
  • Phase started → Read request and re-enter details
  • Read request and re-enter details → Request usable?
  • Request usable? → exclusiveGateway (request-ready): Usable
  • Request usable? → Clarify request with sender: Needs review
  • Clarify request with sender → Proceed with clarified request?
  • Proceed with clarified request? → exclusiveGateway (request-ready): Confirmed
  • Proceed with clarified request? → Needs owner decision: Not confirmed
  • exclusiveGateway (request-ready) → Phase ready

Open this full-size phase diagram

Review billing evidence: activities and connections
  • Phase started (start, Accounting invoice)
  • Review completed-job invoice (person's task, Accounting invoice)
  • Details usable? (decision, Accounting invoice)
  • Clarify missing or changed details (person's task, Accounting invoice)
  • exclusiveGateway (billing-review-merge) (decision, Accounting invoice)
  • Phase ready (end, Accounting invoice)
  • Phase started → Review completed-job invoice
  • Review completed-job invoice → Details usable?
  • Details usable? → exclusiveGateway (billing-review-merge): Usable
  • Details usable? → Clarify missing or changed details: Clarification needed
  • Clarify missing or changed details → exclusiveGateway (billing-review-merge)
  • exclusiveGateway (billing-review-merge) → Phase ready

Open this full-size phase diagram

Complete authorised repair: activities and connections
  • Phase started (start, Technician’s job card)
  • Inspect repair requirement (manual task, Technician’s job card)
  • Within agreed scope? (decision, Technician’s job card)
  • Review and agree extra work (person's task, Job record)
  • exclusiveGateway (scope-merge) (decision, Technician’s job card)
  • Complete authorised field work (manual task, Technician’s job card)
  • Record completion evidence (person's task, Technician’s job card)
  • Phase ready (end, Technician’s job card)
  • Phase started → Inspect repair requirement
  • Inspect repair requirement → Within agreed scope?
  • Within agreed scope? → exclusiveGateway (scope-merge): Within scope
  • Within agreed scope? → Review and agree extra work: Extra work
  • Review and agree extra work → exclusiveGateway (scope-merge)
  • exclusiveGateway (scope-merge) → Complete authorised field work
  • Complete authorised field work → Record completion evidence
  • Record completion evidence → Phase ready

Open this full-size phase diagram

Connected handoffs: static diagram and text

Approved unpublished draft c9352b44-cb08-4f17-8822-c3b8f643c060. Source BPMN SHA-256: 5fae05b85282bf8202649d1286cc2d10c4393106350a03a86be5ed142989c827. Reference BPMN SHA-256: d0f1732e67c4066567046a97e1596e2ff5331cab68251126028d549dd134dc18. Native publication findings remain recorded on the full reference.

Connected handoffs BPMN overview; its activities and connections are listed below.

Open the full-size overview · Download BPMN snapshot

Collaboration_1: activities and connections
  • Work order received (start, Work-order inbox)
  • Request not proceeding (end, Job record)
  • Arrange access and visit (person's task, Dispatch calendar)
  • Prepare linked job pack (proposed system task, Technician’s job card)
  • parallelGateway (prepare-fork) (parallel split or join, Job record)
  • parallelGateway (prepare-join) (parallel split or join, Technician’s job card)
  • Prepare invoice from completed job (proposed system task, Accounting invoice)
  • Issue reviewed invoice (person's task, Accounting invoice)
  • Work order invoiced (end, Accounting invoice)
  • Review original request (detailed phase, Job record)
  • Ready to proceed? (decision, Job record)
  • Review billing evidence (detailed phase, Accounting invoice)
  • Complete authorised repair (detailed phase, Technician’s job card)
  • Checked property, contacts and work-order reference (information)
  • Completed job evidence (information)
  • Work order received → Review original request
  • Arrange access and visit → parallelGateway (prepare-join)
  • Prepare linked job pack → parallelGateway (prepare-join)
  • parallelGateway (prepare-fork) → Arrange access and visit
  • parallelGateway (prepare-fork) → Prepare linked job pack
  • parallelGateway (prepare-join) → Complete authorised repair
  • Prepare invoice from completed job → Review billing evidence
  • Issue reviewed invoice → Work order invoiced
  • Review original request → Ready to proceed?
  • Ready to proceed? → Request not proceeding: Not confirmed
  • Ready to proceed? → parallelGateway (prepare-fork): Confirmed
  • Review billing evidence → Issue reviewed invoice
  • Complete authorised repair → Prepare invoice from completed job
  • Property manager → Work order received: Original request
  • Arrange access and visit uses Checked property, contacts and work-order reference
  • Prepare linked job pack uses Checked property, contacts and work-order reference
  • Prepare invoice from completed job uses Completed job evidence
  • Review original request creates Checked property, contacts and work-order reference
  • Complete authorised repair creates Completed job evidence
Review original request: activities and connections
  • Phase started (start, Job record)
  • Check shared request details (person's task, Job record)
  • Request usable? (decision, Job record)
  • Clarify request with sender (person's task, Job record)
  • Proceed with clarified request? (decision, Job record)
  • exclusiveGateway (request-ready) (decision, Job record)
  • Needs owner decision (end, Job record)
  • Phase ready (end, Job record)
  • Phase started → Check shared request details
  • Check shared request details → Request usable?
  • Request usable? → exclusiveGateway (request-ready): Usable
  • Request usable? → Clarify request with sender: Needs review
  • Clarify request with sender → Proceed with clarified request?
  • Proceed with clarified request? → exclusiveGateway (request-ready): Confirmed
  • Proceed with clarified request? → Needs owner decision: Not confirmed
  • exclusiveGateway (request-ready) → Phase ready

Open this full-size phase diagram

Review billing evidence: activities and connections
  • Phase started (start, Accounting invoice)
  • Review completed-job invoice (person's task, Accounting invoice)
  • Details usable? (decision, Accounting invoice)
  • Clarify missing or changed details (person's task, Accounting invoice)
  • exclusiveGateway (billing-review-merge) (decision, Accounting invoice)
  • Phase ready (end, Accounting invoice)
  • Phase started → Review completed-job invoice
  • Review completed-job invoice → Details usable?
  • Details usable? → exclusiveGateway (billing-review-merge): Usable
  • Details usable? → Clarify missing or changed details: Clarification needed
  • Clarify missing or changed details → exclusiveGateway (billing-review-merge)
  • exclusiveGateway (billing-review-merge) → Phase ready

Open this full-size phase diagram

Complete authorised repair: activities and connections
  • Phase started (start, Technician’s job card)
  • Inspect repair requirement (manual task, Technician’s job card)
  • Within agreed scope? (decision, Technician’s job card)
  • Review and agree extra work (person's task, Job record)
  • exclusiveGateway (scope-merge) (decision, Technician’s job card)
  • Complete authorised field work (manual task, Technician’s job card)
  • Record completion evidence (person's task, Technician’s job card)
  • Phase ready (end, Technician’s job card)
  • Phase started → Inspect repair requirement
  • Inspect repair requirement → Within agreed scope?
  • Within agreed scope? → exclusiveGateway (scope-merge): Within scope
  • Within agreed scope? → Review and agree extra work: Extra work
  • Review and agree extra work → exclusiveGateway (scope-merge)
  • exclusiveGateway (scope-merge) → Complete authorised field work
  • Complete authorised field work → Record completion evidence
  • Record completion evidence → Phase ready

Open this full-size phase diagram

02Wholesale: a customer purchase orderAn existing customer emails an order for stock.

The request: An existing customer emails a purchase order for several products, with item codes, quantities, a delivery address and their order reference.

Before: repeated handling

Pass it on.
Type it again.

Each handoff needs someone to move the details.

Customer-order inboxPerson
Read the purchase order

Read the purchase order and find the customer, items and delivery details.

Sales orderPerson
Retype item codes and quantities

Re-enter the customer, item codes, quantities and prices.

Stock and pick listPerson
Check stock; copy picking details

Check stock separately and write or copy a picking list.

The order is picked and packed.

Confirm stock and final package details before dispatch.

Courier bookingPerson
Retype delivery details

Retype the delivery address and package details into the courier system.

Accounting invoicePerson
Re-enter approved order lines

Re-enter the approved order lines and customer reference for billing.

Read the manual steps
  1. Customer-order inbox.Read the purchase order and find the customer, items and delivery details.
  2. Sales order.Re-enter the customer, item codes, quantities and prices.
  3. Stock and pick list.Check stock separately and write or copy a picking list.
  4. Courier booking.Retype the delivery address and package details into the courier system.
  5. Accounting invoice.Re-enter the approved order lines and customer reference for billing.

After: shared details, parallel preparation

Check once.
Move work together.

Reuse checked details. Prepare independent work together. Keep the decisions that matter.

Customer-order inboxOriginal request
Sales orderPerson
Check the shared details

Check the customer, item codes, quantities and agreed prices once.

CustomerOrder linesDelivery address
Prepared in parallel

After the request details are checked

Stock and pick listPerson
Check stock and prepare picking

Use the checked order lines. Resolve shortages before fulfilment.

Accounting invoiceLinked
Prepare invoice details

Reuse the approved order lines and customer reference. Keep it as a draft.

Stock confirmed. Order packed. Billing reviewed.

Dispatch waits for picking, packing and billing review.

Courier bookingPerson
Confirm dispatch

Pass the checked address and final package details to the courier booking when ready.

Ready to dispatch, with the order and paperwork linked.

Repeated work this design removes
  • Re-keying approved item codes
  • Copying the order reference into billing
  • Re-typing the delivery address
Read the improved steps
  1. Keep the original request.Preserve the incoming details and attachments.
  2. Check the shared details.Check the customer, item codes, quantities and agreed prices once.
  3. Prepare independent work in parallel.Check stock and prepare picking: Use the checked order lines. Resolve shortages before fulfilment. Prepare invoice details: Reuse the approved order lines and customer reference. Keep it as a draft.
  4. Stock confirmed. Order packed. Billing reviewed.Dispatch waits for picking, packing and billing review.
  5. Confirm dispatch.Pass the checked address and final package details to the courier booking when ready.
Reuse checked order lines and delivery details from sales through fulfilment and invoicing. Keep stock and dispatch decisions visible. Independent preparation runs in parallel; completion, permissions and approvals still control when later work can proceed.
When a person needs to step in.

Unknown item codes, stock shortages, changed prices or unclear delivery instructions need a person’s decision.

Flow reference diagrams

Explore the process.

Compare the same request and business systems. These diagrams are illustrative and do not run a process. What can be connected depends on your tools, permissions and checks.

Open the full before and after reference →

Manual handoffs: static diagram and text

Approved unpublished draft 77cdc330-633e-4a92-93b5-74393310f1cc. Source BPMN SHA-256: ba327e7088564e4b1481b2d477889793d8041ec1a51377b07c5482afdadc9183. Reference BPMN SHA-256: 667ea67c5c180425f4c76c1b3c63a68ac4014220e3f7b36b5365111c7518e562. Native publication findings remain recorded on the full reference.

Manual handoffs BPMN overview; its activities and connections are listed below.

Open the full-size overview · Download BPMN snapshot

Collaboration_1: activities and connections
  • Purchase order received (start, Customer-order inbox)
  • Request not proceeding (end, Sales order)
  • Check stock and prepare picking (person's task, Stock and pick list)
  • Stock and order confirmed? (decision, Stock and pick list)
  • Resolve shortage or order discrepancy (person's task, Stock and pick list)
  • exclusiveGateway (stock-merge) (decision, Stock and pick list)
  • Pick, pack and record details (manual task, Stock and pick list)
  • Re-enter approved order lines for billing (person's task, Accounting invoice)
  • Retype courier booking details (person's task, Courier booking)
  • Confirm dispatch readiness (person's task, Courier booking)
  • Ready for dispatch (end, Courier booking)
  • Review original request (detailed phase, Sales order)
  • Ready to proceed? (decision, Sales order)
  • Review billing evidence (detailed phase, Accounting invoice)
  • Reviewed order lines and delivery details (information)
  • Purchase order received → Review original request
  • Check stock and prepare picking → Stock and order confirmed?
  • Stock and order confirmed? → exclusiveGateway (stock-merge): Confirmed
  • Stock and order confirmed? → Resolve shortage or order discrepancy: Needs decision
  • Resolve shortage or order discrepancy → exclusiveGateway (stock-merge)
  • exclusiveGateway (stock-merge) → Pick, pack and record details
  • Pick, pack and record details → Retype courier booking details
  • Re-enter approved order lines for billing → Review billing evidence
  • Retype courier booking details → Re-enter approved order lines for billing
  • Confirm dispatch readiness → Ready for dispatch
  • Review original request → Ready to proceed?
  • Ready to proceed? → Request not proceeding: Not confirmed
  • Ready to proceed? → Check stock and prepare picking: Confirmed
  • Review billing evidence → Confirm dispatch readiness
  • Customer → Purchase order received: Original request
  • Review original request creates Reviewed order lines and delivery details
Review original request: activities and connections
  • Phase started (start, Sales order)
  • Read request and re-enter details (person's task, Sales order)
  • Request usable? (decision, Sales order)
  • Clarify request with sender (person's task, Sales order)
  • Proceed with clarified request? (decision, Sales order)
  • exclusiveGateway (request-ready) (decision, Sales order)
  • Needs owner decision (end, Sales order)
  • Phase ready (end, Sales order)
  • Phase started → Read request and re-enter details
  • Read request and re-enter details → Request usable?
  • Request usable? → exclusiveGateway (request-ready): Usable
  • Request usable? → Clarify request with sender: Needs review
  • Clarify request with sender → Proceed with clarified request?
  • Proceed with clarified request? → exclusiveGateway (request-ready): Confirmed
  • Proceed with clarified request? → Needs owner decision: Not confirmed
  • exclusiveGateway (request-ready) → Phase ready

Open this full-size phase diagram

Review billing evidence: activities and connections
  • Phase started (start, Accounting invoice)
  • Review final packed-order billing (person's task, Accounting invoice)
  • Details usable? (decision, Accounting invoice)
  • Clarify missing or changed details (person's task, Accounting invoice)
  • exclusiveGateway (billing-review-merge) (decision, Accounting invoice)
  • Phase ready (end, Accounting invoice)
  • Phase started → Review final packed-order billing
  • Review final packed-order billing → Details usable?
  • Details usable? → exclusiveGateway (billing-review-merge): Usable
  • Details usable? → Clarify missing or changed details: Clarification needed
  • Clarify missing or changed details → exclusiveGateway (billing-review-merge)
  • exclusiveGateway (billing-review-merge) → Phase ready

Open this full-size phase diagram

Connected handoffs: static diagram and text

Approved unpublished draft 0dcca3d9-2dba-4de5-9b8a-6ccecad87f45. Source BPMN SHA-256: dde0976f12df31686e5b5ec6d39cc70023a4f83f84023cd7284a009af86721dd. Reference BPMN SHA-256: aa2be65a6c9092ad15d88d9b62510c103a02297e2ea7c9ef199c050951e3782a. Native publication findings remain recorded on the full reference.

Connected handoffs BPMN overview; its activities and connections are listed below.

Open the full-size overview · Download BPMN snapshot

Collaboration_1: activities and connections
  • Purchase order received (start, Customer-order inbox)
  • Request not proceeding (end, Sales order)
  • Check stock and prepare picking (person's task, Stock and pick list)
  • Stock and order confirmed? (decision, Stock and pick list)
  • Resolve shortage or order discrepancy (person's task, Stock and pick list)
  • exclusiveGateway (stock-merge) (decision, Stock and pick list)
  • Pick, pack and record details (manual task, Stock and pick list)
  • Prepare linked invoice draft (proposed system task, Accounting invoice)
  • Prepare courier booking (proposed system task, Courier booking)
  • parallelGateway (prepare-fork) (parallel split or join, Sales order)
  • parallelGateway (prepare-join) (parallel split or join, Sales order)
  • Confirm dispatch readiness (person's task, Courier booking)
  • Ready for dispatch (end, Courier booking)
  • Review original request (detailed phase, Sales order)
  • Ready to proceed? (decision, Sales order)
  • Review billing evidence (detailed phase, Accounting invoice)
  • Reviewed order lines and delivery details (information)
  • Purchase order received → Review original request
  • Check stock and prepare picking → Stock and order confirmed?
  • Stock and order confirmed? → exclusiveGateway (stock-merge): Confirmed
  • Stock and order confirmed? → Resolve shortage or order discrepancy: Needs decision
  • Resolve shortage or order discrepancy → exclusiveGateway (stock-merge)
  • exclusiveGateway (stock-merge) → Pick, pack and record details
  • Pick, pack and record details → parallelGateway (prepare-join)
  • Prepare linked invoice draft → parallelGateway (prepare-join)
  • Prepare courier booking → Confirm dispatch readiness
  • parallelGateway (prepare-fork) → Check stock and prepare picking
  • parallelGateway (prepare-fork) → Prepare linked invoice draft
  • parallelGateway (prepare-join) → Review billing evidence
  • Confirm dispatch readiness → Ready for dispatch
  • Review original request → Ready to proceed?
  • Ready to proceed? → Request not proceeding: Not confirmed
  • Ready to proceed? → parallelGateway (prepare-fork): Confirmed
  • Review billing evidence → Prepare courier booking
  • Customer → Purchase order received: Original request
  • Check stock and prepare picking uses Reviewed order lines and delivery details
  • Prepare linked invoice draft uses Reviewed order lines and delivery details
  • Review original request creates Reviewed order lines and delivery details
Review original request: activities and connections
  • Phase started (start, Sales order)
  • Check shared request details (person's task, Sales order)
  • Request usable? (decision, Sales order)
  • Clarify request with sender (person's task, Sales order)
  • Proceed with clarified request? (decision, Sales order)
  • exclusiveGateway (request-ready) (decision, Sales order)
  • Needs owner decision (end, Sales order)
  • Phase ready (end, Sales order)
  • Phase started → Check shared request details
  • Check shared request details → Request usable?
  • Request usable? → exclusiveGateway (request-ready): Usable
  • Request usable? → Clarify request with sender: Needs review
  • Clarify request with sender → Proceed with clarified request?
  • Proceed with clarified request? → exclusiveGateway (request-ready): Confirmed
  • Proceed with clarified request? → Needs owner decision: Not confirmed
  • exclusiveGateway (request-ready) → Phase ready

Open this full-size phase diagram

Review billing evidence: activities and connections
  • Phase started (start, Accounting invoice)
  • Review final packed-order billing (person's task, Accounting invoice)
  • Details usable? (decision, Accounting invoice)
  • Clarify missing or changed details (person's task, Accounting invoice)
  • exclusiveGateway (billing-review-merge) (decision, Accounting invoice)
  • Phase ready (end, Accounting invoice)
  • Phase started → Review final packed-order billing
  • Review final packed-order billing → Details usable?
  • Details usable? → exclusiveGateway (billing-review-merge): Usable
  • Details usable? → Clarify missing or changed details: Clarification needed
  • Clarify missing or changed details → exclusiveGateway (billing-review-merge)
  • exclusiveGateway (billing-review-merge) → Phase ready

Open this full-size phase diagram

03Accounting: onboarding a new business clientA prospective client submits their business details.

The request: A prospective bookkeeping client submits an intake form with their business name, contact details, existing software and the services they want to discuss.

Before: repeated handling

Pass it on.
Type it again.

Each handoff needs someone to move the details.

Client-intake formPerson
Read the submitted details

Read the submission and follow up any missing business details.

Practice client recordPerson
Retype business and contact details

Re-enter the business and contact details into the practice system.

Engagement letterPerson
Copy details into a draft letter

Copy details into a letter and assemble the proposed services.

The engagement is agreed.

Confirm the scope before preparing document requests and onboarding work.

Document workspacePerson
Create folders and document requests

Create a folder, prepare a document list and send separate requests.

Onboarding task boardPerson
Copy the agreed scope into tasks

Copy the agreed work into tasks, assign people and chase missing items.

Read the manual steps
  1. Client-intake form.Read the submission and follow up any missing business details.
  2. Practice client record.Re-enter the business and contact details into the practice system.
  3. Engagement letter.Copy details into a letter and assemble the proposed services.
  4. Document workspace.Create a folder, prepare a document list and send separate requests.
  5. Onboarding task board.Copy the agreed work into tasks, assign people and chase missing items.

After: shared details, parallel preparation

Check once.
Move work together.

Reuse checked details. Prepare independent work together. Keep the decisions that matter.

Client-intake formOriginal request
Practice client recordPerson
Check the shared details

Check the business, contact details and requested services once.

BusinessContactsRequested services
Engagement letterPerson
Agree the engagement

Prepare the letter from checked details. A person reviews the services and agrees the scope.

Prepared in parallel

Once the engagement is agreed

Document workspaceLinked
Prepare document requests

Create the workspace and checklist for the agreed services.

Onboarding task boardLinked
Prepare onboarding tasks

Create linked tasks and assign the agreed work from the same scope.

Documents and permissions checked.

A person follows up missing information and confirms access before dependent work begins.

Onboarding prepared, with requests and work kept together.

Repeated work this design removes
  • Re-typing business contact details
  • Rebuilding the same folder checklist
  • Copying the agreed scope into separate task lists
Read the improved steps
  1. Keep the original request.Preserve the incoming details and attachments.
  2. Check the shared details.Check the business, contact details and requested services once.
  3. Agree the engagement.Prepare the letter from checked details. A person reviews the services and agrees the scope.
  4. Prepare independent work in parallel.Prepare document requests: Create the workspace and checklist for the agreed services. Prepare onboarding tasks: Create linked tasks and assign the agreed work from the same scope.
  5. Documents and permissions checked.A person follows up missing information and confirms access before dependent work begins.
Reuse the agreed business and contact details while preparing the engagement, document requests and onboarding work. Independent preparation runs in parallel; completion, permissions and approvals still control when later work can proceed.
When a person needs to step in.

Unclear services, incomplete details, missing permissions or a changed scope stay with the practice for review.

Flow reference diagrams

Explore the process.

Compare the same request and business systems. These diagrams are illustrative and do not run a process. What can be connected depends on your tools, permissions and checks.

Open the full before and after reference →

Manual handoffs: static diagram and text

Approved unpublished draft b235a665-5a68-4a49-b1fd-d064fd5feec2. Source BPMN SHA-256: 0881109b7b72bb37d9c1ccb33df6ae98b79975172190677c0225aa9dab00e944. Reference BPMN SHA-256: d2ab2443356225824e44bafd9793b905dc976b7bc44039831cd7e024918a7013. Native publication findings remain recorded on the full reference.

Manual handoffs BPMN overview; its activities and connections are listed below.

Open the full-size overview · Download BPMN snapshot

Collaboration_1: activities and connections
  • Intake submitted (start, Client-intake form)
  • Request not proceeding (end, Practice client record)
  • Engagement not agreed (end, Engagement letter)
  • Create folders and requests (person's task, Document workspace)
  • Copy scope into task board (person's task, Onboarding task board)
  • Confirm onboarding prepared (person's task, Onboarding task board)
  • Onboarding prepared (end, Onboarding task board)
  • Review original request (detailed phase, Practice client record)
  • Ready to proceed? (decision, Practice client record)
  • Agree engagement (detailed phase, Engagement letter)
  • Ready to proceed? (decision, Engagement letter)
  • Confirm documents and access (detailed phase, Document workspace)
  • Agreed business details and engagement scope (information)
  • Intake submitted → Review original request
  • Create folders and requests → Copy scope into task board
  • Copy scope into task board → Confirm documents and access
  • Confirm onboarding prepared → Onboarding prepared
  • Review original request → Ready to proceed?
  • Ready to proceed? → Request not proceeding: Not confirmed
  • Ready to proceed? → Agree engagement: Confirmed
  • Agree engagement → Ready to proceed?
  • Ready to proceed? → Engagement not agreed: Not confirmed
  • Ready to proceed? → Create folders and requests: Confirmed
  • Confirm documents and access → Confirm onboarding prepared
  • Prospective client → Intake submitted: Original request
  • Agree engagement creates Agreed business details and engagement scope
Review original request: activities and connections
  • Phase started (start, Practice client record)
  • Read request and re-enter details (person's task, Practice client record)
  • Request usable? (decision, Practice client record)
  • Clarify request with sender (person's task, Practice client record)
  • Proceed with clarified request? (decision, Practice client record)
  • exclusiveGateway (request-ready) (decision, Practice client record)
  • Needs owner decision (end, Practice client record)
  • Phase ready (end, Practice client record)
  • Phase started → Read request and re-enter details
  • Read request and re-enter details → Request usable?
  • Request usable? → exclusiveGateway (request-ready): Usable
  • Request usable? → Clarify request with sender: Needs review
  • Clarify request with sender → Proceed with clarified request?
  • Proceed with clarified request? → exclusiveGateway (request-ready): Confirmed
  • Proceed with clarified request? → Needs owner decision: Not confirmed
  • exclusiveGateway (request-ready) → Phase ready

Open this full-size phase diagram

Agree engagement: activities and connections
  • Phase started (start, Engagement letter)
  • Prepare engagement letter (person's task, Engagement letter)
  • Agree engagement scope (person's task, Engagement letter)
  • Engagement agreed? (decision, Engagement letter)
  • Clarify services and proposed scope (person's task, Engagement letter)
  • Agreement now confirmed? (decision, Engagement letter)
  • exclusiveGateway (agreement-merge) (decision, Engagement letter)
  • Needs owner decision (end, Engagement letter)
  • Phase ready (end, Engagement letter)
  • Phase started → Prepare engagement letter
  • Prepare engagement letter → Agree engagement scope
  • Agree engagement scope → Engagement agreed?
  • Engagement agreed? → exclusiveGateway (agreement-merge): Agreed
  • Engagement agreed? → Clarify services and proposed scope: Needs clarification
  • Clarify services and proposed scope → Agreement now confirmed?
  • Agreement now confirmed? → exclusiveGateway (agreement-merge): Confirmed
  • Agreement now confirmed? → Needs owner decision: Not confirmed
  • exclusiveGateway (agreement-merge) → Phase ready

Open this full-size phase diagram

Confirm documents and access: activities and connections
  • Phase started (start, Document workspace)
  • Check documents and permissions (person's task, Document workspace)
  • Details usable? (decision, Document workspace)
  • Clarify missing or changed details (person's task, Document workspace)
  • exclusiveGateway (access-review-merge) (decision, Document workspace)
  • Phase ready (end, Document workspace)
  • Phase started → Check documents and permissions
  • Check documents and permissions → Details usable?
  • Details usable? → exclusiveGateway (access-review-merge): Usable
  • Details usable? → Clarify missing or changed details: Clarification needed
  • Clarify missing or changed details → exclusiveGateway (access-review-merge)
  • exclusiveGateway (access-review-merge) → Phase ready

Open this full-size phase diagram

Connected handoffs: static diagram and text

Approved unpublished draft faed99c9-1000-495d-93f9-bac512740b3f. Source BPMN SHA-256: 3fc02439130c46d62141a7eb8f3b4fe1b241093b2f95a9bed1aa2d230d7282f3. Reference BPMN SHA-256: 3b4d4019dd11b8883ea96756ff715e9e39d5b0f18cad883b9effb8af6bba6538. Native publication findings remain recorded on the full reference.

Connected handoffs BPMN overview; its activities and connections are listed below.

Open the full-size overview · Download BPMN snapshot

Collaboration_1: activities and connections
  • Intake submitted (start, Client-intake form)
  • Request not proceeding (end, Practice client record)
  • Engagement not agreed (end, Engagement letter)
  • Prepare workspace and requests (proposed system task, Document workspace)
  • Prepare onboarding tasks (proposed system task, Onboarding task board)
  • parallelGateway (prepare-fork) (parallel split or join, Engagement letter)
  • parallelGateway (prepare-join) (parallel split or join, Onboarding task board)
  • Confirm onboarding prepared (person's task, Onboarding task board)
  • Onboarding prepared (end, Onboarding task board)
  • Review original request (detailed phase, Practice client record)
  • Ready to proceed? (decision, Practice client record)
  • Agree engagement (detailed phase, Engagement letter)
  • Ready to proceed? (decision, Engagement letter)
  • Confirm documents and access (detailed phase, Document workspace)
  • Agreed business details and engagement scope (information)
  • Intake submitted → Review original request
  • Prepare workspace and requests → parallelGateway (prepare-join)
  • Prepare onboarding tasks → parallelGateway (prepare-join)
  • parallelGateway (prepare-fork) → Prepare workspace and requests
  • parallelGateway (prepare-fork) → Prepare onboarding tasks
  • parallelGateway (prepare-join) → Confirm documents and access
  • Confirm onboarding prepared → Onboarding prepared
  • Review original request → Ready to proceed?
  • Ready to proceed? → Request not proceeding: Not confirmed
  • Ready to proceed? → Agree engagement: Confirmed
  • Agree engagement → Ready to proceed?
  • Ready to proceed? → Engagement not agreed: Not confirmed
  • Ready to proceed? → parallelGateway (prepare-fork): Confirmed
  • Confirm documents and access → Confirm onboarding prepared
  • Prospective client → Intake submitted: Original request
  • Prepare workspace and requests uses Agreed business details and engagement scope
  • Prepare onboarding tasks uses Agreed business details and engagement scope
  • Agree engagement creates Agreed business details and engagement scope
Review original request: activities and connections
  • Phase started (start, Practice client record)
  • Check shared request details (person's task, Practice client record)
  • Request usable? (decision, Practice client record)
  • Clarify request with sender (person's task, Practice client record)
  • Proceed with clarified request? (decision, Practice client record)
  • exclusiveGateway (request-ready) (decision, Practice client record)
  • Needs owner decision (end, Practice client record)
  • Phase ready (end, Practice client record)
  • Phase started → Check shared request details
  • Check shared request details → Request usable?
  • Request usable? → exclusiveGateway (request-ready): Usable
  • Request usable? → Clarify request with sender: Needs review
  • Clarify request with sender → Proceed with clarified request?
  • Proceed with clarified request? → exclusiveGateway (request-ready): Confirmed
  • Proceed with clarified request? → Needs owner decision: Not confirmed
  • exclusiveGateway (request-ready) → Phase ready

Open this full-size phase diagram

Agree engagement: activities and connections
  • Phase started (start, Engagement letter)
  • Prepare engagement letter (proposed system task, Engagement letter)
  • Agree engagement scope (person's task, Engagement letter)
  • Engagement agreed? (decision, Engagement letter)
  • Clarify services and proposed scope (person's task, Engagement letter)
  • Agreement now confirmed? (decision, Engagement letter)
  • exclusiveGateway (agreement-merge) (decision, Engagement letter)
  • Needs owner decision (end, Engagement letter)
  • Phase ready (end, Engagement letter)
  • Phase started → Prepare engagement letter
  • Prepare engagement letter → Agree engagement scope
  • Agree engagement scope → Engagement agreed?
  • Engagement agreed? → exclusiveGateway (agreement-merge): Agreed
  • Engagement agreed? → Clarify services and proposed scope: Needs clarification
  • Clarify services and proposed scope → Agreement now confirmed?
  • Agreement now confirmed? → exclusiveGateway (agreement-merge): Confirmed
  • Agreement now confirmed? → Needs owner decision: Not confirmed
  • exclusiveGateway (agreement-merge) → Phase ready

Open this full-size phase diagram

Confirm documents and access: activities and connections
  • Phase started (start, Document workspace)
  • Check documents and permissions (person's task, Document workspace)
  • Details usable? (decision, Document workspace)
  • Clarify missing or changed details (person's task, Document workspace)
  • exclusiveGateway (access-review-merge) (decision, Document workspace)
  • Phase ready (end, Document workspace)
  • Phase started → Check documents and permissions
  • Check documents and permissions → Details usable?
  • Details usable? → exclusiveGateway (access-review-merge): Usable
  • Details usable? → Clarify missing or changed details: Clarification needed
  • Clarify missing or changed details → exclusiveGateway (access-review-merge)
  • exclusiveGateway (access-review-merge) → Phase ready

Open this full-size phase diagram

These are illustrative workflows, not client results or live integrations. What can be connected depends on your software, permissions and required checks. Start with the recurring handoffs that take the most effort in your business.

Choose the simplest useful change

You may already have part of the answer.

Remove an unnecessary step.

Does the spreadsheet serve a useful purpose, or is the same information already available in your business app? Start by checking what you still need.

Use the tools you have.

Your existing apps may support shared records, imports or a connection. Check what they can do before adding another subscription or building software.

Build a focused connection.

If there is a gap, a small integration or form could help information move between tools. Agree the scope, permissions and maintenance before building it.

Start with your work

Bring one example. We can work through it together.

If you still use spreadsheets alongside newer apps, start with one recurring process and tell Peter what you have already tried. He can discuss what your tools support, whether a focused change is practical, and the scope and cost of any proposed work.

  1. 01

    Show where the copying happens.

    Describe the task, the tools involved and who uses the information. Start with a description and leave out passwords or confidential client details.

  2. 02

    Discuss what could change.

    Peter can help you consider which steps are needed, what your existing tools support and where a connection might be useful.

  3. 03

    Agree a practical next step.

    If there is useful work to do, discuss the scope before deciding whether to proceed. An enquiry does not commit you to a project.

Tell Peter about your example

Where are you entering
the same details twice?

Peter Reginald

Peter personally reviews your message and replies by email to understand the problem and arrange a conversation if useful.

Tell Peter about repeated data entry

Digital Sanctum knowledge base

Search Digital Sanctum

Find services, processes, products, case studies, and strategic intelligence in the site index.

Type at least two characters to search the knowledge base.