A field crew almost always knows more about the site than someone looking at the plan from behind a desk. While maintaining green areas, a worker may notice a damaged bench. During waste collection, the crew may find an overturned bin or an illegal dumping site. During an inspection, they may come across a tree that needs to be removed, a new piece of infrastructure, or an obstacle that prevents the planned work from being carried out as instructed.
The problem is not noticing these things. It begins a moment later, when the information has to get back to the person managing the plan. Most often it returns by phone, as a photo sent through a messenger, or as a note passed on at the end of the day. The photo is accompanied by a description such as “by the gate near the car park”, “past the second entrance” or “next to the large tree on the street side”.
For the person standing there, such a description is obvious. For a coordinator managing several crews and dozens of locations, it may not be. Someone has to open the map, identify the probable location, re-enter the report, save the photo and connect all this information into something that can later be used to commission work. Sometimes that works, sometimes another phone call is needed, and sometimes the report remains in the message history and no one returns to it.
What is missing from the plan usually stays on someone’s phone
A work plan describes well what is known before the crew goes out. It shows areas scheduled for mowing, waste collection points, infrastructure that needs inspection, or places where specific tasks have been planned. It cannot, however, predict everything workers will find when they arrive.
That is why information from the field is valuable. Someone who walks through a park every day, services successive streets or works across a large site naturally becomes a source of knowledge about its current condition. Without an established way to collect that knowledge, however, a parallel flow of information develops outside the actual plan.
A photo of a damaged bench remains in a messenger, the location is described in a message, and the name of the person who reported it later has to be reconstructed from the conversation history. If the issue is not transferred immediately to the proper register, after a few days it can be difficult to determine whether anyone has already dealt with it. It is worse when the description of the location is insufficient and the site has to be verified during another visit.
The cost of this gap is therefore not limited to additional administrative work. Sometimes it means a second trip solely to determine where a photo was taken. Just as importantly, once the issue has been resolved, there is often no organised record showing what was found, where it was located and who first reported it.
A field report can become part of the plan immediately
Until now, the natural direction of work with a plan has mainly been from the coordinator to the contractor. The person managing the work prepared the scope, marked locations on the map and then shared the view needed to carry out the assignment. Information from the field returned through a different channel.
In PlanPlace, the same shared plan can now also carry information in the opposite direction. The coordinator still sends the contractor a password-protected link, but the settings for that particular share can allow new objects to be added. Permission is granted separately for each contractor and can be withdrawn at any time.
This matters because the ability to add to the plan does not have to be opened to everyone who receives access. One contractor may be allowed to submit field reports while another uses only the plan prepared by the client. The coordinator therefore retains control over who can add new information to the plan.
The location comes from where the contractor is actually standing
The most troublesome part of field reporting is usually not the description of the problem but its location. A photo may clearly show a damaged bin or an obstacle on a route, yet often says nothing about where it was taken. Manually placing a point on a small phone screen would also leave room for error, especially across a large site.
For that reason, an object added by a contractor is not positioned by tapping the map. Its position comes from the current location signal of the reporting person’s phone. PlanPlace uses a GPS reading no more than two minutes old, so the point is created where the contractor is standing rather than where they remember standing some time earlier.
This constraint is intentional. In contractor-led field inventory, the value of a report lies precisely in the fact that the information is created on site. The location is not reconstructed later from memory, a message or a photograph, but comes from the place where the person reporting the object was present.
The coordinator sees the report as soon as it is created
In a traditional information flow, several hours or even days may pass between finding a problem and seeing it on the correct map. The contractor first has to send the information, someone on the client side has to read it, and then the details have to be re-entered into the tool where the plan is maintained. Every one of these stages is a place where the report can stop.
When a contractor adds a report, the object appears on the coordinator’s map immediately. There is no need to refresh the page or transfer the information manually. If a crew finds illegally dumped waste, damaged infrastructure or additional work that needs attention, the coordinator can see the new point on the plan as soon as it is reported.
What changes most is the quality of the information. The GPS-derived location, object name, description and, if added by the contractor, photos from the site are kept together. There is no need to match a photograph from a messenger with a point manually added to the map later.
Photos from field reports count towards the organisation’s shared photo pool. A single shared access link can upload no more than sixty photos per hour, which is also worth considering when planning how larger crews will use the feature.
The map keeps a record of where an object came from
If a plan is developed over a longer period, after several weeks it may contain both elements entered earlier by the team and objects discovered by contractors during field work. Without distinguishing between these two sources, it would quickly become unclear which points belong to the earlier inventory and which were reported later from the field.
Objects added by contractors therefore receive a separate hard-hat symbol. The marker remains with the object permanently, so while viewing the map it is possible to distinguish items prepared by the team from those that arrived through field work. When the object is opened, the coordinator can also see the name of the contractor who reported it.
This is a small detail, but an important one for the reliability of the plan. Months later, there is no need to reconstruct from correspondence where a particular point came from. The plan retains the information that the object was added from the field and identifies the contractor who reported it.
At the same time, these reports do not appear on the ordinary public plan shared with a wider audience. They remain within the client–contractor relationship. Working information from the field therefore does not automatically become part of a view intended for people who only need to see the publicly shared plan.
Each contractor works with their own reports
When several companies service the same area, another problem would arise if all crews could see and modify one another’s reports. A company responsible for green spaces does not need a full view of objects added by a contractor working on a different scope. Nor should it be able to accidentally edit or delete that contractor’s information.
A contractor using the shared plan therefore sees only the objects they have reported themselves. They do not see reports added by other contractors. The coordinator, meanwhile, retains the view needed to manage information coming from different crews.
The contractor can return to their own object, correct its name or note, or delete the report if it was added by mistake. This makes it possible to correct an error without involving the coordinator in every small change, while the contractor’s responsibility remains limited to information they entered themselves.
This separation is particularly important when the same plan is a reference point for several external organisations. From the contractor’s perspective, the scope of their own reports remains clear, while from the coordinator’s perspective, information from the various crews still reaches the shared map.
A contractor can correct their report, but cannot remove it from scheduled work
Information found in the field can quickly become more than an observation. If a contractor reports a damaged bench, the coordinator may decide that it requires repair and connect that object to work in the schedule. From that point onward, another part of the organisation starts to rely on the report.
In this situation, the contractor can no longer delete the object on their own. An attempt to remove it displays a message explaining that the object has been used in the schedule and that the contractor should contact the client. This prevents a point with assigned work from disappearing from the plan simply because the person who originally reported it decides to delete their entry.
This separates two responsibilities. The contractor remains responsible for their report and can correct it while it is field information. Once the coordinator uses it as the basis for planning further work, the object becomes part of a process on which other arrangements depend.
In practice, this protects the schedule from losing its source object without the knowledge of the person managing the work. A change is still possible, but it requires contact between the parties rather than unilateral deletion of the information.
Inventory can develop as part of ordinary work
Traditional field inventory is often a separate task. People have to be sent out, information collected, photos taken, locations described and the results later transferred to the correct map or register. Yet much of this information is already noticed by people who work in the field every day.
A mowing crew passes benches, bins and trees. Waste teams regularly visit the same points around the city. Infrastructure contractors see the condition of assets while carrying out their own assignments. If they can leave information about what they find directly on the plan, part of the inventory begins to develop as a result of everyday work rather than as a separate exercise organised from time to time.
This does not mean that every field observation automatically becomes a task to be carried out. The coordinator still decides which contractors are allowed to add objects and what to do with the information received. In this case, PlanPlace provides a shared place where a field observation can be recorded together with its location, description, photo and information about its author.
Until now, a plan most often answered the question of what a crew should expect and do at a particular place. It can now also record what the coordinator could not have predicted before the work began. Information no longer has to return from the field as a contextless photo and a location reconstructed from memory. It remains on the same map used to organise the work and, over time, creates an increasingly complete picture of what is actually present in the field.
