Work Assignment status
Mobile users can update Work Assignment status directly in IFS Mobile Work Order.
For operations and business teams
The workflow question is whether keeping a work-order reference, site, and job description together gives operations and field teams a clearer handoff. Spindlewick’s current subscriber workflow validates those three details and saves a result for review.
Looking for the broader context? Explore the IFS workflow landing page.
Assessing pilot fit? Read the customer pilot-fit guide.
IFS status behavior
The pilot-discovery guide distinguishes the status mobile users control from the task status that can follow it automatically.
Mobile users can update Work Assignment status directly in IFS Mobile Work Order.
Work Task status cannot be updated directly in mobile. It may update automatically as a result of changes to Work Assignment status.
Pilot discovery readiness
Use this assessment aid to separate documented IFS concepts from the environment, team, device, data, ownership, handoff, and success details your team still needs to confirm. It is published from the same readiness source as the downloadable checklist.
Documented findings
When a Work Order Task is transferred to a mobile user, that user should have access to the task site through Sites per User. A Pool Task synchronizes to resources that have access to its task site [1].
Work Assignments and Pool Tasks are created in IFS Cloud and transferred to mobile users. Mobile users update Work Assignment status; Work Task status is not updated directly in mobile and may change automatically as a result [1][4].
The mobile app works online and offline, but some features are online-only. The supplied assessment also documents an Integration Log that records completion states and supports offline execution [1].
Mobile Integrations can launch third-party apps or web pages from the Home screen or a Task Action. Mandatory integrations can require an expected return parameter and value before task completion; the Allow User to Skip Integration Validation setting controls whether that requirement is hard or soft [1].
Open questions
Open question: which IFS tenant, enabled modules, and release configuration will the pilot use? The supplied assessment does not establish these environment details.
Confirmation needed: has an IFS administrator configured and activated the mobile workflow, site access, workflow rules, and any mandatory integrations for the target environment?
Confirmation needed: which technicians, resources, resource groups, and team owner will participate, and are the resources set up as active Mobile Users with the required company connections?
Confirmation needed: which pilot sites and tasks are in scope, and do participating users have the required Sites per User and, where applicable, Task User Access Group access?
Confirmation needed: which supported devices and OS versions will be used, where are the coverage gaps, and how will charging, authentication, camera/GPS needs, security, and offline recovery be tested?
Confirmation needed: are the customer, site, asset, technician, job-type, open-work-order, Mobile Part Basic Data, assortment, and other records needed for synchronization current and complete?
Confirmation needed: which tasks move to named technicians or a common pool, who owns a pooled task after acceptance, and who handles status or handoff decisions while the assignment is on mobile?
Confirmation needed: what integration names, endpoints, methods, payloads, expected return values, authentication mode, credentials, and administrator activation apply in the target environment?
Confirmation needed: who supports technicians and administrators, who owns recovery after a connectivity gap or failed handoff, and what escalation path applies during the pilot?
Confirmation needed: which representative jobs, field conditions, readiness sign-off, handoffs, and team-defined measures will determine whether the pilot is ready for a broader rollout?
Request details
The supported request surface is organized around three inputs. Capturing them clearly helps a team evaluate the adjacent workflow without implying an external IFS action.
01
Required. Keep the request tied to the work order reference used by the operations team.
Up to 100 characters
02
Required. Record the site where the work will take place.
Up to 200 characters
03
Required. Describe the work and include relevant constraints or operating context.
Up to 5,000 characters
Self-reported baseline
Enter the measures your team uses today. These are user-provided starting points for your own review—not IFS benchmarks, predictions, or savings estimates.
Use the same definitions and time window your team normally uses. Leave a measure blank when it is not available yet; this worksheet does not calculate an outcome or send anything to IFS.
minutes per work order
Average time from work start to repair completion.
percent
Your current productive-time measure for technicians.
percent
The share of work orders currently meeting your SLA.
minutes per work order
Average travel time associated with a work order.
minutes per work order
Time your team currently spends coordinating a work order.
percent
The share of work orders resolved without a repeat visit.
minutes per work order
Time spent on work-order administration outside the repair itself.
Your entries are self-reported and remain in this page while you use it. They do not create, update, or submit an IFS record.
Proposed workflow
The repetitive work Spindlewick proposes to simplify is the handoff between operations and the field: keeping the work item, instructions, progress, and time-reporting context together as it moves through the workflow.
01
Native IFS context
Native IFS Task Pool and Work Assignment concepts provide the context for getting a mobile task to the right resource.
Proposed Spindlewick workflow
Spindlewick's proposal keeps the work order reference, site, and description together at the start of the handoff, so the recipient does not have to reassemble those details across screens.
02
Native IFS context
Native IFS mobile work is where an assigned task is carried into field execution by the technician or other mobile worker.
Proposed Spindlewick workflow
Spindlewick proposes a clearer, repeatable handoff and instruction path for that field task. Today's surface does not execute the task in IFS.
03
Native IFS context
Native IFS uses status and progress as work advances. The documented mandatory integration-validation context can also require validation before a task is completed.
Proposed Spindlewick workflow
The proposal makes current progress and the next handoff explicit, while the current surface writes no status back to IFS.
04
Native IFS context
Native IFS time reporting records the time associated with the work task after field work is performed.
Proposed Spindlewick workflow
The proposal keeps time-reporting context attached to the work item to reduce repeated entry. The current surface does not submit time to IFS.
Buyer-fit lens
Use this as a general field-service evaluation lens. The supplied IFS material describes product capabilities and administrator setup, but it does not document an IFS-specific approval authority or decision hierarchy.
Business owners, operations or service managers, office leaders, and dispatchers can test whether the proposed handoff reflects the work they need to coordinate.
Technicians, field workers, dispatchers, coordinators, and office staff should weigh in because they would use the workflow and carry its information through the day.
IT or IFS administrators, finance, and compliance stakeholders can surface access, configuration, integration, cost, security, and recordkeeping prerequisites early.
Check connectivity and offline conditions, supported iOS or Android devices, and whether field workers can understand and complete the workflow without paper workarounds.
Define what the work record must carry, such as clear notes, photos, videos, signatures, and other evidence needed by the office or customer.
Clarify the existing CMMS and IFS context, synchronization expectations, site access, user access groups, administrator setup, and any configuration prerequisites.
Ask where appointment reminders, customer communication channels, or missed appointments create friction; the supplied IFS customer research highlights these as practical evaluation questions.
Before drawing conclusions, record the current baseline for travel time, scheduling effort, first-time-fix rate, and administrative time per work order.
Reference mapping
This table is a reference to the completed MVP specification only. It does not indicate a live IFS integration, synchronization, work-order creation, or work-order update.
| First-job input | Specification-supported IFS entity or parameter | Detail |
|---|---|---|
| Work order reference | Unknown | Required; up to 100 characters. The exact IFS target is not present in this checkout. |
| Site | Unknown | Required; up to 200 characters; the existing workflow treats this as a site label, not a URL. |
| Work description | Unknown | Required; up to 5,000 characters. The exact IFS target is not present in this checkout. |
Documentation boundary
The points below summarize general IFS product and documentation requirements. They are not evidence that Spindlewick has configured, activated, or connected an external IFS account; this page makes no external IFS request.
In IFS Workflow Configuration, administrators define mandatory integrations that must be completed before a task can be completed.
Each mandatory integration needs an expected return parameter name and value. IFS uses Status / Submitted as an example; that is a documentation example, not a Spindlewick configuration.
Allow User to Skip Integration Validation can permit a technician to confirm the required action manually. When disabled, task completion remains blocked until the mandatory integrations are complete.
Defining Mobile Integrations requires administrator access in IFS. This page does not establish that an administrator has configured or activated anything for Spindlewick.
IFS REST task configurations are environment-specific. Imported workflow configurations can be incomplete when required environment values are not imported; the target environment must supply them before use. URL and method are required task fields, while the required values and credentials for this app are not supplied.
The exact mandatory integration name, expected parameter pair, endpoint, HTTP method and payload, authentication mode and credentials or configuration keys, target environment, administrator activation state, and any external IFS account connection to Spindlewick are not established.
Documentation sources
These official IFS pages describe general product requirements and configuration concepts; they do not confirm a Spindlewick integration:
A compact guide to the completed IFS Mobile Work-Order readiness checklist, documented mobile behavior, and the boundary of Spindlewick’s adjacent workflow.
Recovery context: IFS documents that a stale metadata cache can return HTTP 503 with MI_MODIFIED_ERROR. After the cache refreshes, the same request can be retried. That source-backed condition informs the subscriber guide; it does not mean this page has a connected IFS adapter. Read the IFS metadata cache documentation.
Workflow-needs feedback
Share the handoff, visibility, status, synchronization, or field-execution friction your team is working through. This feedback form is separate from pilot discovery; you can submit it without an account or an email address.
Pilot discovery interest
If your team wants to discuss whether this workflow could fit your IFS work-order process, share a few details below. We will only follow up when you opt in. This starts a conversation to coordinate pilot details; it does not define scope, duration, or capabilities.
Subscriber workflow
An authenticated account with an active subscription can open the submission experience. A valid run validates all three fields and saves the completed first-job result for the initiating member. It does not change IFS records. Review subscription options if you need access; pricing terms are still being finalized.